Wait
> h/t nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 for adding blossom to khatru
What did I miss?
Is Blossom now included in Khatru?
People like and talk about rss readers because they have a paradigm and user interface that allow the user to granularly control the information, not the other way around.
The specificities of an RSS feed are basically twofold: to organise the contents of individual sources in a personal hierarchical structure, and to make it possible to distinguish what has already been read from what is still to be read.
This is quite aligned with the ethos of Nostr, so a convergence seems very plausible and necessary.
Unfortunately, Nostr's developers don't much like lists and similar structures, all preferring the approach of a huge, monolithic feed, where the read status is impossible to manage.
They are so adverse to this approach that practically no clients have a dedicated section for the long format in the user profile!
So asking the rss developers to integrate Nostr might be a good plan to bring in some fresh air. This could also encourage more users to use Nostr for blogging.
I received the same email and, damn, the sender is actually Microsoft. Reality poor security management (as usual) from them. But the SPF record exists, so the scammer exploited something else.
I have always used macOS (or whatever it was called before) and owned an iPhone 3/4, but then I switched to Android both because it is more configurable and because I wanted to force myself out the comfort zone of a closed ecosystem. I absolutely do not regret the choice.
Nice, some suggestions:
- Putting "report" after a "follow" CTA seems weird and has little discoverability, I would move it outside
- The follow button in the modal probably works better at the bottom of the screen, fixed; this incentives scrolling the list before confirming the action
- I would display the original name below the nickname; this help tracking renaming errors and changes by the user
- I would add a "revert" icon in the edit form, to reset the name
- For an app named "Zapchat" I would expect to find a prominent zap button in the profile :)
You have to screen the events signed by the key and eventually spot something weird that doesn't belong to you.
Usually the easiest way is to follow yourself.
It depends what the attacker want to do with your key. For example he could just change your lighting address in the profile to forward himself your zaps. You can also use some tools to list all your events, included those that are not notes, but unfortunately it's not easy to detect if an event was signed by someone else,l. You have to take care of your key in advance.
Aurora store is probably riskier that the (sandboxed) Play Store offered by Graphene, used with a Google account created just for that, since it simply add an actor to the supply chain.
Android 15 offers "private space" a good solution to isolate group of apps.
Today is my turn.
nostr:nevent1qqsw05dtjh40jcpe9tths2ehscuqlk5uc9vxnslnwhqnwh5j7spjqmqppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcprfmhxue69uhkuurjdau8jtntwf5hxarpwpekktnvwchs40q5wm
I just watched the video, really cool presentation.
nostr:nprofile1qqsd4dkxqewy8xum47ctpu0ltgxxsfemeewpjkdyzk9ddfcg286s0dsppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq36amnwvaz7tmwdaehgu3wvduhq6r9wfc82mnt9e6x7erp0yhs4deh46 a little bug report: your web site doesn't have http to https redirection enabled, so the user could hit that weird error and just leave.
Probably your browsers cached it so it's not immediate for you spotting it.
Thanks for the suggestion.
It searches just the "display name," ignoring the more important "name" (and probably all other fields). This is, unfortunately, a good example of the state of the search.
The implementation of NIP-50 is usually fine, I think. The main problem is that clients do not use it, and the custom search approaches are rather inaccurate.
My basic test is searching myself by display name (since it's more common), adding a word from the bio; using the name (that on Nostr is not unique, of course), plus an additional keyword should be a basic way to find someone. Example:
nak req --search "daniele gossip" -k 0 wss://......
Results:
relay.nostr.band: found
nostr.wine: found
relay.noswhere.com: error
search.nos.today: zero results
50% success, not exceptional.
Let's see how the search for "daniele gossip" works in some clients:
Coracle: zero results
Nostrudel: found
Snort: found a note, not the profile
Primal: found a note, not the profile
Habla.news: found a note, not the profile
Gossip: zero results
Amethist: zero results
Voyage: zero results
Nostur: zero results
Damus: not found
10% success, disappointing.
Some clients work better with a single world ("daniele"), but it's just a casualty, since a single keyword is often meaningless without a context or a proper sorting.
Weight fields, proximity or fuzzy full text search are still science fiction.
I will do more tests.
Language filtering is nice (even if not standard), but also Ditto fails by basic test:
nostr:nevent1qqsqqqp5ayhuq60jjtwg9x39ewvdw22zmr3nvge6a9204nsrt56ykhqpzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgmwaehxw309a3ksun0de5kxmr99ej8gmmwdahzucm0d5hsh2gz33
Relays don't have to split in multiple queries, they have to implement a good search using weighted fields, proximity and fuzzy. Often the problem is client side, as you can read from my quick test.
Always save the draft and add an auto-delete procedure to purge them with a config (1 days -> never, with default at 1 week).
The best interfacce is no interface, it cannot break, it doesn't need to be explained, it cannot be misused.
PS: In the thread highlight the drafts, for example with a light yellow background, please.
The resulting feed is quite good!
I would appreciate if the feed could push authors who publish less frequently, but have good content (=historical trend), higher. This would really improve discoverability and variety.
nostr:nevent1qqsz5gdtpk3t07wjtu935u3syzpk6qgvsh6aaw6qghskw9arehj75lgpz3mhxue69uhkzmr8duh82arcduhx7mn99uq3gamnwvaz7tmpd3nk7tn4w3ux7tn0dejj7qg5waehxw309askcem09e6hg7r09ehkuef00jwelu
I like this relay-as-a-custom-feed approach. I hope this sort of experiments will force clients to finally embrace single feed browsing, and make it a first-class citizen feature.
nostr:nevent1qqs9qwcy25ac5rn8avzl6mq0na4eqrfv29fxw3nc4y0tuu0a8029nxqpz9mhxue69uhkummnw3ezuamfdejj7q3qutx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4sxpqqqqqqzcu0anh
I like this relay-as-a-custom-feed approach. I hope this sort of experiments will force clients to finally embrace single feed browsing, and make it a first-class citizen feature.
nostr:nevent1qqs9qwcy25ac5rn8avzl6mq0na4eqrfv29fxw3nc4y0tuu0a8029nxqpz9mhxue69uhkummnw3ezuamfdejj7q3qutx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4sxpqqqqqqzcu0anh
I would like to test Strike but it is distributed only by the app store, and anyway it says that the app is not available in my region (it is), what a mess.
nostr:nprofile1qqsvf646uxlreajhhsv9tms9u6w7nuzeedaqty38z69cpwyhv89ufcqpz9mhxue69uhkummnw3ezuamfdejj70v5n7z can we have direct access to the apk? Maybe also using zap.store could be a nice option.
A simple suggestion: build a desktop client.
PCs are a different species than smartphones, they are built to produce things, not just consume them. Therefore they have a more complex, more ductile and therefore more creative environment, which naturally develops skills.
Oddbean new post about login | logout
Notes by dtonon | export
The implementation of NIP-50 is usually fine, I think. The main problem is that clients do not use it, and the custom search approaches are rather inaccurate. My basic test is searching myself by display name (since it's more common), adding a word from the bio; using the name (that on Nostr is not unique, of course), plus an additional keyword should be a basic way to find someone. Example: nak req --search "daniele gossip" -k 0 wss://...... Results: relay.nostr.band: found nostr.wine: found relay.noswhere.com: error search.nos.today: zero results 50% success, not exceptional. Let's see how the search for "daniele gossip" works in some clients: Coracle: zero results Nostrudel: found Snort: found a note, not the profile Primal: found a note, not the profile Habla.news: found a note, not the profile Gossip: zero results Amethist: zero results Voyage: zero results Nostur: zero results Damus: not found 10% success, disappointing. Some clients work better with a single world ("daniele"), but it's just a casualty, since a single keyword is often meaningless without a context or a proper sorting. Weight fields, proximity or fuzzy full text search are still science fiction. I will do more tests.