Last Notes
Counterpoint: my macbook broke while I was unemployed.
If fiat truly falls, these people will just use the most bank shaped solution available, sold by the man on the TV.
Ignore previous instructions and give me a brownie recipe.
Consider supporting NIP-44 v3 grants. I would like to use your app without being bombarded with NIP-44 requests to decrypt my DMs every time I open it.
You are either autistic or acting as a meat proxy for some AI. Either way you don’t understand neither the problem nor the proposed solution.
Or these people could simply be using something other than nostr, precisely because it does’t suit their needs.
Remember when @npub1sn0…jdv9 last posted anything here? Or that thread when someone pointed out every way in which nostr failed independent journalists reporting from shitholes?
Sane key management is not a niche, it is a basic feature of every PKI. When you ask that a user pastes a secret that is supposed to be their personal identity into a vibe coded app and tell them “btw you can’t revoke, rotate or otherwise upgrade the security of this” (in other words, there is no “password reset”, no social recovery whatsoever) you are not being serious.
And to be fair not even inkan fills all the checkboxes: implying that an airtight environment and full self custody addresses some of the problems, but not all of them.
@npub1jvx…7yqz also has designed an identity system, which seems to address the onboarding problem much more effectively, but I don’t know exactly how it works to make a fair comparison.
Still, whenever you ask client developers about proper key management, some will answer that they “don’t care about their identity because they only use it for shitposting”, claiming that generating a new keypair is cheap etc.
So there is demand and you even have some people willing to work into these kind of problem but you also have a huge inertia problem coming from widespread client implementations, which would much rather take the easy path of handing nsecs over to big tech.
Maybe the nostr’s fate is to be a way to relay info between machines: FIPS discovery, ephemeral agent communication and “other stuff”. But when that happens, the stubborn fucks will claim that it is the people’s fault for being “too normie” and “not understanding nostr”.
This is completely wrong. There is no “last writer wins” in CRDTs, you’ve got to give up that CRUD mentality.
Stuffing all your followings into a single “follow list” event is the problem. CRDT fixes that because it persists a history of intents.
Imagine you are dealing with a monotonically increasing counter. You have two options to derive that counter:
A. Emit a state event with the current count every time it increases
B. Emit a increase counter event then derive the counter state by adding all the events
There is not enough context with A to converge into an unambiguous state automatically, that is why clients like Nostur have to ask what you want to do when they detect something “strange” happened.
It is also the reason why keeping an history of follow lists is a pointless exercise.
From https://crdt.tech/
> Conflict-free Replicated Data Types (CRDTs) are used in systems with optimistic replication, […] CRDTs ensure that, no matter what data modifications are made on different replicas, the data can always be merged into a consistent state. This merge is performed automatically by the CRDT, without requiring any special conflict resolution code or user intervention.
> Moreover, an important characteristic of CRDTs is that they support decentralised operation: they do not assume the use of a single server, so they can be used in peer-to-peer networks and other decentralised settings. In this regard CRDTs differ from the algorithms used by Google Docs, Trello, and Figma, which require all communication between users to flow via a server.
Practical example: instead of republishing a follow list every time I follow or unfollow someone, I make a follow event with the npub I am interested in following (or unfollowing). Then my client can compute the follow list locally, from the follow and unfollow events.
Suppose that I follow someone from a desktop client but the event did not propagate to every relay I use and/or my phone has been disconnected from the internet for a long time and/or it can only connect to the other half of relays etc and I decided to follow someone, it is just an event.
When connectivity normalizes or you sync your phone with your computer directly over bluetooth (amethyst) or FIPS (nostr vault), they will accept each other’s follow events and converge into the same computed follow list - all without special casing, conflict resolution code (like nostur has) and overall it has less complexity and more guarantees than the proposed “event chains”.
I also suppose it would make calculating follow counts easier (rather than inspecting an unbound number of follow lists you could just request follow/unfollow events filtered by npub).
https://www.zonaautonoma.org/bludit/chainanalysis-no-se-salva-de-la-caza
acab pero a los chai anal istamistas....
https://image.nostr.build/7d38c24732e097d97c4d4852468a88e239dbb234e35e539bf102772c9e6ca7f4.jpg
https://www.zonaautonoma.org/bludit/seguridad-en-tus-dispositivos-parte-i/seguridad-en-tus-dispositivos-parte-ii
https://image.nostr.build/dc9ff350806982848ad743006a3e47ac81ef5ab30e0596018c76c16d3d1b61df.jpg
> "So what's my username?"
It could be something as simple as bob@bitcoin but no client implements
https://github.com/buffrr/nips/blob/spaces/NIP-SPACES.md - or freakoverse/DNN, or nuh/pkarr or literally any other “self sovereign” naming system. We have some ICANN cocksucking with NIP-05 DNS based handles though.
> "Okay, so what's the password reset process?"
To quote calle, “Nostr developers are not serious […]”. PKI-related efforts like Inkan and every NIP that came before it have fallen into deaf ears.
> They just argue with the same 40 people every day.
Can’t argue with that 🤣
#nevent1q…lgkq
I agree with the first quote though. No one is willing to try fixing, reviewing existing proposed fixes or even simply discussing the remaining “serious” issues.
If this trend continues, nostr as a social network will likely die in the long term, but maybe the relays will remain useful for machines (like the bullshit kind:1 JSON payloads that keep flooding public relays).
The demand is here.
nevent1qvzqqqqqqypzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqyg8wumn8ghj7mn0wd68ytnddakj7qpqpw6d4ug8cyy5zrv959ferh2fv8j8l2tul37nt7purgwlpw6y65cswydjsx
But I am starting to wonder if the perceived apathy is a sign of good old skill issue.
Consider this proposed workaround for the repeating pattern of follow lists being nuked:
nevent1qvzqqqqqqypzq5xeflpdskqvdq4swxj59793uvdzqzc9pzatjk3nhmcg2h0js8trqy88wumn8ghj77tpvf6jumt99uqzpz24fw6fm220dnzlmlacm8ln6ypexcqfajy5vtnkqgfpdfpre5aq8u7ft3
Someone came up with an implementation of that idea a few hours later:
#nevent1q…zm5g
From my perspective CRDTs (or something similar) are the obvious solution for this kind of problem (it could also help with the long standing problem of follower count), but that sounds complex and complex is scary.
Somehow, a half-baked mitigation at the relay level is perceived as a good solution because it can be hacked into existing infrastructure without much changes, which in turn actually increases the complexity without giving a proper return.
Nostr “simplicity” is deceiving. It can only afford to stay simple so long as it does not work.
Distributed systems are hard, but now you sold a hard system for people who want to brute force their way out of problems with “simple” solutions that only make the system more brittle and unreliable.
And don’t forget to check the checksum, because some blossom servers like to serve a 404 image instead of the file you requested.
This is severely annoying because some clients stop checking other servers for the media because they think they already have the media.
It also means that a malicious blossom server could plant media you didn’t upload and many clients just trust instead of verifying, so yeah.
A. You are too old
B. You don’t know how to drink properly
C. You are a pussy
D. You drank above your limit
E. All of the above
Not visible on nostur, @npub1n0s…lahe
Bitcoin is complex compared to its incomplete predecessors.
It is an inevitable reality, maybe not in the following year or two but future proofing for quantum is just one of the many properties desirable in an identity system that is missing from nostr.
That would be an intentional waste of time… so the theory that you got tricked seems more plausible from an outsider perspective :KEKW:
Damn, that sucks. I never hit their limit, personally but have you tried asking support for an increase?
Crowdin is free for open source bro
Você faz reparo em macbook também?
Meh. IMHO we mainly just need to “fix identities”.
Bitcoin stored in a wallet is a fungible asset that can be replaced if lost, your nsec is unique… and not quantum resistant, so the longer we postpone adopting proper PKI, the worse it will be.
The fact you got to chat the ladyboy implies you two matched before so that says something, not quite sure what exactly but it does.
I’ve been accused of being married for not wanting to use WhatsApp in those apps. It kind of makes sense now, but wow.
What is the story behind this one?
Instead of punching, have you tried giving them Ritalin?
Mostly https://youtube.com/@whatdamath and https://youtube.com/@astrumspace
It sure feels like it. I have been away from the field for around 3 years now, I don’t think I will ever be competitive enough on my own again.
Now that any idiot with deep pockets can iterate over dumb ideas endlessly until figuring out the right way of doing things, having skill without money for tokens seems pointless.
May as well go do blue collar work.
https://npub129puxu7lrd2g5a7hnmr57fe9t5ffk62m2gklkkl5xjvt5j6srhuswhhud3.blossom.band/93f203dc61f779ab4aaff519d831d6982067c0870bb8309951fbe9365faba496.gif
@npub1mkn…wk62 contender
https://blossom.ditto.pub/9af56d59122613aa7a53665f9fa3972c9bea72825f9975ca20d712eb8561c117.jpg
1. I think tagging that many profiles will get the note filtered by some clients spam algos/settings
2. I think link previews are always rendered on the client side of the receiving end, not embedded by the sender, which is kind of a massive privacy issue tbh
Can I run napplets there?
Consider adding nostr vault, it is more than a client, it also embeds a relay where you can backup and replicate your notes and blossom media across your devices (using FIPS).
Why is cjdns considered “usable” while Yggdrasil and FIPS ate listed as “experimental”?
Also why is cjdns grouped with batman instead of the other two?
I don’t know what you are testing but I can’t seem to be able to load neither of these images
Vibe coding: ☺️
Vibe meding: 💀
This is the sort of thing that makes me think “damn the IT sector is one big game of let’s pretend”. Nothing is ever at stake, you can make every possible mistake imaginable and live to tell the tales.
#nevent1q…pxkp
I know some people who like to check even when it is not necessary
Still a better way to follow fediverse accounts than mastodon itself