Mildly Infuriating
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/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.
-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:
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
That part is the worst. I am sick and tired of websites breaking the back button! When I click back it's because I wanted to see the thing that was there before. If I wanted it to just refresh from scratch I would reload the page instead!
It's not just YouTube, by the way. Even Lemmy does that shit too!
That's why I always middle click the links.
...and it drives me insane when it is not real links but some javascript/button/div-with-onclick/etc and middle click won't work
JavaScript frameworks give front end devs enough rope to hang themselves with
I still see websites doing that shit where you click back and end up on a page that redirects you to where you where.
YouTube had a solution not too long ago, when you hovered on a thumbnail it would show a little button that queues up the video on a temporary playlist while you keep browsing. But for whatever reason they hid that in a menu.
That's not really the issue. The issue is that it doesn't give you a proper URL with enough information to uniquely identify the set of results it loaded for you, so if you reload the page it re-runs the query and you get a new set of results instead of the same set you had before. That fundamentally breaks how the Internet is supposed to work: any particular URL should always go to the same resource.
The fact that Youtube also does lazy-loading infinite scroll bullshit makes it even harder to show examples about, so I'll switch to Lemmy now. Take this URL, for example:
(That's from navigating to page 2 of my feed, which is set to "all" and "top 6 hours".)
If I go to that URL now, and then I go to it again, say, six hours from now, it ought to still show the same list of posts. But it doesn't. Instead, it re-runs the query and shows me the new results from six hours in the future, which is an entirely different result set. That's not what I want! I want to be able to keep navigating back and forth through the old result set until I explicitly ask for a new one e.g. by clicking on the instance logo or choosing a new search from the [posts|comments], [subsribed|local|all], and [sort type list] controls.
Just generally speaking, I think of this as “concreteness”.
Software should seek to mimic real spaces, in the sense that one step back takes you to the place you were one step ago.
One pattern that breaks this in my opinion is when a menu appears as soon as you scroll up. It’s just a minor inconvenience, but 95% of the time I scroll up on an article, it’s because I want to re-read a line of text that just disappeared under the top of my screen. This menu reappear crap means I have to scroll up like three inches to get something that’s only a quarter inch under the upper edge.
I think it’s a matter of mental health to have software that faithfully mimics real world causality.
It’s all very vague in my head, but I would love to articulate this fully into a design spec.
It’s kind of like Google’s Material Design spec in its idea, but it’s about the effects of navigation rather than just how UI elements behave.
It kind of relates to the concept of a State Function in math and science.
They could cache the results you receive on your last visit of the home page which would fix this
It would not fix it. I also want to be able to do things like send the URL to someone else and have confidence that it would load the same content for them, too.
I mean of course that would be nice, but that's just not realistic. You can't store that info in a link without it being monstrous.
Why do you say they couldn't cache the results and instead of re-fetching everything just use the cache results?
Sure you can, if your backend is designed reasonably.
How? You put a timestamp (or equivalent) in the URL and filter the search to only operate on the records that existed at that time. Assuming your search algorithm is deterministic, it should find the same results.
I agree with your point, but our algorithms are not deterministic and I doubt they ever will be again. Perhaps they could use a set of tags to create a deterministic result for a certain "genre" of results.
Jerboa doesn't do that in my experience.
All the lemmy clients I’ve tried do this.
I see a thing, try to get back to it, and it just refreshes the whole thing from square one.
I’ve built react apps before, I get how that’s kind of easier because “when in doubt, goto 10” (I’ve written code from BASIC through jsx) but damn.