• 0 Posts
  • 42 Comments
Joined 1 year ago
cake
Cake day: July 11th, 2023

help-circle










  • That’s very weird as with docker on windows you technically run your containers in a linux vm, and besides that, in my experience windows is not nearly stable enough to be useful for running services.
    All while I have been deploying selfhosted services for myself without problems on Linux for years. My only problem has been the constantly overloaded system, but that’s no surprise when you run heavy services on the 10+ year old portable hard drive system disk. Windows would only perform worse in that environment.




  • Besides a TOR node, you can also run an I2P “router” (which is a software package).

    This is not an outproxy/exit node, so unless your country prohibits in law participating in routing network traffic (afaik not really a thing), this can’t get you into trouble.

    I2P is a hidden network like Tor, but compared to that (while it is usable for browsing websites while hiding your IP from it) it’s a better choice for in-network services. Unlike with Tor it does not dislike bittorrent and such.
    Everyone who runs a router can not only access I2P sites/services, but also participates in routing the traffic of other users, and with a stable and relatively fast internet connection you can help to improve connection speeds of the network for everyone.






  • If you can see DMs between 2 e.g. sh.itjust.works users that’s very worrying, but if you can only see messages where one participant is registered on your instance, that’s just natural.

    Other than that, I think vote information should only be visible to

    • the instance’s admins where the user is registered
    • the community’s mods (and in turn the admins of it’s instance) where the reaction has taken place,
      and not to any and all instance admin who is federating with your instance.