IIRC the join page is largely automated and simply scrapes active but “small” instances, other than instances that have been asked to be removed from it due to load issues (such as lemmy.world, lemmy.ml, etc). The devs probably don’t even know its up there. Hopefully this gets their attention.

I’m going to preemptively warn my admins about them and ask for defederation though. Don’t need that shit creeping in.

its a nazi troll account doing nazi troll things

Troll = BUSTED LMAO

Block the lemmit.online and irradiated bots that just spam reddit links, as well as basically every community from lemmit.online Then add reddit to your uBlock lists so any accidental direct links just get blackholed. Bam, reddit is gone from your life.

That’s all Reddit was when it started too- a link aggregator Digg side-site.

Let natural growth run its course, and curate your communities better to see less Reddit content. I spent an afternoon discovering communities thst weren’t built on reposts and see quite a decent amount of original content, and actively hide all the reddit-linked content.

They will not ever be blocking Reddit content because that will be the early death of this platform. Besides, devs choosing to hard block sites in the back end is a horrible, horrible precedent. Learn to deal with it.

A mouse with black, round ears?

Disney Corporation lawyers would like to know your location

You can downvote from your instance and the UI will “show” it, but the votes will not be counted on the originating instance with downvotes disabled.

Magic of activitypub!

It’s an injection vulnerability that some dirty folk found and needs to get patched out. It was inevitable with the sudden user increase.

Yeah, better embed support would go a long way to keeping the load off Lemmy but still supporting additional content. On Desktop it’s not a big deal to just shift-click videos into a new tab, but on mobile it’s slow and I usually lose my spot when I leave the lemmy tab… I’m sure they’ll get to it soon enough.

I’m going to guess no. Video would exponentially increase the bandwidth and data storage requirements of instances when these instances already can barely handle their user load and static images being uploaded.

Use an external hosting service as much as you can. Linking directly to something actually designed to distribute the load, like PeerTube, is vastly more efficient than expecting Lemmy instances to handle it.

I feel as if somehow claiming ownership of user content in the EULA in a way that would be DMCA enforceable would also be antithetical to the tenets of open source software.

Yes, the process to find a new community on another instance is pretty clunky. For one, part of the issue of the “i searched for it and it didn’t appear” is your home instance has to wait for the workers on the remote instance to actually reply with “yes, this community exists” before you can browse to it. And your home instance must have workers free to actually make such a request. Many communities are heavily overloaded and these federation tasks can run many minutes behind which leads to a frustrating experience trying to find a community.

You will only ever see NEW posts that are made AFTER an instance first federates a community. This is intentional, because loading all back history out of the database once these communities exist for a few years would be a gargantuan, horrifyingly resource intensive task. As such, all back history will only be loaded “on request”, aka, the remote instance will only send pre-federation content if a user on the local instance specifically attempts to browse to it.

Lemmy definitely needs to have a lot more aggressive moderation and administrative tools built into it. Not only is deleting things directly from databases or databases themselves super risky for data integrity (gitlab incident, anyone?), but it leaves no trace of who or what was deleted. Which is a huge security hole, both for potential instance admin abuse as well as bad actors gaining access to an instance’s back end and monkeying with it. Ideally such things should be done entirely through Lemmy and tracked in the modlog (or a separate backend admin log).

Part of the idea behind federation is that by only accessing content through your specific instance, you actually reduce the load on the instance you’re browsing to, because your specific instance federates (essentially “caches”) a local copy of the remote content. So by trying to obtain a direct “global” link to the original you’re bypassing a lot of the natural load sharing and that is inherently undesirable for very large instances like lemmy.ml is becoming. As long as federation is working smoothly, you are losing no inherent information about the post by sharing a link to the post from your lemmy.world instance vs lemmy.one, lemmy.ml, or any other instance, whether the post is original to that instance or no.

Besides, the information about the “server/community/post” is sort of baked into Lemmy’s UI with how it defines locations within Lemmy (eg. Technology@beehaw.org, tells you right off the bat the community is on the Beehaw instance, same for users). That’s just down to user’s learning knowledge about how the Lemmy system is laid out and displayed in the UI.

I am one of those influx.

I’m realllllly just hoping we don’t choke the “main” instances completely to death before the lemmy backend can have some developer hours dumped into it to support better per-instance horizontal scaling.