Five

I ship freedom tech

Public Key

npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw

Profile Code

nprofile1qqsdqnk0xw3s8fvc2t7mdq0d3dqjyqd6shvdyxv6a3eukcngr4324yqpzpmhxue69uhnzdps9enrw73wd9hszrmhwden5te0vyhxummn9ekx7mq5ruu85

Publishing to

2jsnlhfnelig5acq6iacydmzdbdmg7xwunm4xl6qwbvzacw4lwrjmlyd.onion

Author Public Key

npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw

Show more details

Last Notes

2026-07-09 05:13:26 UTC

- reply

Do you think Spark and Ark require comparable fees to exit unilaterally? Have you seen a similar study for Ark?
This data liveness requirement is painful but I think comparable to the pain of expiring VTXOs in Ark. There you already always have the state to publish for the unilateral exit but you (wallet or watchtower) must monitor the expiry deadlines.
Of course the other thing is that ark operators are less trusted since they cannot conspire to steal funds.
However I still love Spark because at the end of the day operators don't have enormous liquidity requirements and this will make a big difference in adoption.
Also in Ark has that constant periodical refresh from user wallets, that doesn't look good to me. I don't necessarily open my wallets every month and this is going to be a problem when a lot of users realize this (or have to pay extra for a refresher service).
All in all love the innovation of the L2 space

2026-07-08 10:46:15 UTC

Depending on closed platforms will never pay off.
#nevent1q…8cv8
People expect a baseline convenience with any product though and freedom tech is no exception.
There is nothing holding us back to design our apps with pragmatic defaults.
That is not centralization but caring for users.
Nostr is the real free market for apps and services. The one's not caring enough will be weeded out. Bullish on that sentiment.

2026-06-23 16:35:03 UTC

- reply

Anyone implementing the same set of rules ie the subset of the nostr protocol most agree on will see the same events and the rules can be enforced server side optionally as well.
What I struggle to understand:
1. If you have your own self hosted relays and git servers where you can enforce rules to the extent you want how is that different moderation from Forgejo
2. If I fork and mirror your forgejo instance and maintain a bridge, then develop a client that views both sources, how is that different from what you describe as the issue with nostr?
Forgejo is open source so anyone can build this easily today. You're not bothered by that?
Nostr gives you signatures from sovereign IDs and standard data modeling, so it's more neutral.
Everything else I see comes down product specifics.

2026-06-23 08:44:04 UTC

- reply

BudaBit.club has fine-grained client side enforced moderation features.
However, I understand currently you guys want a tried and tested grug brain solution.
Would love any feedback though! If you get the time, it's just a few minutes to create a test group.
Nostr is easy to hack on so custom solutions can be built relatively simply. You wouldn't be married to forgejo as a platform and make people use dozens of accounts to talk about bitcoin and do basic collaboration.
I know IRC and old forums have their vintage charms but we can have open solutions with good ux today using nostr. Even moderation becomes easier since nostr keys can be used in multiple places so you have more context to work with. AI issues also become much more tenable this way.
Anyway wish you guys success with the migration process!

2026-06-22 14:13:27 UTC

- reply

- Getting the right phone is not trivial. Product descriptions suck mostly and it is quite important in this case
- I got through installation fairly easily being a dev but there are many people who would not. Jargon heavy explanations and lots of custom steps depending on the platform of the machine it's installed from. Some trusted distributor should sell pre-installed devices if not yet the case.
- Google pay and wallet does not work. I know why that is, fiat is painful
- For some reason google account login does not trigger for me
- Contacts had to be manually exported and imported
- Signal can be a hassle to migrate from manual backup. Generally less user friendly migration and linking to other devices compared to captured instant messaging apps
- Many settings are not clear what they do and I don't think most people need 'hardened memory allocator' or such settings. They should be behind an advanced mode
- Also "xyz app used play integrity api" doesn't mean anything to most users, I would expose that differently
- Great variability in experience depending on how private and secure someone wants to be. For me iVPN blocked all network connections when VPN was off. I switched off because gmaps would not load directions while on VPN. The number of such hard to troubleshoot issues will grow as we march towards apps and services heavily relying on captured infra
Storage scopes are a good idea but I find it hard to fine tune all apps and then debug yet another set of issues due to apps nowadays asking for too many perms. Sad reality.
- Silent link and esims also hard to deal with but most people won't go there I guess
These came to mind

2026-06-21 17:35:02 UTC

- reply

I think people caring for #gitvianostr should join the fray here:
https://github.com/bitcoin/bitcoin/issues/35574
@nprofile…cy6q @nprofile…633s

2026-06-21 16:48:45 UTC

Gradually then...
https://blossom.primal.net/4248342f43411f6b24c9841171d3e84cdd089102b279e26b71b31f82cec9d6bd.jpg
@nprofile…mrj5 many have moved to forgejo / Codeberg for the forge and CI e.g. Zig and Ghostty I think. Nostr-git should work better for a public facing open project though, at least in the long run.
If you want to experiment with a moderated social development experience I am keen to hear feedback on #BudaBit :
https://budabit.org
We plan to roll out CI over nostr soon, each community providing for their members for free or for ecash.
Then releases signed with nostr keys.
#gitvianostr

2026-06-13 16:36:34 UTC

- reply

I am convinced that in order to hedge the dependence on data centers we need specialized communities incentivized to run infra for their members.
For git servers, nostr relays and blossom media I see this sufficiently solved now that I built BudaBit.org.
There exists a fallback path to individual infra of course but the right order is not service provider -> individual, but community infra -> individuals, with community leaders using cloud providers and well maintained self hosted fallbacks.
Communities can form a resilient network that mostly makes platforms and cloud providers redundant commodities, especially with nostr discovery.

2026-06-12 17:22:21 UTC

#BudaBit is coming nicely together:
- Create repos on any platform or forge, control on nostr. One primary remote, any number of mirrors, automatic fallback, health checks and backfilling
- Import repos: Import with or without the social data: PRs, issues, comments. Get started easily
- Full fledged repo browsing and collaboration
- Your community, your fine-grained rules: Add new members and moderators or create forms to fill in.
- Event or person moderation, reporting to moderators for review
- Rooms, Forum threads, Calendar events
- Community-first Web of trust and discovery
-... And much more!
https://blossom.primal.net/d27f589cfd0e6e4eba77bcc209b5ee6582e1066f2f012739ab0fb8ed5b7f7a2d.jpg
https://blossom.primal.net/48b4b3c1bd2bb723c0e5e62bf9fd99695e8aa3f7d10410e73f314d892575a584.jpg
https://blossom.primal.net/161598c06fcad3a436448b845efb4092378cc2ec12cc8ad4c5d5064cd3ac40a6.jpg
https://blossom.primal.net/d35ddbb9fbce6885244b1440b19e8f2d793228ed5b0a3e44ba3e61e08a4075c9.jpg
https://blossom.primal.net/9db2a79f742248153f5357cffee8308e59f7f2b197cdf7e838a3b49a58526d87.jpg
https://blossom.primal.net/a9acaa73d91eabc2ef6611d402b004a3853a60e4970dac687794fb17686832ac.jpg
However I am going to increasingly put more effort into building BudaBit the community in physical as well as in Cyberspace rather than spending most of my time with development as it is now.
We must build the future in meatspace just as much, and now that this is usable enough we need to fill it with people who care.
Care for freedom and the future of freedom tech. I will strive to nurture this ecosystem through running my own community and help others run theirs.
So reach out if you're building sth interesting and want to be part of this new community-driven development experience, or want to start your own group!
Share with people who are eager to jump into the wilderness to leave the big tech dependence behind.
Cheers

2026-06-12 15:48:02 UTC

- reply

How easy is it to plug in custom logic for access policies? Does this relay support such a thing?
In BudaBit I have kind-scoped write policies and a custom moderation engine.
It's enforced client-side but would want to mirror that server side optionally. Almost like nip72 just a bit more sophisticated.

2026-06-11 15:54:53 UTC

- reply

Yes, certainly hope so

2026-06-11 05:00:37 UTC

- reply

And so I can have a documented plan with a separate phase checkpoint doc if anything goes wrong and for easier continuation

2026-06-11 04:58:34 UTC

- reply

Codex has it too, opencode doesn't. It's fundamentally a persisted session goal but I found it does too many things auto-pilot so I just designed a similar but more explicit prompt template that I use with a slash command in opencode.
With token budget becoming more of a concern I want to have more control over automatic execution and less implicit opaque prompting like /goal

2026-06-11 04:50:13 UTC

- reply

Good point. So how is this different then from Bitcoin? In that sense Bitcoin is the same as tulips and AI

2026-06-10 17:22:11 UTC

- reply

So you think AI will fade into oblivion?
People overdo things, bubbles burst but that doesn't mean it's going away.
Literally all tech adoption is like this once the utility is identified and adoption accelerates

2026-06-09 17:40:06 UTC

- reply

I'm on GrapheneOS but reality is there will be an increasing number of apps that will be unmaintained like you said, and others you would still need like payments and banking apps that implement the play services API and won't work on graphene for long.
Tap to pay is sth many don't want to just let go it's too convenient for them.
And I estimate more and more websites will just stop working in Chromium based browsers like Vanadium.
The two worlds are splitting at an accelerated rate now.

2026-06-09 12:28:48 UTC

https://blossom.primal.net/1998ac02bf840640b3851d4b824d0aa5f3978489a64b9310538cbfe3711a5f1a.jpg
https://keepandroidopen.org/

2026-06-07 15:34:14 UTC

- reply

Glad to see this coming alive!

2026-06-07 07:15:01 UTC

Want to build your own sovereign community around your software project?
Tired of having to use GitHub with a separate set of social tools like Discord, Telegram or Matrix?
Take a look at
https://budabit.org
BudaBit takes a community-first approach to software development unifying public collaboration with deep nostr-git integration and community-curation as a first-class feature:
- Create and manage Git Repos existing on GitHub, Gitlab, Gitea/Forgejo and self-hosted servers. Import your existing ones with ease! Keep projects mirrored on multiple servers powered by Nostr nip34!
- Code browsing, Issues and PR workflow
- Full-fledged Moderation UX with fine-grained content-scoped permissions
- Chat rooms, Forum Threads, Event Calendar and Fundraiser goals. Everything to keep your contributors and fans engaged! Get funding support from the thousand true fans and reward them with your own bespoke badges!
- The community can curate important Repos and code snippets to its own collections. Admin and moderators can grant access to members to distribute the effort
- Running Community infrastructure is optional but a good opportunity to monetize your efforts with a paid #blossom server, relay or git remote
- No special relay needed like with NIP29 groups!
... Soon Nostr-based CI! Anyone will be able to offer CI via nostr offering it free for selected people or for #Cashu ecash!
There's no real reason to stay locked into platforms now!
Join the developer community network, running exclusively on Open Protocols!
#openprotocoldevelopment #opd #BudaBit

2026-06-05 04:42:40 UTC

- reply

Looks exciting! Can you run dev agentic tasks from mobile this way live?
Would you curate this repo into the BudaBit community?
You can join our nostr-git club on https://budabit.club. Your repo will show up I see you already use ngit.
You can star this repo into the community collection there for everyone to see

2026-06-04 05:34:53 UTC

- reply

Use forgejo it is supposed to be better

2026-06-04 05:29:49 UTC

- reply

Nice! Hope you get some traction, will try it to see if I can recommend this for BudaBit communities!
PS: I miss TGFN :)

2026-06-03 07:32:55 UTC

A platform is highly stable but very much trusted to one entity. Freedom tech is an attempt to introduce multiple user-facing entities to solve the same user need:
A marketplace app can offer remote signing, relay choices, ecash mints, Lightning services and blossom servers for media - none of those he is responsible for. This reduces stability but offers optionality - more freedom.
The key is designing a system that is flexible but stable enough. The missing piece in Nostr to become usable freedom tech is communities.
They are pillars of stabilization without capturing the user in a platform that packages everything into one product.
Communities are not faceless companies and provide a much stronger model for nostr to not be a completely chaotic mess neither a platform.
Look at the client app you are using right now:
Try to count how many pieces it contains that you use directly. You can ask your agent if the source code is available.
And then count how many people you actually exchanged words or messages with, that are responsible for those pieces.
The number of user-facing entites a solution contains has a practical minimum and maximum.
I cannot call Freedom tech where this entity number is one. That is a platform. But usable software has an upper limit as well and this is something we still have to explore.
Software following protocols like Nostr can increase this number and still be usable. They are "APIs over APIs". But realistically we can hardly agree globally about almost anything and the NIPs repo is the proof of that.
A community bundles the choices of the leader - someone who truly cares and has taste. They reduce the burden of choice in freedom tech. This models nature best and I can hardly imagine "sovereign identities" without any community association at this point. Not even for communities. They can form relationships with others as well, and they should.

2026-05-31 18:33:22 UTC

- reply

#nevent1q…y3dm

2026-05-31 18:28:07 UTC

Shipping software or seeking interesting technical conversations rather than a doomsrcoll experience?
Now is the time to join or create your own moderated sovereign community, just a few clicks:
https://budabit.org
#grownostr #devstr #communikeys
cc @nprofile…5s7u @nprofile…8mrq @nprofile…nsnk @nprofile…cy6q
We have been polishing community UX for a while now, and I can say #BudaBit is already a fully usable community experience with nip34 #gitvianostr deeply integrated.
We'll keep being laser-focused on high-signal easy-to-moderate technical communities so the future won't be locked into walled gardens like github.
Keep shipping.

2026-05-24 04:07:47 UTC

- 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-23 17:27:47 UTC

The problem with social media of any kind is that we by default become politicians in a lose-all game of popularity, spiraling into a race to the bottom.
Nostr can change that but not by trying to fit the protocol to social media. It's the right primitives used in the wrong way and it is destined to fail.
What we need is strong communities forming resilient networks, with easy forking/exit guarantees.
As for specs NIP29 and 72 were close but not quite there. I am betting hard on #communikeys from now on designed by @nprofile…4s8y , slightly tweaked and extended to my taste. The most important primitives are in place, now testing moderation features and adjusting #BudaBit to this spec.
You can already start a community at https://budabit.club to or look at the BudaBit community:
ncommunity://0a8ecba4868c13e1e84cc5cb58c02c1fd0880d9e5a25a5050ee96ad8a166d7c8?relay=wss%3A%2F%2Frelay.primal.net%2F&relay=wss%3A%2F%2Fnos.lol%2F&relay=wss%3A%2F%2Fbudabit.nostr1.com%2F&relay=wss%3A%2F%2Frelay.damus.io%2F

2026-05-20 13:43:22 UTC

Package managers and platforms getting rekt over and over again.
The "Trusted third parties are security holes" mantra playing out.
But what can we do? Ditching these big platforms and service providers would leave a big hole for the ecosystem. The classic issue of getting addicted to something and suddenly realizing that cold turkey is really painful.
This is true on so many levels, not just software engineering. Living in big cities, sending our children to state-licensed schools, buying food in supermarkets.
Platforms. Faceless services. Monolith companies. Too many layers of abstraction. Too far removed. Of course we will have serious trust issues and backlashes from this system but we can't make a decent alternative based solely on the "Sovereign Individual". It's a myth.
In real life only concerted effort makes substantial changes in the way we do things. Satoshi had like a thousand serious bugs in Bitcoin when he released it. It was a genius design. But it needed years of polish from hundreds of people in the community to make this usable today. And still does.
The missing layer has always been the community. Those dozens or at most hundreds of ride or dies.
These Communities can form a network that produces proper liquid markets and a culture without the central points of failure and the chaotic mess of what it means to do this all by yourself.
Sovereign Individuals don't exist.
Tyranny is terrible but it's the default.
Community networks is the antidote.
It's the model of #BudaBit

2026-05-19 09:39:07 UTC

- reply

#nevent1q…fkpc

2026-05-18 06:16:51 UTC

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 17:39:51 UTC

- reply

Second that

2026-05-14 07:01:53 UTC

- 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 07:25:28 UTC

- 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 17:28:53 UTC

- 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 08:42:53 UTC

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 17:46:58 UTC

- reply

#gitvianostr

2026-05-01 13:57:53 UTC

People are whining about centralized enshittified platforms like citizens of a democracy about politicians.
Especially GitHub lately. Solution? According to whining users of subsidized CI and hosting, the people are at fault: Replacing the scapegoats and getting better leaders. Perhaps migrate to another platform if this doesn't work.
Cypherpunks write code and design protocols.
They realize that the given word is not enough because relying fully on it incentivizes empty promises. This spirals into a chaotic world without any trust whatsoever.
We build software that requires low trust, so people can trust each other and the system again: A system not merely based on people but cryptography.
Bitcoin is the flagship product of the cypherpunks. Nostr-based markets and communities make coordination of prices and people unstoppable. It's the natural next step for freedom to flourish.
Keep shipping

2026-04-28 05:33:06 UTC

- 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 06:03:56 UTC

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 05:08:25 UTC

- 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 17:16:18 UTC

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

2026-04-03 04:57:35 UTC

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 06:21:29 UTC

- 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 07:21:30 UTC

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 06:39:11 UTC

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 18:51:48 UTC

- reply

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

2026-03-13 06:09:31 UTC

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 18:07:53 UTC

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 06:32:15 UTC

- reply

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

2026-03-10 06:25:15 UTC

- 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 18:07:11 UTC

- 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 18:44:53 UTC

- 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 16:51:17 UTC

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 15:31:08 UTC

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

2026-03-04 14:34:25 UTC

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 11:30:49 UTC

Relay.tools down @npub10np…tl5h

2026-03-03 16:53:14 UTC

## 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 16:19:49 UTC

- 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 18:19:28 UTC

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 08:44:04 UTC

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 07:11:36 UTC

- 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 06:51:18 UTC

- 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 07:06:38 UTC

- 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 16:28:32 UTC

- 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 07:47:21 UTC

- 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 07:47:05 UTC

- reply

2026-02-17 18:25:27 UTC

Thoughts to ponder #naddr1qp…dcj3

2026-02-16 19:10:28 UTC

- reply

I second that

2026-02-14 19:39:56 UTC

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 19:24:06 UTC

- 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 07:58:18 UTC

- 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 06:08:23 UTC

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 19:14:28 UTC

- 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 21:57:19 UTC

- reply

#naddr1qv…39s8

2026-02-12 17:27:23 UTC

Get your demos ready!
#nevent1q…d3nw

2026-02-12 15:38:12 UTC

- 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 08:02:51 UTC

- reply

Just today I thought about this.
Neat

2026-02-11 19:21:21 UTC

- reply

Zapstore is rad. Love it!

2026-02-11 19:06:00 UTC

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 06:54:04 UTC

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 19:55:00 UTC

- reply

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

2026-02-09 08:15:30 UTC

- reply

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

2026-02-08 17:46:19 UTC

- 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 18:06:43 UTC

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 17:43:42 UTC

- reply

First bot I followed deliberately

2026-02-07 17:10:23 UTC

- 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 10:50:32 UTC

#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 16:21:44 UTC

- 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 11:28:37 UTC

- reply

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

2026-01-21 19:10:02 UTC

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 18:10:27 UTC

- 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 07:45:40 UTC

> 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 07:38:42 UTC

> 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 21:40:18 UTC

- reply

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

2026-01-16 21:09:09 UTC

- 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 20:54:38 UTC

- 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 20:29:35 UTC

- 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 20:24:35 UTC

- reply

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

2026-01-16 20:22:11 UTC

- 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 19:31:46 UTC

- reply

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