It's an instance that crossposts posts from Reddit, except it also makes a new user for each Reddit account it came from. So if /u/hello123 made a post, it makes that post under a new account called hello123. That makes it impossible to block posting bots.

Not only that, it makes posts look like they're posted by real people, with many question and text posts being copied as well. I was very confused as to what these posts were until I realized they're crossposts.

Examples:

https://alien.top/post/263029

https://lemm.ee/u/[email protected]

I strongly believe Lemmy isn't the place for mirroring content from other websites. You can host your own alternate Reddit frontend like LibReddit, there's no reason to spam the posts to everyone using Lemmy just because 5 people asked for it. Not to mention there are already enough instances mirroring posts, this is getting obnoxious.

you are viewing a single comment's thread
view the rest of the comments

[+] [email protected] -8 points 1 year ago* (last edited 1 year ago) (2 children)

“What’s the point? OP isn’t here.”

Please don't ever feel discouraged by contributing content to the network, if you think the contribution is positive.

There are other people there. Just check the number of subscribers to get an idea of at least how many people could be reached by your post.
Your comment there can act as a catalyst for other Lemmy users to join in and participate.
Having content on Lemmy that is not available on Reddit creates a positive asymmetry in our favor, and it creates an incentive for people on Reddit to migrate here.

reddit has a mode, which is the default, that’s between Lemmy’s “truly, everything all” and “subscribed”. (...) I hope Lemmy eventually gains something similar.

I agree, and it doesn't even need to be on Lemmy backend. I firmly believe that everything related to content filtering and even algorithmic choices should be part of the client, not the server.

We can have an (mobile/web) app that takes all of the firehose and does the filtering in the client.

[–] uis 0 points 1 year ago (1 children)

Client-side filtering? Easy. Client-side sorting? Not easy.

[–] [email protected] 0 points 1 year ago (1 children)

Why?

[–] uis 0 points 1 year ago (1 children)

Why hard? Client needs to fetch all metadata needed for sorting for every post created during entire lemmy's existance on every discovered lemmy instances, which depending on algo you are using, might include comments metadata. To aid client-side sorting you would need server-side filtering, which will limit data avaliable to sorting algo. For example client-side trending algo would not show old trending post because it was filtered out.

So client-side sorting is basically running stripped version of instance without file hosting.

[–] [email protected] -1 points 1 year ago (1 children)

Client needs to fetch all metadata needed for sorting for every post created during entire lemmy’s existance on every discovered lemmy instances.

Why would you need all data to build the frontpage? Why not just make a sliding window with the content from the last 24/48h?

So client-side sorting is basically running stripped version of instance without file hosting.

Even if that were true, how is that different, e.g, from any modern desktop email client?

[–] uis 0 points 1 year ago* (last edited 1 year ago) (1 children)

Why would you need all data to build the frontpage? Why not just make a sliding window with the content from the last 24/48h?

Exactly what I'm saying. To not be super resource-intensive, client-side sorting needs to be incomplete. As I said, if there is hypothetical post from 49 hours ago with 10k upvotes, you will not see it, but you will see one from 48 hours ago with 1k upvotes.

Even if that were true, how is that different, e.g, from any modern desktop email client?

Not much I guess(sounds like Thunderbird). But what about mobile?

[–] [email protected] 0 points 1 year ago

As I said, if there is hypothetical post from 49 hours ago with 10k upvotes, you will not see it, but you will see one from 48 hours ago with 1k upvotes.

Not necessarily true. You can build an index and keep a cache of the N posts by each sorting method. Your data store will grow linearly with the number of sorting criteria you will have, which should be small.

But what about mobile?

We are talking about an amount of data that a sqlite database process in a breeze. My K-9 email client can handle all my 20 years of gmail...

[+] [email protected] -8 points 1 year ago (1 children)

I can't believe two people downvoted your comment.

You're right about contributing.

As for the filtering, I'm not sure how I feel about that - I use the web interface on my computer and an app on my phone and tablet. I'd prefer them to have similar results. But I see the point you're making; it could be curated by user instead of a massive algorithm for everyone.

[+] [email protected] -11 points 1 year ago (2 children)

Thanks for the support, but I honestly stopped caring about downvotes. I think there is a vocal minority that is already set on not liking what I am doing, so they are going to vote me down even if I post a cure for cancer.

[–] [email protected] 12 points 1 year ago (1 children)

Fucking hell you are tone deaf. Your idea is fine. Your implementation sucks ass.

Did I see in another post where you told people to stop thinking of bots as bots and imagine they are real users because they might be one day, and then redefine what a bot was? Just stop.

People are telling you time and time again what is pissing them off, and then you just try and repackage and resell what you are doing. Just stop.

Put in big bold letters at the top of the posts that "THIS IS A THREAD THAT IS COPIED FROM REDDIT TO HELP FACILITATE USER TRANSITION TO LEMMMY."

Sure, you are driving people to participate in a thread, but it's pointless and counter productive. It's pissing people off and you are poo-poo'ing it like they don't understand your grand plans.

[–] uis 1 points 1 year ago* (last edited 1 year ago)

I had similar effect under post of linux ponies, where every comment had at least one downvote. I call it "brown marks".