Five

I ship freedom tech.

Public Key

npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw

Profile Code

nprofile1qqsdqnk0xw3s8fvc2t7mdq0d3dqjyqd6shvdyxv6a3eukcngr4324yqpp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgcfll9q

Publishing to

nos.lol

relay.primal.net

bitcoiner.social

Author Public Key

npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw

Show more details

Last Notes

2026-05-24 06:07:47 CEST

- reply

Thanks for the link!
Tweaks:
- I use profile lists plus reactions on approval forms for content section permission accounting, no 'badges' tag. I use badges for driving engagement but not perms
- I layer explicit kind 1984 reporting as event or person-bans (from admin or moderators)
Otherwise plumbing is there for targeting but ux needs some thought still.
Especially with repos I find it easier to just target directly with the h-tag for now (not yet implemented) but those are replaceable so this can be pivoted later on

2026-05-19 11:39:07 CEST

- reply

#nevent1q…fkpc

2026-05-18 08:16:51 CEST

I like nutzaps because:
1. Better verification assuming the mint is widely trusted - > reputation builds up
2. Still some degree of plausible deniability: You could say ecash doesn't equal real money, it's an IOU (not a lawyer)
3. No peel-chain type of privacy leak like with Bitcoin
4. More stable from a developer standpoint because there is no third party involved in the publishing of the zap receipt like with LN zaps
5. Funny name
LN zaps:
- Less verifiable probably due to random LN nodes posting the zap receipt
- Worse stability of receipt structure : it is third party publishing with whatever tags they want. You can just propose the event as a client app
- Better deniability due to the above
Onchain:
- Very strong verifiability
- Privacy ramifications most users can't calculate beforehand
- Future fees and waiting times if bitcoin succeeds
Most use a custodian LN wallet (99.9%) anyway and there's really no way to abstract away the privacy consequences of onchain so ecash is my winner.
#nevent1q…8l9f

2026-05-14 19:39:51 CEST

- reply

Second that

2026-05-14 09:01:53 CEST

- reply

Businesses and communities could manage themselves much better.
Keeping nsecs hot for these is insane. Cold storage makes this inconvenient though today.
Frost + signing servers please, looking forward!

2026-05-13 09:25:28 CEST

- reply

Tailwind classes are not for humans. Memory management is not for humans. Build errors, stack traces, and compiler errors are not for humans.
I tell the story of what needs to be built. The AI builds it. I review the code. We refactor. We run the code. AI fixes the errors. I review the behavior.
It works.
I'm happy. User is happy.

2026-05-11 19:28:53 CEST

- reply

Shakespeare is really decent for simple websites, perhaps even more complex webapps too. Liked how it knows nostr better than anything else.
Shakespeare is really nice for vibe coding.
Opencode is still better for agentic engineering though.

2026-05-08 10:42:53 CEST

The exodus from GitHub has begun.
People are complaining: "Again, a platform that we used to build our reputation and discover new stuff and make high-stakes decisions has rugpulled us..."
But the people are looking for the next GitHub not realizing what it truly was:
- Hosting
- Team Collaboration
- Community - broader exploration and interactions beyond the team
The next "GitHub" should be separate services / apps / projects and sharing identities and important metadata formats.
Nostr has the most clean-cut separation and the best design long-term I believe.
But it makes all of these aspects their own marketplaces (and even more like CI) and those take a lot of time and effort to bootstrap.
Will #gitvianostr succeed?
I am not sure but in times like this we have a chance to take a step forward.

2026-05-04 19:46:58 CEST

- reply

#gitvianostr

2026-04-28 07:33:06 CEST

- reply

Because he looks at Nostr and instantly would recognize the change. Probably we would too, if it's very unlike him.
What you talk about is much more relevant in e.g. software release signing.
Benefit of Nostr shines imo where you start mentioning people and events in the Nostr way not twitter way.
That is not mere tamper-resistance but growing this ecosystem rather than deepening the platform network effect twitter has.

2026-04-24 08:03:56 CEST

PSA:
Nostr is much more resilient than Bitcoin.
Many people find this hard to believe but it's really simple to reason about:
Bitcoin must come to a global consensus on the state of its ledger. Simply put, money must be universal.
Nostr does not have this requirement of a consolidated 'global'. Stuff can be distributed anywhere and people still have their own microcosm of Nostr, even when others don't know about you at all.

2026-04-16 07:08:25 CEST

- reply

Main point is, this doesn't work as a proper git remote.
The point of git is effective state sync of commits and branches i.e. a DAG of code collaboration objects.
If you want a signed archive of a repo you could use this but this is not good for code collab purposes.

2026-04-14 19:16:18 CEST

Seems like folks need @npub10r8…t2p8 more than ever
#nevent1q…7sxx

2026-04-03 06:57:35 CEST

Vibed a nice LP on #Shakespeare for BudaBit:
https://budabit.org
Was very pleased with Shakespeare overall great product @nprofile…t7fy and team!
You should listen to the 100% genuine, hand-crafted, no-AI song I wrote, sang, played and produced in the last 5 minutes while the LP was built:
https://a.nostr.build/8aPiIGuKyTngldbn.mp3
#gitvianostr #ngit

2026-04-02 08:21:29 CEST

- reply

Implemented the whole workflow and worked nicely but still mostly I ended up just listening to pods and do deep thinking rather prompting while I'm out and about

2026-03-20 08:21:30 CET

There are a couple of things AI still can't reliably code, most notoriously:
- Authentication
- Payments
But know that is not true if you're using Nostr and Bitcoin.

2026-03-19 07:39:11 CET

I'm a daily active user of nostr.
Just not on the social media front.
I speak to my AI coding agent inside @npub1p28…hpp3 via DMs.
Also doing other dev work in BudaBit that 99% replaced GitHub in my workflow. Organizing BudaBit Demo Day events on @npub1z0l…8ldk
Occasionally managing apps with @npub10r8…t2p8, watching a stream on Zapstream or paying my contributors in sats on @npub1uvj…d955. Tipping sponsored freelancers with nostr-native ecash. Shilling @npub1zzt…ljrv every now and then on my meetups.
Antennapod is still my daily driver rather than fountain, simply the best in this category and open source. Hope I can switch one day though.
Ppl trying to measure nostr usage with social media as a proxy is understandable but the whole picture is very far from what you can extract from such a narrow view of a diverse ecosystem.
Patience pays off. Gradually then suddenly.

2026-03-17 19:51:48 CET

- reply

Cmon man you're too shy to say the obvious, NAK is the most important client and we know it.

2026-03-13 07:09:31 CET

I will believe it's AGI when one of these prompts return sth like this:
https://music.youtube.com/watch?v=kR5Ki6jjPaY

2026-03-12 19:07:53 CET

Working on a new workflow with opencode. Goal: less sitting, more touching grass while staying productive.
- Laptop running opencode on Tmux + termux to access from mobile
- Futo keyboard for easy local voice to text
- When agent finishes sends short summaries with some metadata over nostr in DM (my own spec that I use with budabit based on nip4)
- Can be more interactive back and forth with termux or little less context rich but easy replies via nostr DMs
- Result is shared on a public ip accessible on mobile browser fast
- Laptop in backpack running on shared hotspot or at home
- Can take up where I left off
- Can extend this later to multiple agents deployed on cheap vps
The nostr part is an opencode plugin, and will have a skill for 'nak' too.
Almost there.

2026-03-11 07:32:15 CET

- reply

Building BudaBit for people building on hard mode :)
Social git over Nostr(roughly discord+github):
https://budabit.club

2026-03-10 07:25:15 CET

- reply

The cope is there because ppl think if agents start to use one currency then network effects sink in and we won't have another shot.
This is false FUD. It will be easy to switch once the current system is shaken.
Until then I also think all kinds of stable coins and whatnot will dominate this scene.

2026-03-08 19:07:11 CET

- reply

https://budabit.club
- Community features on your private relay + GitHub-like features. The code collab part can be private or more public.
https://gitworkshop.dev
- GitHub-like client compatible with BudaBit
Both follow nip34 and run git operations in the browser, with shallow-cloning and expanding into full cloned repos in certain cases.
More about my client BudaBit:
- Create, fork or import repos from GitHub, Gitlab, Gitea, Bitbucket
- Handles Grasp: Nostr-authed git server
- Can keep your repo on multiple platforms and Nostr handles authoritative state
- Soon launching: cross-platform PRs over Nostr
- In the coming months: Nostr native CI with Loom protocol - CI job request-response flow with nostr events, paid with cashu.
Web of trust opportunities for filtering slop or untrusted contributors. Gives control to maintainers how strict they want to be and a way to build verifiable lasting reputation.

2026-03-07 19:44:53 CET

- reply

Nostr git is here to solve problems shithub caused.
Cryptographic provenance of all repo metadata that ties into the entire nostr protocol is an immense upgrade people will realize.

2026-03-06 17:51:17 CET

I merged PRs cross-platform today in BudaBit.
GitHub -> Gitlab and the other way round, using the new PR event kinds of NIP34.
Still testing out the new PR workflow but this is going to be a new chapter in code collaboration.
Currently, depending on which platform or forge you use, the PR workflow is dictated by that central place. No standardization, platform-locked identities, and no signatures. Migration is a nightmare and collaboration is hindered.
Nostr solves this problem allowing code collaboration to use a universal sovereign identity and a common format for everyone. More freedom to share and contribute, enabling people and agents alike.
Platforms have been ruling our development processes, now they are becoming redundant hosts for code.
Nostr will rule them all.
... and we haven't even started. Stay tuned.

2026-03-04 16:31:08 CET

Demo day starting!
Join at https://honey.hivetalk.org/meet/BudaBit%20Demo%20Day

2026-03-04 15:34:25 CET

BudaBit demo day in an hour!
Join us 1530 UTC for a freedom tech builder discussion!
Room:
https://honey.hivetalk.org/meet/BudaBit%20Demo%20Day

2026-03-04 12:30:49 CET

Relay.tools down @npub10np…tl5h

2026-03-03 17:53:14 CET

## BudaBit Demo Day application
### Title: BudaBit news
Pitch:
I will demo the most exciting new features and share the learnings from building them!

2026-03-01 17:19:49 CET

- reply

Usability comes first.
- If you want to expose yourself to spam, use nip17.
- If you want to play with incomplete experiments use all the others.
Nip04 if used with proper encryption behind trusted/paid inboxes is a working solution today with acceptable tradeoffs, like it or not. And creates nice incentives to use DM inbox relays.
Privacy is important but if that comes first, I guess you:
- Prefer Monero to Bitcoin
- Always use Tor instead of VPNs
- Run your own AI infra and not using chatgpt or claude
Or not?
It's a hard choice and quite a headache to find the balance, but we need not be enemies based on this.
What we need is a nuanced discussion.

2026-02-26 19:19:28 CET

With #SatShoot you can now configure and view your nip85 Trusted Providers of useful user-related scores:
https://v.nostr.build/1JWgF7MXCLn4HKR1.mp4
Why its useful: Certain metrics help you decide if someone is a bad actor, bot or probably human/good actor. These would be hard to priduce client-side so you choose providers you trust.
So how do you choose providers?
From your client-side verified narrower web of trust!
SatShoot will actually gather public provider info from your narrow trusted network of pubkeys and show who is using which provider.
You can select multiple providers for a "capability" (metric) and compare them.
Capabilities can extend beyond what's defined in nip85 so you can practically gather a bunch of these metrics from WoT preferences and select the ones you find meaningful.
You can verify in SatShoot that metrics are not merely preferred by a user but that metric is actually served by the provider as you saw with "Verify providers" feature.
Then you can go to profile pages and to Analysis that fetches metrics you configured earlier.
This is another one of those features that help extend trust like Vertex does but doesn't actually have an effect on user experience until explicitly following someone.
An important philosophy of SatShoot is that a real digital marketplace is one that you verify but that doesn't exclude optional trusted service providers.
The configured providers will start showing rank metrics on profile icons in #Amethyst client.
This feature was implemented as part of the #wotathon by @npub1hea…vp8p .
Try it at https://satshoot.com

2026-02-24 09:44:04 CET

If you ever wondered why email is broken despite being an open protocol here is a reminder:
Of course today you cannot run your own email sending service realistically, you will be banned in no time. So as @nprofile…vr0z is using anchor (a push and email notif server for flotilla) I wanted to setup my own for BudaBit.
Well, it is not KYC but my account was flagged and suspended immediately after registration. Why? They of course will never tell me the checks they use, completely opaque but my name being causally set to 'John Doe' might be related.
Here's the info they actually ask to review my case:
"
Your account was recently flagged by our automated security system. This occurs when certain patterns are detected that may indicate a risk to our sending reputation. To protect the integrity of our platform, we aren’t able to disclose the specific triggers involved.
....
As your website is hosting very limited information, are you able to share more on:
1. The nature/business model of your business? Could you also tell us what your sites or apps are for, and which industry they belong to?
2. What products or services will you be promoting?
Also, If you have a beta site that is accessible and or screenshots of the site content please share those as well.
Getting to know sending habits of our customers is one of the ways Postmark protects your sender reputation and our overall deliverability, so thank you for your assistance.
"
This is the world without decentralized reputation.
This is going to be massively worse in the upcoming years.
People are not at all prepared for the consequences of this, especially with AI now proliferating.
Trust is eroding. The centralized players haven't the faintest idea what to do about other than KYC the hell out of everyone.
Only #wot can save us now. Freedom tech or bust.

2026-02-24 08:11:36 CET

- reply

No, it's not just auth:
That's why I built Budabit.club , the events are still signed and moderation is a good feature for communities.
- Communities can be interoperable
- Signed events mean forking groups is actually feasible, no other solution has this kind of guarantee.
- You can still keep other things open, and not exclusive: BudaBit keeps code collab features scoped to repo relays (even comments on issues etc) but you have the exclusive group to share things you want to actually be heard targeted to an audience that is there for a good reason.

2026-02-24 07:51:18 CET

- reply

That looks great! Couple questions:
1. Why is my current nip60 wallet not showing by default?
2. Do you only persist the seed(xpriv) locally? If I go to another nip60 client, how is my wallet generating deterministic keys?
3. Where do the mint recommendations come from?

2026-02-23 08:06:38 CET

- reply

SatShoot uses them.
Good for zapping small amounts for sponsored npubs (after you made money as a freelancer you can zap a supported npub) and later could be used for paid services.
The hard parts about implementing them with decent ux:
1. You have to handle state management very well to display a stable balance, and it's also depending on relay stability.
2. In-flight tokens (aka minted but unclaimed nutzaps) are in danger of loss if recipient cannot find it on relays, is offline for a long time etc. Since sender cannot claim those back by default it's slightly risky
3. Mint selection/discovery is crucial and must be addressed in a decentralized way (i.e. personalized nostr-native recommendations)
How SatShoot solves these problems:
1. We introduced seed based recovery (NUT 13) to have a secondary recovery path if you lose nsec or relays screw you
2. We will soon implement NUT-11 to be able to reclaim your nutzaps after a certain time passes and recipient hasn't claimed
3. Web of Trust based mint exploration. Shows which mints are used by your WoT for nutzaps (nip61 kind 10019) and builds a list rank-ordered by how many ppl use a mint.
So it's doable but I haven't seen other clients implement them because this requires quite some work.
Some do use cashu but not as nutzaps but by sending tokens in encrypted DMs.
Not bad at all, I just think with nutzaps you have better guarantees of no double-spending and you can build better verifiable public reputation than with untrusted lightning zaps.
You can experiment on https://satshoot.com with the wallet but it's for freelance purposes so you can't just zap posts (there are no posts).

2026-02-22 17:28:32 CET

- reply

The layered and context-aware solution I believe works and is feasible already:
- It all starts with relays. They must mitigate basic spam. Clients can only filter after they download realistically.
- Clients calculate a naive web of trust and hide everything outside by default (toggle to see filtered content)
- Bootstrapper account helps with onboarding (can be switched off)
- NIP85 trusted providers and requests- response type of social graph services like Vertex help extending your basic wot. Explicit opt-in is better because they're trusted. Client-side wot helps choose a provider, you see which your closest circles use.
- Clients must get better at the trust UX - displaying connection to a pubkey in a compact, informative and context-aware way
The best way to bootstrap trust however is communities.
Everything would become much simpler, and all the rocket-science in the world can't substitute that. Hope they gain more ground.
Nostr is the right tool for the job I believe but a tool is just a tool: We must use it well to achieve substantial progress.

2026-02-20 08:47:21 CET

- reply

That's not quite accurate.
Dig deeper in the headlines you find quite a couple of caveats.
Coding is quite well solved for the most part with AI but working secure reliable software is not (yet). At least not without guidance. It's a sophisticated tool. A very good one.
Doesn't replace taste and values. Neither does it substitute for architectural and product thinking.
Excited to ship more with AI but the job loss narrative only applies to the proverbial code monkey.

2026-02-20 08:47:05 CET

- reply

2026-02-17 19:25:27 CET

Thoughts to ponder #naddr1qp…dcj3

2026-02-16 20:10:28 CET

- reply

I second that

2026-02-14 20:39:56 CET

The ugly truth (and why I still use nip04 and don't give a damn about the true scotsman arguments) :
#nevent1q…y8rk

2026-02-14 20:24:06 CET

- reply

Turns out if you want privacy you must either run sth yourself, pay or trust someone not logging.
No protocol spec can circumvent the economics of this situation.

2026-02-14 08:58:18 CET

- reply

- PRs (merge conflicts, PR updates, reviews, inline comments etc) are being built right now, lot of it is done already.
- Entities outside Nostr: see NIP39 ( https://nips.nostr.com/39)
- CI: We have started to implement the Loom protocol, see this article: #naddr1qq…qgy2

2026-02-14 07:08:23 CET

LET'S SET #BITCOIN CORE FREE!
https://v.nostr.build/RRqVdNDSxaDTM4mI.mp4
Yes, you can now migrate any repo to Nostr, with issues, pr-s and comments.
A couple of clicks in #BudaBit .
This will tag events created by profiles that can be matched to a Nostr account as per NIP39.
> They don't just host our code, they mediate our relationships. When your identity, issue history, contributor graph, and CI tooling are bound to a vendor's database, "open-source" becomes a veneer over a captured workflow.
This is an IMPORTant step for Freedom tech.
#gitvianostr

2026-02-13 20:14:28 CET

- reply

> A real marketplace would let any operator offer compute and any project buy it, without needing permission from a platform, and still get credible outputs. That's the gap Nostr can fill.
#naddr1qq…qgy2

2026-02-12 22:57:19 CET

- reply

#naddr1qv…39s8

2026-02-12 18:27:23 CET

Get your demos ready!
#nevent1q…d3nw

2026-02-12 16:38:12 CET

- reply

Edit: I now think AI can ship spectacularly well-written code so I was wrong on that part. What I still believe is that on the margin human ingenuity is still necessary, especially to build a successful product. However, AI will be essential to make that happen.

2026-02-12 09:02:51 CET

- reply

Just today I thought about this.
Neat

2026-02-11 20:21:21 CET

- reply

Zapstore is rad. Love it!

2026-02-11 20:06:00 CET

Little taste of what's new in #BudaBit :
https://v.nostr.build/yglkCHpcyVigYeTy.mp4
What's on display:
- Browse and bookmark Repos with ease
- Create permalink events: these are snippets on steroids. Contains enough metadata to jump to exact lines of code or to a specific diff context. Share these in any room or thread
- Browse your previously created Snippet collection
MOOAR DEMOS TO COME!
I'll keep posting these demos because it's literally impossible to showcase all the awesome features!
Check it out live to get a taste of what's already possible with #gitvianostr !
https://budabit.club

2026-02-11 07:54:04 CET

I love that #SatShoot has a built-in #Cashu wallet. It is so much easier to pay sponsored npubs with nutzaps, and possibly pay for #Vertex later, and other #wot services.
However... paying for compute is one of the best use-cases of ecash imo. We will make CI/CD into a nostr-wide marketplace in #BudaBit, paid with ecash, for the exact amount of compute.
Marketplaces X Communities.
Stay tuned.

2026-02-09 20:55:00 CET

- reply

And if you want to showcase your work to likeminded builders, apply to BudaBit demo day!
https://budabit.club

2026-02-09 09:15:30 CET

- reply

You forgot to add: "make no mistakes, make it secure"

2026-02-08 18:46:19 CET

- reply

SatShoot is going to implement nip85 soon. I want to grab kind 10040 TA preference of a user and everything would be straightforward if ppl declare their providers.
Will see how the trust scores and metrics can be nicely fit into the ux.
This will decouple SatShoot from the wot service to a degree bc users seelect their own providers external to SatShoot.

2026-02-07 19:06:43 CET

How #Vertex is currently integrated in #SatShoot :
- Search bar that filters page content can be used to search profiles with Vertex
- Brand new pubkeys or pubkeys without vertex credits are sent to buy credits to vertex pricing page:
https://v.nostr.build/UJ08ZYQmpze1bt5I.mp4
- My account has by default some credit allowance and can use profile search as well as analyze profiles with Vertex: verifyReputation method:
https://v.nostr.build/P0icibyX3xfgmDxR.mp4
This is done with DVM-based query. It serves not to replace client-side #wot but to complement it. You want to know more about an npub you potentially want to make a deal with, you can use this to get to know better. Result is cached.
Then you might include this person to your web of trust by following and making a deal. That is how you expand your network and thus grow the business network of Nostr.
Check it out on https://satshoot.com
#freelance #grownostr

2026-02-07 18:43:42 CET

- reply

First bot I followed deliberately

2026-02-07 18:10:23 CET

- reply

Additional confirmation that you got them right.
Could be optional but since I don't show this ever again, better be safe than sorry. Copy-paste works btw for the whole mnemonic sentence

2026-02-07 11:50:32 CET

#Ecash fans alert!
We finally shipped NUT13 in SatShoot ecash wallet!
https://v.nostr.build/2QuGYPmwRAfsqFAW.mp4
What this means: This is the first nostr-based ecash wallet that is backed up by a seed as well.
You are double-protected: ecash is saved on relays, encrypted to your nsec, and additionally you have the seed backup.
Why big deal?
Ecash wallets on nostr have been notoriously unreliable, mostly due to relays and all sorts of state bugs. It is not easy to implement a stateful wallet and if the app loses state (i.e. your money) somehow, you were out of luck.
Your seed allows you to recover from state bugs or relay sync issues.
But at the end of the day your nsec serves as a backup if you lose your seed. That's the neat part.
Try it on https://satshoot.com
CAVEATS:
1. Due to an Amber bug the wallet will not work with amber remote signer. Only try with local key or browser extension login
2. Still experimental! Please don't use it for high amounts
3. Feedback welcome! You can try to deposit on a seed and recover from cashu.me or the other way round! Report bugs and such.
Bonus for the #wot lovers:
Now you can choose a mint based on recommendations from your nostr web of trust! (As shown in the video)
Ecash has two hard problems nostr can help with:
1. Discovery and reputation of mints: From explicit mint recommendations AND implicit nutzap info (which mints ppl want their nutzaps to be received) we can show the user mint usage from his own trusted network. This helps selecting mints for newbies or switch if mints get compromised.
2. Wallet portability: Thanks to nostr relays, your ecash should be synced to all devices. All you need is a nip60-capable nostr app.
Thanks to @nprofile…67u0 for the implementation of NUT13 on Nostr!
cc @nprofile…xnfk

2026-02-05 17:21:44 CET

- reply

Do not underestimate client-side verification. Privacy also much harder with trusted WoT services.
WoT Providers should be optional and ancillary to client-side processing of events.
Also, do you think WoT is not portable when it is calculated client-side?
It is open-source code we are talking about. Anyone can use the same algo.
So:
1. Depends on requirements. Global is much faster and cheaper, but less about you. Should be left to the user. #Vertex does exactly this
2. Standardization I welcome. But there are trade-offs to third-party WoT see on top
3. Yes, user choice is welcome to the degree a non-technical user is NOT left to his own devices by default
4. Agree - privacy is most achievable with client-side calculations or self-hosted services which will be very niche

2026-01-24 12:28:37 CET

- reply

It would be even more private without those UTM params inserted in all links.

2026-01-21 20:10:02 CET

Vibe coding is a slippery slop.
But we dove headfirst into it, and it feels too good to be true.
Perhaps it is.

2026-01-18 19:10:27 CET

- reply

The same inherently insecure architecture that fiat money is.
Users take responsibility and bear consequences = insecure short term, secure longterm
Fiat institutions control almost everything giving little to no responsibility to users = secure short term, insecure longterm
Easy money + centrally controlled identity = weak society, no security, no trust, no abundance.
Hard money + cryptographic identity = strong individuals and society, security, high trust and prosperity

2026-01-18 08:45:40 CET

> Uniquely, every user has their own heavily subjective view of the marketplace. One component of this is relay selection. The other component is past user actions used to build a network of minimally trusted Nostr public keys, known as the Web of Trust (WoT).
#naddr1qq…evs3

2026-01-18 08:38:42 CET

> Enhancement balanced with just enough friction. This is the power of Nostr. Not a fake global view, not a walled garden, and not a purely P2P mess.
#naddr1qq…2ml9

2026-01-16 22:40:18 CET

- reply

You can set up the model temperature in opencode:
https://opencode.ai/docs/agents#temperature

2026-01-16 22:09:09 CET

- reply

You can use any platform you want, even mirror between them but keep them redundant by publishing the state of branches, and other metadata to nostr.
By keeping the metadata on nostr you are not locked in to platform identites and the data is actually portable because it's standardized in a NIP.
Gitea, gitlab, github, forgejo and others give you one model that is hard to migrate and data is not signed by sovereig identities.
In short you are married to their way of things

2026-01-16 21:54:38 CET

- reply

The tools for this either exist or are easy to build.
Relays are using all sorts of content moderation already.
That said, I don't think any software stack on nostr is mature enough to host a project like bitcoin core *currently* but things are movind fast around here.

2026-01-16 21:29:35 CET

- reply

Moderation tools exist for nostr relays already. You can blacklist/whitelist by kinds, pubkeys etc. and use all sorts of web of trust based moderation as well.
#WoT based moderation can be personalized so you can moderate even on an individual basis, seeing only those ppl you actually trust. WoT providers are also in progress to help in these kind of decisions.
Current efforts are spearheaded by the @nprofile…lh4w team

2026-01-16 21:24:35 CET

- reply

Yes, but the #grasp spec can introduce some proactive sync if enabled.
With the benefit of nostr based auth

2026-01-16 21:22:11 CET

- reply

For the source code part git is already decentralized enough, it is not worth trying to censor a repo cloned on tens of thousands of machines locally.
For the social part: censorship resistance is important but it can be a curse, like with radicle which cannot possibly get a decent UX.
As we see with bitcoin, we can hopefully keep one of the most important system decentralized while syncing state every 10 mins.
Nostr trades off with the possibility of centralization around one or a handful of relays, but at the same time it is trivial to backup the already signed messages which are republished any time, anywhere.
Nostr is the practical solution to this problem in my opinion.

2026-01-16 20:31:46 CET

- reply

Forgot to tag #gitvianostr for folks wanting to chime in.

2026-01-16 20:30:47 CET

@nprofile…y7h4 saw yall takin a look at decentralized git solutions and github replacement on bitcoin core discussion:
https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2026-01-16
Here's a couple of sources and Nostr-based solutions you could give a try:
- NIP34 spec: https://nips.nostr.com/34
- GitHub-like client: https://gitworkshop.dev
- Discord/Slack type of client with Git-integration: https://budabit.club
- ... and some others, so there's quite some effort to make code collab work with Nostr
- The grasp spec is also interesting, it is a git server with nostr-native auth, designed to be easy-to-run and to accept code collab oriented nostr events, so a relay is packaged with it:
https://ngit.dev/grasp/
Grasp is the grug-brain solution to what radicle is trying to do for years but I think this has much better chance to work.
Why nostr?
Because it is more decentralized yet much simpler than Fediverse / Mastodon and Bluesky.
All above solutions lack full functionality compared to github but hopefully you can see where this is going.
It is trivial to moderate your relay, be it comments or any other events. Nostr-git is becoming increasingly standardized so your data is portable and signed.
Open to any questions!
cc @nprofile…hk4d @nprofile…xuyp

2026-01-15 17:26:53 CET

Thanks guys for coming to the very first #BudaBit demo day!!
Keep building awesome freedom tech!
Will post about the next one soon!

2026-01-14 02:16:46 CET

- reply

Wallet of Satoshi too

2026-01-13 14:56:16 CET

- reply

Joined from flotilla and see the rooms but can't post, how do I get invited?

2026-01-13 05:01:59 CET

- reply

I'll also try that soon!
Want to run it on ThinkPad t14 g6

2026-01-12 12:39:49 CET

#Vertex is now integrated in #SatShoot :
https://v.nostr.build/TPbZFDTdP5fotNgs.webm
- Uses 'verifyReputation' with personalized pagerank, and gets top 5 followers
- Displays if current user follows any of the top 5
- Result is cached and user can refresh data on demand
Users must currently top up their Vertex account credits after they use up the free credits. SatShoot cannot sign requests on behalf of users at the moment, and I don't know if I want to do that.
It would mean I need a premium subscription system instead of #V4V business model
I think as soon as @nprofile…mwqz implements a way to programatically top up Vertex accounts, that will be the direction. Users can then buy Vertex credits from inside SatShoot.
#wot #dvm

2026-01-09 17:39:36 CET

Keep churning the BIPs, BOLTs, BLIPs, NIPs, and whitepapers.
I'll be shippin stuff in the meantime.
#SatShoot #BudaBit

2026-01-08 16:02:00 CET

- reply

Hey there, the link on your official website seems to be broken:
https://zap.stream/nosfabrica
Gave me:
https://i.nostr.build/I2bLAAP8UhBsfe6O.jpg

2026-01-07 17:49:52 CET

- reply

Value for value needs to incorporate (optional) vanity/status based features to go mainstream. In a way that already happened but we can do much better.
1. Data that's not taken from the past 15-20 years of high internet adoption doesn't matter too much
2. Ads vs. V4V doesn't need to be contrasted sharply: if I showcase the top zappers or make up some other leaderboard of zaps, is that advertising? Yes, to some degree but not totally.
3. What we really have established is that attention is valuable. 'What *kind* of attention?' - is a better question to ask. The flip side of this from v4v perspective is that donating without getting attention and acknowledgement back doesn't work very well
4. So what Adam Curry says about "You just need to ask often" is not enough, you need to do shoutouts, leaderboards, publish summaries, and generally do everything you can to make donors feel special and raise their status. No way around that if you want to take this seriously.
5. Yes, it is hard to do the core thing and this other promo thing too, but that's the way it is. The internet allows more publishing so creators need to stand out by being unique in their craft and also make that obvious, and get creative not merely in the product itself but how it is received. That's not unfair, that is competition
6. Are software developers the same kind of creators as musicians, podcasters, or long-form authors? Don't think so, and there are different nuances people can try to make this work.
The big picture in my book is that this topic is not settled by far. We just need to get more creative.

2026-01-04 15:15:05 CET

- reply

Remember this fun project "note duel" by @npub1u8l…turz it worked with adapter signatures.
https://github.com/MutinyWallet/note-duel/tree/master

2026-01-03 17:27:12 CET

- reply

Fixed this, should work now after reloading page

2026-01-03 17:13:52 CET

- reply

Thanks for reporting this.
Bitcoiner.social relay seems unresponsive and SatShoot is using it for bootstrapping. Will fix in a minute.

2026-01-03 07:59:52 CET

Very cool project, check it out!
Home Mining X Nostr zaps ⚡️🤝⛏️
#nevent1q…fh8p

2026-01-01 12:56:33 CET

If #ecash wants wide adoption, users will need easy discovery of trustworthy mints, even niche ones, serving local communities.
This discovery cannot rely on centralized parties, the obvious and only choice currently is Nostr #WoT .
It is to verify not just that mints haven't rugged yet, Nostr can provide data on:
- Uptime Reliability
- Zap volume
- Data on all audits so far
- ... and kinds of signals of trust
Of course this can be provided live which comes very handy!
This way new users can discover possible new mints and make responsible decisions which to trust.
On the other hand, current users are the watchful eyes over them, vigilantly enforcing the trust that mints were given.
Bitcoiners often make the mistake of only thinking in terms of one system, one protocol, or maybe bitcoin and its layer 2s at most.
What nostr brings to the table is a social protocol orthogonal to others like payment-protocols but very much complementary.
Ecash has trust issues, and Nostr mitigates these in a simple way.
Never underestimate the power of the authentic social layer, tied together by cryptographic proof.

2025-12-31 18:02:47 CET

To end this year in proper PoW fashion I implemented #WoT indicators on Avatars in #SatShoot :
https://v.nostr.build/aOFw1jZwh95FMOXJ.mp4
The circle-borders indicate who's part of your WoT and who's outside. Profile pages show more info and explain in a tooltip.
"Blocking" actually uses kind 10k mutelist to make use of already gathered mutes in SatShoot.
You probably don't want to engage in business with explicitly muted ppl.
Next up: On Service and Job feed pages user will be able to toggle WoT filtering.
The philosophy of SatShoot is that we whitelist and everyone else shows up as "untrusted" and hidden from feeds by default.
This however hurts exploration for new users so there are ways we encourage forming of new relationships:
- DMs and "Freelance follows" punch through WoT filtering
- We encourage sharing of jobs/services via kind1 and URL copying, this can land users on profile pages and job/service landing pages where WoT filtering is not applied
- Search bar also accepts any job/service/user
- If you submit a Bid/Order and you don't follow the target, you are prompted to do so
- Toggling the WoT filter will encourage exploration as well
So heavy filtering is applied but in the end there are plenty of mechanics for users to connect.
Soon I will also implement #Vertex for SatShoot users to gain even more info on "Untrusted" users.
Note: WoT affects visibility and is the filter for events used in Reputation calculation.
Reputation in SatShoot consists of Zaps (money paid as client or received as freelancer) and average ratings from Reviews. It is strictly contextual to freelancing, e.g. zaps on posts don't matter.
WoT is to get on the radar of minimally trusted users.
Reputation matters to actually make a deal.
Will submit the full implementation with Vertex to the #WoTathon and see what others have to say!
#freelance

2025-12-31 07:19:46 CET

427 hours of podcast this year so far.
1 day to go.

2025-12-30 13:41:40 CET

Am an operator myself and love how nostr is gradually eating the lunch of all rent-seekers of the networking stack:
#nevent1q…4s36

2025-12-28 09:40:44 CET

- reply

What if the relay has an outdated record? In a multiple-relay scenario the client might have the latest state synchronized from multiple relays, but the relay that has outdated info will not allow "force push".
Otherwise can you explain how a nip60 wallet get rekt exactly from a race condition? Token events are not replaceable.
I found these scenarios to be problematic:
- relays deleting token events
- app not being able to publish new token events (signing and publishing are async), especially nutzaps
- nutzaps getting lost on relays
- spent tokens disrupting user-experience (unexpected change in balance)
So state management is an issue with Nostr wallets, and precisely that is why SatShoot went the NUT13 (and perhaps later NUT14) way - with the seed based wallets you get double protection:
1. Nostr stores your state on relays so even if you lose the seed you can swap to a different one. Mitigates losing local state as well
2. The NUT13 seed protects from relays deleting, censoring or losing your nsec - an additional hedge on nostr state. Like a recovery code to an account. @nprofile…twvn extended the nip60 spec so the NUT13 counter can also be synchronized to nostr.
NUT14 is important because it makes in-flight payment state atomic. If the nutzap is not redeemed the money is not lost.
Sadly, I haven't found well-maintained apps with nip60-61. A few apps use it with outdated specs and none of them work with the latest spec, using both nip60 and 61, other than #SatShoot

2025-12-27 10:41:22 CET

Are you already planning your next moves as a builder in freedom tech?
Tell us about it!
The best way to do it is applying with your demo on https://budabit.club !

2025-12-25 08:52:56 CET

- reply

Yeah perhaps that makes sense

2025-12-25 08:37:11 CET

- reply

https://ngit.dev/grasp/
It is git server with nostr auth and more. Kinda what you are doing just more efficient for git.
#Gitvianostr pioneer @npub15qy…yejr designed it, @npub180c…h6w6 and others are already migrating to this spec.

2025-12-25 08:32:23 CET

- reply

Read July 18th from @npub1hqa…t56s , it is perfect Christmas reading for me!
It is crime, mystery, bitcoin... love it so far!

2025-12-24 15:26:50 CET

- reply

Are you aware of grasp?

2025-12-22 19:35:35 CET

- reply

Good idea!
We can add this with a feature flag to start experimenting where it would fit in the user experience - perhaps a tab under the repos.
We can then make kanban boards available on the test page.
I know some people love kanban boards but I tend to either use issues OR kanban to keep things simple. Often I see if both are present, it becomes a bureaucratic double accounting.

2025-12-22 07:18:37 CET

When I found Bitcoin, I was mostly alone with my thoughts and my plans to reorient my life around PoW and decentralization.
I've always been fond of doing things in a community though, so when I learned there were no active meetups in Hungary I started one.
Now that's officially part of the "twentyone" family of meetups:
https://portal.huszonegy.world/hu/meetup/budabit-cypherpunk-meetup .
Thanks for the awesome website @nprofile…9lpv !
But to me who is working on freedom tech full time, a monthly meetup still wasn't enough:
I started #BudaBit for all builders and aspiring devs in freedom tech to connect, share and collaborate like never before.
It is an attempt to transcend the platform model for open-source development, and bring it to the next level: Community driven development, powered by Nostr.
BudaBit Demo Day is part of that plan:
What I've found on my journey is that feedback is essential to the process, and it is not easy to find people who get it and can provide valuable feedback.
If you're a builder in freedom tech, this event is for you! Go to https://budabit.club for details!

2025-12-21 14:58:49 CET

📢 ANNOUNCING BUDABIT DEMO DAY
Have you got something exciting cooking in Freedom tech?
It's time show it off to an audience that truly cares!
Early next year I am launching BudaBit Demo Day - a regular event series focused on Builders in Freedom tech! 🤙
Want to get honest feedback on your project from other builders in the space?
This is your chance then!
Go to https://budabit.club for details, and **apply with your demo today!**
Spoiler alert!
Everyone’s invited but only the best are chosen! 🏅
PS: If you got friends in the space, please share!
I created BudaBit for all freedom tech builders to find inspiration, get feedback and supercharge their work with the power of Nostr!
Haven't got a demo to share just yet? You are still invited to the party! Come, get inspired and provide constructive feedback to the presenters!
#budabit #gitvianostr #ngit #community

2025-12-19 06:10:22 CET

So bullish every time I listen to @nprofile…sxzq talking about #wot !
We need optimistic builders tirelessly working on the proliferation of nostr and the new trust model:
#nevent1q…el2c

2025-12-16 18:18:53 CET

- reply

Sure, in your case because you designed it that way.
I can imagine a service that queries some data from another service as _part_ of the end result, but the user is hitting your endpoint.
Anyway, what you *can* do with nostr is hitting any service with *any* pubkey - meaning you can decide to pay for your users or make your users pay for it directly, or some other clever combination.
IP addresses don't give you that freedom - it is not a good idea to use them as identity on the internet, so you see most paid services requiring an account.
Nostr could be that account.