I’m the administrator of kbin.life, a general purpose/tech orientated kbin instance.

  • 0 Posts
  • 327 Comments
Joined 1 year ago
cake
Cake day: June 29th, 2023

help-circle


  • There’s a certbot addon which uses nginx directly to renew the certificate (so you don’t need to stop the web server to renew). If you install the addon you just use the same certbot commands but with --nginx instead and it will perform the actions without interfering with web server operation.

    You just then make sure the cron job to renew also includes --nginx and you’re done.






  • When you post in a thread you get an ID for that thread. When you post in a different thread you get a different id.

    That’s what I said. You don’t need any ID to federate the messages. If you reply to a comment the nesting is based on the comment/post ID and not the usernames.

    You couldn’t track a users posts after the fact, and I think that’s kinda the point.


  • Not so sure that’s true though. If you look at a 4chan threads in some boards, you can recognize the individual anonymous’ from the ID next to them.

    I suspect it’s using either a cookie, or the IP address to track a user and while not storing that info, generating an ID hash from perhaps a unique ID for the thread + their details.

    No reason you couldn’t federate using the same. But, even without that, each post and comment has a post ID and replies would be tracked that way. Just, you’d need to remember which replies were your own.

    The home instance could store for a thread some info about posts/comments from an IP or cookie too and highlight them. But that info wouldn’t be federated.

    I actually don’t think it’d be a problem, really. But, is this something missing from our lives? I’m not so sure.


  • I mean, while they can block most things, to give people a usable experience they’re going to allow http and https traffic through, and they can’t really proxy https because of the TLS layer.

    So for universal chance of success, running openvpn tcp over port 443 is the most likely to get past this level of bad. I guess they could block suspicious traffic in the session before TLS is established (in order to block certain domains). OpenVPN does support traversing a proxy, but it might only work if you specify it. If their network sets a proxy via DHCP, maybe you could see that and work around it.

    I did have fun working around an ex gf’s university network many years ago to get a VPN running over it. They were very, very serious about blocking non-standard services. A similar “through” the proxy method was the last resort they didn’t seem to bother trying to stop.