Subnostr

Sep

3e294d2fd339bb16a5403a86e3664947dd408c4d87a0066524f8a573ae53ca8e

Ex Humble Other Stuff Builder 💜

https://github.com/sepehr-safari

That's what I thought. Thanks.

I guess it can just be markdown actually.

tables in markdown is a headache. you just need to play with tags in a parameterized replaceable event (kinds 30000~40000). each tag is an array of strings which can represent a row of a table. so a couple of tags together would create the whole table. simple.

This kind of app could have:

👉 Feed of work outs of your peers.

You can zap, copy, fork, react, comment, ... Help each other reach goals.

👉 Feed of tips & tricks in long form articles.

Filtration & Discovery of methods (how to lift, what to eat, ...) your peers actually found useful.

👉 Your personal track record

What else?

nostr:nevent1qqs2vjv40a7jndlq04mgfyygff4kn2t2gre6fqsd3jj0296gwqsp2fspz9mhxue69uhkummnw3ezuamfdejj7q3q49p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklqxpqqqqqqzl0jqku

design it and I will build it 🤝

I'm designing parts of Pinstr to pitch to nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7

Let me know if you have any ideas to consider. What would make pinstr userful and superior to alternatives?

We Are Cooking up Some Exciting Stuff! Just Stay Tuned! 😍

nostr:nevent1qqsp4y787w7x83nh89v2aq2jnd0jva7x6wypjvg30qqsnjuljahn8kgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qgewaehxw309amk2mrrdakk2tnwdaehgu3wwa5kuef0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcppemhxue69uhkummn9ekx7mp0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qgawaehxw309ahx7um5wghx6at5d9h8jampd3kx2apwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjf37e4

I have decided to fork the nostr protocol. This new fork is maximum compatible with the legacy nostr protocol. This fork will be аіrdrοpped for free on all existing and future npubs, and any client connecting to existing nostr network will be also be able to connect to the new fork. The fork is called: postr: Posts and Other Stuff Transmitted by Relays.

NIPs have been renamed to NIPs, which stands for: Now Its Posts. The new Github is at: https://github.com/nostr-protocol/nips I see many of you have joined already.

Thank you and lets keep building!

since it's an open protocol you can't force me to use postr. I still wanna use nostr. but thanks.

People keep telling me to call my Nostr posts "notes".

Yes, it is "notes and other stuff transmitted by relay". But my note is a post. I posted it. I have used the term "post" for two decades. I posted it.

This is Nostr. We don't have rules. I'll call them what I want. I called it a post. Fight me.

I continue to call posts on "X" tweets as well. I tweet them. My father called tissues "Kleenex" down to his end days and I plan to do the same for this unless or until it just naturally feels right to do otherwise. Every time someone tells me to change my terminology, I just channel my late father and say, "no". I called it what I called it.

I tweet on X and I post on Nostr.

technically, we don't "post" notes here! we "publish" them! so you should call your notes "Publish" I guess 😂

We need these things. More stuff integrated with nostr. Let's connect all the traditional apps.

nostr:nevent1qqst8ns599n70tmmqa3gzxfy3jj3ffuamvvdenq2y5lquaayukydauqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygz47pzeqe60xey0fnwfmjxwxtdz52pqwnxskqs9jmhqx0gj6wz3s5psgqqqqqqs4n9rvz

Nostr has serious SEO problems atm. things like Wordpress are mostly focused on SEO! so I believe these things could not put together! any thoughts on this?

I'm designing parts of Pinstr to pitch to nostr:npub18c556t7n8xa3df2q82rwxejfglw5przds7sqvefylzjh8tjne28qld0we7

Let me know if you have any ideas to consider. What would make pinstr userful and superior to alternatives?

what do you think guys?

nostr:nevent1qqsp4y787w7x83nh89v2aq2jnd0jva7x6wypjvg30qqsnjuljahn8kgpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qgewaehxw309amk2mrrdakk2tnwdaehgu3wwa5kuef0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcppemhxue69uhkummn9ekx7mp0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qgawaehxw309ahx7um5wghx6at5d9h8jampd3kx2apwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsjf37e4

To be specific:

- I don't want to have to make a new list of my favorite movies on every app

- It'd be great if I can just rate/review movies on Nostr Tomatoes (or any other app) and then just include a list of, let's say, the top 10 of those in Nostree/Pinstr.

we could kill diversity by making every client following the same rule and the options!

I think it's not just about a list of movies (we can always publish a simple note for such thing), it's more about those unique features on which each client focused.

This is why I didn't introduce a new NIP for Pinstr! nostr:note1lqcvsvn845juvffzkffgzfhcw4l6tdazq88e3mz623gmsxyx9hzsg3wq8v

Haha, you're really trying to convince me here. Must be hard to work if your prototypes look like this 😉.

This is a layout that is not easy to understand though for me.

On the right: how does the user know if these are pictures or albums?

On the bottom left: having the details on top instead of the pic or Title is confusing. Also, this segment could use a title or something, if not I don't know what I'm looking at and it looks the same as the profile info on top.

thanks for the feedback. it's all about iterations. we are redesigning pinstr for the 2nd time! your concerns are already foreseen.

NDK is amazing! A huge shout-out to nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzpmhxue69uhkummnw3ezuamfdejszynhwden5te0wp6hyurvv4cxzeewv4eszrthwden5te0dehhxtnvdakq6a647p ; He is superb! I've been contributing to it for a while now. It's exactly what every client needs! I've just fallen in love with ndk-cache-dexie 🤌

https://void.cat/d/KXxAgK7RBABUREC2To1Le4.mp4

the what the are the you the doing 😂🤦🏻‍♂️

I'm happy to see a lot of Other Stuff in the latest rounds of grants from OpenSats. I'm also tickled to see the NOSTR referenced 😂😂 Congrats to all. This train is nowhere close to being done and there's a lot more places for us to go. Thanks nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f 🤙🏻🤙🏻🤙🏻

https://opensats.org/blog/nostr-grants-october-2023

nostr:npub10pensatlcfwktnvjjw2dtem38n6rvw8g6fv73h84cuacxn4c28eqyfn34f is doing really great! they are gathering the most talented devs and designers together all around the world! and it's just the beginning! 😍

this is the power of OPEN SOURCE! 😍 nostr:note1p5c0jgpyz2ywur39fy7neurqsuhu4hxac6t545hr4eku3kzh0avsfcgqgp

Introducing Nostr Playground: Dive Deep into the World of Nostr! 🚀

https://playground.nostr.com/

Hello everyone!

I'm thrilled to unveil Nostr Playground, your go-to hub for all things on Nostr. Whether you're new to the protocol or an experienced developer, the playground offers a unique, hands-on experience to interact, test, and experiment with Nostr's multifaceted features.

Why Nostr Playground?

Experiment with Ease: Play around with custom filters, see results in real-time, and gain a deeper understanding of Nostr's potential.

Flexible Relays: Don't be confined to predefined servers. Test with any custom relay and discover endless possibilities.

Visualize Data: View events both as raw JSON and in a user-friendly format. It's the best of both worlds.

Save & Share: Use the local storage feature to continue where you left off and the import/export function to share your setups with peers.

Remember, learning is best done through doing. So, dive in, get your hands dirty, and explore the vast universe of Nostr. Whether you're fine-tuning an application or merely satisfying your curiosity, Nostr Playground is your sandbox.

Ready to embark on this journey? Visit Nostr Playground now!

https://playground.nostr.com/

Happy experimenting! 🌌

what other features do you want to see on Nostr Playground?

nostr:note1s757cwk5wxafqvdz6gek249m4zrp85n6c93vdngd6v28687gm7zq4scrgx

GM FIATJAF, THANK YOU FOR NOSTR. nostr:note1zcraapp8kucc94m2haldd7sf47lvw5la2mtcvjgzg2p5w763xdqs6r2tjy

Ah. Not sure if it makes sense but that's indeed what I did. Is that something from replaceable events?

Yes, they are addressed by their “d” tag which is also the board title.

I've been thinking about a Portfolio client as well 😉

Just because I want to bring more designers to nostr hehe.

#portfolio #logo #nostrdesign

Pinstr for Portfolio 👀🫡💜 nostr:nprofile1qqs2js6wu9j76qdjs6lvlsnhrmchqhf4xlg9rvu89zyf3nqq6hygt0spp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq35amnwvaz7tmwdaehgu3wdaexzmn8v4cxjmrv9ejx2asmsv6lf

nostr:nevent1qqsfyvfpenzge30xl05mp9exdvq6u39sjywly3ewsqytl03xhes2x9gpp4mhxue69uhkummn9ekx7mqaxfq0y

Oh, That's the NIP!

It should be shared with the official list to avoid kind number conflicts, even as an issue.

nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpr9mhxue69uhkummnw3ezu7n9vfjkget99e3kcmm4vsq3camnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdsqs6amnwvaz7tmwdaejumr0dsjwmwen doesn't believe in creating extra NIPs for every single use cases! pinstr is just using `Parameterized Replaceable Events` at the end.

Question: I editted a pin which had been zapped, but after the edit the zaps were not showing anymore. Is that correct?

correct if you've changed title of the board.

Load More