Avatar
Five
d04ecf33a303a59852fdb681ed8b412201ba85d8d2199aec73cb62681d62aa90
Bitcoin and Nostr FTW Freedom Tech dev

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.

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

427 hours of podcast this year so far.

1 day to go.

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. nostr:nprofile1qqs8rheprycaymhyzysa99dag09u0cuz2p0rxw6uz02qzm8dj4pdn4cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszgrhwden5te0dehhxarj9ejkjmn4dej85ampdeaxjeewwdcxzcm99uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59u2ftwvn 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

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 !

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 nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr designed it, nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 and others are already migrating to this spec.

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.

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 nostr:nprofile1qqsq4hm8gawvch9y2m7nqghydaw4ym4s4a3gf0u9f9xqm4uy0ul9qvcpremhxue69uhkstnrdajxjmn8v9ex2mnp9e6x7up0da6hgcn00qq3zamnwvaz7tmwdaehgu3wwa5kuef0qyd8wumn8ghj7am0wshxxmmyd9hxwctjv4hxztn5dacz7pf9lpv !

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!

📢 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

So bullish every time I listen to nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4auspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshse9sxzq talking about #wot !

We need optimistic builders tirelessly working on the proliferation of nostr and the new trust model:

nostr:nevent1qqs0hhy6nc8eu6wn9wk9ndupyafa87n3d38fhh5psyy3dcr9pzjp0zgpz9mhxue69uhkummnw3ezumrpdejz7q3qtrustldqg4fnp40f3g75mu0p03zj4dxpa4jg7dclzqp9g3aunsgsxpqqqqqqz8del2c

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.

Of course you want to present your best case to get back a valuable account. There's nothing surprising here.

The problem is when people start accepting bullshit harmful narratives like "There's no smoke without fire" or "He really shouldn't have pissed them off now he ruffled too many feathers".

... and get back to business as usual. Stories like this point to important truths about the current reality: We are controlled and this could happen to anyone, REGARDLESS of what he did.

Like that idea.

More power to you!

The more options the better, and I think in the long run if any of the clients are successful they will have some kind of native app.

The web has its limits and is really bloated indeed.

For me it's just a problem above ca 10k users. It's cheaper, faster and easier distribution on the web today.

I can relate to that btw.

But here's the thing:

Once I learned how easy it is to censor native app distribution I realized I won't put my efforts into a project to then have a petty bureaucrat at google or apple gatekeep my app.

But I guess now I will have to properly redirect the .org :)

nostr:nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppyspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qa3xytq fountain subs are buggy.

You say sub from $5 (5.530 sats) which is then converted to $55.30 incorrectly and that amount is calculated in sats (61.162) .

This is a serious bug fix it soon.

nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgkwaehxw309a3x2an09ehx7um5wgcjucm0d5hsvlnggv Trex stopped working, cannot browse events on my relay.

It's not showing any events when I put in a specific kind that must exist (eg kind9 as chat msg). Tried desktop and mobile, neither works.

Otherwise curious about this issue as well:

Can't auth to my relay with nak, but only when I want to send events.

Returns "Failed... you must auth"

I gave it the auth flag and otherwise when I run "nak req ..." it works.

Only problem is when I want to post.

Other relays also auth alright (e.g. filter.nostr.wine)

Appreciate your help.

Due to the nak problem + trex not showing I cannot delete any events from my relay.

Hey Nostr,

Please help me with this issue and I can pay sats for your time:

## BudaBit Landing page and Home page design and implementation

#BudaBit is the community for builders in Freedom tech.

It enables limitless possibilities for devs to connect, learn, share and contribute.

BudaBit connects mentors and mentees, contributors to projects, helps find code and concept reviewers and much more, to be the epicenter of freedom tech development.

We are very close to announce v1 and start community activities.

I want to express this in a nice LP and community Home page.

Only apply if you can implement your design (Svelte 5, Tailwind css) , Figma is not enough.

Landing page from scratch, Home page must be modified / adjusted / redesigned possibly.

Current home page: https://budabit.club

We go through your concept and implement in steps. The usual drill.

Point me to your portfolio if you apply. State your estimated delivery time and your price.

Make a bid on this URL:

https://satshoot.com/naddr1qvzqqqrllupzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sqy88wumn8ghj7mn0wvhxcmmv9uqsuamnwvaz7tmwdaejumr0dshsqs6zw4jxzsnfwsk5cctwv35kueedwpskwefdv9hxgt2gdakk2ttsv9nk2ttyv4ekjemw94skuepdd9khqmr9d4jkuarpw35k7m3dv9mxvefhv56q5nvp

#satshoot #asknostr #freelance #design #web #budabit #landing_page #home_page

Today I started to implement a new #WoT UX for #SatShoot .

Client-side Web of Trust is already working, taking extended social follows, mutes and reports into account.

New users are bootstrapped with SatShoot account follow network (can be switched off in settings)

Plan for improvements:

1. Implement Mutes as blocklists. Network (ppl you follow) mutes can remove from WoT but user-mutes (kind 10k) will hide blacklisted ppl from Services and Jobs feed.

You can still land on a profile page or service/job landing page of a blocked user avatar will be shown as blocked. DMs will be blocked from these ppl and there's no way to allow them in Reputation calculation. Only affects visibility

2. You will be able to show/hide ppl outside WoT in Job/Service feed

3. I will implement #Vertex analysis in Profile pages. I will query top 5 reputable follows (personalized). I will make this feature paid (thinking 100 sats / query) but Vertex is not yet able to handle ecash or LN payments easily so I will get some credits myself.

I'll cache the result so it will be reusable. Will show the user if he follows any of those reputable followers of the analyzed pubkey.

I think of this as sort of a fallback or extra info for the user to be able to trust more and eventually follow people in freelance context (kind30k) which is explicit trust in SatShoot.

Later community memberlists of uswr can be added as well, when they come alive.

Plan to demo this in the #wotathon later.

Thoughts?

#devstr

Both APIs you mention live off donations. This is not really feasible for the whole internet.

Furthermore, they still apply rate limiting and such to not be abused. What if I want to run a service that puts heavy load on the that api but am ready to pay for it?

IP based rate limiting is a primitive technique compared to what Nostr offers.

If you want curated data sustainably you will need authentication and you are better off with a paid service beyond a threshold for sure.

If on the other hand some successful service goes rogue you will have much better guarantees to fork that service and jailbreak the data, if it uses signed and standardized Nostr events.

Otherwise your left with unverifiable data that only makes sense in a proprietary format that no one else uses.

The primary issue in my mind is that the api-s don't follow one well-defined standard, like signed Nostr events queried with filters.

This way you don't have to keep rewriting interfaces, and all data is verfiable.

The "closed" part is tricky: Even with wide-spread Nostr adoption I don't think that we would have completely free access to data.

Data is precious and people will protect it with digital fences, even if everything is signed and standardized.

But to the degree everything is interoperable and verifiable, we are in a very good place.

Even small backups can help in a major way. Real censorship becomes too costly in practice even for a large player.

It will result in more competition and therefore more openness as well.

Signal is really frustrating and we could do so much better with Nostr.

Phone numbers, limited devices, tied to one business entity, and running unsustainably on charities.

Hope a Nostr-based solution like #Keychat and #Whitenoise will eventually replace it fully for me. Monetization is very important.

Privacy is not for free.

In my demo of BudaBit in #Bitfest I was asked if I was after the 10BTC bounty originally promised by Jack Dorsey to replace GitHub.

My answer has always been:

I really don't care about bounties as primary incentives to build anything in freedom tech.

I like when people donate to worthy projects but that motivation alone gets nowhere.

I build #SatShoot and #BudaBit for my own goals: Making code collaboration and digital work platformless and social.

I put my own sats and time in my projects and will see how far that goes. If people find it useful enough they will contribute in ways they can, money or otherwise. I already received a lot of support from many people in the space which I am really grateful for.

But receiving charity support is not my goal.

Bitcoin allows us to store, send and measure value but it does NOT help figuring out who to trust.

Think about it: yes you can accept sats in exchange for your services and products almost trustlessly with bitcoin, but what about the other party?

When I buy anything, I need to put trust in my counterparty to give me what he promised because it is very hard to recover from a deal or trade gone wrong. We need to focus on prevention of conflicts which is more trust between parties beforehand.

This kind of trust comes from people, not money. And I prefer to put my trust in people I know in the first place, and then widen the circle of trust further to degrees of separation.

Nostr turbocharges this trust because we are bootstrapping communities and markets where all communication is signed and standardized.

Communities bootstrap markets which in turn feed more flourishing in communities in a virtuous cycle (quite similar to how bitcoin is monetizing).

Bitcoin is the most trustless.

Nostr can become the most _trusted_ .

Any project that bases their #WoT solution merely on microblog follows is doomed to fail.

Explicit trust assertions don't work either. Yahoo failed against Google for a reason. Manual curation simply doesn't work, _unless_ it is done in a decentralized way, by leaders and moderators of _organically_ built communities.

Without communities (read: relay-based moderated groups with enthusiastic leaders) it is not possible to align nostr closely with the reality of how people form networks, and we are destined to reintroduce central chokepoints.

I know it's tempting to just sit at your desk all day and write algorithms. It will not solve the problem of decentralized WoT alone though. You won't just suddenly engineer your way out of a massive problem that existed since the internet came along.

With all seriousness, I hope no one in their right mind thinks that we will do better than Google by running massive crawlers and algos on twitter-follows to build and faithfully represent authentic trust relationships on nostr.

Don't get me wrong, I really appreciate the work some people put into wot algos, but **these should be used as ancillary services, not as the foundations of Trust**. And precisely this allows niche wot score providers to come alive. Don't put the cart before the horse, or we will subject ourselves to machines again, whatever ingenious idea we had before. People should come first.

The real solution is to onboard freedom-oriented community leaders to Nostr. Farmers, artists, religious communities, cypherpunk groups...

Bitcoin anchored itself to reality by introducing PoW mining.

The Proof of Work for Nostr will be building and onboarding communities. It is the thermodynamic anchor to Trust. I see no other way we can avoid centralization (1-2 wot providers used by everyone) or uselessness (spam).

Resist WoT alchemy. Focus on building good software for communities and marketplaces that tap into that Trust. Everything else will fall into place.

That's how Nostr wins.

Or why not just deploy it for yourself via Shakespeare?

- People want features they care for, but the owner of the project probably has his own roadmap for a good reason

- Vibe coded stuff probably needs more work and reviews to actually fit in the project and make the code future proof. Lots of vibecoded PRs will inundate projects with half-baked code

- If mostly only you want that change then it is normal that you bear the cost of deployment and since it's nostr you will not lose connection with others running a different version of the app, with your own quirks

- I know you are working on a simple deployment pipeline, you can make money on hosting here, why not make use of this?

The most reliable energy source for freedom tech development is if you first and foremost do it for your own (or family or loved ones') sake, not for "humanity".

Humanity can do without you, and you don't need to save everyone. Just care for those next to you with low time-preference, and see the magic happen.

Replying to Avatar Awiteb

Today, I’m thrilled to introduce n34 (https://n34.dev), a command-line interface (CLI) for sending and receiving Git issues, patches, and comments via the Nostr protocol.

I hope you all like it, and I’m eager to hear your feedback!

A special thank you to:

- nostr:nprofile1qyghwumn8ghj7mn0wd68ytnhd9hx2tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qqsx3kq3vkgczq9hmfplc28h687py42yvms3zkyxh8nmkvn0vhkyyusu07hes for his awesome https://rust-nostr.org

- nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq36amnwvaz7tmgv9mx2m3wv3skucm0demkz7tyv4mzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngn9kt4z for his invaluable feedback, answers to my questions, and insightful conversations.

- nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq3wamnwvaz7tmzd96xxmmfdejhytnnda3kjctv9uqzp5zweue6xqa9npf0md5pak95zgsph2za35sentk88jmzdqwk925sd33mtj for his constructive feedback.

- nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmjv4kxz7fwdehhxarj9emkjun9v3hx2apwdfcz7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7qpquseke4f9maul5nf67dj0m9sq6jcsmnjzzk4ycvldwl4qss35fvgqcs77zh for suggest the keyring

- nostr:nprofile1qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5qnvvze for encouraging me to bring this to life after I had initially shelved the idea. <3

Examples:

- For sending a patch: `n34 patch send ./patches/*.patch`

- Receiving one: `n34 patch fetch `

- List them: `n34 patch list`

Almost the same with issues. Check out the documentation

Let a thousand nostr git projects blossom!

Once you have an onchain address, you can send as much as you want unlike with LN.

The mints would have no control over how much money they are comfortable with handling. Since still a lot of things are experimental in this space and mints have non-negligible risks, this would possibly create an unwanted situation for them.

Refunding is an option but in practice it might be complicated.

I assume yo are talking to a software engineer.

I would follow up with a question to clarify the areas of interests / experience and point the person to one of the open-source projects to get inspired.

The benefit is that most probably the person can view a live version of the app which is cool, and the repo would explain what NIPs, libraries and tools it uses.

On a bitcoin standard people can thrive from the fruits of the radically free market, as long as they demonstrate creativity and proof of work.

I think in the era of AI, the process of obsoleting redundant work is accelerated, which puts those people in the top ranks that strive to learn every day, coupled with strong work ethics and integrity.

As to the early stackers:

It doesn't matter in the long run how much you stacked early. What matters is if you can really see the world through the lens of bitcoin and understood its implications. And it's never too late.

The idea that "those who have plenty will be given even more" seems like a proof of stake idea from this perspective and doesn't make sense in a system based on proof of work.

How are you constructing the right filters for the right relays to fetch new posts for the "follows" feed?

Are you sending filters with all the user's follows listed as authors to all relays, or you do some smart selection ?

Replying to Avatar hodlbod

Nostr will fail to the extent that people can't tell an impersonator from the real thing. The number of reports I get about my impersonator indicates to me that nostr is failing. But it doesn't have to be this way! Web of trust fixes this.

Let's play a game of "spot the impersonator". I created a fresh impersonator account with a valid NIP 05 from nostrplebs and all the same profile data. I didn't bother to clone my notes or create a bunch of sock puppet followers, but that could easily be done, and would improve the resemblance.

Coracle:

Pretty good if I do say so myself. Social trust is shown in two separate ways: web of trust indicator and followers tab (although followers is not complete or sybil resistant).

0xchat:

Exactly the same, other than NIP 05 address, which I don't consider any sort of validation at all. This is a classic phishing maneuver, and recently allowed nostr:nprofile1qyfhwumn8ghj7am0wsh82arcduhx7mn99uqjzamnwvaz7tmjv4kxz7fwwd5xzamw09jkzem9wghxxmmd9a5kucn00qqjqamnwvaz7tmjv4kxz7fwwd5xzamw09jkzem9wghxxmmd9a3ksct5qy38wumn8ghj7un9d3shjtnndpshwmnev4skwetj9e3k7mf0da6hgcn00qqjxamnwvaz7tmjv4kxz7fwwd5xzamw09jkzem9wghxxmmd9ac8y6tkv96x2qpqclk6vc9xhjp8q5cws262wuf2eh4zuvwupft03hy4ttqqnm7e0jrqlg4lcf's impersonator to trick some people.

Yakihonne:

Some social indicators are shown, but are not sybil resistant. They're also down the page a bit, and might not be noticed by users.

Jumble:

No social proof indicated at all — the tabs at the bottom can easily be faked by the impersonator.

Nostter:

No social proof, and failed to validate the NIP 05 for the real user.

Nostrudel:

Nostrudel does something original in showing the public key color. But how often are you going to memorize a user's color? I'd argue this is even worse than nothing because it obscures the NIP 05, which _might_ tip you off.

Iris:

Iris shows wot-vetted "known followers", which is good. In other places, a wot-based check mark is shown next to user avatars. This should probably be added to the profile page too, but still, pretty good.

Amethyst:

Amethyst shows some social proof, but it's hard to tell exactly what those profile pictures mean.

Primal:

Like yakihonne, social proof is visible, but not sybil-resistant.

Let's take a look at search now. Some clients do a much better job at this, some do a MUCH worse job.

Coracle:

WOT indicators, correct sorting, complete results. Arguably, the impersonators should be filtered out entirely, but I personally prefer to have them included.

Jumble:

Same thing, minus WOT indicators. Not bad.

Nostrudel:

It's a pass, but I'm not sure if duplicates are filtered out on purpose or not. The check marks indicate NIP 05 validation, not wot validation.

Yakihonne:

Only shows the legit version, along with a badge (I'm unsure if it's NIP 05 or something else). Pretty good.

Iris:

Very limited results, WOT-based check, pretty good.

Primal:

Eliminates impersonators, show follower count, pretty good (though not sybil resistant in all cases).

The winners are Iris and Coracle for web of trust indicators, and Primal and Yakihonne in the "global view of the network" category. I'd love to see this get better though, and not just because I am now famous enough to have an impersonator. WOT calculations are low-hanging fruit, especially with the vertex DVM by nostr:nprofile1qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0qyt8wumn8ghj7ct4w35zumn0wd68yvfwvdhk6tcpzemhxue69uhk6mr9dd6juun9v9k8jtnvdakz7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uqzpa5rapcrtaadfazwpwvvl0v4xlskg4df9nfcem7yevcaka2h7hhjm9zju5 around. Getting this right is a core value proposition of nostr and is worth the effort.

My estimation is that the norm will eventually be to hide absolutely everything outside of the web of trust by default, and show only optionally.

As a minimum posts should be ordered by wot.

Also, kind3 follows and 10k mutes are just the beginning. Communities will offer more reliable starting points.

Other nip51 stuff is also useful.

Context is key, and the general kind1 client use-case makes it hard to find that specific context where wot can be fine-tuned to user needs.

Marching ahead with #BudaBit , where you can own your sovereign developer community, using nostr!

- Search and Bookmark multiple Repos

- View Repo metadata

- View Issues, Patches, Comments

- Browse files and Commits

nostr:nevent1qqsyvc0ga78dsyy4zd95f8lzpucpleld2fhl6r0p54a3g6kuhcyqh4qpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyrx7a9puhvvu2x4cg7nx6hthgde648mr62rjg6a4nvyz07j7vd6qqqcyqqqqqqgfvxcrh

View live [demo website](https://budabit.club)

Features are added rapidly!

Soon:

- Edit issues

- Sharing git stuff in rooms and threads

- Merge PRs

- ... Our short-term target is to manage the whole development workflow in BudaBit

PS: If you want to join and your not whitelisted contact me on nostr or deploy your own BudaBit community, it's open source and just a static PWA you can host very cheaply, using your own name and branding !