Could you specify wether these support physical keyboards? (showing only a toolbar when one is detected). I’m using the default proprietary Kika-keyboard on my device and it’s not great. Microsoft Swiftkey works but is a bit worse.

I use Signal, but I’m unable to force everybody to do the same.

Re-implementation means reverse-engineering and building new binaries. What’s the point of MicroG if it is just downloading google binaries? An app with privileged access is different than a remote access trojan. The whole point of a sandbox is not to have the same access as the original app.

What you are saying doesn’t make any sense.

Any chance to use Whatsapp on /e/ ?

Yeah that’s unbelievable, I had the same experience! You must never install your bank app, otherwise it will start always requiring it.

Sounds to me that it would have been easier to create a web-based client for an existing messaging system with such features (like Briar).

A space station with artificial gravity would be a good project, rather than sending a man on Mars just to take a selfie.

It’s so hard to differenciate manipulators from plain idiots 😔

This is very detailed 😆 I would have appreciated going for Codeberg too. This is not so bad as used just for hosting the repo, a future migration away from GH would be a breeze.

It seems to me that there will be much less relays than there are AP nodes. Users won’t publish/subscribe to hundred of relays (if they did, relays would not scale). Hence more bad content to less moderators, and poor moderation.

Adding client filters would just shift the censorship power to those maintaining them.

I’m still using MPD+ncmpcpp. For remote access, I use Wireguard and stream via HTTP on VLC. It’s amazingly fast and lightweight (26MB RAM for 30K+ songs).

MALP also works on Android, might be better with no physical keyboard (now supports streaming also).

Checkout the list of recommendations published by the Free Software Foundation: https://www.fsf.org/resources/webmail-systems

A bunch of eDonkey servers were seized in 2006. This was before the implementation of Kademlia in emule. It highlighted the vulnerable centralized part of the protocol and pushed people to alternatives. Also compared to bittorrent, the lack of moderation and low speed played a role.

I would add:

3. Paid 24/7 support
4. Pay for custom features
5. Accept donations

I had a try ad Bookwyrm, which seems similar to what you intend to build. I was disappointed because the database itself is federated, meaning it’s full of duplicated entries.

I wish they chose IPFS instead of Bittorrent v1.

It seems like it is about using public pages to broadcast information. Mastodon seems fairly appropriate for that.

I highly doubt that there are 2.8M members on my instance (not to mention potus subscribers)

This feels so creepy to, being watched spending your money by slaves on the other side of the globe, and Amazon pretending it to be automated !

duplicate of: https://lemmy.ml/post/13989534