If better data had been available to us, we would've been able to make a more informed decision. We've decided that privacy-preserving telemetry is one of the ways worth exploring to improve that data for the next time. If it is something we roll out to customers, customers will have the choice to participate. We will not collect any telemetry data unless we've obtained consent.
Does any one have the data(or where to look for the data) on how many banks depositor's were reimbursed over and above the FDIC insured amount of 250k in the last 1-2 years of bank failures?
The article doesn't support the claims of how nostr is better than mastodon.
From my quick glance at the site, it looks like relays are the equivalent to servers in mastodon, given that it's unclear why relay owners can't also ban you (as they suggest mastodon servers can ban you), why you can't post to multiple mastodon servers simultaneously (similar to broadcasting to multiple relays in nostr) and so on.
Nonetheless it's good to see the broader adoption of "account creation as equivalent to public/private key creation" in social media services
With Nostr, your identity isn't attached to a relay, so if one relay doesn't like you other relays will still relay your content, while still keeping your followerbase
How would my followers (or whatever they’re called in nostr) know where to get my events from?
It seems like optimal strategy is to send to/fetch from every relay possible. Effectively, every relay would host the whole network. In this regard federation seem a little more scalable.
> How would my followers (or whatever they’re called in nostr) know where to get my events from?
I don't know anything about Nostr, but couldn't that easily be solved by adding the relays that you use as a field in your event? Or even using a DHT to find relays that carry content from a particular user?
I don't know if clients support this yet but you can transmit a suggested relay with your post that people can add to their list of relays. That suggested relay should be one you control. That way they always have a point of truth for your notes.
This is a current problem. The solution is sending a small message telling everyone where you post to lots and lots of relays, then just posting to a few of them.
The main difference is that on mastodon your identity is tied to the server you registered on.
So, if a mastodon server bans you, you lose your account, your friends list, and your post history.
On nostr, your identity is a key pair and not tied to any particular relay. If a relay bans you, you can just connect to a new relay, re-broadcast your old notes to it, and keep going. Your friends list stays in-tact.
Yup spot on. The main issue though is that if you want to ensure that you have absolutely unassailable content, you need to run you own relay that ensures all your events are stored. You can’t assume that the relays you connect to via clients are perfect.
I imagine relay services will get better over time here but something to be aware of.
I don't quite understand why a client can't do it's own backup... it's really not that much data i would think. you could sync it to google drive or equivalent, and while your posts may temporarily be unavailable if all the relays are down, you could theoretically re-populate another relay (or your own) with that backed up data right?
A client can do this. There’s nothing stopping this from being implemented. I think it’s a good idea, really. It’s just a PR away from becoming reality :).
See also https://en.m.wikipedia.org/wiki/Marchetti's_constant
IMO there is a clear analogue for this with organizational size and the extent of your product offering, the further off from your core offering you extend the worse your entire offering becomes
