Its not really what you are looking for, but you could my project Ibis for this. Its a wiki so instead of separate files you could use multiple markdown code blocks. Instead of a whole new project you could possibly implement gists as a custom frontend which converts to markdown for the backend. Note that the project is still in early development, so neither syntax highlighting nor federation with other platforms are available yet.

I am currently working on admin only reports.

https://github.com/LemmyNet/lemmy/pull/5350

Mainly SEO spam with text copied from other sites and lots of ads/referral links to make the owner a profit. But after thinking about it more, those would be rather easy to filter based on ad code in the HTML.

A much bigger challenge will be the ranking of search results. When searching for a term and there are 100 pages in the index that contain it, which of these pages should be shown first? Google developed the Pagerank when they started out, so that might be a good starting point to research further.

This sounds like a very interesting idea. I agree that Yacy doesnt work, when I checked it out years ago it was a completely bloated mess. Not sure how viable how your idea is, because Im not familiar with webrings, and not sure how the federation will work. Anyway the main challenge for this project will be to actually give useful search results, both early on when there are very few crawlers, and also later once spammers try to abuse it.

Ive never met any person named “Lemmy”, nor seen it in any kind of movie. And the first time I heard about Lemmy the musicion was when I searched for Lemmy the software. For me it mostly sounds similar to cute little lemmings.

Funny, Mastodon just posted a similar thing about creating a foundation. But the problem is, the existence of a foundation does nothing to prevent billionaires from controlling social media. For billionaires its very easy to donate a few hundred thousand USD to the foundation and gain influence that way. I expect that Bluesky will be fine for the first years (maybe like early Twitter), but sooner or later the foundation will take decisions that the users dont like, and there is nothing they can do about it.

In my view, the only way to avoid influence from billionaires is to avoid any large centralized structures. In the Fediverse there are dozens of platforms and thousands of instances. Even if a billionaire were to take control over a couple of projects or large instances, people would create forks in a matter of days. Some admins would block these corrupted instances, and their users would barely notice that anything changed.

So Bluesky is just trying to repeat something that has already failed. The Fediverse is the future, but it will take a long time for most people to understand that.

It’s like Blaze says, we are already working towards version 0.20 now which will have various breaking changes. There will be an announcement a while before the final release to let developers know about the changes. Also the current api v3 will still be available for backwards compatibility.

Sounds like you are familiar with this topic. I dont have time to work more on this particular aspect (there are lots of other tasks like comment support, federation with Lemmy, etc). But contributions are definitely welcome, preferably directly to leptos_use so that others can benefit and its easier to maintain.

It uses the browser preference for light/dark theme by default. After you click the theme toggle on the site, it keeps using that chosen theme by storing it in a cookie.

Seems unlikely, but maybe it will happen in many years if Ibis shows that its possible and desirable.

This would be neat to generate forum avatars, to show something similar to your real face.

The post yes, but not the comments at depth > 50.

No the max comment depth is generally lower now. However this doesnt affect comments created before upgrading.

Changing post.url from varchar(512) to varchar(2000) really messed up database performance so lemmy.ml became unusable. Turns out that column statistics are removed when the type is changed, so we had to run analyze as part of the migration. Seems like a bug in postgres.

https://github.com/LemmyNet/lemmy/issues/4983#issuecomment-2446945046

Dont think I did, it was really a team effort. And in the end the working solution was suggested by @phiresky@lemmy.world, thanks for that!

It will be rejected by the api (or by federation).

Correct, I suppose the ban button could be hidden from the ui in that case.

Right I will also have to make a template with these common parts of the release announcement. Instance blocking is not implemented yet, but it uses the same federation library as Lemmy so that will be easy to add when its needed.

Thank you, fixed!

No domestic flight, just Europe -> Texas -> Mexico.