Lemmy maintainer

  • 79 Posts
  • 645 Comments
Joined 5 years ago
cake
Cake day: January 17th, 2020

help-circle














  • 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.




  • 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.




  • 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.