

Irrelevant, this is not a ship.
Irrelevant, this is not a ship.
If he’s dictating that they have to stay, that’s work time.
EU laws would kill your “I’m not paying you but I’m dictating what you’re doing” part.
Is it? Or is it a question of which communities you’re looking at? Because mine isn’t.
There is no need to run Traefik if you already have a working reverse proxy. Also, unless your nginx is running on non-standard ports, the ports 80 and 443 should not be available for traefik, which will prevent it from working correctly.
unfairly treated.
Not really.
Imho I - after the remark that sparked all this - acted responsibly and sensitively and did not deserve this.
Nope. You deserved this.
Well in that case…
Most of them are simply irrelevant to me. Yes, the book might be award-worthy, but I can virtually guarantee that I have differing preferences than the committees. The more “highbrow” the further I’m usually from their rating.
You can narrow it down: attach to the container, this’ll give you a life “feed” of all messages the container produces. Then with that running, open your app and see if the container has anything to say about the sync process.
Yeah, absolutely not sketchy at all
As always: have you checked the logs?
Not for a Synology, but I doubt Hetzner cares where the data comes from. Works well, especially once you got the keys in place. Have stored and restored, it’s a simple file storage.
Do you think the fediverse has a civility problem
This has little to do with the Fediverse itself and mostly with the people involved. It would be the same on any other platform, so simply switching the software stack or whatever would do exactly zilch.
A fraction of people are going to be assholes. Sad but inevitable.
and is there anything we can do about it?
You can ban the dickheads, but that’ll only get you so far.
Last year. If you’re into nonstop action, then yes, they’re probably not for you.
Or you go all-in with a mix of Sütterlin and cursive and arrive at the only logical conclusion:
As much as I hate it, I think I’ll have to go through the logs after all.
Selfhosting without checking the logs to hunt down errors? That’s not going to be pretty.
Let’s Encrypt is fully automated and will issue certificates as long as you provide an email address AND have a proper, working config. Don’t get stuck on that email “issue”, your problems will lie somewhere else.
As always when problems arise: check the log files.
Is there any way to mitigate this while still keeping the connection active?
Paying seems to be their preferred way.
Not automatically. Check the ship contract law.