Hello there!

I’m also @savvywolf@furry.engineer , and I have a website at https://www.savagewolf.org/ .

He/They

  • 2 Posts
  • 224 Comments
Joined 3 years ago
cake
Cake day: June 27th, 2023

help-circle
  • A self-hosted app has a different threat model.

    I can think of other cases where even if it’s self hosted, you still want this sort of encryption. What about the use case of a mother setting it up for a group of other mums in a group chat. The other mums would still want their data to be private. The hosting provider thing is valid, and I think actually extends further than you think. I may trust my own server, but I don’t know if I trust Linode or Hetzner or whoever I buy my server from to not snoop in my files. There’s also the fact that if I fuck up the configuration on my server, at least they aren’t going to get that data in the breach. (“I” in this case being an abstract person wanting to use the server. I don’t have any use for a tool like this).

    The vote counter: you’re right, it can be spammed.

    That’s fair, just be aware of it. The amount of people that make decisions based on flawed customer data is a big problem for software development.

    What I can offer is that all of it is public, with tests, fuzzing and static analysis in CI

    The recent SSH bug had all of this and let a security exploit slip through. The reason was that people made a sensible sounding but ultimately flawed design decision. Those are the types of errors that AIs love to make and that inexperienced users can let slip through.


  • Whoever administers [hosting provider’s servers] can read your records.

    Why not encrypt things locally before they get sent to the server? This is standard practice for most “privacy-first” applications nowadays.

    Counts one anonymous click. No email, no cookie, nothing about you is stored.

    For the “what to work on next”. How do you prevent bots spam clicking buttons multiple times?

    These are just two things that jumped out to me upon browsing your web site. But honestly, using AI to write code that handles such intimate data is a huge red flag to me - you have no guarantees that it is secure.














  • Going forward, I’d suggest reading the room better.

    All of your marketing documents hype up the AI features to the exclusion of all else. If I were such a “puritan” and turned off all AI features what does dragons roost offer that DndBeyond, roll20 and Foundry do not?

    The only thing I can see is that it’s “free”, but that’s freeness that is built on the backs of the lives and livlihoods of thousands of people.






  • People exfiltrating movies from your Jellyfin account sounds harmless until you get a knock on the door from the police asking why you’re running a piracy sharing site. Depending on the attacker’s level of access, they may also wonder why your server is now serving kiddie fiddling videos. Or maybe the attacker just replaces all your movie metadata images with ones from the Bee Movie.

    To me at least, DOS and region locking should come after properly locking down public facing services. They aren’t 100% reliable at preventing intrusions.

    I’d be surprised if there wasn’t a large difference between the power usage of a cpu at rest (like most servers will be) and one at full power. Especially if it had a gpu in it. They certainly sound a lot louder in my experience.

    You can never be truly sure how bad a compromised system has been compromised, or even easily detect when it has happened. It could be running as part of a botnet, stealing your credentials or probing your local/mesh network.

    In my eyes, competent cybersecurity abilities are an important part of selhosting which seems to fall by the wayside. It’s important to know exactly what your server is doing, what is running and who has access. If your system is on the public internet, you have a moral obligation to behave and not have it turn into a botnet or spam machine.