Reboot them once in a while

Switched to stable to get my system to fucking build and boot again, so I can get all the fixes

This is a gold mine for LLM scrapers to have a source of human written code XD BSDs in general as their cuck license doesn't even try to protect them

Android is kinda the only OS actually using SELinux and unix users for sandboxing user apps

So Rustdesk but vibecoded and without Wayland support??

Does it have easy LUKS BTRFS + snapshots setup?

That is somehow really hard on Debian

The thing is, Kate has LSPs, debugger integration, inline hints, compiler integration and warnings, projects and more.

The ecosystem is just not huge and it doesnt have full 3rd party extension support like VSCodium etc

They dont want to give control to platforms and their policies or update frequencies or some nonsense. Meanwhile they love Google

That depends on where you got the APK from

• the playstore apk only supports FCM
• the standalone, hidden (you only find it via search engines), apk on their website also supports websocket
• Twinhelix Signal-FOSS only supports websocket
• molly also supports blobfree FCM and UnifiedPush

But note that UnifiedPush is not supported by signal, so you need to register a fake device on a server running MollySocket. Which is very much additional attack surface and only worth it if you really rarely use signal

Use Verified-Apps from PrivacyGuides to verify the signature of the APK before installing.

Before Appverifier was a thing, it was very obscure how to even check that signature.

Yeah, since a month or so, and emphasis on 2 and not unlimited

Yeah unofficially... that is very much a bandaid. It is really bad of Signal to not have a blobfree reproducible build on F-Droid and Flathub, or even just external repos (for F-Droid and flathub).

Instead they have a hidden self-updating APK (which is a very cursed concept) with blobs, and a damn Appimage on Linux.

Session has removed forward secrecy. I dont know if they still have broken autodeletion and still store all messages in a blockchain (delaying actual deletion). Overall though, I would stay away from it.

Signal-FOSS as alternative

I use Signal-FOSS by twinhelix. It exists since many years and upatches are fully automated.

They are very simple, deblob signal, remove firebase messages and maps and whatnot.

Twinhelix has also added some of the jw patches, which are nice to have.

It does not

• remove donations (which is nice and kinda shit of molly)
• remove payments with mobilecoin (kinda useless sadly as very few exchanges support it)
• add blobfree firebase messaging
• add unifiedpush support
• support linking multiple phones
• support encrypting the database
• probably more

If you dont need those features, I highly recommend it. Signal shipping Google blobs and having no F-Droid repo is very bad and that shouldn't be supported.

See the list of known 3rd party F-Droid repos

UnifiedPush issues

Note that UnifiedPush needs to be supported by the server. The server then sends the push message to a UnifiedPush distributor (like Conversations, ntfy or Sunup). That distributor wakes up the app, which sends you the notification.

There is a slight polling delay of about 1 minute, so notifications are delayed.

I measured the effect of this by comparing molly with UP and the Signal APK with websocket. On a Pixel 8a running GrapheneOS, 12 hours idle on Wifi, airplane mode on (as the modem uses by far the most battery). I configured to send 10 messages to the device using Signals "send later" feature.

Websocket used 3% of the batterylife. Thats it.

And that effect is only significant for people who rarely use Signal, so the likelyhood of a nerd configuring MollySocket falling into that category is pretty low. If you regularly open Signal, this only delays notification alerts for no benefit.

And because the Signal servers don't officially support this you need to either selfhost MollySocket (which would be fine apart from potential update delays, what this post is about) or trust some server operator. MollySocket is registered as another device, so the Signal servers and any standard Signal client would treat it as a trusted device with its own decryption key.

Apparently MollySocket discards the key and only receives "you have a message" (and no other metadata? I have obviously not researched this a lot), and I suppose Molly ensures that the device will never get a decryption key either. Still, it increases attack surface for very limited benefit.

It would be great if Signal officially supported UP instead of Google FCM.

Check your autocorrect....

Haruna is a nicer frontend for MPV

I would include the 2-letter and 3-letter code in your searches

That seems to be kinda standard. If Sonarr/Radarr have a more elegant solution than looking in the title, that might be preferred

Your GPU might support AV1 encoding, but svtav1 is a software encoder running on your GPU.

Libaom is also a software encoder but not optimized and extremely slow as you noticed.

I think the size differences simply come from the parameters you chose, each encoder has its own parameters, arguments, maximum and minimum.

If your NVIDIA GPU supports AV1 encoding, then via nvenc.

Here is documentation and how you can list encoders and their options:

https://ffmpeg.org/ffmpeg-codecs.html#Encoders

ffmpeg --list-encoders

#list encoder options, here example for the "quicksync video" encoder from Intel
ffmpeg -h encoder=av1_qsv

GPU encoding is extremely fast but does not have the benefits of svtav1

• size is way bigger, at the benefit of speed
• there might be very big blocky artefacts
• no artificial noise generation and denoising, which make the image look smooth and add artificial grain, instead of trying to compress the grain and causing visible blocks everywhere. This is controversial but especially for
• no multipass encoding afaik. Multipass is a fancy thing where the encoder analyzes a video first and then encodes it in the second run (as far as I know), so it "knows" the video better and can react to bitrate changes better and give smaller sizes

For livestreaming, GPU encoding is essential. For reencoding movies (always use the highest available quality, e.g. a 2160p Bluray remux -> 1080p AV1 encode) software encoders are way better.

I have an Intel Arc and basically gave up on GPU encoding because of horrible quality, maybe nvenc is better though.

I read a lot on printed papers these days

Well you are obviously not the norm XD

Though of course simple, fast pages are amazing. Or normal? They should be easy to convert to darkmode locally, use with a screenreader etc.

https://purecss.com/

Corpos do weird shit and call that attestation

Having integrity verification of the system is very useful and essential for things like Banking software to be potentially available on Linux.

If we want that proprietary malware... another question. Do we have a choice?