I you use the external player, and mpv in particular with yt-dlp installed, then you’ll have an alternative still using freetube as frontend to navigate YT.

I do prefer ytcui with yt-dlp backend, which is native, low on resources and I really like ncurses, but that’s up to anyone.

That said, yt-dlp also gets IP blocked every once in a while, and also find itself non working at all depending on G. moves…

You’re right, I forgot, in that regard for example with xmpp, besides being able to self-host you have multiple services, perhaps eventually there might be non just simpleX services but hosted by others as well, though it seems whether simpleX or self-host for now. So it’s true it’s decentralized by definition, perhaps not so much in practice though.

There’s another sad thing I just remember, it doesn’t yet support multi-divice syncing, and the alternative is to create groups with different members, one per device, and then in the same group apply the same for all other multi-device members. The reaction so far from the devs is that it’s not so important having a workaround at hand. So both things made me drop my trials with simpleX…

The only sad thing is that it’s centralized, kind of signal but better.

On the privacy front I believe xmpp + omemo shines, and jami is also very interesting (though jami for some reason is doing efforts to allow LLMs agents and bots, through plugins of course not by default, but I don’t see the need of any of that stuff on something like jami). Sadly briar is on maintain mode and it was really bad on phones’ batteries, tox never took of leaving only jami like a viable distributed alternative. xmpp is decentralized and federated, doing pretty well with omemo…

xmpp + omemo. Signal is centralized, matrix leaks tons of metadata to sync between services…

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…

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.

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…

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…

artix, and honorific mentions to parabola and hyperbola (hyperbola is moving towards becoming a gnu + kopenbsd thing, like there was an attempt for a debian gnu + kfreebsd effort though this one got dropped)

• terminal: profanity (really cool, it became what I regularly use, no audio/video calls though in which case a gui like dino can be used, syncing between the two)
• gui: dino (there’s a fork called dinox)
• android: conversations (from f-droid)

It depends on your preferences of course. Notmuch offers a way fast indexer you can’t get with traditional gui applications, but by itself it’s not pretty useful, however the integration with other tools makes it really powerful, with afew you get your personal tagging when messages arrive (filters), with alot you just get the email frontend. If you like the terminal experience, then you’d know you need something extra for smtp (writing emails) and there you have for example msmtp. It’s a matter of choice. I mentioned notmuch since the traditional approach to the terminal is plain neomutt, but there are alternatives. isync (mbsync) actually interacts well with neomutt but it also does it with notmuch, and neomutt can be used as a frontend for notmuch as well. A matter of choices.

The thing with solutions like thunderbird is that you have to adhere to their design decisions. For example I don’t like their librnp implementation, and I had to create alpm hooks on artix to keep updating such library with sequoia-octopus-librnp, not because I like rust (I don’t dislike it either), but because at least I can keep just one keyring, and thunderbird when not having a master password (the default) keeps its keyring unencrypted, and I pretty much see no reason not to use gnupg. So I decided I better kept using gnupg’s keyring and stuff. Integrating different tools designed for specific purposes you have more freedom of choice. At any rate that’s how unix was conceived, and you can choose to do it that way if you want.

Cool, it never came back to arch/artix, however I see it on aur. I actually don’t use gui for mpd, I use ncmpcpp, but good to know it has quite good gui frontend. ario is good as well, particularly if not much into Qt apps.

cantata is no longer maintained AFAIK, but as mentioned there are other clients such as ario, which on arch/artix it is build on gtk3, not gtk2

How about isync + notmuch + afew + alot + msmtp? gpg decryption not directly supported but using alot’s pipeto it can be used to decrypt messages. As using notmuch as indexer it’s flow is pretty similar/compatible to/with gmail.

apkupdater installing from apkpure?

I’m wondering about LOS re-locking on particular devices. DivestOS used to allow that, not sure if only on pixels, but if divestOS which was based on LOS could, I don’t see how that code can not be ported over upstream LOS. Have anyone seen an effort similar to divestOS in this regard?

if someone is up to the challenge to take lemoa over, a gtk app, the original author seems to be open for that.

neonmodem