Mildly Infuriating
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that. Please post actually infuriating posts to !actually_infuriating@lemmy.world
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/Explicit
Content
-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. If your post better fits !Actually_Infuriating put it there.
-The Community !actuallyinfuriating has been born so that's where you should post the big stuff.
...
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:
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.
view the rest of the comments
I hate the websites that have "Accept all" or "Accept necessary only", but if you use a privacy browser that refuses all cookies the site works anyway.
Their "necessary" cookies aren't actually necessary, you just can't reject them.
I wonder if there's even a difference between "all" and "necessary".
As a web developer, I can confirm that there are sometimes necessary cookies that aren't just for the wankstains in marketing!
What would happen if a browser never saved those cookies? Would the website fail to load, some elements not run, or something else?
I'm always curious about edge cases and failure modes.
Yes, you're spot on; it's mostly about elements and functionality not working. Just as a heads up, I work in the WordPress ecosystem so the following brief descriptions will be focused on PHP based sites. I'm sure there are ways round using cookies, such as using
localStoragein JavaScript etc. Anyway!The biggest thing you'll run into is anything to do with login systems. Any website that offers a login/account typically makes use of cookies, in order to let the website "remember" that you're logged in, between page navigation.
One of our clients offers a comparison calculator for investments. This calculator relies on cookies when you want to "save" your results, and also makes use of them when you're not logged in, in order to allow you to access your previous runs of the calculator without having to create an account.
Another of our clients, also in the financial space, produces documents containing financial info about funds, and marketing materials. These docs are subject to strict compliance rules determining what can be shown to users based on what "type" of investor is viewing the site, and where in the world they're viewing from.
Anybody visiting the site self-identifies by manually selecting an investor "type" and a location. This info gets set into a cookie, and the site serves content based on the values in that cookie. If the site can't identify the cookie or it has an invalid value, it'll basically be unusable, in order to protect the company themselves.
Another example might be shopping carts or session storage. Anything that persists from page to page. Does the site have an option for dark mode display? Probably stored in a cookie. Option to change the display language? Yeah, also likely a cookie.
Yeah, 100%! And the languages point generally opens up to a third-party system like WeGlot, whether the cookie is first-party or not. It's sort of amazing to me how collaborative the modern web is, but also just how insecure it can be.
It can be really locked down but I would say at least half of the wordpress sites online (and wordpress powers something like 20%+ of the whole open internet, iirc) pull in all sorts of third-party scripts and code that isn't vetted by the people including them (including me! Only so many hours in a workday, after all).
FWIW you could do this with the localStorage API.
Funny enough, I mentioned that in my first paragraph as I've had to do that for a client recently who had some specific niche use case for something that wouldn't allow cookies to be used.
I can't read.