Show newer

but if we change the trust model to a federation with a strong "leader", then it basically becomes pretty similar to what we have here today, with the added benefit that the admin doesn't have to carry all the costs of running the instance

Show thread

I have this weird idea for a distributed and private Mastodon instance:

- the instance would be Tor-only
- anybody* could help host an instance they like by installing and running some software (let's say a "node")
- the nodes would connect with each other and coordinate which one should do what (storage, database, http, etc)
- by using OnionBalance one can split the traffic among all the "http" instances

*not really "anybody" because this would make it trivial to take down the instance

@Francispouliot more than @nvk i guess Cloudflare (or a cloud provider if they are using one) could censor the instance fairly easily.

i'm trying to see if there's a nice way to build solid/scalable/fast Mastodon instances over Tor

❓ Write in C the definition of a pointer to a constant of type char pointer.

@nvk i think there's a way to let cloudflare generate an onion for you: blog.cloudflare.com/cloudflare

probably not the best solution but a good compromise still

Is there an onion address for this instance as well?

cc @nvk

Highly recommend the latest Crypto Voices podcast with @giacomozucco, excellent discussion on BTC proof of work and the RGB spec he's working on with @afilini

soundcloud.com/cryptovoices/sh

rgb.network/

@pizzamarinara yes (thought about it) but no (it won't work), this is going to be x86..

@Dennis @kelbie it's "private" in the sense that other users cannot see them. But messages are saved in plain-text on the server.

Admins, hosting providers, governments, they all can read them if they want to..

@Dennis @kelbie it's "private" in the sense that other users cannot see them. But messages are saved in plain-text on the server.

Admins, hosting providers, governments, they all can read them if they want to..

@kelbie I saw a discussione about that yesterday: the main point was that this design is actually pretty cool, to remove the fake sense of privacy that Twitter's DMs give.

There's no E2E encryption, so messages are not private at all. Not that @nvk is bad, but what if the hosting provider decides to "have a look" into the instance *they* host?

My proposal would be to completely remove them, and encourage users to communicate using something else.

@kelbie seems like Tusky just uploads the image (sometimes after a quick resize if it's too big). I'll work on that as soon as I have some spare time!

Hopefully with the Bitcoin community jumping into mastodon, some PR to improve its privacy/safety will come 💪

@kelbie seems like Tusky just uploads the image (sometimes after a quick resize if it's too big). I'll work on that as soon as I have some spare time!

Hopefully with the Bitcoin community jumping into mastodon, some PR to improve its privacy/safety will come 💪

@kelbie okay, looks like it's done - at least server side.

I'll check out the sources of the app I'm using, just to make sure it's done locally too. I might open a PR if that's not the case :)

Does anyone know if mastodon strips EXIF metadata out of uploaded pictures? 🤔🤔

Show older
Bitcoin Mastodon

Bitcoin Maston Instance