this post was submitted on 21 Jul 2023
175 points (95.8% liked)

Mildly Infuriating

35744 readers
283 users here now

Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.

I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!

It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.


Rules:

1. Be Respectful


Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...


2. No Illegal Content


Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means: -No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...


3. No Spam


Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...


4. No Porn/ExplicitContent


-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...


5. No Enciting Harassment,Brigading, Doxxing or Witch Hunts


-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...


6. NSFW should be behind NSFW tags.


-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...


7. Content should match the theme of this community.


-Content should be Mildly infuriating.

-At this time we permit content that is infuriating until an infuriating community is made available.

...


8. Reposting of Reddit content is permitted, try to credit the OC.


-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.

...

...


Also check out:

Partnered Communities:

1.Lemmy Review

2.Lemmy Be Wholesome

3.Lemmy Shitpost

4.No Stupid Questions

5.You Should Know

6.Credible Defense


Reach out to LillianVS for inclusion on the sidebar.

All communities included on the sidebar are to be made in compliance with the instance rules.

founded 2 years ago
MODERATORS
 
top 17 comments
sorted by: hot top controversial new old
[–] PeachyMcPeachface 16 points 1 year ago

Naw, these are extremely frustrating. They make navigating websites super difficult for anyone using a screen reader. Websites are supposed to have a certain level of accessibility by law that 97% of them don't follow.

[–] [email protected] 15 points 1 year ago (4 children)

I wish I could toggle a switch natively in firefox (without a fishy extension) to set a flag, that sites have to respect/follow. Cookie banner are only the frontend result of something that could be implemented in software. In the same way as the EU can make everyone follow these rules or get fined, they could extend the rules to acknowledge my set flag automatically in the browser or get fined. Maybe in the future… I can’t believe my children will still have to click deny on every website in the year 2030.

[–] [email protected] 12 points 1 year ago (1 children)

There is consent-o-matic for Firefox which will answer these for you to say reject everything. It is run by a team in a Danish University.

[–] [email protected] 10 points 1 year ago* (last edited 1 year ago) (1 children)

Do you know why it is so badly reviewed? 4.3 is not that high. I skimmed the reviews and saw some people say it only works 30% of the time and another said it "does not work in FF but in Brave" (so relatively sure its just a astroturfing comment). I see they have a github, so I could go the way of reading the JS code and package it myself into a extension somehow that never updates, but that is easier said than done.

I really wish there were more ways to trust extensions. There are so many shady extensions who update in the background and insert malicious code on a later state when they gained track, that it is really hard for me to trust any of them. Eespecially when those Extension ask for nothing less than all my data on all my visited websites. For this reason I really would like to see this implemented natively in FF and not via an extension. Extensions are good for edge cases. The GDPR consent request is not an edge case. It is something everyone has to click several times a day. This is screaming for a permanent solution.

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

I think I just saw a post earlier where someone noticed in the latest Android FF nightly there was an option for this built in. Maybe it will be available for desktop soon (or maybe it already is?)

Edit: oh look the guy below talked about it and you replied 🫣

[–] [email protected] 7 points 1 year ago (1 children)

Firefox nightly (the beta version of firefox) has been testing a native cookie denier. So we will probably get it soon.

[–] [email protected] 4 points 1 year ago

This is the best thing I heard all day. Thank you!

[–] [email protected] 3 points 1 year ago (1 children)

This was a thing already, it was called Do-Not-Track

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/DNT

Firefox tied it in to their existing Tracking Protection. Not sure how or if Chrome implemented it. Websites ignored the flag as you'd sadly expect, so it's been deprecated

[–] [email protected] 1 points 1 year ago

That’s slightly different and more often than not completely ignored. This is a better alternative: https://feddit.nl/comment/1153941.

[–] [email protected] 2 points 1 year ago

That already exist: https://community.mozilla.org/en/campaigns/firefox-cookie-banner-handling/. There is also a flag to enable it in the GUI (to let it appear in the settings).

[–] [email protected] 8 points 1 year ago (1 children)

That's not a annoying one. One click to disagree.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Yes, those banners were hard-won and are great.

I wonder if anyone's made a plugin that autofills them.

Edit: Yep, looks like beta Firefox has it natively.

[–] [email protected] 5 points 1 year ago

But that one isn't that annoying, it's a simple one click agree/disagree by the look of it

[–] [email protected] 4 points 1 year ago (1 children)

They are legally required to have that banner. Sorry.

[–] [email protected] 2 points 1 year ago

What if the website doesn't use cookies?

[–] [email protected] 2 points 1 year ago

I’ve installed the extension they said, now I can’t access their website 🙂

[–] [email protected] 1 points 1 year ago

OK, replying to myself here rather than individually, as it seemed easier... Maybe I should have posted this to c/mildlyironic, but that's what caught my attention. There's no easy way to specify what I consent too here—their ToS, tracking cookies, it's all or nothing†. And this is a legal requirement only if you're storing cookies. If your website will work without cookies, just get rid of them instead of asking. If it won't, make this the landing page and see how much traffic you get (note this would also help with accessibility).

I do use consent-o-matic, but it didn't help with this one. Never mind, I'm no stranger to devtools, and see this eventually as just a challenge. This site though was pretty tricky. First usual trick is to right click and 'Inspect' the overlay, with a view to, ahem, closing it. But this isn't gadgethacks first rodeo—no, they have a page level click handler installed which repeats the small print, and ends with a double negative "If you do not agree, click Cancel". There's no way back to read the ToS or privacy policy without reloading the page.

Oh well, lets start again and open devtools. The content is structured in 3 main bits: a <header>, a <section class="page-wrapper"> and a <footer>. Well, that's not too bad, so we can safely delete the header & footer, and that also gets rid of the click handler. Now just a simple matter or finding where overflow: hidden is buried (only 1 div down), and a pesky position: fixed alongside it, and voila we have scroll bars.

I could read all the way to the end of the article, and guess what? It didn't need cookies after all.

† Perhaps their ToS requires the use of cookies, but, TL;DR;, it doesn't.

load more comments
view more: next ›