>No catalog mode

Wrong: https://smelle.xyz/lynx/catalog.html

>shit loading while scrolling

I don't know where you got this from either. It scrolls perfectly fine on my end. Every page is available in plain HTML and it even works without client-side JavaScript.

Compared to other open source imageboard engines, it has the most features AFAIK. You can search through the list on https://imageboards.net/ to check out the different chans using LynxChan (NSFW warning: e.g., https://kohlchan.net, https://bunkerchan.xyz and https://8chan.moe are among the big instances).

>Wrong: https://smelle.xyz/lynx/catalog.html

Well, you've got usability problems. I actually tried to find the catalog, and could not.

Now, I was able to see it's a link on the top right corner, for some reason. Very unlike what I'd expect, being used to browsing 4chan.

>Every page is available in plain HTML and it even works without client-side JavaScript.

I scrolled the overboard, and stuff suddently appeared while scrolling. I'll have to assume that the page was still loading, slower than I'd expect due to HN hug of death.

In this software context, front-end is the collection of templates and static files, including but not limited to css, js, html. The front-end is detached from the back-end. So how visible the catalog icon/link is is entirely up to the front-end being used.

And how it loads is up to the server and client. It's just a basic html with <img> tags. Starting from a more recent version lazy loading is used on those. So if either the server or client is under performing, you will scroll and the lazy loading won't be able to load faster than you scroll.

So what if Github itself is not OSS? The technology behind is already open source and decentralized. You can switch to a Gitlab instance with just a few mouse clicks while also migrating your issues and pull requests.

I don't believe issues or pull requests are part of the Git repo. If there is a way to migrate them it would involve some GitHub API which could be shut down.

The commits in pull requests are part of the git repo, in that they can be fetched from the repo's remote. The comments are not.

as said; the issues are not part of the repo.

as much as many projects could use a clean slate here, i dont think the burden of migranting them manually or the act of just dumping them is realistic.

> So what if Github itself is not OSS? The technology behind is already open source…

So is much of the technology behind Discourse.[1]

[1] https://discord.com/open-source (click on "OS Libraries")