cfcosta
Cainã Costa

Worst part is not even the network itself, couldn’t care less and much prefer nostr.
It’s the people that are there and that now will be out of our reach. I’m not going to fucking instagram

2024-04-29 21:02:05 GMT

- reply

I've specified something like this before, worked almost full time just thinking about this problem for 3 months or so. In a short answer: Double Ratchet/X3DH for messaging, zero-knowledge proofs so the server doesn't know the sender or the receiver.
Keep the merkle root of a Merkle Search Tree, derive the next key based on the root of the current chat tree. Tree is self-balancing and automatically ordered to keep causality in check.
Inside each message, keep an encrypted Hybrid Logical Clock id on each message, to keep both causal and wall clock synchrony, even in case of clock drifts.
For each destination (like a group), publish a single entry, and multiple public keys, one for each destination. Add a random number of other public keys to obfuscate which are real and which are not.
When fetching, user sends a proof that, given the sender public key, they have ownership of the proof. Proof is consumed on the relay. User updates their own Merkle Search Tree on the client with each proof they consumed.
User then publishes new proofs for the same content they received, but with their own "backup key". These are kept in the relay for user device backup.
All keys are ephemeral, except the backup key, which can be the user nsec key. User publishes public one-time-use keys (either by publishing to relays or NIP-05).
Basically the chat conversation is a CRDT, and the same relay mechanism that nostr uses guarantees delivery without the need for consistency (which are also not required for crdts).
A little bit stream of counciousness, but I can give detailed explanations about everything I talked about here, and even wrote most of it down, just ping me if you need.

2023-03-13 17:01:48 GMT

https://i.imgur.com/k4QRjcE.jpg

2023-03-08 17:20:17 GMT

- reply

Usually the answer is not loading them at all, or if you do, not building objects for everything. Usually splitting into arrays of structs instead of structs of arrays also helps, as you can vectorize better (not sure if NEON is available for cellphones though)

2023-03-07 21:35:32 GMT

https://void.cat/d/9Eic1iLuhBbVAVubqBDtv6.webp

2023-03-01 16:37:31 GMT

https://i.imgur.com/u7EdeYe.jpg

2023-03-01 16:15:39 GMT

- reply

Sup!

2023-03-01 01:28:03 GMT

#[0] silence

2023-02-28 21:19:24 GMT

https://i.imgur.com/q3fY8HR.jpg

2023-02-28 17:25:10 GMT

We do exactly this on my team at work, and it’s working great. Learning curve is still kinda bad, but damn if the results aren’t worth it.
https://floxdev.com/blog/flox-and-containers

2023-02-28 14:57:30 GMT

Just to prove me wrong, someone zapped me 17 sats hehehe
Point still stands though.

2023-02-28 14:52:20 GMT

Zaps can do something that I thought wasn't possible before: it's more lucrative to actually generate good content than it is to scam people with stuff.
The smallest zap I've seen so far is 500 sats ($0.12). That's more than the CPM of many platforms. Posts from people like #[0] get much, much more than 1 zap per tweet.
It's easier to spam here than it is on other networks, but as more people move to paid relays, it becomes much much more expensive to do. Or, you can just write something cool and watch the money flows to your account. Which one seems cheaper?

2023-02-28 14:37:39 GMT

I've seen lots of people with a reachability problem here.
There's a simple way to fix it: listen to only the relays you do care about, but publish to as many active relays as possible.
People that don't share your relays are not going to have access to your posts, but posting is "free".
https://nostr-wine.github.io/filter-relay is a great "one-relay" solution if you are using nostr.wine already.

2023-02-28 14:25:46 GMT

https://i.imgur.com/IFvcDXp.jpg

2023-02-28 10:14:50 GMT

Morning, famiglia nostra

2023-02-28 01:55:43 GMT

Nostr is an incredible social network, it's much harder to find stuff to post than it is to develop stuff for it.

2023-02-27 22:59:24 GMT

Ok, zapping is pretty cool. I think the biggest barrier to entry is to actually move BTC to LN. It's really surprising how dificult it is.

2023-02-27 22:40:17 GMT

So yeah, finally have bitten the bullet, and am on nostr.wine and eden.nostr.land :D Global feed looks so much better already.
And hi guys!

2023-02-27 21:36:34 GMT

Verifying my Nostr Nests identity: XTph2inYQsvQ31WaU3P-vEkTatpKHKHbGD57K0vllRo
https://nostrnests.com

2023-02-04 22:33:33 GMT

- reply

Moved from what to what? PostgreSQL to something else?

2023-02-04 11:22:49 GMT

Thinking about forking nostr-rs-relay and generalizing the storage backend. Thinking there’s lots of performance to be gained by going away from sql into something more tailored to the usage.