Tools > Options
Or you can install them manually
https://joplinapp.org/help/apps/plugins#installing-a-plugin


A service is an option (it supports sync), but we don't need it. The plugin could just REQ all my reactions, filter them and do the fetch/backup.


Maybe a sort of read-later, you react with specific emoji and the note, *with all the assets*, is backuped up in Joplin.
For me this would be extremely useful.


Are you on mobile? Plugins unlucky are not supported yet.
https://discourse.joplinapp.org/t/plan-for-plugins-in-mobile/20276


This.
For collaborative I would start simple, sharing with read/write permission (and a proper locking mode). Real-time multi editing is complex and overrated, seeing the other cursor and live updates in read mode is enough, imho.


I never look at it before.
I see they have an API and all is build in JS, so it should be quite easy for our NDK army.

https://joplinapp.org/help/api/get_started/plugins


Astonishing!


This is not a photograph! It’s my PENCIL DRAWING I would love to share with you.
Took me over 300 hours to finish.

Title: Her self made braids.
Medium: Charcoal and graphite on archival paper
Size: 30 x 41 inches

Much love ❤ https://image.nostr.build/f7f4ced4d6e8cec8f1d46c4e65aece7e1015dbb75c5ab541a3be9b0919f42bcd.jpg https://image.nostr.build/32cc19f533ed6cf8ed6b26fd20ee3dc82563537562777906e0cd3322236ac792.jpg https://image.nostr.build/7d846a825b631319c782fd374d9bcc8f334e2b5e7f04dbf87db408a552cfe31b.jpg https://image.nostr.build/d80a14f915a25a460ec706652db9ed5a410a1a2211ee3d2d80d530d83e8d0eed.jpg


Gem software


Oh, and as I pointed out in my original note, a central point is the registration process. You ask for a NIP-05 and usually show a fictional user@host example, the user could think to use his Gmail. We should at least remove the example and add an informative contextual help.
And if he however try to put it, return a well crafted message that points out the matter.


I definitively agree that changing the separator is probably a mess, and that we can anyway capture the email at the end.
The main problem is in fact when the address is not contestualized, think about an adv. Or when I have to input an email address or a nip-05 for the same user, and they are slightly different.
We need at least a fallback for email, e.g. a forwarder.


I fell the problem.
But the double @ is confusing, imho.
If we have to stick with @, let's capture the user@host syntax.

I was talking about this matter here:

nostr:nevent1qqsy282x04w20mcs2h2jd7eeltxj23r54enxwrhhc335rmcnafwe5qqppamhxue69uhkummnw3ezumt0d5pzq77777lz9hvwt86xqrsyf2jn588ewk5aclf8mavr80rhmduy5kq9qvzqqqqqqyef2x9e


I was thinking the same


Magic, of course


Source: https://signal.org/blog/signal-is-expensive/


"fully $6 million annually, goes to telecom firms to pay for the SMS text messages Signal uses to send registration codes to verify new Signal accounts’ phone numbers,"

It's the 15% off the total costs!
Nostr will save some money on this :)

https://www.wired.com/story/signal-operating-costs/


I will investigate, thanks for the hint!


It is an interesting use case, but as I can see, the Podcasting 2.0 format is quite different and has (obviously) specific fields. It could be interesting for something like https://zap.stream
Btw, I just moved from RSS to Atom, because it seems more supported by the classic feed readers.


Several clients, such as Gossip, Amethyst, Nostur, Lume, alredy use njump.ne for web sharing.
If your app doesn't support it yet, ask them :)


Njump's CEO has spoken, done!


I don't know, you could inquiry the service owner.
I suspect a possible problem with the html escaping, it's not fully spec compliant, I will check.


I would replace the 1 with "Spend Bitcoin instead of just showing you have them"


A nip-05 profile url, like

https://njump.me/dtonon.com

Or a npub one

https://njump.me/npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk

Or a relay

https://njump.me/r/relay.nostr.band

If you feed reader does not auto discover the rss, add ".rss" to the npub or the relay versions:

https://njump.me/npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk.rss

https://njump.me/r/relay.nostr.band.rss


It also shows inline the parent note and any mentions, to offer a more pleasant reading experience:
https://image.nostr.build/ec6ba3ebbdea9d066544b9213f8243658e5a492c04ad9b6bb54d45611934cecf.png


Njump now has RSS support!
It works for profiles and relays, just smash the URL in your feed reader, and you are ready to go.

Why?
It is an additional jump-in channel, for example you can use it as a trojan horse to nostr-pill your old nerdy colleague.
Or you can pick it up as a temporary tool to curate some personal feeds, while waiting for your preferred client to implement lists and a good relay-centric view.
Maybe more creative uses?

https://image.nostr.build/23f3457f201ea7fa262cad20d758737c3f30f7eb6dc4b9bbb39bf7c13384c6f1.jpg


You should use njump.me
:P


A standardized signups component could help apps that put low effort on this step, but I don't know how is possible without a webview.
However this could not be a rule, it would kill creativity and personalization on new solutions.

An onboarding app with a good educational support can work well for non tech users. And it implicitly and practically shows the concept of an open ecosystem. A lot of users are fashinated when they see they can move from app to app with the same account, having a continuous experience.


This. Would be awesome.


Sad, but probably true.


Because on a PC any program can inspect the clipboard and steal data, it is a classic and quite danger attack vector.
Downloading a file is (slightly) more secure because is not so usual that a malware scans realtime the full disk, and in some PC you can also set permissions by folder.


Great review and nice design!

I would add:

* The nsec generation is a needed and crucial function (I was thinking to add it to nos2x), I would add some informations about what it is and how to keep it secure;

* The possibility to download the nsec in a txt would be nice, and more secure that copy it to the clipboard;

* If there are no profiles show immediatly the form with a prefilled nsec, instead of a empty panel;


I share the pain over the lack of full text, but we can't blame the site owner for wanting the content to be cosumed as it has "designed". Then there are the adv incentives...


Btw this is not spam!

https://image.nostr.build/a27d39ec5c04e4a13ca81465b3947f4ac0d20198e858fe20bc5bcdd7b6008cda.png

I would not remove the message, maybe a setting to enforce the minimum you want receive?


Spammers are clever haha

https://image.nostr.build/11deefee0650f6b780d6cdc07db0c582f2abdd2dafe0455642bfc0c957c82484.png


Would be really nice.
But they think we are stupid.


Offer them a coffee


Do you use RSS?


A notifications micro app with background permission (aka Nostr Notification Service) + standardized deeplinks.
Is this a viable solution?

nostr:nevent1qqsv6p7uxlawjhw3cgpt6er25pcungt2wvqhf7huxltuuec0fcq3hssppamhxue69uhkummnw3ezumt0d5pzq77777lz9hvwt86xqrsyf2jn588ewk5aclf8mavr80rhmduy5kq9qvzqqqqqqyuqf3zm


The problem are the multiple background tasks (one per app), usually not specific and so quite resources hungry.
Check this: https://grapheneos.org/faq#notifications


A little surprised by the vote numbers, I would have expected more than 2 clowns. Anyway happy.


It would not be a problem if it did his work in the first stage.
Pairing it with a signer is a nice option, in fact I thought that Amber by nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 can be a nice fit, it would only need a proper UI/UX redesign.
Or embedding nesecbunker (idea by nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn) using a reverse proxy like ngrok.


Fascinating


I like it, great idea!
You could propose in the homepage some preloaded profiles to choose from.

If clients supported a standardized deeplink API, it would be possible at the end of the wizard to pass all the account details, minus the nsec that would be generated in the app.
So onboarding would be: download the nostr xxxxxx app and click on this link.


It's an onboarding app that express the concept "you own your identity". The contacts are only a side utility.


I suppose your app will do much more :)


We need a native, cross-platform micro-app that offers account creation (nsec generation), teaches best practices on key security, allows profile (metadata) management, and perhaps permits historical backup of metadata and contact list.
Just that.

Does this already exist?


Really nice!


It is exactly the use case I'm thinking about


I agree that in this context we need to offer a strong and simple call to action.

Maybe a web client could be an accessible and frictionless option for a first read-only dive in Nostr?

I will think more about this.

Thanks again for your work!


I love the "Use other Nostr clients" attitude!


Your videos are great and this is a really interesting experiment!

For a small budget campaign, since the videos are in english, I would set this language as filter to avoid wasting impressions in low conversion segments.

The landing page is a critical point, plebstr.com is good but it is just one app, and not open source (right?); we would need a captivating but simple landing page that could offer both a direct conversion goal (download an app, use a web client) and more generic informations for different kind of users (developers, content creators, business, etc). I cannot think of any resource that can fully meet these requirements; a good prototype might be https://getnostr.xyz.

Ideally the landing page should include the video itself and propose an easy way to share it outside the fb/instagram garden.


Great 🚀


🚨 Today I'm launching Ontolo. 🚀

Ontolo is a super simple micro-app that will hopefully entice everyone spend a bit of time labeling other Nostr events. NIP-32, if you're not familiar, allows anyone to label/review/comment on any nostr post. It's an insanely powerful concept (thanks nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, who wrote the NIP), but it's still pretty underused in clients.

Why would you want to have labeled events?

1. Discovery: Labeled events can be used directly by social clients–like nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 or nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg when trying to suggest content that users might like.
2. Training data: We're at the gates of the era of AI. Classification algorithms and machine learning have been pretty good to classifying content but with a training dataset they can become WAAAAAY better. Hopefully, labels in Nostr will become a public good that all clients can lean on to create their own AI models for discovery, onboarding, and a hundred other things I've not thought of.

This is an experiment, like all of them, so please hit me with your feedback. Expect more fun social features soon. 🫂 LFG!

Thanks to everyone who helped me think through this over the last few days, from Tokyo until now.

🫂 nostr:npub1t3ggcd843pnwcu6p4tcsesd02t5jx2aelpvusypu5hk0925nhauqjjl5g4 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1cd0l3s6qgj0s6690rtkys39mgj5upwxpm4856nhmce0pyqu6xj9qh7xlvx nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w

https://www.ontolo.social


Too complex to type, unfortunately


The "async-microblogging communities" use case is interesting, works well also for magazines.


nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h this might interest you


It's really fascinating how a novel vision can open new energies and transform in better consolidated project and business.
Good luck!

PS: The three main product images in the homepage are linked to non https sub-domains, this prompt a nasty alert.


👀

nostr:nevent1qqsdv3gwhvepseuwy48s899yhs9td9kmvqgxpwljjaetmhugeudws7cpz3mhxue69uhkummnw3ezummcw3ezuer9wcpzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqvzqqqqqqy2m055y


The content should be the context, primary.

But I agree that it can be improved, at least to trigger some curiosity in the user.

Maybe the top-left "What is Nostr" is too conceptually distant for newcomers, we can add something like

"Do you know that what you are reading is on Nostr, a decentralized network? Read more"

that when clicked briefly explain the background context (this stuff is a note on Nostr, that can be viewed choosing from different apps, blabla, read more about the nostr protocol here).


Error page added and /<hex-id> fallback supported


Thanks for the hint Petri, indeed we can support the event id from the homepage too.
Currently you can load it with njump.me/e/<event-id>

Proper error handling is on my roadmap!


Thanks Neil for mentioning me in the discussion.
As I already told you privately, I like the details grid layout, and the "What..?" hints are definitely needed.
I'm not convinced about the dropdown, as explained in my other note.


I know that Njump has some technical points, but they are largely intentional; in fact, if one of the goals is to let the user jump to a complete Nostr experience, there are other goals as well, such as educating (perhaps even subliminally) about a new paradigm.
This includes showing, even if only in passing, some "strange" but necessary concepts such as public key, relays, and having multiple apps to choose from.
I am 100% in favor of a fluid UX, but I don't think babysitting users too much is the way to go; we need to leverage some awareness to promote a more informed use of technology. How is a continuous work in progress, with the necessary trial and error.

On the UX side: granted that hiding the main call to action below a dropdown, requiring 2 clicks (hover brings accessibility problems) where there is plenty of space doesn't seem the inevitable choice, we are talking just about the desktop view here, forgetting than about ~80% users use a smartphone :) And there the dropdown is present, for obvious reasons.

However thank you (and Niel) for the suggestions, I will take them into consideration; there are definitely some elements that can be improved, such as labeling, the date visualization, adding contestual helps, and the localization, of course.


The relay is the mailing list.


I'm sorry, we are not using any design sketches.
If you have any suggestions feel free to share them by opening an issue on github. Thanks!


> titel font smaller so it doesnt break line

You cannot know how long the title will be, and currently it's hard to guess an average, it could always wrap. So better give him more visibility for now, and then we will adapt the size. Instead the Live badge will probably be moved elsewhere.

> put the relay 'seen on' and 'author npub' info under 'show more details' toggle (it already shows on top under NoGood)

We want to surface, not hidden, the Nostr key points (Public key, Relays, etc). For this reason are outside the "details". However they are at the bottom, so they should not harm.

> 'open in your native client' to 'open in app'

Make sense! There are some news in progress on this front.

Thanks for the suggestions!


Twitter preview is nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 territory.

The brand is already present in the textual part, but a very small icon on the corner could make sense, since a lot of times people grab screenshot (like in your note) and so there is an hint of the source.


What a coincidence! Thanks 🔥


Happy birthday Vitor!

This is my present for you 😂

nostr:nevent1qqsqqqqqgt8t5ca08t4dvvc96zv0tkxz6eny966fxgfgrm6jh7k9qksprpmhxue69uhhyetvv9ujumn0wd68yct5dyhxxmmdqgs8hhhhhc3dmrje73squpz255ape7t448w86f7ltqemca7m0p99spgrqsqqqqqp4kec7l


Njump now supports Live Events (kind:30311) and Live Chat Messages (kind:1311).

https://image.nostr.build/ed40d904c9d75b3b1f04e5d80684aabadff8f4b2282d4bd503a1db543d34a983.jpg

For a live example, check nostr:npub12hcytyr8fumy3axde8wgeced523gyp6v6zczqktwuqeaztfc2xzsz3rdp4 radio:
https://njump.me/naddr1qq9rzd3c8qenzv34xgesygz47pzeqe60xey0fnwfmjxwxtdz52pqwnxskqs9jmhqx0gj6wz3s5psgqqqwenslj8h0y


Take a look to backblaze.com for low cost S3 compatible storage


Julian has been granted honorary citizenship by the city of Naples. This Thursday and Friday I will be there for the celebrations. #FreeAssange https://image.nostr.build/0a72a93a42c0df4d0133ec9abbac70e04e3d137874e8753c3b36fccded3ec3fd.jpg https://image.nostr.build/6d8896477acb2d5c277cf4de17836fba90098f01e4f1cffbbd7b955500abcee2.jpg


Yessongs


I love this attitude.
Anon, please ping me if I lose it sometimes.

nostr:nevent1qqszhallqkmn7yvs9420w50tsl0hf0hnq6sehfxmxhds48ufxxqf37cppamhxue69uhkummnw3ezumt0d5pzqmjxss3dld622uu8q25gywum9qtg4w4cv4064jmg20xsac2aam5nqvzqqqqqqy6t9trx


I knew it would end this way, capture the @ haha
Okay!


Let's see now what happens to my cheap server if everyone starts adding njump.me to the relay list :D

nostr:nevent1qqsf3995kh94zekj8m5gnxjp288sce4wcq9auyqes2snhr5vawtjm7gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsc6rvmk


You are right, the 'at' paradigm is present elsewhere, and it is always connected to the fact that the user is included, with his data, in that domain.tld system.
But Nostr is decentralized, the user identity and data are disconnected from the NIP-05 domain, this is just a proxy to the npub and some additional informations. Actually, I can have more NIP-05 too.

I don't know, I understand we are exiting a comfort zone, but I think it's worth thinking about now.


Not exactly an easy combination to type :)


Right, more chaos.


Are you describing njump.me ? :)


Nice, but qwerty USA keyboard doesn't have it.


'at' makes sense, in fact it has been a great pick for the email protocol.

The problem is actually the "multiple uses" with completely different goals. Try to explain to a casual user that your are giving him an email that does not work as an email, paired with a 65 chars password that cannot change... panic.

Should a Nostr identifier suffers this bootstrap weight? Or is better to start telling a new story with new rules?

I suppose that for this reason someone (maybe Alby?) started to propose to prefix the LN addresses with the emoji ⚡, to mitigate the problem and make them recognizable, by humans and programmatically.


I agree that the hashtag is not optimal, but unluckly the keyboard ascii subset is limited, and we need a characters easy to type.
Maybe with the user prefix the perception is different.
The alternative is a double char, e.g.
user!!domain.tld


BRIEF OUTLINE OF THE GRAPHENEOS FEATURE ROADMAP

Take a look... 👀

In the near future, we plan to ship support for a per-app toggle for memory tagging, a per-app toggle for ptrace replacing the global one, duress PIN/password and a toggle for enabling Android Auto by granting a list of special privileges which can be reduced via shims over time.

We're also working on various other small features and initial work on some longer term projects including App Communication Scopes. In order to work on more at the same time, we need more developers, and we're currently moving forward with hiring additional full time developers.

This is a preview of App Communication Scopes from an incomplete proof of concept we made for a previous version. The goal is to provide the ability to disable communication with user installed apps within a profile with the ability to enable it on a case-by-case basis instead.

nostr:nevent1qqsghaz2c6u5e223fplp9l99cfrc3uhmejn55pasxescc278y3vmmespr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qgsyxcm6xydptuwz2w6avpmc4d65ftrrnwywz688yf9fqr22gy5rrqcrqsqqqpp8mslepx

GrapheneOS already provides Contact Scopes and Storage Scopes as alternatives to granting apps contacts and media/storage permissions where apps will work without access to any of the user's data and the user grants it case-by-case. We plan to provide more features like these.


I suppose NIP-05 syntax has been derived from LN addresses. I don't know if choosing an email like format has been the best idea (in both cases) because it's easily recognizable, but the goal is completely different and this can create a lot of troubles in the UX.

Why not simply change the separator and create a new and unique Nostr address?

user#domain.tld

If I see a @ linked address on a web page I expect to click it to open my email client. If I found a # linked  address I know it will open my Nostr DM micro app to the user chat, or will fallback to the user profile.
In fact it can actually be a landing page pointer too; root domains can be ##domain.tld

Nostr apps that extensively use NIP-05, like the just proposed "shared login" by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft could improve the communication and avoid a lot of confusion.
Probably we can save newcomers from silly frustrations, e.g. "why I cannot login in Coracle with my Gmail?!", and perhaps prevent some security related problems too.

Maybe it can also help to spread the protocol, becoming a neutral brand in business cards and advertising.

Make sense?
Any cons?

#nostrdesign


OAuth via nostr using nbunker? Nice.
Do you envision it for business contexts or for casual users too?


I like how you mixed vertical and horizontal scrolling!

#nostrdesign


Thanks! Fixed.


Ops!
We just did an heavy css refactor, something broke.
Can you share the viewport resolution, please?


I think VPN is only useful to obfuscate, given the shared ip, against large corporations and adv networks that collect data. In that sense they can help privacy. For any other use it is a matter of trust VS your IP, and Tor of course is the real solution.


Always ahead of the curve, thanks.


Nostr for young minds

nostr:nevent1qqsfkydp7cqcft9lvwvarflmrxfhrdj4jxvpjs6sq6k5xjt6g4f6vjgl0splm


nostr:npub1hlq93jdtkfg29a8s7fqzzzh82q3pkc20rxucwt4geh6e56wk3y2qxdz5wg I'm doing a couple of more tests, tagging also myself @nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk ending with a space, without hitting enter


Absolutely :)


Thank you for the precious energy you daily give to a better world 🫂


PS: Njump now supports kind:1063


Works great!
Testing in production is the way 😀🤙


The fact that we have a thread full of both VJL*** and lq1*** addresses maybe points out that there is an UX problem somewhere to consider. It is confusing.

Intuitively I would have bet on "lq1", but with Green Wallet I got a VJL:

VJLJeZsckWbyXwMNWMAzNSQt3nJfF3SiSZYui9rb48mgSg9EBzrTJ7RCsqVCexHZLAKH1EmqyhYc7MhQ

I cannot find any information to argue whether it is "valid". nostr:npub1jg552aulj07skd6e7y2hu0vl5g8nl5jvfw8jhn6jpjk0vjd0waksvl6n8n any explanation, please?

nostr:nevent1qqsyehq365dx9qne8paryjjlgq4987hm2j8ukwvu8za29ukv0u9v5wcppamhxue69uhkummnw3ezumt0d5pzpy3fg4melylapvm4nug40c7elgs08lfycju09084yr9v7ey67amdqvzqqqqqqyz9xkxu


HN is great, especially for non-software related things.


Next time!


Remembering Japan, circa 2012.
What an amazing country.
Enjoy #nostrasia, I'm a little jealous!

https://image.nostr.build/b7f84f1fff518428e34e1beb31ba48f4ab81aae8f7567443c2af73318821eb3e.jpg

https://image.nostr.build/3c1ee399b8a040f229c88a5cc41bdbde8825ab70e7614bf5b3a60f02ce7af320.jpg

https://image.nostr.build/3faf9c5c3c266d1e68913a6d1927b8cb6a1e6f49f683908f9578c67ce6e0de07.jpg


Yes


It seems there is a glitch. When I load the page I see my note (kind:1) that textually refers to the nevent and other 2 notes (kind:1) that mention the nevent. If I click something and then hit back I can see on the top also the original and correct event (kind:1063) by lukeonchain.


Next year in many countries it will be able to obtain a driver's license, imagine the speed with which it will move...

nostr:nevent1qqsq0rqrgx0w6ehf5h88erm6cm5ru22jkcq824up436a4x2sykdch7spp4mhxue69uhkummn9ekx7mqzyzprg8ug9dh2hnft5lc7ly92m9su7p6279deaaz2p8ua928ml0n2yqcyqqqqqqgnrmk99


Nostter doesn't seem to correctly show kinds 1063, e.g.
https://nostter.vercel.app/nevent1qqsyuk8ldy0wltex6x58a4uccg6yxkex587fh70ejng2q5cauenlnpq0ut44h

For comparison:
https://coracle.social/nevent1qqsyuk8ldy0wltex6x58a4uccg6yxkex587fh70ejng2q5cauenlnpq0ut44h


Instead of generic clients that happen to support NIP-94 we need clients that specialize in NIP-94 and use that for filesharing networks or related things.


Which clients have a good NIP-94 (Metadata File) support and are able to show the file via deeplink?
So far I have found only Coracle and Snort (which, however, shows an alert message).


Thanks for the suggestion, I will look into this


Good!


Wait to sleep in a capsule hotel


Was a thing before too. As others said makes are first of all for courtesy.
Then if I'm not wrong, they are also used to keep the skin white and clean, protecting from sun and smog.


Can you check how njump.me check on iMessage, please?


Njump.me is the way.

https://njump.me/community@blink.sv


Yes.
I love OBW for the Hosted Channels. This sort of custodial entry points are really great to permit an easy onboarding, and then invite the user to switch full custodial, without move to (and learn) a new wallet.


Thanks tanel!

I know that "X replies" / "Reply" buttons seems a bit strage / repetitive, but I never felt right the single reply icon with next the replies number that fires the compose window (Twitter introduced it), I would expect to see the replies clicking it; now clients that use this patterne ask you to click elsewhere in the note, minus the reply counter, to view the replies; I feel this counter intuitive. And it also creates some repercussions, e.g. weird interactions with links or image-only posts, difficulty to select/copy the text, etc.
So I'm experimenting something different, idk if can be wrong, but doesn't seem too bad. It is a work in progress.

There is also an "incentive" consideration to take in account: do we prefer if the user to read the replies before posting, to enter the discussion in a more consciously? If so, the reply button should be moved inside the thread.


I planned to orange pill a business with Blink, even if custodial it has a nice set of tools, first of all the sharable web POS, really useful to let the cashier receive in a easy way, without any control on the funds. The only con is the stablesats addition :|
Do you have any other suggestion for this specific use case?


I thought about this option, I'm worried this would promote short, low effort notes. But I planned something similar for the replies.


It is a good option!
I would like to try a bottom navigation with fewer elements, fewer notifications, and a strong incentive to *produce* content, thus the central Post button.


Toward multi feeds. Make sense?
(for reference, it's a 5.8" screen)

https://image.nostr.build/a800ddfccb74bebe1a109d66fba0e6af5c77c89349889dc87d3ee976834751eb.jpg

https://video.nostr.build/e783b5d60f9d9cf78448aa544491c9fa0238740fda3054e85f8b5d702ecc8b26.mp4

#coracle
#nostrdesign


What could be the use?
I see on the horizon one of the criticism that plagued NIP-26: the clients need to merge more keys in the visualization.


Thanks, I will check.


Have you tried to click the bottom right icon with 4 little squares?
Which browser/OS?


Maybe you already know, njump has a new home: https://njump.me

Read the homepage for a quick recap!
It brings a lot of improvements, including sharing modes on Twitter and Telegram (Instant View included), by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6.

If you are developing a client with a condivision notes/profiles feature, consider using njump to facilitate onboarding new users and help Nostr content be more discoverable.


I did more tests with the share API, no way.
The hard coded app prefix schema seems to be the only solution.


Oh sorry, you are talking about web url matching, I was thinking about the nostr: matter


It does, the problem he is pointing out is that you cannot (easily) change the app after you approved the schema association. Same happens on Android.


I just tried and on Android even if you prefix a specific schema, e.g. "myapp:nostr:xxx", using the Web Share API chromium instead of switching immediately offers to open the already "nostr:" registered app, but without giving the option to pick a different one:

https://image.nostr.build/224bdae90cc256719a8cce92163aee060e2c62a9ce3a77ac4f34240d282b609a.jpg

The weird thing is that this happens even if I completely change the schema removing the "nostr" part, it seems it has a cache somewhere.

Instead, using a simple href I got a more logic "Failed to launch "myapp:nostr:xxxxx .... because the schema does not have a registered handler". So registering the apps as nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe did should solve the problem, but we need to hard-code all the possibilities.

I need to do more tests, I have the remote debug broken right now, so I'm doing it by trial and error.
I don't know if IOS acts differently.


How the deep part can help?
Maybe a solution is what nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is proposing, offer apps-specific prefix-protocols.


I just tested the idea, and unfortunately the Web Share API does not solve the problem because after an app registers the protocol, it is not possible to show all the options anymore. It's a shame, but it is a limitation of the OS.


Njump, or any web app, cannot force the opening of a specific app. It can only ask the OS to open a schema (nostr:) passing some parameters. Because of that, there is only a single "Native app" item in the selector.

Maybe we can add the Web Share API: this should open the share drawer and let the user choose from all the apps that registered the nostr: schema. I will experiment.


Go go go! 🤟

nostr:nevent1qqsp5552ax995vhme0numwm4px53ktcyd6h7ms4x90x0tjzwx2445lspz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzqpxfzhdwlm3cx9l6wdzyft8w8y9gy607tqgtyfq7tekaxs7lhmxfqvzqqqqqqyhrvngw


Haha, you are right, "as much as possible" was a bit excessive :)


Great!

But the outbox (aka Gossip) model is by nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c
More at https://mikedilger.com/gossip-model/
Maybe you can ping Mike to add Lume to the "Client support" list.


This is a really nice idea: www.QuestionsForGood.com


I see you are using Wordpress, I'm not used to it but probably you have to create/use a plugin to match the endpoint with the json. Something like this:

```
<?php

function nostr_nip_05_endpoint() {
   register_rest_route('nostr-nip-05/v1', '/.well-known/nostr.json', array(
       'methods'  => 'GET',
       'callback' => 'nostr_nip_05_json',
   ));
}
add_action('rest_api_init', 'nostr_nip_05_endpoint');

function nostr_nip_05_json($request) {
   $json_data = '{
      "names": {
        "_": "5cad82c898ee66013711945d687f7d9549f645a0118467dae2f5e274c598d6ff"
      },
      "relays": {
        "5cad82c898ee66013711945d687f7d9549f645a0118467dae2f5e274c598d6ff": [
          "wss://relay.damus.io",
          "wss://nos.lol",
          "wss://nostr.orangepill.dev"
        ]
      }
    }';
   $data = json_decode($json_data, true);
   return rest_ensure_response($data);
}
```


Interesting point. How?


This is really helpful!

Some time ago, I was hypothesizing something similar, with these areas of action:

- Faked events (security)
- Wrong answers (consistency)
- Random timeouts (network)
- Complex content and interactions (design)

This could be a nice test suite.
nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 feel free to pick up these ideas if they make sense to you.


No need to apologize, we are all brainstorming tougher and learning how to manage this new paradigm :)

I grasped your idea, the fact is that rarely you can precisely know the "correct" nip-05 address in advance, so at the end it's easily spoofable.


Padawan Wallet, a really genius Bitcoin educational project.
Is "thunderbiscuit" here on nostr?

https://github.com/thunderbiscuit/padawan-wallet


While you are digging the code, can you also kindly check why my nip05 fails? :D

https://image.nostr.build/908a829b8ae3a3a965f6703551aff7a76ec81681bae3c02bbc568dd3c96f6323.png

Thanks!
PS: Listr rocks :)


nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc on listr.lol pressing enter to add a new entry to the list, remove all the others; I suspect a unwanted form submssion under the hood.


Have you applied anything from https://nostrdesign.org yet? Or read through any of the content?

I’m curious to know if any of it is useful. Give it to me straight.


Nice! :)

I just released a quick favicon to easily spot njump notes/profiles in the tabs/history:

https://image.nostr.build/b14e087fd795cca171dbc60cc73c59bf2fcb908e5c6598ab4109513d0fc3aa68.jpg

and I was thinking about a derived logo too.
As you can see, currently njump has no illustration-design at all. From my part, I wanted to keep it as neutral and low-profile as possible to follow the "not capture users" ethos; but maybe adding some graphics could make sense to improve communication and so sponsor its usage. Actually an homepage / readme review on this logic is already in progress.

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 opinions?


It already exists: njump.me


Same here, I skipped Amsterdam and Nostrasia because I think the ROI for nostr would have been lower than staying at home and working on the projects I'm contributing to.


Faster is not equal to safer.
To prove this, without checking, tell me which is the correct Snowden NIP-05 in this list :)

snowden@nostrplebs.com
edward.snowden@nostrplebs.com
snowden@nostr-check.com
edward.snowden@nostr-check.com
snowden@getalby.com
snowden@nostrpurple.com
edward.snowden@nostrpurple.com
edward.snowden@getalby.com
@edward-snowden.org

I agree that it is faster to *communicate* that the legitimate account is xxx@zzzz.com, but this ease of use is intrinsically risky. If I register a similar domain changing a character, I can easily pass this check and fool people. Forcing the user to complete a full npub check is boring, but really secure. The following counter list is the best trade-off: watching it, I can immediately spot if a big account has been impersonated.
if we want to keep nostr working, we also need to adapt to a new UX paradigm.


Unluckly the "verified" doesn't help, the fake one could also easily setup a nip-05. The only way to spot the real one without knowing the npub is the web of trust, aka followers list.

nostr:npub1tjkc9jycaenqzdc3j3wkslmaj4ylv3dqzxzx0khz7h38f3vc6mls4ys9w3 but you can use your own domain for nip-05, this would help for sure.


Okay, it's not that obvious yet haha 😉


For me, collapsible threads are very useful for easily scrolling through long discussions. They are especially valuable on mobile where the page is longer and it is not so easy visually follow the thread hierarchy.
In fact I like them so much that a few months ago I implemented them in Gossip, struggling a bit with Rust :)
In the future we will have more users and therefore more complex discussions, their usefulness should increase.

I think the current Coracle user interface can be improved; in the design I'm working on, the switch has been moved to the left, attaching it to the line connecting parents and children, to make the goal obvious, and has been made a little larger to make it easier to click.
But I need to review it further, because this design does not work well with 2nd+ levels.

An important note: to be really useful the collapsible action should work on the parent note too, hiding it. This way you can actually "mute" the whole sub-thread.
For this reason I'm also tempted to move the action to the top of the note, I need to think more about this.

https://image.nostr.build/7bef20b4ee4a0016aade18aafa4ff1afc47e4f92cf161883124d2940eca05228.jpg


Me too ;)


Nip-05 is useful only if it uses a domain that is tied to a well know organization. For all the generic domains it is more a trap for this goal, because it is trivial to register a legitimate-looking address.


Yeah


Hey nostr:npub18tcc00lqpysdsurg567dllzg7jeyr5wcyk2v6w23rx3s3ygyze2qv32nxx, you are following a fake nostr:npub16pnryyfvs7cs4vhufac0e4k5davk7fjh5jxealyzlpznfmsw3z3qsj57fe , the real is this one: nostr:npub1tjkc9jycaenqzdc3j3wkslmaj4ylv3dqzxzx0khz7h38f3vc6mls4ys9w3

Pay attention to impersonators, they are multiplying. They often use the same technique: copy cat profile and reboost some notes of the original profile.
Checking the followers list and search on nostr.band helps to catch them. The npub is always the final source of truth (until it's compromised haha).


I'm excited to announce that thanks to nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f I'll be full time designing for nostr/bitcoin in the coming 12 months!

Need design help? 👉  Feel free to reach out.

On my design list for now:
🟣  Further help with nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft 's avalanche of apps (Highlighter, Vendata, Shipyard, nsecbunker...)
🟣  Getting Nostree.me to UX/UI heaven
🟣  Contribute to Nostrdesign.org (reference designs, icon library, custom vector graphics, ...) #nostrdesign
🟣  Building a nostr UI component library (long term)
🟣  Continue to drop logos that nobody asked for 😉

GM 🤙


Not much to say...  a friend and I corebooted our beloved Thinkpads x220, removing also the Intel Management Engine. We used a Raspberry with a Pomona clip to read/write the bios.

The only drawback is that we couldn't set the initial splash screen, I'm reading that it has to be a jpg with a voodoo color space and a non-progressive setting. This is the handmade bootsplash, ready for the next time:
https://image.nostr.build/f67be7917b661b979cf035f784655b3a56e784a842e1b6f579956f604a424f12.jpg


Sunday Coreboot party.
Free software on free hardware.

https://image.nostr.build/67430d2ef1d983709d3702b3e9d56bf315935d70808257a1ce6915aa677cb7cf.jpg

https://image.nostr.build/0b12b167ba1924b15fa43815ce0ff1785bb6b6589f3349ff054e6e1e15de9223.jpg


Can you elaborate?


Just tested, it's fast!
Thank you for the valuable sharing.


You said it, 20 years ago.
And there weren't any big corporations that captured billions of people on less than 10 platforms, built with the focus to lazy people and put them on a consumption habit.
We are fighting a different beast.
But we need to, so let's go :)


https://www.privacyguides.org/en/basics/vpn-overview/

TLDR:

VPN -> Privacy
Tor -> Anonymity
VPN + Tor -> Troubles


Kagi is testing an AI engine, and it's the first time I've seen an AI output paired with the used sources. This is really useful to verify the context and don't blindly accept the response.

https://image.nostr.build/253039dcfb00fc70fb0fdd03cdff028b651ccbbea56394908d75f3d0f1e91a04.jpg


That's interesting.


100%
Tools are evolving.


Exactly.

And someone is cooking something for them to make this possible, right nostr:npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5h? :)


I also think that the local, togheter with family and individuality, are great starting points.

Maybe "Topical relays"? :)


What nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 says is painfully true.
This means learning and building a new UX paradigm, for a better future. And being patient and kind in its broad adoption.

nostr:nevent1qqsx6mff4qv9mqr9zetkhje0lqvspys5f8ujawfdgcjk8lsr359572qpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qgsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8grqsqqqqqpyytrzg

#nostrdesign


Done!


- Click on the qr code could fire the share option


Nice!
Unsolicited UI/UX suggestions:

- Remove the gray bg from the top text (more space, more contrast, uniformity with the LN address view)

- Move up a bit the content reducing the top passing (optimize space)

- Align "Tap to learn more" to the right, remove the dot, underline it (more visibility)

- Put the Bitcoin address on one line offering a short preview/check version (optimize space, a click could show both full in a modal)

- Add more space before the buttons and between them (increase usability and accessibility)

- Remove the pull effect if all the content is visible without scrolling (improve accessibility)


Announcing NDK 2.0:

🏡 Automatic connection to main user's relays -- no longer a task your app needs to perform
🤫 Automatic flagging of muted events / pubkeys
🪲 Many, many bugfixes and performance enhancements.
🤞 Better NIP-07 (e.g. getalby/nos2x) handling when NDK is called before they are ready to sign.
⚠ Deprecation of user.hexpubkey in favor of user.pubkey

And from earlier today, NDK Svelte components:
🧵 Threading component to make rendering threads as good as it is on Twitter and work as any sensible person would expect.

From now on, all NDK packages will follow the same version number.


Do you have any specific example to share, where more guidelines/docs would really improve the tool?


But it is also true that developers, as individuals, cannot always be teachers. We need more people like nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc and nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 focused on creating good informative content.


Absolutely agree.


How does it works?


We need tools that promote *creation" over consumption, to win and really rebuild the current social media perspective.
Shipyard by nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft focus on that.

nostr:nevent1qqs0xqm6h0kg9uxu5hvjnnawnu0nkrnlr0wf9rfs4axegsnfxnqkz2cpz9mhxue69uhkummnw3ezuamfdejj7q3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqqqqz28cxcc


That's great! We need tools that promote creation over consumption. Exactly what I was planning to do, but you are too fast haha


I suppose it's a raw solution to integrate your own posts in the timeline, I don't know any client that has this specific preference. At the beginning, profile pages were also nonexistent, so it was a hack to easily find your own content.
But I like your biggest fan hypothesis better :)


Yes, nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk implemented it and it works great. It also provides a numerical preview of the expected network size, interesting data!


Guys, I fixed global

https://v.nostr.build/ZlKP.mov

 Of course, I also made it impossible for new people to find followers for people who use this feature. What should the default be for new users? I'm thinking 1 — enough to keep people safe, but a low enough bar to allow for discoverability.


The world is headed in this direction. Resist now or suffer in tyranny forever.

https://video.nostr.build/ed59c268dca89b8a259c9c667ef23101de94cd212f1379a96f6b139a2f88541b.mp4


The x tag contains the file hash, you don't need the time attestation to spot a remote update.


Sure. My point was made to confirm your view and relax the matter in response to Will observation, not to highlight any specific criticism.
That said, it would be nice to have an "atomic" way to store multimedia notes.


NIP-94 could solve this.


"p2p" triggered.


Users are more inclined to understand that a external link can change, but they hardly can think that this apply to an embedded content:

nostr:nevent1qqswx0yxhlrwvj5a2w60pezkwdh0rnj47nerejz8ev3zrmv74dch4xgpzpmhxue69uhkztnwdaejumr0dshsz9mhwden5te0v96xcctn9ehx7um5wghxcctwvshszyrhwden5te0v5hxummn9ekx7mp0qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcprdmhxue69uhkvet9v3ejumn0wd68ytnzv9hxgtmsd93hxqg7waehxw309anx2etywvhxummnw3ezucnpdejz7ur0wp6kcctjq9n8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99ah8qatzx9erqunnx4cnyemtxpjnxertxdhxccehvah82veh8pjkxdnrdekx2mn3wquxzvmrdf58j7n4xenrs6e4wdnhxdrnwyukzcelvfex7ctyvdshxapaw3e82egp2amhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33wscxu7t8xc6xwdtkwac8yanpx5e8wmrrd46rwentv3erqdmkx4j8ydmnxv6hyct389nnq7r8vvcxkdrcvdek2er2vachvqtxwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tmwwp6kyvtcd3a8wunsdp58sursv4uk5aeswpexcaesv3m8qumd0qexzwr2vsm8j6rwwscrvcmv0qm85anvxpn857nywdnkxefhwucr7cnjdaskgcmpwd6r6arjw4jszrnhwden5te0dehhxtnvdakz7qg7waehxw309ahx7um5wgkhqatz9emk2mrvdaexgetj9ehx2ap0qyv8wumn8ghj7mn0wd68ytnxd46zuamf0ghxy6t69uq3zamnwvaz7tmwdaehgu3wwa5kuef0qyd8wumn8ghj7ur4wfshv6tyvyhxummnw3ezumrpdejz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq32amnwvaz7tmjv4kxz7fwdehhxarj9e3xwtcprfmhxue69uhhyetvv9ujuam9d3kx7unyv4ezumn9wshskn3a78


You are already living the problem with short notes :)


An important and interesting note: what you are worried about is already possible today replacing a image/video linked content, without any formal edit. And it can happens on short notes too. So Damus, like any other clients, is already vulnerable to this sort of "attack".


Yes, I see it.
It's the same problem that exists today with any self hosted blog, of course. Platforms storically solved it disabling or limiting the edit on a short period.

Maybe the solution is to include the revisions and make them accessible at comments' level. So if something happens the user can always reply to himself and point out that the comment was related to a different context, highlighting the shady update.
A real win would be to somehow force every update/event to include *all* the previous revisions, in this way we can also solve the "vanished from relay" problem, but currently we have only the `d` tag, so revisions are not chainable.


Why is it dangerous?


Nostr Design guide update!

- Updated settings page
- Updated sharing page
- Added community reference designs
- Added hashtag reference designs
- Added feed content
- Added threads reference designs
- Updated onboarding with mute list

If you have any requests for anything, please let me know!

#nostrdesign

https://nostrdesign.org/


Really interesting brainstorming by nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn on a possible privacy attack vector on nostr.
Nostr is different and so are the security paradigms, therefore we have to think outside the box to find every possible vulnerability.

nostr:nevent1qqs0xmg7s8xeeq94u7fjrelm7qj503z2trzjyyl0gp0fqfupgm40veqpz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqvzqqqqqqy9djts8


I think that asking when a relay is unknown is an effective strategy, that doesn't ruin the UX.
You can always check the already approved relays first and try to fetch the note from them, this would slow down the loading a bit, but it makes the process completely transparent for a good amount of notes/profiles.


https://njump.me/ links make great Twitter previews: https://cdn.satellite.earth/ce040816a8c0aac50191f4815c8a1101907bb7c19baa4c0135027ccb31538ad2.png


Yes, because it use Open Graph :)


Do they now use API calls instead of daily ftp uploads?


Marketing puns are harder on nostr :D

A kind reminder that "published online" is always potentially forever. Nostr is just more transparent about it.

https://image.nostr.build/9440f405d4cf34155f687b6ea2b0998e554051f2a0084c22515afe7ed6f7bd34.png


Hei nostr:npub1qnm52v9xahnty3e3h9mt3eu0k3y75c05plcsu0vxngcrp38dey0sqwn5hz are you still elaborating my image? :)


They are wonderful.
A friend has had this LP cover tattooed on the back, full size :)


I hit reply just to say that haha


nostr:npub1qnm52v9xahnty3e3h9mt3eu0k3y75c05plcsu0vxngcrp38dey0sqwn5hz a promotional graphic for a Nostr decentralized social app named Gossip, nerdy and retro taste, washed out colors


In the meantime, someone uses all this as an adv:

https://image.nostr.build/e60752237b448daeb95d47d1556f7ec05663cdf402d75bd0428ce77ab0796649.png


Which is the branch to try?


https://asciiflow.com is a gem.

Wouldn't anyone want to fork and make it collaborative in real time, using nostr?
It seems a perfect fit 👀


Good observation
.


NIP-46 is nice and necessary, but it seems to solve a different class of problems, with a different paradigm. It requires a dynamic "signer" who must be online when the event is signed; since a not custodial signer is 99.99% a smartphone application, this means that events cannot be signed if the user's device is offline.
In the example case of sms2nostr, the user would have to configure a VPS with a signer, and obviously this is not feasible for consumer applications.


Pablo, do you have an alert notification on the "nip-26" keyword, right? :))

PS: I'm waiting the nip26.lol sarchastic update ;)


https://github.com/dtonon/sms2nostr
🤣

I need to revamp it somehow; I have the NIP-26 delegation implementation ready by months but one day before presenting it the NIP has been suddenly boycotted by everyone hahaha; so I'm waiting the next delegation nip to udpate it.


Interesting.
Last time I was in China (2019) the use of VPN was the norm, and I was quite surprised by how well they worked, without much interruption! I suspect that the great firewall cannot close them all, would be like chokeing.


This graph really hurts if you think how much time someone has to take away from his family and healthy activities.


Why no VPN?


Ooh, yes! 🤝


A rare red calm.

https://image.nostr.build/70254cb3d56700052fcb88204ffed1a282000e82b0a223c124a809eade4b3a18.jpg


I did some tests zapping myself and you, the behavior is totally random regardless of the cold/resune state.

PS: The zap from the profile should disable the inputs and the button, and show some "in progress" indicator while trying to send the payment; currently, the user doesn't understand what's happening, and he may press the button more times.


Typo 😅
nostr:npub1sfzw0vlez4gxz83hnrgzzvcw22frfrhrdv5yry67k9qee0w7erwsj688hv


It was not online, pushed right now:
https://github.com/dtonon/gossip/tree/feature/sidebar-restyling


Thanks!
But it hasn't been released yet :)
If you are building from source I can share the branch.


The message was related to the inability to fetch https://vitorpamplona.com/.well-known/lnurlp/vitor
I tried again now and it passed, did you received it?
(I'm asking because I just discovered that my Outgoing tab in nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm is empty! So I cannot verify the payment)


I'm reviewing/fixing the #gossip sidebar colors, that have been changed by mistake in a merge somewhere :) In the end I am leaning towards removing the accent color, which seems a little too prominent to some users.
The idea for the future is to allow the user to choose their own personal accent color and perhaps optionally be able to apply it to the sidebar with appropriate brightness.
Opinions?

https://image.nostr.build/401fb621d37eda51321e5c1a5dcbc68cf763d5cb0e8fc272d7a24ab38d81ee3d.png

https://image.nostr.build/7175e8d72110286c37bd170a9c3a3bc99646b5e8f15c829489200107f962d4d0.png

#nostrdesign


And that's okay.


Okay, I just realized that I have more free RAM than disk space.
What a weird time to live.

nostr:nevent1qqsqqqqqz7d4rkj9rr5kk67024ruaq6dvgkd455yqjuac9ylmyygqjcpzpmhxue69uhk2tnwdaejumr0dshsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9uqsuamnwvaz7tmwdaejumr0dshsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcprpmhxue69uhkummnw3ezuendwsh8w6t69e3xj730qyg8wumn8ghj7mn0wd68ytnddakj7qg3waehxw309ahx7um5wgh8w6twv5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qy2hwumn8ghj7un9d3shjtnwdaehgu3wvfnj7qg6waehxw309aex2mrp0yh8wetvd3hhyer9wghxuet59u2fk3pf


A subtle way to get this stupid Photoshop to start without a blank disk reserved:

> # diskutil erasevolume HFS+ 'RAM Disk' `hdiutil attach -nobrowse -nomount ram://26388608`
Started erase on disk4
Unmounting disk
Erasing
Initialized /dev/rdisk4 as a 13 GB case-insensitive HFS Plus volume
Mounting disk
Finished erase on disk4 (RAM Disk)


I was speculating about a key rotation for a security breach, or because the user lost the private key. In these cases you *want* to create a easy way to connect the two accounts and promote the last one as official.

About your idea of using a nip-05 address to login: you could add to the json a new field "encrypted_key" and there store the nsec protected by a password using a widely used algorithm. This way, you can bootstrap your account starting with a new device, just fetching the nip-05 data and decrypting the nsec with a memorized password.


^ nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6


Same if a view your your profile in the mentioned clients.
Checking your last kind:0 I find this today event:
https://njump.me/e/1fac5eae6ad79d9fe6791847a0f76401b10dad15be8be3e77af89c018159e040?details=yes
where the nip-05 is empty.
So Primal and Iris refreshed it correctly. It also vanished on Gossip, after refreshing the metadata.


Weird. Thanks for the test! 🙏


@npub1sfzw0vlez4gxz83hnrgzzvcw22frfrhrdv5yry67k9qee0w7erwsj688hv I received your zap (to the other note), thanks, can I ask you what client/wallet are you using? (feel free to reply via dm if you prefer)


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I received your zap, just zapped back and on Amethyst I'm getting the same error!


Mmh, so the problem happens after retrieving the invoice? Or you pass to WoS the LN address and input the amount there?


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 can you help me debuging a problem with my (experimental) LN address, please?

On Amethyst I got an error fetching the URL but after a second the zap is done (via NWC).
Snort just gives me an error.
Coracle, Gossip creare the invoice without any problems.

https://image.nostr.build/6646af95b1ecc7a660c935407e08dbc4983a8bc3123bb532523d7404ee0b3c96.jpg

https://image.nostr.build/0a33fb2479b0887beb144c534d42d4a743f0788da89dd4e4c6116ebe9df4adaf.jpg


Great, and thanks for the generous zap.
Feel free to ping me for a further review!


On both Amethyst and Coracle I can see your pamela@iris.to address:

https://image.nostr.build/994ff38909dad22b73919afaef278f8275b73b70f2465b41e778b2d0b41cd08a.jpg

Maybe a sync issue? I would be not surprised if clients updates with a different frequency/logic the contact list and the user profile.


Offf, I am doing some experiments with a personal domain, in fact, lately my incoming zaps have dropped haha.
Can I ask you which client/wallet are you using?


No 1 is related to the ability of the client to search an user by nip-05. Because there is not a standard way to query a relay for a nip-05, the client have to to cache them or use an external service.
An user can have multiple valid addresses, but every client should show only the most recent one, querying the metadata (kind:0) event.

About the key rotation: because a nip-05 is a proxy to the pubkey, if you need to trash the old key and spinup a new one, you don't have to update it everywhere. Users that find your nip-05 (e.g. business card) will find always your update account. Users that already follow you will see an invalid nip-05, and they would be alerted.


I think NIP-05 are still useful, even if not mandatory at all:

1) They enable to quick search someone without sharing a long npub.

2) In some cases they are useful to mitigate the troubles of a key's rotation.

3) If associated with a well know domain (ex. company) they can prove the user Identity.

Having a strong control of the address is crucial, of course.


"“Unnecessary noise is the most cruel abuse of care which can be inflicted on either the sick or the well,”

-- Florence Nightingale

https://image.nostr.build/f43a1fc426e72fd0111b8c48d6b3de0febc3ad474d423977ae391556cad215f8.jpg


Sorry, I don't use IOS, but a similar problem happens with nos2x/Alby on Android.
You should solve opening the website with Safari again, give the permission and then switch back to the homescreen app.


Which OS/browser?


Announcing my first nostr client https://nosotros.app

Nosotros.app is a web-based client, the goal is to provide a great experience on mobile (PWA) and to be "almost" on pair with the native clients, but will work great on desktop too.

Nosotros doesn't need permission from anyone (not even from google or apple)

For now the client still readonly, but feel free to enter your npub and check your feed.

All feedback is appreciated (especially from nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk and nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac) and don't forget to add the page to your iOS/Android homescreen.

Pura Vida 🤙 https://video.nostr.build/056d04b0c7e33a6f5fb5767c3181409628a5bfa8da0cd37cfb958e067fc167b9.mov


Sleek. It is clear that you have paid a lot of attention from the beginning to the UX, which is great!

Just a quick feedback after a few minutes of use:

- Don't be worried by empty spaces, use them to strengthen the UI readability. For example, between text and images, around the "post a reply" area, between posts on mobile. Of course, spacing is relative, so you probably also have to reduce it a little in some areas (line-height, after the post top row, before the bottom row), to balance it and give components/areas the sense of a unique element.
And remember that spaces are perceived differently in light and dark modes.

- On mobile, pay attention to the use of the back button; the user expects to go back to the preview view, e.g., when you zoom an image or open the replies.

- The hamburger menu to the left is okay if you let the user open it with a horizontal swipe; otherwise, it is better to put it on the right.

Good work!


What a coincidence, I noted the same thing yesterday!


## Nostree release note
### v.0.1.4.2 Added summary field, improved hashtags and bugfixes, added e.nos.lol relay, njump.me for nostr links, added magnet prefix, minor bugfixes

Before I start I would like to thank nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f again for the opportunity to receive their grant, thanks to this the project can continue to grow in a more sustainable way. 💜

This is a minor update of nostree, and we could say that the most important new feature is the new field for the lists, "summary", with which you can make a brief description of your list, you can see it here for example: https://nostree.me/gzuuus/repos (maximum 120 characters) (thanks nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7 ), also have improved the display of hashtags in the explore section, and has added a hashtags search engine. Also thanks to the pr made by nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk all nostr links will now open using njump (formerly nostr.com). Another new change has been the addition of e.nos.lol relay, and the magnet: prefix for links in lists, yes, now you can share your magnet links too 🧲. On the other hand and as every update some small bugs have been destroyed :)

Finally I would like to talk about what's coming next for nostree. This is the last update in which I add new features until the next phase is completed, developing a design system, from now on I will focus on developing and improving the design of the application, thanks to the prototypes of nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac and nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q, I will also focus on developing the customization of the user pages, this way in the next releases users will have the ability to customize themes for their personal pages, this is very cool, and the truth is very exciting for me to develop. I imagine a kind of mySpace coming back to life with a new spirit and capabilities thanks to nostr.

With nothing more to add, thank you for following the project, I hope these new features and the new ones to come will excite you as much as they do me.

Greetings, love y'all
nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk


Collaborations are good, allow more than the sum of the parts, great!


> first touch the case to make sure you won't make the item the conduit for your discharge.

I always did this, no problems


I like it


The name is absolutely genius.
Great service 🤙


Etiquette, oh good old times.


I was not referring to the underlying technologies, but simply to the emerging need for a decentralized and private communication tool. If nostr is here now, it's quite certain that the previous experiments did not succeed, and for a good reason.


Great work JeffG!


https://retroshare.cc - 2006
Nostr vibes.

From the homepage:

---

# How does it work?

Retroshare allows you to create a network of computers (called nodes). Every user has it's own node. The exact location (the IP-address) of nodes is only known to neighbor nodes. You invite a person to become a neighbor by exchanging your Retroshare certificates with that person.

Links between nodes are authenticated using strong asymmetric keys (PGP format) and encrypted using Perfect Forward Secrecy (OpenSSL implementation of TLS).

On top of the network mesh, Retroshare provides services to securely and anonymously exchange data with other nodes in the network beyond your own friends.


Did they ask you to sit on a comfortable sofa and offer you a glass of champagne before telling you the amount?

Damn...


I like this separation.
Njump was developed with a bit of 1 in mind.
And I'm brainstorming something like 2 for long form content.


Cool!

UX suggestion: as usual I suggest not validating relays by protocol, we are basically using one (wss); if the user doesn't input it, just prepend it.


Fixed.


If there were a camera that captured the energetic and spiritual shape, pics social networks would be a wonderfu and usefull source of truth.

And we would probably see far fewer selfies :P


I will check, thanks for the report!


It's only me or it seems a little slower changing sections with the bottom menu?


GrapheneOS Foundation Transition Clarification Update:

We're continuing to make progress towards moving stewardship of GrapheneOS to the non-profit GrapheneOS Foundation. We'll be replacing our previous announcement with more detailed info on our website. We removed the thread here since it was being misunderstood and misrepresented.

There has been a significant effort to spread fabrications and spin targeting our project members with the clear aim of directing harassment towards them. Our founder stepped down as lead developer due to extreme level of harassment including multiple extreme swatting attacks.

We explained in detail how we were moving forward by transferring responsibilities to the GrapheneOS Foundation and the new lead developer. We explained it would be a long process. We don't understand how what we posted was so widely misinterpreted as someone leaving the project.

We have a team of 6 full time developers that's growing along with people working on the non-profit organization. Nearly all have been involved for many years. We've avoided other project members being targeted with significant harassment by minimizing their public exposure.

Due to the extreme attacks on GrapheneOS, most of our project members aren't comfortable with a public facing role. It's why there are so few interviews with our team, and part of why it's so difficult for us to build up the non-profit since people don't want to become targets.

We have a substantial amount of funding available to the non-profit that's not yet being used because of the difficulty in expanding the team under these adverse conditions. We could have 12 full time developers or more, but we don't because of these attacks on the project.

The way we've protected our team led to increasingly more targeted harassment towards the only person who had a public-facing role. The attacks shifted from technical misinformation to bullying/harassment based on misrepresentations/fabrications referencing the past harassment.


Check https://github.com/penpot/penpot-exporter-figma-plugin
Never used!


This is refueling with energy!


It is the same. In Primal the mentioned note has not been rendered/linked for a regular expression bug.


It is basically a Figma clone (Imitation is the sincerest form of flattery, right?), really well done but with quite few raw points to smooth.
I'm just trying it for some days and the most problematic thing is a not-so good management of the components and their update hierarchy.


This is is an abstract condition, if the app has the proper extension permission the user is virtually always logged in. The question is, what should the app *do* with this power? Asking for resource intensive actions (ex. download a lot of data) or expose the user visibility/actions (set a status, push a config, etc) after an interrupted session would be a nice touch.
Of course we can use the login concept as a general permission switch.

A good and easy solution is to actively and prominently (ex. a modal) ask the user to enable the login status after an expired (X hours) session.


And this is really cool!


Ditto.

nostr:nevent1qqsxh04dtgh5hr0959gzwwtes22crg4fw9n38alu4fd5uq5cv3vtxucppemhxue69uhkummn9ekx7mp0qgsr9cvzwc652r4m83d86ykplrnm9dg5gwdvzzn8ameanlvut35wy3grqsqqqqqp3kdfgj


https://m.youtube.com/watch?v=IVnPotcVkFQ

# Non insegnate ai bambini

Non insegnate ai bambini
Non insegnate la vostra morale
è così stanca e malata
Potrebbe far male
Forse una grave imprudenza
è lasciarli in balia di una falsa coscienza.
Non elogiate il pensiero
Che è sempre più raro
Non indicate per loro
Una via conosciuta
Ma se proprio volete
Insegnate soltanto la magia della vita.
Giro giro tondo cambia il mondo.
Non insegnate ai bambini
Non divulgate illusioni sociali
Non gli riempite il futuro
Di vecchi ideali
L'unica cosa sicura è tenerli lontano
Dalla nostra cultura.
Non esaltate il talento
Che è sempre più spento
Non li avviate al bel canto, al teatro
Alla danza
Ma se proprio volete
Raccontategli il sogno di
Un'antica speranza.
Non insegnate ai bambini
Ma coltivate voi stessi il cuore e la mente
Stategli sempre vicini
Date fiducia all'amore il resto è niente.
Giro giro tondo cambia il mondo.
Giro giro tondo cambia il mondo.


Thanks for the explanation!
Prism should copy/paste it on their website :)


Not from Amethyst, also the related notification is (correctly) muted


The answer: amethyst also hides my own notes. nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqyg8wumn8ghj7mn0wd68ytnhd9hx2qgdwaehxw309ahx7uewd3hkch24sev  maybe a bug?


Testing the new Amethyst keywords filter with this boost madness. Peaceful...
Oh, will I see my own message? 😂

https://image.nostr.build/63f826091f6a4f9e27a2d13237b7329bb1eda87a9bf841e496b8e6ffd6eadd25.jpg


Really excited about https://proxnut.com by nostr:npub1cj6ndx5akfazux7f0vjl4fyx9k0ulf682p437fe03a9ndwqjm0tqj886t6 🤖+🥜


Can anyone who has ChatGPT4 confirm this craziness?

https://video.nostr.build/ca952e471fa28d8bb3468cfb1fb179c60488fda1c4c384073525d4cb76d02937.mp4


Looks cool! 🔥

But I was thinking about a different scenario: a client deployed with a hard configuration that locks a list of relays (family, sport-1, sport-2, church, friends-children, friends-parents, ...) that can "auto discover" which relays show to the user testing the access authentication.
I was also speculating if this config can be managed dynamically, for example, using only one hard-coded "bootstrap relay", write accessible by an admin, where he can post kind:10002 events (NIP-65) to populate and update the relays list.
There could be a mechanism (via giftwrapped messages?) to config the accessibility of public relays.

Of course, the two worlds can work hand in hand. I will explore both by design and share the results with you.


You are a hype killer!


Agreed.
The first paragraph should be, "What is a prism?"


Beautiful reading!
As you and nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspzdmhxue69uhhyetvv9ukzcnvv5hx7un8qyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hs5l62g9  already know, I think that topical/private/paid relays are the right tool to implement communities, at every level.
A "configurable client implementation" (selected relays for single feed, and granular access to feeds) paired with a personal relay is my top wish for Coracle on the functional list, because we could push it to families and so offer a healthy way to introduce young people to digital communication. This format can easily expands to schools, sport groups, church, etc. Raising a new generation of conscientious, privacy and free speech minded people, can really change the society for the better.
I share all your values and goals, so now I'm doubly excited to collaborate to push Coracle forward!


It's your naddr ;) You forgot the "nostr:" prefix in front of it, so many clients don't render it.

nostr:nprofile1qqsph3c2q9yt8uckmgelu0yf7glruudvfluesqn7cuftjpwdynm2gygpzpmhxue69uhkummnw3ezuamfdejsz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgg6dq49  nostr:nprofile1qqsqkyvwgrt08hatk9ljr222v3msru2qmzcx820gflnwfqmyfmwqnjcpz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5tk0hq0  https://njump.me/naddr1qqvhw6r9wfjj66tn94khjttrdaexzcmvv5kkwmmfdensygyhcu9ygdn2v56uz3dnx0uh865xmlwz675emfsccsxxguz6mx8rygpsgqqqw4rs9ch9mg


True.
Testing in bad conditions should be a best practice; unluckily developers are too used to their high specs pc and fast connections.


A wrong note can be more expensive than a zap, indeed :)


Nice to know it is planned! I will propose you an UX for this ;)


Nice feature!


Core i7, very good.


Just learning.


PoW acts on the ID generation, so it can be applied to any events.


It would be nice if clients that support PoW (NIP-13) also used it as a delayed send, letting the user undo it with a ctrl+z.


Running Gossip :)
https://github.com/nostr-protocol/nips/blob/master/13.md


/badbot


Vivaldi is great as a background during coding.


It's true.

nostr:nevent1qqsgcugr9ut0ts248wre7r00thq7uerpv49mklvd2kvuqt9844ktz7cpp4mhxue69uhkummn9ekx7mqzyzqhzjxrdyq42sqmf9zcppclkpty5ha2lw29fqf7722lyurteye4jqcyqqqqqqgpwn7f9


I'm ignoring.
Maybe.


"In a meeting in the mountains"

Make sense.


Build build build 🔥

nostr:nevent1qqs8n3canmwammqq00gc02670qxqkjcf93ec0kgd0szs3fs7yf0drmcpz3mhxue69uhhyetvv9ujumn0wd68ytnzvupzqs9eep0ll6hurjkl3sc2fewgses07mjfwxsdcu3at2m8fd0xrdz3qvzqqqqqqyypd83h


> somewhere cheap

Check Backblaze: S3 compatible, solid and really cheap.


Evacuation procedure: follow EXIT signs to the nearest safe protocol and related platforms.

nostr:nevent1qqsy6k5375ccgqz80jzv2g69ygx79k5x0d3srjkk6007h8c2lscy0ygppemhxue69uhkummn9ekx7mp0qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhss6f4ft


Great name/logo/execution 🤙


Yeah, accounting frictions :/


Got it.


An xpub is all that is needed for payments on the chain. You can export hundreds of address upfront, and so you have your basic raw API at hand in a text file.
The problem is integrating it smoothly with the user billing system. Perhaps you can use something like https://books.libreoffice.org/en/WG71/WG7114-MailMerge.html for a basic automation (but you miss the qrcode goodie).

For LN you can use some service like LNbits, I suppose there are several that expose an API, along with a GUI for the invoicing system.


Yeah. So how can works the *serverveless* p2p envisioned by Vitor? I cannot grasp this.


Fair questions.
The #1 is the elephant in the room, I really cannot understand how this can work.


Snort supports NIP-65 so it should fetch my relay list. I will double check it.


Something nuked the list, now I advertised the list again via Gossip and Coracle shows it correctly. Snort, Amethyst, Primal still show only 3 items.


#amethyst suddenly shows; only 3 of my ~15 relays, anyone else has this problem?


Are there still relays that control the origin header or is this a thing of the past?

/cc nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z


Hahahaha. It is an Amethyst bug. I never understood why the followers count is not cached. It is recalculated from scratch every time I enter my own profile.
Then, in the last few days, I see only 3 relays, while I advertised ~10-15, weird.


Noted! I will talk with the boss :)
Can you kindly share an event for every type so I can start to test them?


What? :)


nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I just discovered that Amethyst supports more accounts! Well, the side menu hides this because it doesn't point out that it is possible to scroll to reach more content!
Here is a quick fix using a gradient and an arrow (that should vanish when the user reach the end of the menu).
I would also move the qr code up near the Profile label, following a principle of proximity.

https://image.nostr.build/26a87b349f3c330f986f6b3380ac91fc95c6aea632309c4e2b718b0f894396fe.jpg

#nostrdesign


No new kinds have been added, the current list is quite essential and focuses on widely supported kinds: 1, 7 and 30023.
What kind do you think we should add next?


Anons tipping me encrypted Bitcoin Ecash nuts via Nostr is truly the peak of my cypherpunk experience so far.


Ahhh, less is more :)))


It is really interesting to understand the average data available around the world, it helps to develop apps that are truly and wordwide accessibile.
May I ask you in which country?
In Italy the best offer (lowcost carrier) is 150GB/month for ~€10.


#japan craftsmanship and love for food are astonishing

https://m.youtube.com/watch?v=Chi8hk1Vqs8


Which customer? How many GBs does your plan have?
Months ago it was a bloodbath with every client; now it's much better.

In extreme situations, turning off image preview helps a lot.


Yes, these guys are crazy!


And this will not help me at all because my nick is 'dtonon' but all know me as 'daniele' because I set this display_name from the beginning! But it is better for nostr. Simplicity is power here.


Sure! :)


Pesto is good everywhere!
Try it on pizza :)


Tell me it is not AI, we need to be surprised by life!


The small joy of the day: finding a booklet of beautiful poems, printed in 150 copies in Kamthandu, Nepal, in '90.
The seller asked me 0,50 euros.

https://image.nostr.build/4ef0a25800fdd61242f41a83dc047d60452d425166296cb7a4d0dbc93f5e06b4.jpg

https://image.nostr.build/76461fe0358d64d7d1448ad57e6e6b181e198c86cfc5b036623d8a476ff16a14.jpg


I wish you a blooming and grateful day 🙏


Something related to the emotional detox, ah! :)


Life is short and precious, act accordingly.
GM ☀💀

https://image.nostr.build/be5c057a6074b077de4725c3356ada136065cbc806007d0ade9315666508430c.jpg


It pulls the precompiled app from the project's official repo/home, usually github. No middleman.


Yes, how?


Where?


I'm late at the party. I agree with the position of  nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6,  nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn, nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj, nostr:npub1qqqqqqyz0la2jjl752yv8h7wgs3v098mh9nztd4nr6gynaef6uqqt0n47m and many others: no new kind for kind-1 edits.

However I like the patch idea, for small edits/addendum. It could be implemented as a simple kind-1 reply with a special tag. This way it would be always visible in the same thread; clients can choose to use it to overwrite the parent and let the user inspecting the history. In this case they should also manage (merge?) replies and reactions.

But to make it usable on every client the patch format should be really simple and understandable in plain text, something like like a quote (>) paradigm. This would also permit to use the edit manually on clients that formerly doesn't support it.

Examples of edit and append:

~the bat is on the table
the cat is on the table

+PS: the original source is xxxxx


Cool.
SlowNostr, we need it.


Are trains bad?


45??
I missed the last 6 releases 😅
Tomorrow I will upgrade my little x220.


Do you really think that software bugs are boring?
https://500mile.email


My first bounty for Lume

I want to bundle Lume as Flatpak, but after few hours research I gave up 😅,  I don't have much knowledge with it. So I made a bounty instead 😂

https://nostrbounties.com/b/naddr1qq9rzd3ex5cnjwpe8ycsygqjvypmlhwgmujkkms2hltlx7tusrwvf65g7lp0slw5zppzpdxktupsgqqqw4rs5pgcdk


> Who should I zap next?

All those who bring value to nostr.
All those who need more value to build a decent life.


Good point. We know that currently the nsec management is critical, because it's the single point of failure of a nostr sovereign digital identity. I hid it in the "register" step, we will see different approaches.

I think that a good and cheap one is converting the nsec to something that the user can easily write down and doesn't seem data garbage (psychology matters), so he is encouraged to do so with care. A BIP39 seed phrase seems a decent solution. Snort already proposes it.
Maybe clients could offer the option to add an additional passphrase too, so the seed can be shared with a semi-trusted party (ex. a family member) for backup.

The nsec can be encrypted locally and the app requires just a password/pin/fingerprint to unlock. Gossip and Lume already do this (the problem is more sensible in the desktop env because apps are not sandboxed). This solution is robust, user friendly and discourages copy/pasting of the nsec (with a well done procedure of key generation and backup I would not neither let the user to retrieve it from the app!).


Oh, I was about to ask you the same thing!


It is improving, great work!
I like very much the new "Enrich your network" version.
I would just explain what "trending" means, from what data this selection is made. A popover on the linked word could be a good UI.
https://image.nostr.build/714344afb33096e700f0c34f3419276bffc685cf8c2f66d01d4fedb43a291d5b.png


The fingerprint is usually a string create with an hash function that guarantees the correctness of the information. Using the first/last 4 chars does *not* do this, of course, because the inner part could differ; in fact it is possible to brute force-forge a npub with the same 4+4 chars.  Because of that, I used the word "fingerprint" in quotes.
So it is only probabilistic, but it is also unlikely that someone would spoof my mom account ;)
Adding a real fingerprint is possible, but we need a trade-off between robustness and ease of use, I don't know if it is worth it.


Searching by names can show duplicates, of course. So a good habit could be to show newcomers how to check the npub; because this is quite long, we can use and usually trust its "fingerprint", for example, the common four starting and ending chars: npubXXXX...ZZZZ.

Me: Mom, which username did you choose?
Mom: Maria, I used a purple cat as an avatar!
Me: Ehm... a lot of Purple-Cat-Marias around, check in your profile, it is npubXXXX...ZZZZ?
Mom: Yes!

Maybe the "fingerprint" idea could be standardized in a NIP and pushed as best practice.


We are all building it, step by step.


This.


I quickly pressed "ok" to stop the siren and so I was unable to read the message. Good, and safe, UX...


Dreaming about a convincing nostr onboarding:

- Ask my mom to use/download a web/desktop client and register.
- Find her by username, asking to confirm the npub.
- Send each other a few DMs.
- Kindly request all you to welcome her with some zaps.
- Show her that she now has 5k sats in her wallet!
- Ask her to download a mobile client, press "share login by qrcode" on the desktop, scan the QR code with the app, done.
- Point out that the 5k sats are shown in the app too.
- Watch her take a walk and buy a coffee from the app.
- Read her note where she thanks all you showing a pic of an espresso.
- Receive a reply to my first DM saying "You are right, nostr is great!".


Lume v1.2.5-beta is released

In this update, I’ve improved onboarding process based on #nostrdesign reviews (thank nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac and nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk) as well as improve nostr wallet connect UX, but it still need more work, I’ll keep working on it.

You can read full changelog here: https://github.com/luminous-devs/lume/releases/tag/v1.2.5

After that, I’ll focus on building flatpak version for Linux users and improve consistent between platform. I’m also explore a way to integrate nsecBunker or alternative, so user don’t need to provide private key to use Lume


Agree. In the end, the important thing is that the message can somehow be read certainly by the recipients. How this can be easily obtained in a typical onboarding, is a point to evaluate.


Zero fee*, simpler/faster transaction, full anonimity.

https://github.com/cashubtc/xcashu

*If the service accepts tokens from another mints it may incur in a LN fee if/when decides to swap them.

nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg correct me if I'm wrong, please


Please read the word "file" with an open mind:

nostr:nevent1qqsqt6jadfdlgap98lxt7mql246q72qahhtqr5en0l8znwdnvz93r7sppemhxue69uhkummn9ekx7mp0qgs9afryspzmk8ljyfj4mhfkumwwmhzrtyxzvzgvfp477w80g5x6t0grqsqqqqqpm60kg7


> Complexity in integrating the protocol into other systems results in centralization of development. The consequence is a limited offer in software resulting in a no longer really open standard that is in the hands of those who facilitate the tools used to speak the protocol.

I have heard this before...


I was thinking the same, haha


A possible workaround:

A) the user buids his gift wrap event
B) the user creates a new DM with recipient the relay and content the A id signed with his real key
C) the user send B and A to the relay
D) the relay decodes B, whitelists the id and so accepts A

Of course this way the relay knows the user.
It is really ugly in this form, but something like this could be a viable solution for paid relays.

The alternative is to pay the relay for each sending (ex. embedding a cashu token in the headers).


Great idea, OAuth sounds perfect for nsecBunker. It would be a nice example of how nostr can be integrated using a standard and easily recognizable flow.


I think your intuition is right.
I would try keeping the same color/icon and adding top-right a little round badge with a "Z".


Super! 👏👏🤙


Attention, a fake Derek Ross is going around!

FAKE: nostr:npub19qharf5037zxxp8dgws7ukcxqjvxt9vq3rf3gqye94ga85jmu2dsvyy3ww

REAL: nostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424


100% true

In fact, there has never been a real need for a decentralized, uncensored blockchain except for sound money: Bitcoin.
Or rather, the need maybe might arise, but it would be too expensive.


Wow
Monochrome is better :)


"For the first time in history, users were allowed to own their social media identities directly"

What?
Hei CEO, is Durov somehow confused or just bought nostr to integrate it in Telegram?

https://image.nostr.build/e4111a107b9c24ed2489c863944fe32321903578139ae04f6681293d4ff8b8c3.jpg


Google is pushing encrypted DMs, it seems a hot topic lately.

https://image.nostr.build/038857775e6e57e6e34f31d3b2ac2a3f51942197f09bf9902ab18bddfcce3c5b.jpg


👀

nostr:nevent1qqst06dfxc9dyjz6ak3ksear39xae5we6sukg95nmt0xv9ykkwavdespremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tczyw0fg


Keep a different shape is ok, but why not leave the marker squares with a different color, as in the debugging session? I think it is really clear and usable this way. Maybe a 50% gray may already be fine.

Have a fast recovery!


Remember: with great power comes great responsibility.


Also Lume by nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 uses them, and it seems they play nice!


BREAKING: @Snowden has agreed to speak at #Nostrasia

join us here: https://tally.so/r/meM1yx


Priorities that come to mind:

- Good onboarding with some instruction on nostr concepts (keys, relays, etc.).
- Consistent sync of the following list
- Custom lists management
- Discoverability tools (search, suggestions by following network, etc)
- Mute lists


In order for nostr to be ready for prime-time with a big influx of users, I think there are a core set of features every client needs that work nearly flawlessly including the interop with other clients.

I would be very interested if somebody was working on a list of such things, so I could make sure my client (gossip) is up to scratch, and help set priorities.

Things I know I still need to do: guided onboarding, key/signer interop, mute list sync (working on now), fixing the @mention UI


I don't often step back and marvel at the big picture, but.... I fucking love nostr! We did it. This rocks.


No, sorry :(


nostr:npub15369wu3wzzar5fclhecyqfv683x69n6nhlg7rxqnsg2dydgxflpq3apswl
Great UI/UX, and they seem quite interested in nostr ;)


And growing...


He said *anonymous*.
Are you really trusting nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 by using his app but not being available to help him with some anonymous data? Really?


This is a false solution that reduces accessibility/usability for everyone that don't know what Alby is, and also promotes single vendor, in my opinion.
Just remove the danger "login with nsec", create a unique "Login with Nostr extension" and below explain what this extension is, why it is important and how to choose/install it.


Ah pinstr.app, I didn't remember this nice UI, cool!


What's this? Details please :)


The automatic SSL provisioning works really well on localhost where usually is a pain to setup hhtps

nostr:nevent1qqsr3pawmym02w8mqhlr9kuelnxaadqx38rhk2xhcp0fe8xmq3v2gqgppemhxue69uhkummn9ekx7mp0qgsgzu2gcd5sz42qrdy5tqy8r7c9vjjl4taeg4yp8meftunsd0ynxkgrqsqqqqqpwys25l


Lume by nostr:npub1zfss807aer0j26mwp2la0ume0jqde3823rmu97ra6sgyyg956e0s6xw445 has an excellent onboarding flow.
Nevertheless, everything can be improved, and this basic UI/UX review is an example of how the login/signup can be a little further optimized.
If you are developing a nostr client, take the opportunity to read it and self-analyze your work. Does your app need any fixes?
Then don't miss the gift nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f is giving you, immediately visit https://opensats.org/nostr and find out #nostrdesign

nostr:nevent1qqsqqqqqf6wq882jj0296jcnhrrv8ev8t9a67v6wc50t0jtayc8wffgpz9mhxue69uhkummnw3ezuamfdejj7q3q0000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsxpqqqqqqzuc59fd


“The answer is found in the fact that there are two types of laws: There are just laws and there are unjust laws. I would be the first to advocate obeying just laws. One has not only a legal but a moral responsibility to obey just laws. Conversely, one has a moral responsibility to disobey unjust laws.”

- MLK Jr.


Got it, good point.
PR in progress to hide/prettyfy the URLs.


Gossip, just turn off images auto fetching in the preferences 💯


The code is the same, it is just https://github.com/nostr-protocol/nips/blob/master/07.md
In fact it also works with nos2x whitout any problem.
It is just a bad communication/UI/UX, easy to fix


The original one by fiatjaf: nos2x


And the EU SEPA (a sort of inverse bank wire where you charge the user account) is a joke too: if the customer account is empty or locked, a dispute is opened and closed in the same instant, the seller lost it and have to pay a chargeback fee of ~$10, plus the Stripe % fee on the amount, and the original transaction is rolled back of course. All this automatically.
This happens also if the customer open manually the dispute.
There isn't any valuation by Stripe.


I agree, I'm also testing it the same way.

The only thing I really don't like is the not standard management of the images, they are sent as events, base64 encoded.


"the true essence"

https://image.nostr.build/f4b8bd9b1cd2a4972e3be13620edfe093c9152f6e8793fad0f8093b4b21fda53.jpg


👀

nostr:nevent1qqsq2cf6lldsa0507pengsv03j5z5kujc9t60da0cp0wgr90sqz9vwgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtc0m56qj

nostr:nevent1qqsy5h9kd7kwnhscstp4pypps7xm2xzsp3zwm38kdwdzkcclg59cyqspzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtchw6w3f


Absolutely agree.
Tangible utilities should be the positive virus that brings all the great censorship-resistant and free-speech weapons of Nostr.

nostr:nevent1qqs8k7lxs6ppnm2eamzkct97tptfcne2r7s6ejctnkqecmdyya7qv8spzdmhxue69uhhyetvv9ujue3h0ghxjme0gffgxr


Brilliant.

nostr:nevent1qqs87hp66q2q6eynpkvgwlftks9qzdajjwpw2twj9me8xx6j53n35vc6el3ek


Lume is growing *fast*

nostr:nevent1qqs20qlgj99dn0dy0m4dfvslxsqdr85arzcukpv56u440379u8fsv2cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsc9lef9


nostr is creating some having a family FOMO in me, and I’m loving it 💜


Already tested ;)


Ok, so "different", not "bullshit".
Btw, it is interesting that you have been using it for months despite thinking the UX is bad.
I thing nostr:npub1exv22uulqnmlluszc4yk92jhs2e5ajcs6mu3t00a6avzjcalj9csm7d828 guys would love to have some feedbacks about any problem you've encountered, it is the only way to improve.
Have a great sunday.


Can you explain, please?


Buongiorno!


This really is the worst. Instagram started the trend with their hideous "log in or else" flow. Then Twitter and reddit went to insanely privacy-hostile API changes instead of simply requiring a proof of work or anon payment. Even some major nostr relays seem to be doing Tor blocking now (damus? Not sure, but I get a ton of errors connecting to certain relays via Tor.)

Platforms have become so fearful of bots/spam/scraping (or rather pretend to be fearful, so as to justify blatantly commercial and anti-social decision-making) that they've totally destroyed the open access model that a functioning freenet depends on.

This is the main reason I want to see "unowned" protocols succeed. Jack has it right: we're at a turning point.

nostr:nevent1qqsd0vg2qvd63qsrlravfujy5ret8pzeke59hxlwhzx4v0n0r0paa3qpzpmhxue69uhkummnw3ezuamfdejsyg8h9rv7decysdvwwzfs7h9xfvyhwuxe38xds6z5lescak5u3gupqcpsgqqqqqqs9pjua5


Here is my #nostrdesign review:
https://github.com/luminous-devs/lume/issues/83

Feel free to ping me to discuss any details!


As requested:
nostr:nevent1qqsrd8ymfcp2sqxpfy8uxta6c7ckwa6syd7vrfgkgsj0ynvzww90usqpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhszxrhwden5te0wfjkccte9ecxcetzwd68ytnrdakj74wykx8

this is a review of the onboarding on [Lume](https://github.com/luminous-devs/lume).

The overall process is excellent, kudos.
It's great that if the app is closed during onboarding, the next time it starts again from the correct step.
I would also add a button on the footer at every step to cancel the procedure; this action should wipe all the saved data, with a confirmation dialog.

## Login flow

![](https://github.com/luminous-devs/lume/assets/89577423/319454bb-4690-466c-b119-921629e23640)

The buttons are too close, adding a little space would improve accessibility and make the UI prettier.
The "Create new key" has low contrast, I would change the background to white or a color.
I would add somewhere a link/button to a resource that explains Nostr in depth.

---

![](https://github.com/luminous-devs/lume/assets/89577423/120065af-829f-442a-8ae6-7b3161c1d077)

I would be more descriptive with the texts: "Import your Nostr key" / "Insert your nostr private key, in nsec or hex format".
The user should be able to go back to the first screen (maybe in the next steps too).

---

![](https://github.com/luminous-devs/lume/assets/89577423/86db886e-7c74-4b84-8897-e23d8f505234)

If the user inserts a formally invalid key, the button label is wrongly set to "Creating.." and the spinner keeps running.
I would use a yellow/orange color for the error message, it is more visible.

---

![](https://github.com/luminous-devs/lume/assets/89577423/5dbd1a32-9ebb-415b-90b8-ad2e69893680)

It's very important in this context to explain the password use and point out that it is not related to the "nostr account". Good!
I would focus the input so the user could immediately type.
When the form is submitted, the button text changes to "Creating..", I would use "Securing your account...".

---

Here I would add (actually integrate, because you have something similar later) a really important step: try to fetch the account relays (NIP-95) and if none are found, optionally let the user insert one or more relays. This helps find the profile and improve the next steps.

---

![](https://github.com/luminous-devs/lume/assets/89577423/bab32736-1721-4488-a3ba-4474b4665845)

![](https://github.com/luminous-devs/lume/assets/89577423/c7c87577-be4d-465a-90fa-ea49bb58e986)

If you don't find any metadata information, I would show a warning: "I'm unable to find any information about this nostr account, please double-check the npub before continuing.".
If a metadata event is found, I would change the title to "Account found!" and I would show the picture / infos (add the bio, ln address, etc) bigger.

![](https://github.com/luminous-devs/lume/assets/89577423/4a8dfa48-3789-43f9-8877-8aaa1f8fcdfb)

Add #nostrdesign ;)

---

![](https://github.com/luminous-devs/lume/assets/89577423/8b9937ae-f90d-45d6-a33d-e1c9e8c274c7)

Here I would show first the user relays fetched previously, then some suggestions: followed relays (like now), and if this selection is empty, a preset of 2/3 well-known relays. It would be nice to let him add new relays too.
I would avoid "Skip using Lume's default relays" without letting the user know what they are.
The user should not be able to go on without selecting at least 1 relay.
The informative note about the relay is perfect, the hover on the link should be a "pointer" (hand).

---

## New account flow

![](https://github.com/luminous-devs/lume/assets/89577423/520423e0-444f-47af-b141-7f44d4c1eb73)

This is a really important step for the newcomers, we need to keep things really clear and secure.
I would update the title in "This is your new Nostr account"  and move the descriptive text below the title; the text should explain why there are two keys (strings) and which one should be saved and kept secret (the nsec of course), while the public one should be saved for convenience but is restorable from the private one. The user has to understand that the keypair does not work like the username/password paradigm, here we have just one private key that rules the account.
It is ok to hide the nsec, but this can create some confusion because the npub is more visibile and the messages (title and button) talk about a "key" without point out which one.
I would show the private key first, hidden but showing the start "nsec" string, with a light yellow background; on the top right of the input put a "Copy key" link.
Below let's show the public key.
Then put the "Download the key" button, white background to improve readability; the user should be able to choose the location.
Then add a checkbox: [  ]  "I confirm I have saved my private key in a secure place".
If the user downloaded the key the checkbox is auto-checked.
Finally, put a simple "Continue" button.

---

For the password step, see the Login flow.

---

![](https://github.com/luminous-devs/lume/assets/89577423/e2e39306-db82-4985-93ce-75c624c75cd8)

I would title this "Personalize your Nostr profile".
At the bottom I would add descriptive text explaining that the profile, including name, can be updated at any time.
The name input should have the focus.
Below the + sign in the banner area add something descriptive, ex: "Add a banner image".
I would size up the profile image (that is more important than the banner one).
Warning: the upload is not working for me.

---

![](https://github.com/luminous-devs/lume/assets/89577423/47504e8b-6d01-4785-83fd-958300951be2)

In the descriptive text I would add that you can search for any contact later.
Add yourself in the first position with the highlight label "Lume developer"; you deserve it, and users are interested in following the developers related to the tools they use. Then also show my account, hahaha.

---

For the tags step, see the Login flow.

---

For the relays step, see the Login flow.

----

## General UI/UX suggestions:

The fonts should be a little bigger to improve readability.
The buttons should be disabled (gray) until the form is filled;
When a button is locked with a spinner it should not have a hover effect;

----

🧡 Are you working on an open-source project that needs some design help? Want to improve the UX of your nostr app?
💜 Post on nostr using #nostrdesign to summon help or reach out to design@opensats.org
🧡 https://opensats.org/blog/announcing-nostr-design


Nerdy #nuts.
Try to use nostr:nprofile1qqsxn2q9vlnek6umcu5z44v42yklpwqy0prpd0kmvg7pytadgg9zvdgpzemhxue69uhky6t5vdhkjmn9wgh8xmmrd9skcqg4waehxw309ajkgetw9ehx7um5wghxcctwvsq3wamnwvaz7tm2d9nkw7t5dakjuerydeejumn9ws04dkhf   to redeem.

https://image.nostr.build/a097e476ef5cfee6210015035d2988e00ca9db0ef31aabcb656ba7d33ba7f246.png

nostr:nevent1qqsgxm238l26t7m662nxt43td4ua6pdk0sar8k3t6s3w5zl5ua2fwksptamhxue69uhkummnw3ezummcw3ezuer9wck8wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wsk8wumn8ghj7un9d3shjtnrw4e8yetwwshxv7tf93mhxue69uhhyetvv9ujuerpd46hxtnfdu4r0s8n

#cashu


This works with a github organization, you can zap every collaborator that has a LN address in the profile: https://github.com/sudonym-btc/zap


Where is this poll? ZBD app?


Level up your Nostr project, don't miss this opportunity 💜🧡

nostr:nevent1qqsrcx2hjv00jwat5lwvhke7xfneegslmup47l4m6ep5veld380wsvcpzpmhxue69uhkummnw3ezumt0d5hsygrcwvu82l7zt4jumy5njn27wufu7smr36xjt85deaw88wp5awz37gpsgqqqqqqs4g603g


I really love and embrace the nature of async communication and a way of life in general.

Today, nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f  announced the thing I was working on for a while (nostrdesign.org). This initiative was made possible only because of them and everyone who contributes to the nostr fund. I also want to thank nostr:npub1dergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsh9xzpc  and nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk  for their assistance! But while this was happening, I was at the beach with my family, enjoying our weekend.

In a corporate world that stresses so much the importance of clear communication and perfect timing this would have been a total disaster. But here, people have long time preference for all sorts of things including their lives. We value freedom, autonomy, you know… LIVING. After all, what is the point of any of this if not to make our lives better somehow?

To me, this was authentic, human, and even funny. It shows that we can all come together in a single place while living totally different lives in different parts of the world. It shows that we are human and can forget about time zone differences - and that is totally fine.

Coincidentally, it gives me many reasons to talk about #nostrdesign and is a great way to raise awareness (perhaps too much 😂). What can I say… marketing! 😈


Already in touch with Reya :)


Ride a bike

https://foundation.mozilla.org/en/blog/privacy-nightmare-on-wheels-every-car-brand-reviewed-by-mozilla-including-ford-volkswagen-and-toyota-flunks-privacy-test/

#privacy