eternaldeiwos

Microsoft aren’t exactly big on implementing “the latest” stuff. Not at a keyboard currently but I’d be willing to bet GH doesn’t support TLS1.3 either.

Lemmy is compatible with bots which can cause some serious headaches, however there are tools that can combat these.

Every instance of Lemmy has a reputation that is associated with it. If it becomes clear that a particular instance is being used as a bot hub and the moderators are unresponsive then other instances will quickly start to black list it for being too spammy. More so if word starts to get out about it. Point is that the admins of an instance will make a good job of ensuring their users aren’t bots (or at least being misused as a bot) or face their whole instance being blocked across the board.

Even if the bots have their own instance then other instances will resort to enforcing whitelists for connections. Over time we may also see the development of additional mod tools too.

Considering I am looking at this – while having disabled NSFW for myself and my instance – this is a problem?

This sounds oddly familiar 🤔

This should be filed as a feature suggestion on the GIthub repo. That way it will actually be tracked.

And I thought FF containers were great! FF have their problems but always good to see where priorities are.

Depends on how you're currently set up. My intention was to use something like k3s + https://cloudnative-pg.io to handle most of the details for me.

I prefer to version my configs so this approach serves my MO better, even if it is a little more work initially.

Personally I would go with /c/csharp to keep the community on-topic. Could also easily have /c/fsharp et al. That said I probably won't subscribe to those.

/c/loud on the other hand I would definitely prefer to be /c/cloud to prevent the inevitable 🤨 when mentioning inline.

This is not a bad idea. This is how the Fediverse is supposed to work.

I responded in your DB optimization thread as well but can you share the improvements you made?

As with /c/sharp making a cool URL is one thing but this would be referred to inline as !loud

The URL might be /c/sharp but it would be referred to inline as !sharp.