I blow hot air.

  • 1 Post
  • 28 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle









  • If you’re worried about unauthorized access to the physical machine, you could always just do disk-level encryption instead or store the app’s data in something like a Veracrypt virtual disk. They’d still be able to access the data if they go through your OS/user, but wouldn’t pick anything up by accessing the drive directly.

    Nothing short of E2EE can truly stop someone from accessing your data if they have physical access to the server, but disk encryption would require a targeted attack to break, and no host is wasting their time targeting your meme server. I seriously doubt they’d access it even if you had no encryption at all, since if they get caught doing that they’d get in a heap of legal trouble and lose a ton of business.


  • Vent@lemm.eetoProgramming@programming.devProgramming Sucks
    link
    fedilink
    arrow-up
    15
    ·
    edit-2
    7 months ago

    Oh, it’s drag-and-drop only with no keyboard support whatsoever. Changing a variable is hidden beneath 12 menus, and it uses a proprietary IDE that locks up after every click. Looks great in screenshots though!

    You can 100% fire all your developers!*

    *As long as your business users have loads of free time and the skillset of developers.






  • Is each instance like another person with a server?

    Yes.

    Could that person just shut it down whenever they wanted to?

    Yes.

    Are there any companies that have invested in hosting Lemmy/ other fediverse servers?

    Idk, they’d be very niche.

    Sorry I’m sure I messed up some of the terminology, I hope my questions make sense!

    Nah, you pretty much nailed it.

    Lemmy, and a lot of the fediverse, functions very similarly to email. Gmail can send emails to Proton even though they’re hosted by two completely separate companies. A post/comment/vote/interaction is like an email in that a copy of every interaction is sent to every federated instance, like emails sent to recipients. This creates a lot of redundancy and traffic between instances, which has its pros and cons.






  • The article is not talking about async processing. It’s talking about the process scheduler and thread blocking. It even has a section titled “Real-time Scheduling” that talks specifically about the process scheduler.

    It’s simply not possible to fit the author’s definition of real-time without using something like an RTOS, and the author seems to understand that. The main feature of an RTOS is a different scheduler implementation that can guarantee cpu time to events. The catch is that an RTOS isn’t going to handle general purpose usecases like a personal computer very well since it requires purpose-built programs and won’t be great at juggling a lot of different processes at the same time.