For example: The blinking you're seeing is due to the replication of the BSD Cafe's media, which happens almost in real-time thanks to SeaweedFS, via VPN.
For example: The blinking you're seeing is due to the replication of the BSD Cafe's media, which happens almost in real-time thanks to SeaweedFS, via VPN.
For example: The blinking you're seeing is due to the replication of the BSD Cafe's media, which happens almost in real-time thanks to SeaweedFS, via VPN. And yes, all that excites me.
@mxjaygrant Can you share a bit more about what is making you say that? This post wasn't directed at Mastodon users, and I don't feel that way about our users at all. But if there's something I've done to make you feel that way, I'd like to work to improve.
@emaytch@mcc Pale Moon has forked a long time ago and had been maintained independently from Firefox, so for all intents and purposes it can be considered truly an independent browser now with its own engine and it will survive even without FF. For LibreWolf and WaterFox, though, their survival without Firefox behind them is a huge question mark indeed.
@maswan for me, it's the exact opposite: having all the services inside a single jail means that one dependency could break other stuff - while keeping them separate means I can upgrade, for example, valkey without having to upgrade, for example, ruby
I've fixed a problem with #brew and ipv6, when connecting via SSH. The jail was correctly listening on ipv6 but there's a catch: the brew.bsd.cafe AAAA record points to the nginx reverse proxy, which has another public ipv6 address. I've fixed it with a rdr rule, redirecting port 2222 to the correct ipv6 address. #BSDCafe #BSDCafeFixes