Yes, absolutely! The guidelines for now are basically "same as HN, but Euro-centric content please" :) I'll write these down somewhere explicitly soon.
Can you also consider adapting Linux from scratch as a part of this series? Or Maybe after this series, you can expand what is learnt to build a minimal Linux distribution. I suppose that might give a good understanding on how to apply this knowledge and a have a foundation on the internals of the os itself.
The other day, another os - tiny core Linux - was posted. Today this, I really wonder what is the trade off? Day to day use, security, and something else surely will be missing?
X11 applications will still "work" on Plasma Wayland session by utilizing XWayland, a tool that (afaik) runs a compact X11 session for each application.
What is being removed is running an X11-native Plasma session, only Wayland Plasma sessions will be available starting with Plasma 6.8.
I hope you will continue maintaining a mirror in GH. Some tools like deepwiki are excellent resources to learn about a codebase when their is not much documentation going around. But these tools only support pulling from GH.
A neat thing about GitHub is that every file on it can be accessed from URLs like https://raw.githubusercontent.com/simonw/llm-prices/refs/hea... which are served through a CDN with open CORS headers - which means any JavaScript application running anywhere can access them.
It's also not being served via a caching CDN, which means I don't feel comfortable running anything automated against it as that might add load to the server that they aren't ready for.
It's less about pulling and more about tools like DeepWiki making the assumption that its inputs live in GitHub, so repository URLs are expected to be GH URLs as opposed to a URL to a git repository anywhere.
That being said, there's no reason for tools like it to have those constraints other than pushing users into an ecosystem they prefer (i.e. GitHub instead of other forges).
reply