More Privacy Frontends

[redoomed1]

@cmc

I can at least go through the ones I use personally

I prefer this as opposed to presenting a laundry list of tool suggestions in one thread. This is particularly relevant for frontends, as they are the tools that may be most subject to major changes that impact their usability and reliability.

@cmc

my aim was more to see if the community values anything highly enough to add to the recommendation[s]

To add to my previous point, you are a part of the community, so if you value any frontend highly enough from the list you presented, you are welcome to open a Site Development > Tool Suggestions thread for each of them.

---

@cmc

my suggestions alone would be close to 10 and would feel like spam to me

It would not feel like spam if the thread for each tool suggestion is distinct enough to highlight why you think it should be added to the website, how it conforms with the current criteria for frontends, your personal experiences with the frontend as an end user, etc.

As a quite recent example, there are 5 different threads which suggest tools for private media consumption, as well as one Site Development > Guide Suggestions thread proposing a knowledge base article for it.

1. VLC (Media Player Software)
2. Jellyfin (Media Management)
3. Kodi (Home Theater Software)
4. IINA (macOS Media Player)
5. Raspberry Pi TV HAT (Hardware Device)
6. Private Media Streaming/Consumption

Yet these suggestions do not feel like spam to me because the original posts for each thread are detailed and distinct enough to invite discussion and input from community members.

@cmc

Makes more sense to bring them all together in a single thread, like this one in 2022 where they discussed numerous frontends simultaneously

I disagree that one thread housing multiple suggestions makes sense because if a new or returning community member wants to look for community opinions on a specific frontend, then they would have to scroll through comments about other frontends to find what they’re looking for.

This is the reason for this reminder post about keeping threads on-topic:

A reminder on keeping threads on-topic

I want to give a gentle reminder to keep threads on-topic. If you want to start a side discussion that is is prompted by an existing post, but does not serve the original conversation/topic, please use Discourse’s reply as linked topic feature. This is a great way to politely split off the conversation in the original thread, keeping that thread on-topic, while giving you the freedom to have a conversation about a new idea. This will create a link between the two topics that people who are in…

And this post:

Secureblue - Atomic Fedora Hardening

Thanks. You’re certainly welcome to answer questions in other topics if you’d like (obviously general support from developers is not an expectation for this forum), I just need to keep the Site Development category specifically clean.

Opening a separate thread for a tool not mentioned in the thread’s original post not only makes forum administration and moderation easier, but also makes the forum experience for community members more streamlined.

@GorujoCY

I/anyone else can make a separate thread [about Libredirect]

Please do if you or anyone else reading your comment feel so inclined.