I believe they are claiming that with the new discoveries it's pointless to keep trying. Whether that's shared with other devs or not probably won't affect their decision:

These three bugs basically ruin the whole point of arkenfox: // sec bugs: offscreencanvas / preconnect / cookie_exceptions

I'm not that familiar with them, but sounds like there's no way to keep a sane balance between usability and privacy, and clearly upstream doesn't help a bit, it's like following the Borg advice "resistance is futile". Battling the privacy fight is not an easy fight I guess. The only hope for those who are non experts as the arkenfox guys is that phoenix keeps up the good work. Overall I pretty much prefer arkenfox over phoenix, but fortunately Librewolf is neither arkenfox nor phoenix, even though they are discussing if they are better based of phoenix the are different projects making different decisions...

I wish frozen fennec didn't die on the attempt, :( The current option is ironfox on LOS/AOSP based/..., and I don't agree with several of their decisions. The amount of filter lists is so stubbornly huge, that there's no time to deselect and/or remove them on low end phones for example, and the whole thing just slow things down. And I know it's picky but I really like decisions like taking bad things off from build time if possible, even if they are opt-in... Any ways, to me it's sad to see them closing the project, but I'm also hopeful some others as expert as they were on several of the topics they dealt with will fill up some of the the hole when they stop...

Like apple claims to protect its users privacy I guess. It ends up being a matter of trust with now a days mobile phones with wheels and motor

Thanks a lot for the reference !

Anyone aware of conversion kits for old off-roads including pickups, which would ship out of US? This not just to look for better prices, but also avoid the modern always connected vehicles and kind of saas deals. Any sturdy chassis those kits are made for? Before Tesla, and then BYD and so on, there were kits for enthusiastic people, but they were kind of expensive, and I guess now prices for such kits might have dropped considerably.

Unified push is great news in general for AOSP based ROMs phones for battery life, it's an open notification standard and system. There are several providers or distributors. If you're already using nextCloud with the unified push support on the server (murena has enabled this already because they want apps to consume less energy because of having to run in the background if not wanting to use the proprietary google services notifications) then you can use the unified push app already available on f-droid. If using conversations (xmpp client) it already supports working as an unified push provider and perhaps other xmmp clients already added such support and conversations is also available on f-droid. Or you can use the ntfy provided app also available on f-droid. There's an apps list available to find out if particular apps already support unified push, and as you can see fennec is one of them. BTW, if one doesn't want or need push notifications on fennec this can be disabled on its notifications settings, When installing an unified push notification provider, the apps supporting it will attempt to subscribe with a particular topic name on the provider, and usually the providers come with default settings to automatically accept subscriptions, and one can just check if the subscription is there already or not, one might need to stop and re-open the app for it to attempt to subscribe. Make sure the provider is running in the background without restrictions, I can tell conversations and ntfy are pretty low battery consumers so no worries about no restrictions on battery consumption.

Does that help? Otherwise I'm kind of lost with the questiosn.

Please define suckless. See on under suckless.org one can find rocking software, meaning suckless alternatives not developed/maintained by them, and on the editors section I see:

• acme - Rob Pike's framing text editor for Plan 9. Included in plan9port.
• ed - ED IS THE STANDARD TEXT EDITOR!
• ired - A minimalist hexadecimal editor and bindiffer for p9, w32 and *nix.
• mg - A portable version of mg.
• mle - A small, flexible console text editor.
• nano - A pico clone - this is small simple code and easy to use.
• neatvi - A minimal vi implementation supporting bidirectional UTF-8
• nextvi - A continuation of neatvi development with more features.
• nvi - A small, multiple file vi-alike.
• micro - A terminal text editor, written in go with common key bindings like ctrl-c to copy and ctrl-v to paste.
• sam - An editor by Rob Pike with inspiration from ed.
• sim - The sim text editor. Based on vim and sam.
• traditional vi - A fixed version of the original vi.
• vim (With the GUI, use :set go+=c to kill popup dialogs). It can be compiled to be as minimal as possible (see vim-tiny in Debian repos).
• vis - A modern, legacy free, simple yet efficient vim-like editor.
• wily - An acme clone for POSIX.

That said, also note there's an emacs-nox package available in most distros, which only includes the editor able to run on a terminal emulator, if emacs OS is too much. And can you share URLs justifying why vim is a big security hole? BTW I don't see neovim as part of the suckless.org/rocks software. What is suckless depends a lot about what one might consider it to be, even though there might be some common characteristics that can be recognized as not good such as bloated, too big code base and so on.

Not only those, it was google removing support for extractors, knowing that would affect frontends, particularly yt-dlp, and of course they had to react. BTW, libretube, what I prefer from f-droid was also affected. See this yt-dlp issue which was already fixed with a commit and the immediate release they provided. I grabbed the yt-dlp fix on artix Today and the libretube fix on f-droid Today as well.

I believe all frontends got affected (attacked?) in pretty similar ways...

Yyup, notmuch doesn't sync folders AFAIK since it is an indexer (a fast one), one needs mbsync and/or imapnotify to keep mail up to date (the combination might be mbsync to sync on boot, and then imapnotify to keep things up to date based on such notifications) to keep mail up to date. Another options is khard which is menat for cardav contacts just as khal is meant for caldav calendar... mutt-ics sounds great for ics calendar invitations, which I sometimes get from non family and non organization parties, otherwise I receive caldav ones, which I'd like to integrate with the caldav calendar so it syncs, perhaps mutt-ics handles that as well, first time reading about it, :)

Many thanks for answering !

how does khal integrate with neomutt for received invitations? khard works pretty well AFAIK with neomutt. Also, have you tried alot (notmuch + afew + alot + ...)? It sounds alot integrates much better than neomutt with notmuch, which in turn integrates much more better than mutt...