![](https://infosec.pub/pictrs/image/6974f67d-0f4b-4d85-8561-66763db949cf.jpeg)
![](https://infosec.pub/pictrs/image/ffa014c8-749c-4482-8599-b4be5064f8b1.png)
The SEO-angle is interesting, thank you for the insight!
The SEO-angle is interesting, thank you for the insight!
Trying to catch up on documentation, I’ve been implementing a couple of services during the past few weeks and need to write it all down before I forget.
I do this for every service I implement as part of my backup strategy, it tends to be easier to recover from a disaster when you have reproducible steps to follow.
See edit :)
I respect and understand your decision, I’ve personally had to block a few communities from that instance due to their problematic content.
For the sake of transparency (which I feel have been the spirit of this instance so far), could you give us some examples that led up to this decision?
It might be a question of moderation.
What do you do as an instance owner if you get notified that one of your communities are acting abusive to other instances/communities? You could take a look at the activity yourself and take action accordingly, this process becomes harder if the community is in a language you do not speak.
Or perhaps this is a non-issue and it’s sufficient with a dutch-speaking community moderator.
Perhaps one of our community moderators (or our instance owner) here at infosec.pub could share their thoughts on language and moderation?
I think everyone that selfhost their RSS-feeds have at one point or another thought “now what?”.
I have 3 recommendations that might help get you started:
feedspot is a great place to start to just discover what’s out there.
GitHub releases can be followed as RSS (atom) feeds. This is a great way to keep up with changelogs for services that you selfhost. For example, here is the RSS/Atom feed for Jellyfin: link
Do you listen to podcasts? These can usually be found as RSS-feeds and is a great way to get your daily dose of news on your morning commute.
I read your response, thank you for taking the time to clear it up!
I’m assuming this means death for image-based communities here on infosec (the hardware community comes to mind).
Will this impact images originating from (served by) other instances?