You may find the contract unfulfilled, it's certainly something real people do.
Same with nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn . I try to trigger him with absolutely absurd questions like what does the Bible say on jaywalking and he goes and makes a serious effort to properly answer that.
nostr:note1zqq2u2hj69y289jc68j43mg2c5zg49l02kf00wx7jgmn7r92vv7sucnthn
Yeah any such numbers metric will easily be gamed.
This guy's notes are too rational and level headed to properly lampoon him.
Can't he pull a nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc once in a while and post something like "LOL TEH BITCOIN WOWZERS" so that I have something to pick on.
nostr:note19fhasyxra9ykdek368un8cux7dy73cesn40q7w3p4yjgpue3e48qvjjp7w
Same with nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn . I try to trigger him with absolutely absurd questions like what does the Bible say on jaywalking and he goes and makes a serious effort to properly answer that.
This guy's notes are too rational and level headed to properly lampoon him.
Can't he pull a nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc once in a while and post something like "LOL TEH BITCOIN WOWZERS" so that I have something to pick on.
nostr:note19fhasyxra9ykdek368un8cux7dy73cesn40q7w3p4yjgpue3e48qvjjp7w
Every npub on nostr is as real as the next one. You may prefer to follow one, that doesn't make the other one "fake".
"Web of trust" is some sort of buzzword only. It can mean anything and everything.
There is also a larger problem here. Your thinking revolves around isolated, single responsitories. But the open source world has repositories referring to one another.
Example: https://github.com/simplex-chat/simplex-chat/blob/stable/cabal.project #L34
The whole chain of repositories must be decentralized and highly available. This is the problem I have to solve.
> Currently if there are multiple people who claim the same repository and they don't list the others as 'maintainers', gitworkshop.dev uses the one with the most references in other events. If they do, the event with the most recent created_at timestamp is used.
Whatever consensus protocol you come up with must also work decentralized. Gitworkshop.dev is centralized.
Better earlier than later. Duh.
> If someone tries to game this, the intention is to add web of trust into this.
I believe that when I see that.
Maybe ... I think this needs to be figured out and baked into the system. Don't leave solving the hard part to the user if that's what you head in mind.
Drop it.
nostr:note1alkgtvnyhhs2acu4fpgph3vvnv98rcf6kd743s8u42aryaaqmrtsll0uyr
Woke got triggered #win
nostr:note1n2ujrgq3fseluw38uvkxq6nejpvr0uql9h2ry20a2fdtdhryqwtsxcgtvw
Yeah nah this gossip idea isn't great and will scale even more poorly than DHT.
There isn't a problem with chunking and deduplication.
Blossom, nostr and the likes only work if there's a few dozen servers/relays.
That's not decentralized enough.
Totally.
I've been posting food porn and will keep doing so. My home cooking isn't very "instagrammable" though so only if I go out for dinner.
nostr:note13epk8eveg5ug7mffcczzpefrlknpw2httt8z8g3wpszqcpjc6j4svl7sgz
Sorry, "multiple" and "authoritative" are contradictions in terms.
I know Linux has multiple branches but each branch only has one state.
If both you and I push commits to branch "foo" which one is the correct "foo".
I don't think you've thought this through.
Gossip client selects a pool of relays to used based on your follows.. this pool has an adjustable total size and has a 'coverage' score for your follows. It's unlikely that every user is on a unique relay. It will group the queries onto this set of relays for maximum coverage. You can specify the total following feed pool size and also number of relays per follow.
I understand that web clients have headaches using lots of websockets. This could be part of the issue? nostr:npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnf was saying that force closing a websocket doesn't work in a browser, is that correct?.. This and having poor cache/local db makes it harder to make a well performing web client but not impossible? My native gossip client rotates through a pool of only 15 sockets for 1000+ follows.
I think also maybe nip65 is missing additional fields that could make the calculations easier such as inbox/outbox/read/write/rank (the settings it has in its UI).
I think the whole thing is above and beyond the competence of nostr devs and they should just abandon it.
Decentralized systems are hard.
The apparent simplicity of the current nostr is what appeals to the peasants here.
The next level of decentralized social network will come out of a different corner of the Internet and likely even be called something different entirely.
If there's an authoritative state it has to be centralized somehow.
If there isn't an authoritative state then there has to be a consensus mechanism and I don't see one.