You don't have to be a right winger to be uncomfortable with tankies

Yeah, having swallowed decades of US propaganda is enough

I have hosted a PeerTube instance and surprisingly the storage is not a problem because it is very cheap these days.

About the bandwidth, if you enable PeerTube's p2p tech (WebTorrent) you can have a fair number of users streaming at the same time (but it's not great for privacy).

I have proposed a network of PeerTube instances to a group of youtubers each with tens to hundreds of thousands subscribers and the benefits/costs ratio looked pretty good to them. It didn't work for other reasons.

Notice that youtubers earn basically nothing from YouTube except those with millions of subscribers. They are on YouTube just for visibility but if enough creators move at the same time they can also move a good percentage of the userbase in my opinion.

Thanks, though the article also says that Telegram states they didn't share any data because they have never stored it (like IP).

Telegram is known to occasionally hand out users' data in extraordinary circumstances

Source? And what circumstances? AFAIK it never happened.

Akregator is part of KDE PIM, not Plasma. Maybe it will be ported to Qt6/KF6 but the average user won't be able to notice the difference.

Because in English all proper names have the first letter capitalized, it doesn't matter if it's a brand that uses only lowercase in its logotype. This is the rule.

So: Systemd, Git, KDE Neon, Iphone, Ipad, Mac OS and so on.

On the license: https://discuss.logseq.com/t/on-the-agpl-license-and-the-idea-to-move-away-from-it/14716

On ChatGPT: https://discuss.logseq.com/t/why-logseq-ai-and-how-to-preserve-privacy/17486

And here it will be harder to abuse your mod powers since there is a public mod-log!

Everywhere, no matter the page, you can write:

- [[Book name]]
  - [[Quotes]]
   - Plain quote here.
   - Another quote here.

or:

- [[Book name]]
 - Plain quote here.
   #quotes

You can retrieve them with the query:

{{query (and [[Book name]] [[quotes]])}}

Remember that queries look for references also in the parent blocks, so the following:

- [[Author name]]
  - [[Book name]]
   - [[Quotes]]
    - A quote.

matches:

{{query (and [[Author name]] [[Book name]] [[quotes]])}}

So you can group your quotes and tag them only once instead of repeating the same tag on different lines.

You can embed the quote somewhere else and style it as a quote using the > symbol:

- > ((block-id))

What a stretch to save US imperialism, lol

I think the least worst is OpenSUSE Leap or Tumbleweed with Plasma, because they have good support of containerization technologies, so you use the OCI images you prefer to develop and you can rest assured that the system will boot even in case of errors if you use snapshots by BTRFS. Plasma has desktop widgets for viewing issues from GitHub and GitLab which are very handy.

So why not Jami? (https://jami.net/)

It's P2P so no servers and it's a GNU project.

I'm not talking about Lemmy, but the entire Fediverse. Matrix is not for instant messaging only, as its authors keep saying. Matrix is basically a decentralized database for real-time content with permissions and end-to-end encryption built-in. ActivityPub is good only for public content and can't guarantee a modern user experience when it comes to federation, as I said as the network grows it adds inconsistencies and common users are confused by it.

P.S. nothing stops someone from implementing both Matrix and ActivityPub on the same server: the former to federate with other Matrix servers and the latter to keep the federation with Mastodon & Co.

Did you not realize that if your instance has not yet interacted with another and you want to see the profile of a user you will never see his old posts but you will only receive new ones if you click "follow"? Or the busted counters that are different depending on how your instance is connected to the others? Practically with ActivityPub the information hardly spreads, with Matrix you have the assured consistency.

And then the Access Control Lists, they are not supported by ActivityPub so no stuff like private groups. When it comes to Matrix,they are built-in.

And Matrix defines APIs for both server-to-server federation and client-server communication, while ActivityPub is currently only used for federation. Client-server ActivityPub APIs have been discarded in favor of thin-client APIs such as Mastodon's.

Matrix continually adds new features. ActivityPub is stopped and too generic, it could be expanded in many ways for different use cases but each group of people works on it separately and for now without big results (see ForgeFed).

I hope the opposite i.e. using Matrix protocol for federation instead of ActivityPub, this would solve a lot of problems with federation and enable chats like you wish.

You can think of democracy itself not as a condition but as that process that gradually decentralizes power, be it economic, political, technological, informative or otherwise.

Right to control your data, for example export it in an open format

While I hope in the long term Matrix ecosystem will suit all the use cases, even the social ones by replacing/complementing ActivityPub, at the moment even its flagship client that most people are mentioning (Element) can't replace Discord.

Instead I think the best alternative at the moment is Telegram because it has a large userbase, native clients for Linux, Android, Windows etc, voice chats that suit the Discord-like use case and it doesn't use/sell users' data.

I thought "Communities" were already used to group rooms?

Anyway I searched more for these "Spaces" and I found this:

Spaces are particularly interesting because they open up the possibility of Matrix being more than just a big flat namespace of conversations: instead they provide a global fully decentralised hierarchical filesystem, complete with decentralised ACLs, allowing users to publish and curate an arbitrary taxonomy of whatever data they choose (be it real-time conversations, history, data streams, files, objects, etc). This has potential to flip Matrix entirely on its head: Spaces could become the main backbone of the protocol, with chatrooms being mere leaf nodes in a giant tree of collaboration.