Oddbean new post about login | logout Good point. I could change it to something else. But what other way can you do versioning? The root problem that I would like to address is when your profile gets overwritten. What do you do then as a user?
You could probably just forget versioning. If your profile is hosted on a webserver, like on .well-known page, you know it's the latest version. So if your profile is overwritten on some relays by a client, you still can rely on the .well-known version and publish this version. Do I understand correctly?
Ah, I see. That could work. But then it seems it would be a more manual process of overwriting. So each workflow would involve some UX complexity. Good thought, I'll bear it in mind. I'll loosen the git part to a SHOULD for now, as there can be more than one approach.
Normie end users will not set up a well known pointer. This only works if handled automagically (e.g. onboarding app adds well known on behalf of the user).
That's the idea, to have it automagically in the .well-known, but as an opt-in not as a mandatory requirement. There are clients who just absolutely refuse to update profiles, or worse yet wipes out your profile and it drives me nuts. took well over a month for njump to update
Can you tell me which clients give you trouble with profile updates?
Added placeholder: https://github.com/nostrability/nostrability/issues/111
Flockstr, njump, if i find more i will keep u posted
Do you suspect cloudflare/cache?
No, because njump persisted for weeks and flockstr would not update after i edited and pushed.
What app are you changing your profile with? What app are you using yo verify changes?
changed with flockstr, didn't update, still isn't updated changed with primal; it updates changes take a really super long time to propagate on njump
Which app(s) are you using to verify the change went through?
Are you QA King?
😅No. It is not trivial to reproduce about anything in nostr given all the permutations of app interactions - 1,000 nostr apps is approaching half a million app pairs. This is why I ask. If we have this info it becomes possible to debug. In the mid to long run we have @sandwich @Arjen and others working on various angles on CI to where we automate the QA.
I know that. I was just tryin to figure out why you wanted to chase this so hard when its not clear to me some Of these apps are maintained or not
I’m the nostrability product janitor. nostrability repo contains negative interoperability issues like the one you run into. There are many of these. If we dont systematically catalogue, these wont be fixed. If these are not fixed, the average normie big tech user who expects things to “just work” in app, and across apps will drop off. Specifically the “hop” between apps is a user friction point. If the hop friction is too high, users wont bother with using the strength of nostr - many apps, and nostr will recede into obscurity. Now that I write this, there may be perpetually unmaintained apps. Maybe its worthwhile to catalog these to a high friction list to warn devs, and end users of potential for a crap experience.
Per fan’s request.
Fan as in fanquake?
This is a good strategy for public service. But can be difficult If the devs who are targets are not paying attention
I cannot guarantee human action of others, and I have been bringing up to the attention of devs various issues their app is involved with. Thus far, many devs have been receptive and worked together with their counterparties to resolve multi-app bugs, negative UX behaviors. https://image.nostr.build/6941ccc7bd3e54e2c05958756ff1818fd82ae550e8ad36dda5975cde9453cf0f.jpg https://image.nostr.build/a953542b1f42f250d8e3b0f354e8f3f0fe69d50b5f1ad36128f05f2d1835e685.jpg https://image.nostr.build/03c8f9f9ccb3059f8866d2ce779ad444b40430f7fff06dce00574c8bcc4cde6f.jpg
Yes that is because they are full time paid by grants and have lots of free time. Good for them. I am not so if i get spammed, all you will likely get is no response for a long time😅
#yestr
Wikifreedia
njump actually updates now?
It's been slowly updating for a while nostr.at still doesn't
Use the id of the event as a version control. It changes everytime you update your profile
Yes that is I think an ideal way of doing it. Except I would need to write more code and create more tooling to get to a full solution. Using git as an intermediate step (which I've now made optional), it is easier to prototype, and let the user trying, work on the UX etc. A next version could remove the git dependency all together.
