Jon

@autonomysolidarity@todon.eu @cavallette@mastodon.bida.im Inspired me to bring this back: https://boston.indymedia.org/archive/index.html Just a static archive for now, that's the easy part. Let's see if I can get a tech stack and some people together. #Boston #Indymedia #Media #Journalism

@anarchademic @Em0nM4stodon This is why I build https://mastodon.social It's pretty straight Mastodon but all authenticated traffic it through #Tor and no email addresses are collected. So there's nothing beyond the public posts to identify users. What you put in a public post can be much more identifying that you may think but at least with this model full control is with the user the service doesn't need to know anything extra

@wonka@chaos.social @mcfly@milliways.social yes there is that *if*! it is an ugly one and I wonder how many more similar vulnerabilities will be found. luckily for me ipsec isn't part of my world as all the VPNs I deal with use other methods. I do (did) have some systems using kafs which requires the rxrpc module...

@mcfly@milliways.social It's making for an interesting evening but there is a simple mitigation given in the github (as long as you don't actually need any of the three kernel modules it blocks from loading...) https://github.com/V4bel/dirtyfrag#mitigation

@frogglin I'm old enough to remember the "Don't be evil" days, should have known if they had to set not being evil as a *goal* there would be problems...

@gregstoll@techhub.social I've been usung a dedicated server not VPS so i'm not 100% sure if this is relevant, but over the past year GigaHost https://gigahost.no/en has treated me well. As a small provider their web based tooling hasn't always worked as i'd like (mostly around installs and custom boot media, VPS would likely not have issues there) but their support has been good and responsive wich has definately balanced it out. So over all for a 'no frills' experience i'd say they are excellent value.

@prettygood I feel personally attacked by this relatable content 😁

We use a Docker Compose based deployment generally on the lines of what's in the official Mastodon source tree. Recently I configured the docker containers to forward their logs to a remote server so if there was an issue that rendered the production server unreachable the logs would still be available for debugging.

#DomumSocial connectivity will be unstable over the next few hours for switch replacement. Hopefully actual downtime will be minimal. As always updates will be posted to https://status.domum.social

This log-server rebooted yesterday but was awaiting for me to type in an encryption key to unlock it's disks. Turns out when the production docker containers can send their logs they hang! They can be set to non-blocking, which I'll do shortly. Clearly a larger re-architecture of the log system with a more critical eye on failure cases needs to be done.

you can bet I checked lots of things before I checked that...

The work is completed successfully. We're back on a proper wired connection 😁

@autonomysolidarity@todon.eu @cavallette@mastodon.bida.im Indymedia.org ? Now that's a name I've not heard in a long time... A long time