this post was submitted on 01 Aug 2023

77 points (88.9% liked)

Mildly Infuriating

35403 readers

1841 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/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:

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 1 year ago

MODERATORS

LillianVS@lemmy.world

STRIKINGdebate2@lemmy.world

Tenthrow@lemmy.world

"Load more" on any microblogging app for any platform... (lemmy.world)

submitted 1 year ago by Kyyrypyy@lemmy.world to c/mildlyinfuriating@lemmy.world

13 comments fedilink hide all child comments

Yeah, I understand that everything can't be loaded at the sam time, but this is not the solution. The reason to browse by chronological order, from oldest to newest, is so that I don't miss posts. But on everey single microblogging app, decentralized or ran by a lunatic wit too much money, there is the barrier between the last few new posts, and where you last left reading.

The eorst part: this loads the newest first, and prefers to push you to the top, requiring you to search where you actually left off.

How about we just have a button to "go to the newest" that throws you to whatever has been published within the 5 minutes, and assume if you're browsing from bottom to top, you want more to be shown, but properly chronologically.

all 14 comments

sorted by: hot top controversial new old

[–] dojan@lemmy.world 9 points 1 year ago (1 children)

I’ve never been a fan of these either. They’re some sort of in between cop out between proper pagination and endless scrolling.

Like choose one and be done with it.

[–] Kyyrypyy@lemmy.world 1 points 1 year ago (1 children)

I feel these ecmxist precisely because endless scrolling doesn't. These load more, but I'm not sure the apps ever unload, so for the optiomization I understand why they have implemented this as they have BUT for me that way is just an excuse to be lazy with garbage cleaning. And these also might be one of the biggest reasons why the trending stuff doesn't stick on Mastodon; Mastodon users don't sort by popular, and while scrolling by chronological order, these things create obstacles for seeing all things posted.

[–] ericisshort@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

I don’t think it has anything to do with laziness. Endless scrolling has been around for a long time and is really easy to implement.

They do this for one reason - because on average, this method costs less in data served to the average user than something like endless scrolling. They serve up the most popular comments to you thinking that is what the majority will want. Then they put a button to load more because only a small percentage actually use it, and that saves them money.

They don’t load the comments in order because they don’t want you to click the button, so making the results of the button inconvenient will detract more people from using it. It’s all about trying to subtly convince you to trust that the comments that they served up originally are the only important ones so that you don’t even bother to click the see more link. Enshitification at its finest.

[–] AnalogyAddict@lemmy.world 4 points 1 year ago* (last edited 1 year ago)

As a UX designer, the first part is part of the reason. Companies actually "want" you to continue to scroll and to click the view more button. Every time you view more, they get more ad revenue and more data.

Endless scrolling is an accessibility and data conservation nightmare. It's also arguably grey UX, as it encourages scrolling addiction. Having the user have to make a decision to load more saves the user data, and keeps the page from shifting context without user input. Global apps should consider the needs of the bulk of the world, which is still on pay-for-data plans.

The answer tends to be to also implement server-side sort and filtering that includes "show new."

[–] Carighan@lemmy.world 4 points 1 year ago (1 children)

I'm not sure I understand.

You mean when you scrolled down, say, the newest 50 posts, then you have to click a load more button for the next 50 to load?

[–] Kyyrypyy@lemmy.world 3 points 1 year ago (1 children)

I'm scrolling UP. That's the thing, I don't scroll down, because the newest post are always on top, and I continue scrolling from where I stopped. So I scroll up, and when tou press that horrendous exuse of a button, it loads more posts, and prefers to set the scrolling position to the post above. To my knowledge there is no option to display "oldest first".

[–] Carighan@lemmy.world 5 points 1 year ago

Oooh, sorry, I completely misunderstood. Yeah I agree, that's indeed terrible UX. And sadly super common.

[–] kratoz29@lemmy.world 3 points 1 year ago

I hate this.

[–] amycatgirl@lemmy.blahaj.zone 1 points 1 year ago

This is usually the app failing to fetch remote posts in your timeline, on Fedilab you can set the app to do it for you

It's never been too much of an annoyance for me, but that's because I am already used to it. I think that the app needs to do it by itself without needing user intervention.

[–] quortez@kbin.social 1 points 1 year ago

I'm...mixed on situations like these

Like yeah, it's very annoying having to manually refresh for more content, but at the same time I do appreciate having more time to fully explore my timeline instead of coming back from a post to see they completely discarded my reading place, losing whatever is was looking at, likely forever.

Of course, for quieter networks you may run into the problem of content refreshing too little...

[–] quortez@kbin.social 1 points 1 year ago (1 children)

I'm...mixed on situations like these

Of course, for quieter networks you may run into the problem of content refreshing too little...

[–] Kyyrypyy@lemmy.world 1 points 1 year ago

To be fair, I don't mind the button itself, if it worked as I wanted it to, and could be changed to load from oldest to new, and sustain your scrolling position. But as they do now, you can sustain your position by fiddling with the loading, and you need to load everything to get back to scrolling if you want to read from oldest to newest.

This button was basically designed for people that sort only by popular, but I think I'm not the onlyone who prefers not to have their microblogs pre-curated by popularity, and I really hate it when I am forced to miss posts just because of the general design practices that are designed for commercialized services.

And as I said in another post, the "trending" -statistics of Mastodon is just a peak, and then forgotten. I have my suspicion that it's because people do not sort by popular, and by end up missing the stuff that has trended, because design choises like the funcrionality of this button. Surely, the other element is the trending algorithm, and how it is pushed, but that's a whilly different can of worms to open.