meta-raspberrypi VS murder

How do you figure Pis have bad integration with Yocto?

https://github.com/agherzan/meta-raspberrypi

For what it's worth, the entire Pi lineup is also well supported by Buildroot. In-tree, no less.

Embedded linux exactly. Major OEMs are using yocto. Check https://www.yoctoproject.org/

Been there. You don't want alpine or debian. Good gpos, but what you want is Yocto, which will let you build exactly and only what you need piece by piece including only the kernel modules for your hardware, the exact applications you use and no extras, and with a little extra tweaking, you can wire in Mender for ota updates and the ability to push custom images to clients that need specialization, or even fully unlocked images for customers that need it, plus if you're using an SD card, you can send users recovery drives instead of shipping full devices or let them build their own images without your proprietary code

I second Yocto. It's the kernel in use by the OpenBMC project

One last "option" is yocto but tis is not good for desktop, but it can be a fun project.

When a user submits a tweet or post URL: https://twitter.com//status/

You can send a Tweet URL that looks something like this to the bot: https://twitter.com//status/

4. X

I went to https://twitter.com/ and only got the login page. You can see individual posts without an account, but most other read-only functionality is hidden behind the login wall.

It is this ublock origin custom rules

    news.ycombinator.com##tr.athing:has(a[href^="https://twitter.com"]) + tr + tr.spacer

I don’t know that the rename is going to stick. The logo is still an X in blackboard bold, but https://x.com/ links now redirect to https://twitter.com/.

Case in point.

Also, an easy work around is to take a twitter url and replace twitter.com with nitter.net to see the tweet and all replies.