After examination, it still appears that Bastyon does a better job of providing a Twitter like interface while remaining private and anonymous as you choose to. However, my assumption that using the block-chain being the only way to do that may have been in error. I’ve also learned a bit about Session and done a little reading on Nostr, but although Session seems to be a WhatsApp OR Signal - killer, it doesn’t appear to have the same ability to share news and create followers like Twitter or Telegram. I am very enthusiastic about all the new activity in the decentralized communication space.

I’ve bounced around alot, have numerous distributions on my Proxmox Hypervisor, but my favorite daily driver, for a really old computer, is ( MX Linux ) I’ve twice tried other distros to see if I could improve upon the stability and performance, as well as the very convenient availability of a feature rich KDE Desktop environment, and I came back to MX twice now. When I get a new fast computer, I’ll switch to Qubes OS, for it’s built-in hypervisor and security/privacy and isolation features, but until then, I’ll stick with MX.

IMHO, there are excellent reasons why MX ranks highest. I think it’s original roots in AntiX with the elimination of systemd has afforded it a substantial advantage over stock-standard Debian, my last daily driver which always had performance issues. With MX, on same hardware, system lock ups are far less frequent when the system is overtaxed.

After some additional education on the broad topic of decentralized communications tools, I’ve learned of Matrix/Element and Session Messenger, which seem to accomplish alot of the privacy and anonymity goals without the use of blockchain, yet it is decentralized, so they also will survive a widespread DNS blocking, also referred to as the Internet Kill Switch.

A little off topic, but with the way censorship is ramping up all over the globe, this may be the new norm for savvy Linux users everywhere.

Funny, flatpak works on MX, but it kills performance. I launch any flatpak program and it’s literally up to five minutes to launch. After re-imaging and using AppImages instead, it’s blazing fast. There must be something about the way MX implements flatpaks that screws the pooch.

This is the first I’ve seen of this. We’re talking about which redesign before the obvious discussion that we should have, “whether” the site needs a redesign. I’m open to changes if someone can justify them with a requirements change. Let’s first discuss current requirements, whether the current site meets those requirements, then decide if we want to change those requirements. From a consumer of the website, the current site meets all the requirements for it’s current mission. Thoughts??

I discourage the implementation of AppImage creation because it’s a cheap and dirty way to tick the box for Linux compatibility, yet this does not translate into usability for the Linux user. Some cons to this half-baked shortcut IMHO are:

• packages don’t update with operating system updates using native package managers like apt or yum so updates are clumsy and in some cases have broken my system.
• packages don’t integrate with operating system menu hierarchy.
• it can tend to circumvent the quality controls inherent in the package introduction processes of these distributions, therefore reducing it’s overall reliability as a tool. (it’s also a great way to sneak malicious code on to your machine, btw)

What you end up with is a broken app, which may not break your system entirely at first. Any of those that continue to attempt to correct these broken apps can either get lucky and fix the app, or make things worse and really break the Operating System. It is for these reasons I urge the developer community to avoid using snap, AppImage, or Flatpak and stick to releasing binaries for specific distributions like .deb or .rpm.

I’d rather wait a year longer for it than have you check off your “Linux compatibility” box and never look at it again.

I’m not a programmer, so if you find any statements factually incorrect, I’ll beg your forgiveness in advance and ask that you don’t bite my head off in your reply, just politely point out and correct factual misstatements and save your energy for writing code for binary installation package files like .deb or .rpm.

Sincerely,

Prancing389

It’s because the Khazarian bankers are behind Proton, as deep state as it gets.