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

help-circle



  • It could be a good idea to move more critical things to a different machine. It’s often said that you shouldn’t run your router and/or firewall on your main server, but I think there are also security reasons for that.

    Or to move those to a low power consumption machine with cheaper hardwRe that are either more resource friendly, or very heavy but it’s fine if they can only finish their task over a longer time.

    Also, think about how could things go wrong. Have a second DNS and DHCP server (it’s difficult to run a secondary DHCP besides the primary, maybe you don’t need that), and some way you can reach the internet if the router or the firewall gets borked. That “way” does not need to be accessible at all times, but you should be able to switch it on when needed.
    Don’t forget to test that these are actually working after you have sweet them up.

    Whatever you decide on, don’t forget that you don’t have to do everything at once. Don’t let it overload you. Learning new tech takes time.








  • but who would have thought something that sounds as simple as wanting to RDP across 4 monitors would be so damn difficult.

    The ubuntu unstability surprised me (not that I would recommend it anyways), but this didn’t. Isn’t RDP a proprietary protocol of Microsoft? Probably not too many use it in the Linux world





  • 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.






  • 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.