Biohazardous Catfox @Elizafox@treehouse.systems
Public

Also it might be worth writing more on preferences encryption:

It takes a password you provide it. It uses PBKDF2 (not the best option but it's the most widely supported by WebCrypto), right now I have it at 500,000 iterations to create an AES-256 key. This key is then used to encrypt your preferences.

As aforementioned, preferences updates must still be signed to be attested. Otherwise they are not applied.

Pros:

  • You can share preferences without sharing the root key

Cons:

  • You need good password hygiene or you lose control of your metadata (just like... everything else)
Biohazardous Catfox @Elizafox@treehouse.systems
Public

A good question about this is "why this and not Fedi"

Fedi is fine.

However, it is HEAVYWEIGHT infrastructure.

It's big. It's not cheap to run. Even Misskey/Sharkey/Pleroma/etc. are not cheap to run.

mastodon.social is the default instance. There is no real way around that. People want a default instance.

It is not super seamless to move instances, migration is better than it used to be but far from perfect. It means bringing all your data with you to a new server.

With this... there is no migration, ever again.

With a backend like OrbitDB, you have a distributed storage network that is basically a cockroach.

There will be no "RIP <instance>" it will just be "RIP <home page gateway>". And you can run one yourself or use someone else's. My goal is you can run this on GitHub pages or any static site.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.treehouse.systems/users/Elizafox/statuses/116084948963056544 on your instance and quote it. (Note that quoting is not supported in Mastodon.)