Privacy

31876 readers

484 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

Chat rooms

[Matrix/Element]Dead
Discord

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

240

Problem with Mull and Duolingo (slrpnk.net)

submitted 9 months ago by franzpow@slrpnk.net to c/privacy@lemmy.ml

77 comments fedilink hide all child comments

Hello, I started to experience a problem with Mull and Duolingo (and also bromite) that started about 1 month ago.

Basically Duolingo tells me that my browser is not supported but it worked perfectly fine before. Anyone experienced this issue? I can't find an issue on mull repo apparently about this specific issue. Dunno if it is something about resisting fingerprint but I wonder why that happens..

you are viewing a single comment's thread
view the rest of the comments

[–] ErwinLottemann@feddit.de 27 points 9 months ago (2 children)

i guess it's not about the actual site not supporting some browser. it's usually about not wanting to deal with users that have problems with the page in some obscure browser caused by some random plugin or something but the user blaming it on the service. or because of tracking.

[–] brianary@startrek.website 23 points 9 months ago (2 children)

So do feature testing, not user-agent sniffing! For Pete's sake, it's 2024! That's been the best practice for decades!

[–] ErwinLottemann@feddit.de 6 points 9 months ago (3 children)

that's not the point. the user is going to open a ticket because something does not work because their browser does not support it. and it's way easier to tell them to install 'this browser' than to install 'a browser that supports a specific feature'. most of the users don't even know what a browser is...

[–] HumanPerson@sh.itjust.works 4 points 9 months ago (1 children)

Ok, but why not do both? If the browser supports all needed features, then let the user continue. If not, recommend list of supported browsers with small text at the bottom describing what feature is needed for technical users.

[–] Outtatime@sh.itjust.works -1 points 9 months ago

Read the previous comment

[–] reddig33@lemmy.world 2 points 9 months ago* (last edited 9 months ago)

Updating to the browsers listed isn’t going to solve a problem like the one you describe. Extensions and plug ins are still a thing in modern browsers.

[–] brianary@startrek.website 1 points 9 months ago

I guess you're completely right if you just assume your own conclusion.

[–] toastal@lemmy.ml 4 points 9 months ago

I like that Google is always the one recommending this while also being the one that does some of the most obvious user agent sniffing

[–] stoly@lemmy.world 5 points 9 months ago* (last edited 9 months ago)

I used to work for a web hosting company and have seen so many horror cases that I agree with you that this is what is happening. I also think it's kinda lazy to just say that they won't support what people are using because it's hard. Even 5 - 7 years ago, this was much harder than it is now.