laenurd

Depending on what you mean by “AI”, this bot doesn’t fit the criteria. It works by extracting and ranking sentences and does not apply a LLM.

While I don’t agree with OP’s view that the world as a whole is anti-intellectual, I also wouldn’t assume that these people don’t exist at all. I’ve personally had interactions with people who thought less of me or others for having a higher level of education, and (at least overtly) not in the sense that they were jealous. It was more of a general antipathy against people who know things / enjoy to learn, because they saw them as arrogant etc.

But this is probably more an example of tribalism.

While not community-developed per se, the RISC-V processor architecture is completely open, in contrast to all other architectures which are widely deployed, such as x86, AMD64 or ARM.

Out of interest - which tool(s) did you use to generate this outline?

For a little perspective:

Mastodon has an official way of migrating your account. It migrates your followers and accounts you follow, but doesn’t migrate your posts afaik.

Migrating posts (and comments in Lemmy’s case) would be iffy in itself imho and I’m also not sure whether that would even be possible since posts are synchronized to federated instances, where they would have to be updated too.

Yes. You can use the search function for that, just search for “community@instance”, so for example “worldnews@lemmy.world”.

Linking to communities from other instances works similarly, using a “!”: !worldnews@lemmy.world

You can also append this type of address to your instance url like so:

https://lemmy.ml/c/worldnews@lemmy.world

As long as another instance is not explicitly defederated (blocked) from yours, you can visit any community from any instance this way.

Firstly: I was partially wrong about what gets cached, see my original comment.

There is an open pull request which is meant to give some options regarding media serving. Right now it’s only a rough sketch though and does not implement a lot functionality.

I was wrong about what gets cached: media that is hosted directly on remote instances is not cached, while media from outside sources (imgur etc.) is cached and served from that cache.

So, from a small instance’s point of view, the best case scenario would be if everyone used Lemmy’s own media hosting exclusively. But that would, of course, greatly increase the storage requirements of larger instances.

I updated my comment as I was partially wrong about what gets cached.

I was partially wrong about what is cached and updated my comment.

That would be great to know, any chance you remember where you read that?

The obvious way would be to just not cache content locally and always link to the source instance. While this would concentrate the strain immensely, it would also greatly decrease the storage space used by all other instances.

There might also be other viable alternatives such as using a CDN and having it selectively cache content which is requested often etc.

~~As of now, Lemmy does not support either, though. ~~

Edit: I want to clarify that I was partially wrong - Lemmy only locally caches content which is hosted on outside sites. It does (should?) not cache content that was directly uploaded to a Lemmy instance and just embeds the source media.

Right now you can only disable caching of nsfw content by disabling NSFW for the instance, but of course this has nothing to do with “soft” rules that are only written out in text.

Imo the best solution would be to allow admins to have more granular control over caching, e.g. disabling caching for specific instances / communities or whitelisting. And we need an option to disable caching altogether.

Agree. If I’m not mistaken, you can only disable the caching of sensitive (NSFW) content on your instance by disabling NSFW in general. This doesn’t go for SFW content though.

It shouldn’t be very hard to do this for all content though, if I find the time I might look into implementing this.

Also probably ITT: many non-Americans to whom that draconian law thankfully does not apply

No need to thank me, currently I am the only non-bot-user of my instance and do not allow registrations 😅

Many of the bigger instances have links to donate to their operators, but I am doubtful that relying solely on donations will be enough in the long run.

Everything. It does some re-encoding when it retrieves content from other instances and you can set limits for pictrs (the software Lemmy uses to host media) regarding file sizes etc.

Edit: I was partially wrong about what is cached, see my original comment

This will differ greatly from instance to instance. The people running lemmy.world have published some info on their infrastructure. My instance is running on a rather small VPS with 100GB storage, but I will have to rethink my solution rather soon as images and videos from my subbed communities [Edit: which are stored on outside sites] are eating around a gigabyte per day and I think this is likely to increase.

Edit: I want to clarify that I was partially wrong - Lemmy only locally caches content which is hosted on outside sites (e.g. imgur). It does not cache content that was directly uploaded to another Lemmy instance and just embeds the source media.

That is not true. As long as a user on your instance is subscribed to a community, the media content of posts [Edit: only posts linking to outside sources, e.g imgur] of that community is stored locally on your instance as well.

This, of course, only applies to media which is uploaded to Lemmy, links to media hosted externally are not downloaded.

See this issue for more context.

Edit: I want to clarify that I was partially wrong - Lemmy only locally caches content which is hosted on outside sites. It does (should?) not cache content that was directly uploaded to a Lemmy instance and just embeds the source media.

Sorry, I must’ve missed that somehow, then my comment only applies to llama and its direct derivates.