• 0 Posts
  • 38 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • 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.



  • I think OP is referring to the fact that bad actors, who are exploiting facets of SEO (rather then providing “meaningful” content), use to need to programically generate content (pre-AI/LLM).

    For a real reader, it was obvious (at a quick glance) this was meaningless garbage. As they would often be large walls of text that didn’t make sense, or just lists of random key words.

    With LLM/AI, they’re still walls of text and random key words, but now they grammatically/structurally correct and require no real effort to generate. Unfortunately, it means that the reader actually need to invest time in reading it. You’ll also notice a growing trend in articles (especially in “compare X vs Y” type articles), the same content is recycled and rephrased to “pad” the article and give it a higher SEO ranking.


  • 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.