This is loosely related to “online experience” (as you’ve covered most of the “tech tips”) :

When choosing a movie don’t watch the trailers, instead (blindly) watch what’s popular. (obviously, if you’re into niche genres - this won’t work.)

I’ve found Trackt is a good place to understand recent trends (and it just shows film posters). Then I’ll go to IMDB, maybe read the summary, but I always read the first/popular user review and decide if it’s worth my time and money.

The first/popular user review usually doesn’t contain spoilers.

Since I’ve actively avoided trailers and spoilers, my enjoyment for films has nearly doubled - even for “bad movies” (I probably wouldn’t have watched otherwise). It’s such a shame that a 2 minute trailer often shows many/most of the highlights of the film.

Welp, I guess this means something bad is gonna happen and Spez is trying to get in front of the inevitable protests.

I wonder what it could be…

There has to be a better way to keep the strengths of federating without partitioning the community smaller and smaller until there is no community left.

Can you imagine Lemmy with a similar amount of Reddit users? Anytime you’d post, you’d have to replicate it between X number of instances (for visibility). Conversations would be fragemented and duplicated, votes would be duplicated. To me this almost sounds like “work”…

There has to be something better.

For example, instead of “every instance is an island”. Meaning the current hierarchy is “instance” - > “community” - > “post” - > “threads”. We could instead have “community (ie: asklemmy)” - > “post (ie: this post)” - > “instance (Lemmy.ml, Lemmy.world, etc)” - > “threads (this comment)”.

From a technical perspective, it would mean that each instance would replicate the community names and posts. Which is already beginning done (this post is a perfect example), but as long as each instance would share a unique identifier to associate the two communities/posts as “the same thing” (and this could simply be the hash of the community /post name). Everything else would be UX. Each instance would take ownership of the copy of the community and post, which means they could moderate it according to their standards.

I fixed the link. For some reason the Lemmy Client (Voyager) keeps generating ‘.ml’ links (even though I’m on Lemm.ee)

This whole identical thread really confused Voyager, I thought I was seeing double.

Off-topic: Lemmy really needs better crosspost functionality.

Lemmy is a small group of people, let’s not divide it further by having the exact same conversation in two (or more) places.

edit: Fixed the link.

The “downvote to disagree” thing isn’t just an attitude problem, it’s a structural issue. No amount of asking people nicely to obey site etiquette will change the fact that the downvote button is a disagree button. If you don’t want a hive mind, you necessarily need to be able to allow for things you don’t like to be amplified.

Actually, with enough interactions from different people (ie: enough data points) Lemmy should be able to determine if a comment brings value to the conversation (either positive or negative) or if it’s noise that should be ignored (and prioritized lower).

If you have 4 comments:

1. Has 100 upvotes (in total)
2. Another has 100 downvote (in total)
3. Another has 50 upvotes and 50 downvote (100 in total with a 0 sum)
4. The last was a new comment with 0 votes.

It’s obvious that 1 and 3 are providing more to the conversation than 2. 4 is a bit of an outlier, but probably provides more value than 2.

Regarding 3: The challenge would be that there’s a low chance that there will be such a wide margin of upvotes/downvotes. Due to the hive mind, the voting will probably look like 30 upvotes and 130 downvotes. So, there would need to be a weight accordingly, so those fewer upvotes had a greater impact (in terms of sorting and scoring comments)

Reddit has a “sort by controversial” algorithm that seems to be missing from Lemmy (or maybe it’s hidden in the “what’s hot" - I haven’t looked at the code).

It would be awesome (and resource intensive) if Lemmy could provide the federated instances with custom sorting algorithms. It would allow federated instances to be unique, provide some playful competition, and given the open source nature of Lemmy - I’m sure these algorithms would be open sourced, which would improve the entire Lemmy ecosystem as a whole.

Herbie?