Why Nostr? What is Njump?
2023-01-27 01:22:41
in reply to

NostReport on Nostr: **THE NOSTR REPORT** 🍆 D-Day🍆 26 January 2023 [773785] Our quote of the day ...

**THE NOSTR REPORT**

🍆 D-Day🍆
26 January 2023
[773785]

Our quote of the day comes from who marked this auspicious day, the day the pr0n bots took over the global feed, as 🍆 D-Day🍆 .

**Headline Nostr News**

***To Markdown*** or not to Markdown
**Markdown maxis** and never Markdowners clash. Does markdown kill the Nostr experience? Carlito helped spark a conversation over markdown use in Nostr
quoting
markdown links not only look ugly in clients that don't support them but at present they also produce broken links in bija =(

Parenthesis are valid chars (if they come after the ?) in urls so my current regex interprets the closing ) as part of the url. I guess I'll try and rework the regex but would be good if clients just stopped using markdown TBH!

***PRO:***
proclaims "Long live markdown."
quoting
I normally write a long, well thought out post in the morning and also in the evening. Both have plenty of markdown.

**Long live markdown.**
CON:
quoting
# PLEASE STOP USING MARKDOWN

![](/your-stuff-looks-like-unreadable-shit-on-saner-clietns-that-do-not-support-this-moronic-language)
wants everyone to stop using MD for good reason. Read his note on protocol bloat here:
quoting
How being "flexible" can bloat a protocol (a somewhat absurd example, but you'll get the idea):

Iimagine some client decides to add support for a variant of nip05 that checks for values at /.well-known/nostr.yaml besides /.well-known/nostr.json. "Why not?", they think, "I like YAML more than JSON, this can't hurt anyone".

Then some user makes a nip05 file in YAML and it will work on that client, they will think their file is good since it works on that client. When the user sees that other clients are not recognizing their YAML file, they will complain to the other client developers: "Hey, your client is broken, it is not supporting my YAML file!".

The developer of the other client, astonished, replies: "Oh, I am sorry, I didn't know that was part of the nip05 spec!"
The user, thinking it is doing a good thing, replies: "I don't know, but it works on this other client here, see?"

Now the other client adds support. The cycle repeats now with more users making YAML files, more and more clients adding YAML support, for fear of providing a client that is incomplete or provides bad user experience.

The end result of this is that now nip05 extra-officially requires support for both JSON and YAML files. Every client must now check for /.well-known/nostr.yaml too besides just /.well-known/nostr.json, because a user's key could be in either of these. A lot of work was wasted for nothing. And now, going forward, any new clients will require the double of work than before to implement.
wants to move "micro-blogging" to purpose-built Nostr clients/relays.
quoting

The best way to prevent markdown on Nostr “micro-blogging” is to channel that demand for longer formatted form to other Nostr clients/relays intended for those purposes.

Like the mailing lists and medium.com or substack replacement.

https://bountsr.org/code/2023/01/25/medium-replacement.html


(Like this, add to the bounty with a pull request)

learns that there are more than 10 emojis that can be used on Nostr🕺🪩💃🏽🦗🎯🍍🐒🥥🍻💅🆒.
Expanding his armamentarium wasn't enough to stop the onslaught of 🐰 porn and 🍆pics that filled the global feed today.

JOINS Nostr
The Queen of macro joins Nostr making the plebs 🤯 lose their minds! Jack gives his customary Nostr welcome. 🫂
quoting

🫂
and reminds us **Don't trust, verify**
quoting
Whether that is Lyn or not… Kinda astonished at how many of you all immediately believed it. Literally no cross referencing facts to verify right now, not even someone to say “yeah that’s her.”
. Lyn did eventually confirm her npub on her 🐦 profile.

**#Nostrica Update**
Nostrica shuttle from SJO to Uvita announced
quoting
There will be shuttles available for #nostrica conference attendees from SJO airport to Uvita. Cost will be $25-50 per person each way. If you would like to share a ride with other Nostriches to/from the Airport, fill out the form below. Please fill this out as soon as your flights are booked, so that the organizers can start planning this. As we get closer to the event, we will share more info on reserving ride spots, etc.


Tendremos transporte disponible para los asistentes a la conferencia #nostrica desde el aeropuerto de SJO a Uvita. El costo será de $25-50 por persona por trayecto. Si desea compartir un viaje con otros Nostricans desde el aeropuerto, rellene el siguiente formulario. Por favor, rellene este formulario tan pronto como sus vuelos estén reservados, para que los organizadores puedan empezar a planificar los viajes. A medida que nos acerquemos al evento, compartiremos más información sobre la reserva de transporte, etc.

https://forms.gle/DRWEm8EkXCUMoHQs8

Follow the Nostrica account and #nostrica to stay up to date on the event.

#newMusicFriday created by
is a wonderful opportunity for nostriches everywhere round the 🌎to share their favorite new music every Friday on Nostr, join in the fun and share your new fav songs
quoting
Any other music nerds up for getting #newMusicFriday going? Share your fave new finds when they drop on Fridays.
Shill us your favorite tracks to be featured in Friday’s NR!

Nostr Heath of the Network 📈
• Pubkeys = 353,051
• Events = 1,483,866
• Relays = 258

🔥 Meme of the Day🔥
quoting


Stay Classy Nostr.
Author Public Key
npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk