Some dingbat that occasionally builds neat stuff without breaking others. The person running this public-but-not-promoted instance because reasons.

  • 1 Post
  • 701 Comments
Joined 1 month ago
cake
Cake day: May 24th, 2024

help-circle











  • They’re a part of the mix. Firewalls, Proxies, WAF (often built into a proxy), IPS, AV, and whatever intelligence systems one may like work together to do their tasks. Visibility of traffic is important as well as the management burden being low enough. I used to have to manually log into several boxes on a regular basis to update software, certs, and configs, now a majority of that is automated and I just get an email to schedule a restart if needed.

    A reverse proxy can be a lot more than just host based routing though. Take something like a Bluecoat or F5 and look at the options on it. Now you might say it’s not a proxy then because it does X/Y/Z but at the heart of things creating that bridged intercept for the traffic is still the core functionality.





  • Fedi platforms have a key distinction putting them separate from most other online platforms in that you can literally create your own and have all the rights of a platform admin today, and have access to the very same content as you would having an account on another’s node. In that regard there’s much less room to complain about unilateral actions by the instance owner than there would be for other systems. As the size of an instance grows you run a greater risk any time you take such an action, but so long as it’s consistent with past behavior it shouldn’t be a major problem. Large instances like .world have made some cuts that ruffled a few feathers and then backed them off if people objected, but sometimes direct democracy isn’t particularly viable in what might be a time sensitive situation.