Avatar
Leo Wandersleb
46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d
https://walletscrutiny.com https://nostr.info Working on Bitcoin, Nostr and being a good dad.

*cringe* at "regulations". What do you want our overlords to do? Require national IDs for all social media activity? Will my Chilean ID do for your social network?

Replying to Avatar david

A fully decentralized solution is definitely possible. And desirable. Not just the App Store, but all sorts of questions and decisions. Many of them, including the App Store, boil down to the tools that we use to communicate with each other: what are those tools and more importantly who is in charge of deciding how they work.

The question is not whether we want moderation and curation, yes or no. Bc the answer to that question is yes. The real question is who decides, and how does the moderation and curation take place. Saying it should be done in a decentralized fashion does not equal let’s have zero moderation or curation, although it understandably might seem that way without having a clear vision of how it is even possible, or without even believing that it is possible.

But it is possible. Consider the English language, a tool for communication in the analog world. Who’s in charge of deciding what words mean what? Answer: nobody is in charge. No centralized bodies at all. And yet we — seemingly magically — somehow manage to agree to call a pencil a pencil. No committees, no standards bodies, yet we agree on most of these tools of communication. That is an example of loose consensus, in the non-digital world.

In the digital world, I think loose consensus is very much possible. We just haven’t implemented it yet. What would happen to the English language if websters dictionary shut down, and no one took their place? Basically nothing. Old words would still work, new ones would still churn into existence. But what would happen if the w3c stopped issuing standards, and no one took their place? Chaos, relatively speaking. No one would be able to agree on new standards for anything. Just like the cartoon, every attempt at fixing the problem of “too many standards” would just mean adding one more standard to the pile. Without centralized standards bodies, it would be a digital Tower of Babel.

But the thing is, I think loose consensus is actually not that complex to implement digitally. It’s just that we haven’t done it yet. 🤷🏻‍♂️

Awesome post!

I think we are mainly hesitant about building solutions because the simple solutions would require a lot of data to be duplicated and stored. If I like your "app store" and want to make sure it sticks around, I'd not only give it a like, I would copy it and every iteration that I approve of. And thousands would do that to signal what's a worthy app repository, right?

In nostr, relays could de-duplicate events by tracking the hash of + . Now if Alice's App Store is stored as a stupid huge event, Bob's approval - Bob's copy of it would cost the relay only one hash. The relay might spread the cost over all supporters. Now if Alice wants to update the data she would initially leave Bob and others behind and be charged by the relay for the full new blob but if popular, others would quickly abandon the old blob, reducing the individual cost per hour in hosting the Alice-blob and increasing the individual cost of the Bob-blob as users abandon it.

Now Bob would have to

* rally support for resisting the change Alice introduced or

* join Alice or

* fund the full blob or

* curate the blob down to what he can afford to maintain as a separate - niche - "App Store"

What I hate about AI: I don't want to follow AI accounts and whenever somebody made a really nice and smart reply to my notes, I'm hesitant to follow them because "really nice and smart" is what AI can definitely do on a regular basis.

Web of Trust.

App Store as a protocol.

Guy maintains a list of apps and either recommends to also consider others or automatically copies from these select others.

A bit like Linux distributions. Each has their own set of apps with huge overlaps but the user picks consciously a curator/distribution and adds more curators/distributions or individual apps when needed.

If we build this as a protocol, you could build tools that don't just search one person's repository of apps but all such repositories. Imagine you ask your client for "Snort" and it told you:

* 12 of your follows agree on Kieran being the maintainer of such a product addressable as Kieran.SnortSocial

* 2 of your follows list a product addressable as Eve.Snort

Yeah but ... online doesn't count. I would say the easiness of finding one's tribe online is making us picky about real world acquaintances.

Online, 99% of my interactions are with bitcoiners. In the real world, if knowing bitcoin was a precondition, I'd filter out 99% of the people I bump into.

You need some reason to be around other people and see the same faces a dozen times, ideally with a shared interest.

Bitcoin meetups are not available where I live and I certainly got to know some people from trying to organize one but there is other meetups. Pick something that happens weekly with not too much and not too little turn over. If it's the same people every week (bowling club), it's probably not easy to fit in. If it's different people every time (Sunday cinema matinee), it's not good neither.

Since I have a kid it's definitely easier but the shared interest being kids can get a bit boring ;)

This "bull" looks an awful lot like a devil.

Unless the client limits events to a certain follows graph.

I would want to see replies by - in this order:

* my follows

* your follows

* my follows follows

* all the rest

and it doesn't need to be a configuration thing. It could quite literally be replies sorted by this heuristic.

I would want each user to be marked according to the group he's in and wouldn't mind having to click a button to see the "all the rest".

I reviewed many wallets for walletscrutiny.com and many use web technology for their UI. It's not exactly PWAs but if you offer a PWA website, it's easy to bundle that website into a "native" app such that the executable code can be audited and reproducible.

https://walletscrutiny.com/android/it.airgap.vault/ proves that you can have full transparency.

Now for nostr apps we need separate signing apps like we have browser extensions on the desktop as there is just too many irresistible web tools and pasting your private keys into all - or any - of them should be avoided. If we can separate the delicate signing and decryption, I wouldn't worry too much about using websites and their lack of pinning versions and auditing them. Yes, some tools leaking your chats would be a problem but it should be detectable and with limited impact once we avoid private key exposure to all these apps.

I wrote the post twice and filed this issue in Snort ;)

https://git.v0l.io/Kieran/snort/issues/583

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 you asked my opinion on PWAs. Allow me to answer in public ...

As a mobile app developer since the early days of Android, the biggest decision when starting a new project always was: "How can we provide our product for Android, iPhone and maybe even desktop?" The answer was one of these:

* Single Code Base using web technology: The UI will be poor and not adjusted to the respective platform. The performance will be poor as you don't get to use multiple threads.

* Single Code Base using some proprietary framework: The UI will be poor to ok. The performance will be good. You pay the framework provider forever and/or struggle when they go out of business.

* One dev team per platform: This is expensive of course.

The advances in mobile phone performance and the advent of web frameworks such as Svelte moved the dial more and more towards web technology in recent years.

You asked in the context of Apple dictating Damus modifications to not get removed from the App Store and some argue that Apple could do the same with a PWA but I would argue that the hurdle to block certain websites would be much higher than to remove certain products from their store front.

With apps being removed from App Store, users usually don't protest but with some links not working ... what would users do? Imagine links to my blog at habla.news not loading on iPhones? Imagine links to your posts on snort.social not working on iPads? How would users feel about that? I think it rings very differently than a removed app. But ultimately, if Apple really did remove access to these sites, the work that went into developing them would not go to waste. Users would know how to consume them and Apple would know they know.

For me, the browser is a dearly needed compatibility layer and PWA is just the topping that makes these browser apps even better on mobile devices. If possible, I would always opt for "PWA" or "a website".

Replying to Avatar Robert Allen

I’m building a reputation badge/long form attestation/NIP5 service with nostr:npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6 that is a lot like what you are describing. Initial impetus was to help people preserve their LocalBitcoins reputation. Would be cool to chat with you about it: https://toastr.space

nostr:npub1t289s8ck5qfwynf2vsq49t2kypvvkpj7rhegayrur0ag9s2sezaqgunkzs our service attests to the published reputation of users. If BullBitcoin exposes the reputation rating publicly, we would love to hook our bot in and offer your users similar attestation or you do it yourself.

We see ourselves as neutral to Localbitcoins users, so we consider our attestation of their soon to be offline reputation as a neutral attestation of a fact. Of course, BullBitcoin not planning to go out of business any time soon, you could ask your users for their npubs and attest to their reputation on your platform and share a signed event to that end yourself.

We chose badges as a quick way of communicating the fact but badge support is somewhat limited in nostr, so many people don't see them or when they see them, they have no concept of why it should matter as the issuer is not very prominent, while the issuer is in my opinion the most important aspect of a badge.

Due to the lacking badge ecosystem, we chose to also provide long-form articles where the author is more prominent and where we can better explain what's going on.

Nobody is entitled to an income from content creation and nostr is still tiny. With scale will come audience.

You are talking about nostr content creators, not creators in general as those also still lack a lot of discoverability on nostr.

But ... nostr is great for zapping or ... will be. For the zap ecosystem I think the main hurdle is still to get people setup with zapping. I'm a self-custody maximalist and jump between clients all the time, paranoid about sharing my keys with more than the browser extension. I can't zap with any client yet and would feel uncomfortable giving all the clients I'm using access to my zapping budget. I think we need some improvement there.

Now the video is playing. No idea why it was complaining about the content before.