Your topic was merged to the authoritative All around Qubes topic because it was a duplicate topic of the latter. The reasoning behind the centralization is this reply in the topic:
You appear to fail to realise that I cannot access the category where you have moved my topic. It doesn’t matter if there are a huindred ‘similar’ topics already threaded in a hidden ‘private’ subforum, because if I can’t access that hidden private subforum, then for all it’s worth to me, they do not exist. So, you have two options, Frank.
- Put my thread back where I can get to it.
- Change my trust level so that I can access wherever you’ve put my thread.
Otherwise, what was the point of writing it?
It seems to be having a go at it now. The hidden private challenge thread is just stuck in a whirlygig but the 404 error is leaving the scene just after a reload. Is there anything you need to help speed things up there?
Nope, now it’s back to its Oops routine again. I don’t see a 404 there but maybe I imagined it when the Page Not Found message appeared.
What are you doing about it, Frank? Are you admitting me to the subforum or moving my thread back to where I can see it? Or will I need to write another one with different wording to get this mess you’ve made sorted out?
inappropriate message
Can someone please explain how I am supposed to read replies and write on a thread which I have opened in good faith for a perfectly legitimate and highly important subject when some twit has moved my thread to a hidden private subforum which I am unable to access to even read, let alone write?
It is really quite baffling. I get the feeling that there are people around here who use Qubes and realise that akamai and cloudflare et al. are not really in the business of fighting ‘malicious’ 'bots, but fighting Qubes. and then they will go after Linux, and then anything that Google don’t own. I think that might be what it’s all about, because it’s the deafening silence about it all which indicates that there’s something really bad going on and no one who knows what it is has the guts to talk about it.
Your original post (ACCESS DENIED For Qubes By Akamai Edgesuite and Cloudfare) was off-topic. This forum is about things specific to Qubes OS (fingerprinting from third parties is out of scope), so we had two options:
- to close your topic as being off-topic for the forum;
- or move it to a category limited to members who made a significant contribution to the forum and where topic related but not specific to Qubes OS are allowed.
@FranklyFlawless choose the second option and it is perfectly fine. Discourse works with a “trust level” system where users gain access to more things based on their contributions. We won’t allow you to a higher trust level just because you asked for it (and @FranklyFlawless does not have that capacity).
Note that rewording your original post won’t change anything. A better option would be to post in a forum where fingerprinting might be something of interest for their members (like https://discuss.privacyguides.net ?).
There is no need to push a TL4 member to do something. They have the possibility to move post to help with organizing this forum. If you don’t understand some decision, you can ask the reason but don’t try to force someone to act as you would like. If you strongly disagree, flag the post and leave it to the mods.
Discourse doesn’t allow more than three consecutive answers for good reasons. Next time, edit your previous posts or wait for an answer. Opening a duplicate topic is not the solution.
Another thing: we are a small community with a specific focus. Just because your personal interest doesn’t meet others’ interest doesn’t mean anything special.
There are three conditions for the topic to move out of the All around Qubes category:
- Exclusivity
- Persistence
- Reproducibility
As of this post, the issue is not specific to Qubes OS, and furthermore, ephemeral across time and not reproducible across various TemplateVMs and web browsers. CDN networks are not targeting and quarantining Qubes OS users at the edge using challenge-response mechanisms while other non-Qubes OS users pass through. The rejection heuristic is overbroad and encapsulates a wider swathe of agents and clients regardless of origin, so the topic remains unspecific to Qubes OS at this time.