The final api version would probably be in 1.0-beta.0, which will still take a few months. But at this time you can already start to adapt for the major changes like combined endpoints, and give feedback if anything else in the api needs changing.

Yes we always release backend and frontend versions together.

On the other hand it gives an indication to client developers that such big breaking changes wont be a regular occurence. So they have a reason to upgrade and then keep using 1.0 long-term. I believe that practically all the needed breaking changes are already implemented, and remaining issues are mostly new feature requests which can be added as new api endpoints or parameters.

You can enable multiple languages with ctrl + click. And user blocks might be another reason for missing posts.

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.

Im seeing the same posts in both cases, so its probably related to your account settings. For example user blocks, language settings etc.

I had a look at those communities, the only one which looks out of date is monero.town. And that instance has federation problems with many other instances, as you can see here under “lagging instances”.

cc @admin@monero.town

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.

This is correct, the changes on main branch will be released as 0.20 because there are lots of breaking changes now. We sometimes backport commits to 0.19.x, but only for minor changes or bug fixes.

@Blaze@feddit.org

Not sure really.

If there are still problems you should open a new issue. We cant leave issues open forever because they go stale and dont account for new features. By the way we are planning to implement multi-communities.

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.