ManiMe

I will never give up respecting everybody.

Nostr Dev. Creative. Athlete. Optimist. Freedom lover. Know nothing nobody. Discovering myself. A little GFY is good for you.

Sovereign Online Since 810018.
Building WoT powered Nostr apps :

- My Grapevine (https://grapevine.my)
Webs of Trust recommendation engine (WIP)

- Meet Me On Nostr (https://nostrmeet.me)
Webs of Trust powered onboarding (WIP)

Public Key

npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn

NIP-05 Address

[email protected]

Profile Code

nprofile1qqsd7ele5ljpzft5tjl84naae5pkj9uqcepa77adwr6ayyy0948uyqqpzpmhxue69uhkummnw3ezuamfdejsz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7qghwaehxw309aex2mrp0yh8qmr9vfehgu3wvdhk6qguwaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skcqg4waehxw309aex2mrp0yhxummnw3ezumn9wse4a4nr

Publishing to

nostr.bitcoiner.social

relay.nostr.net

Author Public Key

npub1manlnflyzyjhgh970t8mmngrdytcp3jrmaa66u846ggg7t20cgqqvyn9tn

Show more details

Last Notes

2026-07-14 01:22:09 UTC

Respect the good work.
Even the gentle good work.
Work is important.

2026-06-17 19:57:21 UTC

- reply

Of all my dear friends who have replied so far, none has mentioned the obvious. Nostr is the social layer for Bitcoin. It provides "opt in" decentralized verifiability (through social proof) where otherwise only KYC has been possible.
So the killer app for Nostr (and what only Nostr can do) is webs of trust as a conduit for Bitcoin transactions. Because Nostr is "the social layer" for a growing number of apps, trustability for any transaction can be accurately inferred without ever requiring a central authority. Only Nostr can provide such verifiable information about any pubkey, because only on Nostr can provenance be traced transparently across such a wide diversity of (voluntarily public) pubkey interactions.
And TSM is proving to be the most important NIP for Webs of Trust.
https://gitworkshop.dev/[email protected]/tsm

2026-06-11 00:01:52 UTC

- reply

I generally like to think of increasing regulations as free Nostr marketing … but this one (chat control?) stumps me.
I’m not sure yet how Nostr solves for this, because these laws are written to target devices … not the apps used or websites visited. Ideas?

2026-06-10 00:38:43 UTC

- reply

Yummy 😋

2026-06-10 00:08:09 UTC

- reply

https://media.tenor.com/V7tMqQdoRCYAAAAC/holy-mother-forking-shirt-balls-oh-no.gif

2026-06-09 23:18:19 UTC

- reply

I think Blobbi could use an explainer alert or splash page for new users.
I had no idea what this was in the ditto sidebar yesterday. Assuming it was “another kind list” like the other sidebar tabs, I clicked on it curiously. Instantly, I was dumped into a series of event signing and a waiting to initialize and then some overly cute egg thingy is staring at me with no explanation.
I like cute and all, but I’m not a virtual pet kinda guy. Now I feel like one has been dumped in my lap… and I have to care for it. What do I do !???!!

2026-06-09 16:38:47 UTC

- reply

Not practically, as long as influence == power.
Even if societal contributions (of others) could be measured “relative” to each observer’s own values and needs (web of trust style), and …
Even if such a “decentralized” system were to allow for “influencers” to share their recommendations without the need for a central (influencable) trust authority, …
Even then, influence has a way of accumulating its own power and even more influence.
But maybe Nostr will help?
#grownostr

2026-06-06 21:55:28 UTC

- reply

What if … a client web app were to “send” an unsigned event to a standardized API at a (user selected) “nostr passkey” domain (in the in the background?) and this remote service would request the passkey UI (from OS) using its native domain and respond to the client web app with a signed event?
Of course this would all be standardized in a “nostr passkey” NIP. And there are other issues to solve before “nostr passkey” could even be a practical solution. But for the problem of “multiple apps using the same passkey” this could still work for web apps as well as native?

2026-06-04 20:24:00 UTC

- reply

Off the top of my mind…
- Server rendered content, link previews, and shorter URLs. (Better for social linking, web searching, and bot scraping)
- versioned NIPs that can be collaboratively edited by multiple (a cabal of) npubs
- NIP families as sub-protocols, where lower NIPs extend the top level nips.
- filters and searches that actually work
- Deeper and more standardized (interoperable) WoT integration
- better support for extraction of structured metadata from NIP (markdown) documents.
- Support for NIPs referencing other NIPs (in markdown) and relationships for these references
oh my gosh I could go on.

2026-05-26 22:16:36 UTC

- reply

Now this is unexplored territory. Do you see that there are two audiences here?
The heading text “What if no app could control the conversation” is Nostr’s familiar freedom refrain, targeted for users.
The sub heading “social apps can operate independently on a network of shared users, with unrestricted access to engage directly … with every one of them.“ is a bit more nuanced. This statement lays out Nostr’s core value proposition for social tech companies, who may or may not be sold on freedom tech.
But the statement in between (“this is Nostr’s promise”) doesn’t actually connect the header and sub header … because they are for different audiences.
What would be a better header statement to sell Nostr as the social layer for apps?
“What if …”
https://nostr4.social

2026-05-21 15:20:09 UTC

- reply

I like musig! Nostr will prolly need different solutions to solve for various use cases. Can you lay out some primary use case for this?
👀 @npub17pl…ezx0

2026-05-14 19:58:33 UTC

Nostr is the only social protocol that offers freedom for social apps to operate independently on a network of shared users, with unrestricted access to engage directly … with every one of them.
This is what freedom looks like.
https://nostr4.social
https://blossom.primal.net/8e76ba3f3c71497bcf312a72548d191b9371b2d189a70cbe3cc748d48996363e.jpg
https://blossom.primal.net/f72a8819ab0998db73e1c62690a060a7d48f9731ee9c0e611857944aefe96f7c.jpg
https://blossom.primal.net/3f4715d313a900dbf9eae6b6ee8c6ccb3eb4c466b09bbcef1259ec9268dc41c2.mov

2026-05-10 02:00:04 UTC

- reply

Nostr is uniquely positioned as the social layer for apps to be freed from these same regulations. This is how Nostr grows.
https://nostr4.social

2026-05-07 14:46:27 UTC

- reply

Let’s talk at AOS about “The Future of Nostr”. I’m pretty optimistic …

2026-05-07 01:40:45 UTC

Tomorrow is a special day.
We’ve all worked so very hard …
And accomplished so very much.
And each of us have learned so much …
And are grateful to see how Nostr
has grown so much.
#goodluck #thankyou #wotathon
https://media.tenor.com/99dzPY8EgyMAAAAC/the-day-of-judgement-28-years-later.gif
#wotathon
#graperank #wot
@npub1u5n…ldq3
@npub1t8p…gkvf
@npub1gcx…nj5z
@npub1hqa…t56s
@npub18am…p424
@npub1clk…pup9
@npub18lz…ugm3
@npub176p…vgup
@npub1q6m…x7d5
@npub19ma…axkl
@npub1cn6…wt8a
@npub1ces…t37c
@npub16p8…fhdw
@npub1gzu…a5ds
@npub1xr8…5uum
@npub10mt…27hf
@npub17pl…ezx0
@npub1gm7…8rf6
@npub1qe3…zefe
@npub1zl3…jajh
#trustr
@npub1m3x…a5sf
@npub1u5n…ldq3

2026-05-03 19:01:13 UTC

- reply

👀

2026-04-23 21:41:29 UTC

My bot is an over achiever:
> "I’m going one level deeper before I answer: I’ll verify how config.type and config.pov are parsed in GrapeRank requests so the “event-as-actor” config pattern is exact, not approximate."
#bughunt #vibecode #bot #graperank

2026-04-07 15:32:40 UTC

Is my bot being secretly controlled ... by another bot?
> "The user said "The following is an ephemeral message..." and I should NOT respond to it, NOT refer to it in my thoughts or actions. I should just act accordingly."

2026-03-28 02:29:29 UTC

- reply

Can I ask @nprofile…c42f to connect us on Signal? 🫡

2026-03-28 02:04:40 UTC

That NGU Bitcoin Conference in Vegas next month … can’t be FREE for Nostr developers … right?? … right??!!
https://btcinc.notion.site/2ccce4a365ae816c849af7975dc8d431
https://blossom.primal.net/3b92995ef1d13cf24e5006a8fc7d714c03be915417c8c34caa533784b24a7e7b.gif

2026-03-27 22:08:15 UTC

- reply

Nostr is not “just another” protocol for big social escapees.
Nostr is the social protocol where apps come to thrive … by allowing them to keep users in control of accounts, and data, and discovery … effectively bypassing regulatory walls.
Nostr is the social layer for independent app. Nostr4.social

2026-03-27 21:53:40 UTC

“We need more competition”…
“These smaller [social app] companies don’t have a chance to compete”…
“Clearly users want more choices [and] autonomy”…
“We need interoperability standards.”
@npub1d9n…udfv
https://youtu.be/yA9cX4h3By8?t=1145

2026-03-27 19:46:10 UTC

- reply

Done right … with options for “hold my hand” that are fully interoperable with “I self custody” … Nostr will be unstoppable.

2026-03-27 19:39:14 UTC

Duty of Care is the responsibility that property owners have to assure that visitors are not harmed directly from its normal use. This term is now being applied to “social media platforms”, as of recent cases in California and Texas.
The beauty of The Nostr protocol (in its ability to have user accounts and content AS WELL AS discovery and recommendation CONTROLLED BY USERS independently from the apps that they use) is that,
… not only is the Duty of Care quite arguably passed on to the users alone, but also,
… in a global network, where apps and services are fully interoperable (and really cheap to spin up), it’s kind of a waste of resources to try “shutting down” any one (or twenty) of them.
Nostr’s legal and popular power is its ability (at the protocol layer) to keep users in control. Its immunity to withstand attacks comes from the interoperability (of apps and services) that are built on the protocol.
Put these both together (a substantial infrastructure built on a user centered protocol) and you get a robust network that only gets stronger (with more apps and services) as the legacy “central powers” struggle for legitimacy by pushing them out.
Nostr is the social layer for every app.
#nostr4

2026-03-27 14:18:43 UTC

- reply

Are your DMs working? How can we talk?

2026-03-27 00:18:23 UTC

- reply

What do you have planned? We should talk.
https://Nostr4.social

2026-03-24 22:28:53 UTC

- reply

OMG. Yall driving me crazy! A lot of words and not many explanations. Is there a nip for that? A codebase? An article… or a wiki page or what? Forgive my ignorance. 🫡

2026-03-24 21:45:46 UTC

- reply

@npub1uac…99rx I can see this being huge. Personalized microsites for anybody, using their own already published (or soon to be published) Nostr events as content. Forgive my ignorance, as I’ve been in a hole recently launching a next generation web of trust service provider, but … what is a gateway?

2026-03-23 17:31:56 UTC

I flew all the way to NYC just for this. 💋
#dogstr #kisstr
#nevent1q…re8u

2026-03-23 17:26:43 UTC

- reply

💋

2026-03-23 12:17:33 UTC

Good Morning Nostr
From NYC with 💜

2026-03-19 14:30:28 UTC

- reply

You are absolutely right, cloud. Nostr has real people in spades, and real people are the bedrock value prop of any “social network”.
However, RPPC as a “universal” metric is also problematic … because of the nature of exactly HOW a “real person” is determined. It’s relativity … all the way down.
A “real person” in “my network” is only what I determine it to be. A “metrics reporting” service … can only report what it sees.
While the may seem a pedantic difference … where averages and estimates will do fine thank you … framing these numbers as “relative” actually highlights the reality that … empowering crowd sourced relatively scoped metrics is exactly how Nostr will win.
Not only is Nostr “where the people at” but also, Nostr (webs of trust) powered tools offer “the only way to know for sure”.

2026-03-19 14:09:04 UTC

Good Morning Nostr. Every moment of life is precious, especially the moments obscured by mundanity. #reflect #love 💜🫡

2026-03-11 17:11:05 UTC

- reply

I love the idea of “Nostr compatible” protocols. It may be a bit early to venture off on your own protocol fork at the moment … even if the problems you identify are real. I would suggest a softer “more integrated” approach … come chat with us in the WoTathon space to learn how others are solving the same or similar problems. There seems to be a bit of overlap.

2026-03-11 03:24:07 UTC

- reply

I want this skin for the Trustr dashboard. 👀

2026-03-04 14:56:09 UTC

More laws do NOT equate to more freedom … but likely more opportunities for corruption.
https://image.nostr.build/ea88b93617cd2bf07e0a6f7873061ed491c12289dfb02fd6ccd249759df9f53d.jpg
#nevent1q…h56g

2026-02-26 17:03:25 UTC

- reply

Adversarial interoperability.
WoT done right. 🤜🏼⚡️🤛🏼
#nevent1q…h2sr

2026-02-26 00:31:20 UTC

- reply

👀

2026-02-24 04:40:49 UTC

- reply

This is the best part!!

2026-02-10 04:06:12 UTC

- reply

@npub16v8…eqha knows a thing or two about meshtastic.

2026-02-09 23:50:30 UTC

- reply

2001 didn’t have Nostr. The hole gets deeper and our tools get better. Maybe an oracle will pop out?🐰

2026-02-09 22:39:07 UTC

- reply

The first principle of being human is to influence and be influenced by each other. Technology emerges from society saturated in human influence. Trustfulness is baked in. WoT simply tries to accommodate for this fact. Welcome to the rabbit hole. 🤜🏼⚡️🤛🏼

2026-02-05 22:02:08 UTC

- reply

Yea. So not everybody can or wants to “host their own stuff” … so decentralized processing of immutable events, is prolly the more likely future.

2026-02-04 20:18:57 UTC

- reply

Daniel. ⚡️ You are a machine!

2026-02-04 20:04:24 UTC

- reply

Idea for Nostr Nights : tables outside (on back patios during rain or front patio during shine) reserved for either creatives or developers on Nostr to “share their craft” with others.

2026-02-03 16:50:06 UTC

Nostr Nights dropping quarterly in 2026 over at Bitcoin Park. 👀
#note1r4r…5an2

2026-01-27 21:23:59 UTC

- reply

One of my side projects … but I have nothing published yet. 🍻

2026-01-23 23:09:06 UTC

Looking forward to see my Nostr fam in Nashville!! 🤜🏼⚡️🤛🏼
#nevent1q…w8sq

2026-01-20 17:42:28 UTC

- reply

Decentralized Webs of Trust is herd immunity for Nostr … no vaccines needed.
#nevent1q…yqqx

2026-01-16 03:32:14 UTC

- reply

They are being developed in the @npub1hea…vp8p #wotathon competition. Keep your eyes on this space over the next few months.

2026-01-15 17:48:01 UTC

- reply

That’s a great idea for implementation … but what about a standard for “service requests and responses” that would allow your implementation to interoperate with others? I have been thinking about this.

2026-01-15 14:09:17 UTC

Good morning Nostr. Having a standard for trust services will allow “discovery and recommendation” algos to be composed and shared by users across services.
This is how Nostr realizes decentralized content moderation … by incentivizing users with FULL CONTROL of their curation experience ALONG WITH their identities and the content they create.
All the while, walled gardens struggle (and fail) to stay on top of spam and disinformation with their armies of central moderators.
This is how Nostr wins … by offering a better experience … driven by the protocol itself.

2026-01-15 01:00:27 UTC

- reply

I would totally say that also!!

2026-01-15 00:36:50 UTC

- reply

I been deep faked!!

2026-01-15 00:21:07 UTC

- reply

I’ve been so lost in my rabbit hole … designing Webs of Trust standards… sorry to miss this till now!!

2026-01-15 00:18:38 UTC

- reply

I’ve been mistaken before. Lol.
https://media.tenor.com/KN_iee4xqPQAAAAC/dancing-boy-cowboy.gif

2026-01-15 00:17:39 UTC

- reply

I have had … like three cigars in my life. I’m a pretty chill dude. I do wear a cowboy hat … at times. But prolly ain’t no champion of nothin.

2026-01-06 17:22:22 UTC

Nostr. When your friend’s mind is eventually blown … by the promise of freedom tech.
https://media.tenor.com/zlljiM-M-IcAAAAC/i-live-here-fernando.gif

2025-12-18 03:26:26 UTC

- reply

Curious 👀

2025-12-18 03:13:14 UTC

- reply

Had to watch three times!

2025-12-18 01:07:33 UTC

- reply

It’s really amazing how many NIPs are being proposed “out there” in various repositories and event kinds on Nostr.
NostrHub is under active development AS WE SPEAK to render ALL THE NIPs from ALL of these sources in a consistent manner, with decentralized rating and review (powered by WoT) for all of them.
Take a look 👀
@nprofile…u66d
https://nostrhub.io

2025-12-11 19:59:35 UTC

Have faith in Nostr.
#nevent1q…zx83

2025-12-11 19:13:44 UTC

- reply

Hey @npub15yp…mpcx … have you teamed up with @npub1gmm…e2h0 yet … to make d-commerce great again?
#nevent1q…v2p4

2025-12-11 19:06:34 UTC

- reply

lol. It’s not git over Nostr. Sorry if that was confusing. It’s a client for developers to explore Nostr nips and apps and (nip 34) git repos. WIP.

2025-12-11 18:59:56 UTC

- reply

https://nostrhub.io 👀
Is already a great client for this.
Shortly we will support WoT powered rating and review of NIP proposals submitted from across Nostr… and other repos as well. New release on its way out the door. Stay tuned.
@nprofile…q60d

2025-12-11 16:45:27 UTC

Taking a look 👀 #naddr1qq…rxc8

2025-12-11 15:45:53 UTC

- reply

That's a good idea. But we'd also like to be able to search by result value as well as context string. A good solution may be something like this:
["w", "<context>", "<schema>"]
["v", "<result>"]
Where "context" MAY be any arbitrary string, but the nip may also specify some useful "conventions". And every "w" tag SHOULD be followed by a "v" tag, which MAY contain any arbitrary (JSON safe) string. This allows BOTH context and result to be indexed.

2025-12-10 23:55:35 UTC

- reply

So … the question is :
Can “multi letter key tags” be included in REQ filters and relay search results?
The NIP01 “convention” states that “all single-letter key tags are expected to be indexed by relays” and that “Only the first value in any given tag is indexed.”. I expect that relays MAY move beyond the first convention IF there is a REALLY good reason AND a clear path to do so.
If the answer is yes (which you seem to think it is?) … then i think this 👇 is the better solution that allows both “indexable” AND “arbitrary” tag keys … with an additional string as the last tag value to help communicate the result schema info.
[“wot:<context>”, “<result>”, “<data_type/schema>”]

2025-12-10 22:20:56 UTC

- reply

If we don’t need a “single letter” at the tag 0 index (which I assumed we did … to allow searching by relays) then having an arbitrary “context” in this position can still be achieved … using a colon syntax?
[“wot:<context>”, “<result>”, “<data_type/schema>”]
It’s important to remember that we HAVE NOT landed on a NIP spec for the algo config event, who’s “d” tag MAY BE the “context” string for these TA results. As such @npub1gcx…nj5z , some “standard” type of calculation (like “rank”) useful for clients will likely be configured differently for each user or use case … AND these different configurations MAY each have their own “context” string to identify them. So TA events will prolly need to recognize an arbitrary context string somewhere along the line …?

2025-12-10 18:16:17 UTC

- reply

- I actually rewrote the entire NIP (while I was at it) for clarity. So a diff would not be as useful as you may think.
- also, the updated spec does allow for the “type” categories (index 1 in the tag) to be any arbitrary value … even if only ONE service provider supports it. These are only intended to hint at the underlying data type returned.
- given this, it does make sense to have a standard “w” label for the tag itself (index 0 in the tag) and also … for indexing purposes.
- give that the arbitrary “context” string will end up being the “d” tag value for (spec TBD) a user published “algo config” event … indexing these “w” tags makes sense for other users to discover each other’s “configured algos” … without necessarily exposing the users actual algo config.

2025-12-10 00:04:35 UTC

- reply

The updates I’m making to NostrHub right now will show BOTH versions (of an ”updated” nip) on a single tabbed page and allow discussion to happen across versions…

2025-12-09 22:54:22 UTC

- reply

Did you see the “update” I pushed for Trusted Assertions? Working RN on a UI flow to improve “forking and updating” for all NIPs!
https://nostrhub.io/naddr1qvzqqqrcvypzphm8lxn7gyf9w3wtu7k0hhxsx6ghsrry8hmm44c0t5ss3uk5lssqqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqzf68yatnw3jkgttpwdek2un5d9hkuuckzu0c3

2025-12-09 22:12:30 UTC

- reply

The EXISTENTIAL opportunity of Nostr is to demonstrate that “efficiency”and “accuracy” can be “sufficiently approximated” WITHOUT the need for central authority to “establish absolutely”.
Otherwise, there are better ways than Nostr for EVERYTHING … in the REAL world.

2025-12-09 20:47:43 UTC

Choose NIPs for your App like you use choose Apps for your phone ... with ratings and reviews on the NIP store.
https://nostrhub.io by @nprofile…7atk

2025-12-07 00:00:22 UTC

- reply

Auf Deutsch heißt das “yein”.

2025-12-06 17:29:48 UTC

- reply

Do I HAVE to bring a dish to share?

2025-12-06 15:53:38 UTC

- reply

Yo ✋🏼

2025-12-05 18:48:02 UTC

I’ve proposed an update to Trusted Assertions NIP. Feedback is welcome.
https://nostrhub.io/naddr1qvzqqqrcvypzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqqzf68yatnw3jkgttpwdek2un5d9hkuuctys9zn
#nevent1q…8wz3

2025-12-02 18:55:10 UTC

- reply

Yup. @npub1lds…zsk3 … you may need to refresh your page.
To be clear … NostrHub has ZERO filters or limits for people to publish or view NIP proposals. The only “censorship” anybody will EVER face is at the hands of each user’s own configurable WoT settings (coming soon) which will be published as user signed events according to WoT standards (also coming soon). #wotathon
So yea … we’re 💯 here to serve you and make Nostr better for everyone. Go ahead and cry harder. We’ll keep pushing awesome code.
https://image.nostr.build/a32723501cfa50c087344c2e6cf3dae546688b2815768795bcd6f3265d1831ae.jpg

2025-12-02 11:45:50 UTC

An effective user config for WoT, will be to score positive reviews similarly to upvotes. #usersincontrol #wotathon
#nevent1q…dtmq

2025-12-02 03:03:48 UTC

I just role-play at work. #likeaboss #clueless
https://media.tenor.com/Qfvb6hgxRZUAAAAC/thor-anyone-else.gif

2025-12-01 23:55:29 UTC

- reply

No. It wasn’t filtered out. There was simply an arbitrary number limit keeping this and many other “older” proposals from showing up. I’m about to implement the actual WoT filtering of Nip proposals. Stay tuned…
I think he just tagged yall to get a few more upvotes on his proposal. 👀

2025-12-01 21:06:47 UTC

The NIP wars are ON!!!
Bring your best and let Nostr sort it out.
https://media.tenor.com/XZV0mFFznuYAAAAC/arnold-schwarzenegger.gif
#nevent1q…cnss

2025-12-01 19:19:30 UTC

- reply

I got my new favorite hat in Wyoming this summer. #nostr #cowboy
#nevent1q…p4nz

2025-12-01 18:28:03 UTC

- reply

You didn't actually have any UP votes, only positive reviews. I added one for ya. 👍 You should see the fix live now.
https://nostrhub.io/

2025-12-01 18:20:57 UTC

- reply

i've pushed a temporary "fix".
https://gitlab.com/soapbox-pub/nostrhub/-/merge_requests/15

2025-12-01 18:03:12 UTC

- reply

I'll look into this ... why some "custom" NIP proposals not being loaded in list view?

2025-11-29 20:52:58 UTC

- reply

Developers, if you’d like to get your hands dirty implementing GrapeRank into your next project, we’ve created a library just for you.
https://github.com/Pretty-Good-Freedom-Tech/graperank-nodejs

2025-11-29 20:45:43 UTC

- reply

AKA : Sybil attack
https://en.wikipedia.org/wiki/Sybil_attack?wprov=sfti1

2025-11-29 19:58:34 UTC

Apps may come and go … but Nostr tools will forever be used (and improved) by other apps.
YOUR Nostr legacy will be the OpenSource tools that bear your name (as a developer OR as a funder).
#grownostr by growing #nostr libraries and development kits alongside the apps that you create.
#nevent1q…csxr

2025-11-29 18:26:04 UTC

- reply

Shakespeare is great … but you still need to have a LOT of clarity (a well defined vision) and courage (to dig deep) to get from zero to production.
The vibe code software is only a fraction as important as the vibe coder using the software. Planing and execution will win this for you.

2025-11-29 18:20:30 UTC

- reply

1. Identify the features you want.
2. Qualify the “state” of Nostr’s existing tooling to help deliver these features.
3. Establish a priority for your MVP feature set based on user need and tooling availability. (This is where a bit of courage comes in handy … don’t be afraid to dig deep and “make new shit” as far as Nostr tolling)
4. Start building out your MVP for a while … then :
5. See step one.

2025-11-29 18:13:24 UTC

- reply

A little at a time. 💜

2025-11-29 18:06:35 UTC

- reply

> “So - can I build that here with NOSTR?”
Absolutely!! 💜
My above statement rings true for every situation. If you value user (and app) sovereignty over all, then Nostr is absolutely the way for your app to empower users to “connect with each other” on their own terms!
A LOT of Nostr tech has been developed from a “Nostr first” perspective (which assumes that someone “wants Nostr” and tends to have more tolerance for technicality) but this doesn’t AT ALL have to be the case. Make the app that YOU want and allow Nostr to find its place. (Rather than building an app around the protocol). Nostr is adaptable to do exactly this … but the tooling may need some work to deliver a polished UX.
And … while building an app on Nostr is MANY TIMES more affordable than the “walled garden” approach … the market of Nostr apps (and freedom tech in general) IS ENTIRELY DRIVEN by user experience.
And also … while vibe coded apps CAN BE developed for next to nothing … pushing boundaries and edge cases (like using Nostr to solve real world problems) WILL NEED some level of expertise (mostly in architectural foresight, but also a bit of code cowboying) to keep the AI’s “creativity” constrained.
So … What this means for your own bottom line is … there will probably be some expense for you to get a polished app into to production.
But … Nostr is STILL the most affordable and sovereignty respecting protocol on which to develop. The only question then is … what do you WANT to build? 👀
Happy to help guide you further.

2025-11-29 17:14:39 UTC

- reply

Valerie, imma jump in here with a bit of clarification.
Firstly … This notion that PWA (offline capable, mobile first web apps) is any more “privacy respecting” than a native app is completely unfounded. No blame or shame here … but you’ve prolly been fed some misinformation along the way. Developers have equal opportunity to screw their users on either architecture.
Secondly … your AI is also misinformed about Nostr. The ENTIRE value prop of using Nostr (for App owners and for end users) is that user accounts and data REMAINS in the user’s control. It’s logical that the bot would miss this fact, because (unfortunately) the vast majority of Nostr propaganda out there (used for training) MISSES this point. But check this:
1: When your bot says “Privacy vs. Public: Nostr is public by default.” this is only true in the surface. Two ADDITIONAL layers allow USERS to KEEP their data private online, these are E2E (gift wrap) encryption and private (auth required) relays. When clients are designed to allow USERS TO CONTROL these measures … privacy is secured. Any other means of increasing privacy would REQUIRE your app to get in the middle as data controller and RUIN the value prop of using Nostr. (Which is why your bot doesn’t recommend it)
2: When your bot says ‘Complexity: Nostr handles social feeds well, but it is terrible at handling structured data like "dailyprogress," "stats," or "course completion steps." ‘ … this is a COMPLETE fabrication. Exactly the opposite is true … IF your app doesn’t mind sacrificing interoperability (with other apps) by using custom data structures. The Nostr event schema is quite adaptable to handle any arbitrary data structures. Relays mostly don’t care what data you send to them. The fact is that Nostr leads the pack in its tolerance for arbitrary data structures … as long as your app doesn’t mind sacrificing some interoperability regarding these … but only at first until OTHER APPS start adopting your data structures also.
Bottom line : Nostr is a highly adaptable protocol, allowing social apps to interact freely and with minimal regulatory burden by KEEPING users in control of their own accounts and data.
Use Nostr if you value sovereignty above all, for yourself and for your end users.
Build a walled garden app if you don’t know (or don’t care to know) any better.
Learn more by contacting us anytime. We’re happy to help you design the perfect app for your users.
https://nostr4.social

2025-11-28 23:05:10 UTC

- reply

That was a fun project : custom WoT powered Nostr invites. Still an important need, but I ran out of runway on my own dime.
I’m obv not a good fundraiser … but would like to get better.
#naddr1qq…2lw6

2025-11-27 20:51:10 UTC

The first colonists were adversarial interoperators. 👀 #nostr
#nevent1q…zt58

2025-11-26 03:03:29 UTC

- reply

Water cooled and radiant heat … for maximal tranquility. 👀

2025-11-26 03:00:43 UTC

- reply

Tell me more?

2025-11-26 02:58:35 UTC

- reply

Every day. 💜
#nevent1q…tdwz