“Merge pull request #8 from [branch name]”

Not the most exciting but hey, someone has to do it.

You didn’t read the post. The suggestion is to make the platform more decentralized not centralized. I’m not even going to reply to most comments in this thread that also, clearly, did not read the post and is making stuff up.

Right? Who gives a shit about user experience anyways? When someone has an issue, you just tell them to man up and figure it out.

No, it’s not always obvious which is the “main” community and there are many communities that died due to lack of traction, often because there are duplicate communities that also lacked traction. Community following would not only help unify communities and unify comments in crossposts, it also encourages decentralization by making 5 useful communities instead of 4 dead and 1 active.

It’s not insane or narcissistic to want to reach a big audience. The same audience, across multiple instances, without effort. It’s social media 101. Saying who cares to that is a great way to see a dwindling userbase. Maybe you can’t feel it because it doesn’t directly affect your usage, but it does many others, and providing an optional solution is not a bad thing to consider.

I’d also like to take this moment to show that this is the most popular issue in Lemmy’s github, getting over twice as many likes as the 2nd most liked issue. Everyone convincing eachother in the comments that nobody cares about this is clearly wrong, and are being so in an insanely toxic and dismissive manner. Thanks.

Same solutions apply. They don’t have to be across different instances to be able to group them somehow.

I hope they can revisit the idea. There are many cases of duplicate communities splintering the community, making finding content more difficult.

Followed posts would just link to the original post and wouldn’t be a crosspost, yeah. So assuming a and b are following each other, a post from a would show up in b. If someone in b clicks on the post, they would just open the same post from a.

Ideally only one post would be made, no crossposts. One pancake post would be on your feed, and that same post would be visible from other communities

Obsessive and narcissistic because there are many duplicate communities and it’s frustrating to try and find out which ones to use? Okay…

All this work to make Lemmy “more organized” feels like it’s missing the point that communities here on Lemmy actually have the opportunity to grow organically, instead of being forced open by bots and fake engagement like on Reddit.

Does it mean the average user has to do more work for community discovery? Yes. Get used to it and stop trying to ruin a good thing by trying to make it more like the corporate shitholes we have been trying to escape.

It just sounds like you didn’t read the post and made up a narrative in your head about what it’s about.

I’m aware that people are slowly grouping up to one specific community per topic but I don’t think this means there isn’t an issue with communities being fractured. Using a third party tool to gauge which communities are popular also isn’t a great solution. Just searching Linux shows:

• !linux@lemmy.ml
• !linux@lemmy.world
• !linux@sopuli.xyz
• !linux@programming.dev

I don’t think each one of these communities has a different audience. It’s the same audience, but there isn’t an obvious answer for which one to visit or post in.

I’ve reached a point where I avoid these types of updates. An update post like that either means nothing important changed or they’re up to something.

A while ago I saw that style of patch notes, updated an app, and suddenly I can’t use it anymore because it got limited to a maximum of 2 devices. Another time I updated an app putting a harmless “we improved the user experience” message, they put dark mode behind a paywall. This isn’t counting the number of times an app got redesigned to make the user experience worse for no reason. Maybe they wanted to justify hiring 5 UI/UX interns in that quarter or something.

The patch notes look harmless, but my god, they are usually up to something.

Pretty cool. Has anyone tried this? How does it compare to https://gpt4all.io/ ?

• git pull

• git add *

• git commit -m “Some stuff”

• git push

And occasionally when you mess up

• git reflog

• git reset HEAD@{n} (where n is where you wanna roll back to)

And occasionally if you mess up so hard you give up

• git reset --hard origin/main

And there you go. You are now a master at using git. Try not to mess up.

FWIW not everyone using source control is a programmer. I’ve seen artists in game dev using GUI tools to pull new changes and push their assets.