Avatar
Nusa
d475ce4b3977507130f42c7f86346ef936800f3ae74d5ecf8089280cdc1923e9
Frontend dev

The categories are up to the editor or publisher. Completely customizable. The current magazine is a showcase and the catagories are my own choice. It’s possible they only make any sense to me. The plan is to make it possible for anyone to create their own, on the scale of a specialized blog or a full blown newspaper with world news coverage.

It’s modular by design. It doesn’t require multiple devs, although any volunteers would be welcome. This is what I do and I know how to put it all together. But it won’t be in a week. I’m ok with that. This is important to me.

It’s like coming to the theater and sitting in the first row facing the back. Everyone will notice and many will gossip about it trying to figure out what you know that they don’t while trying desperately to appear as if they know what they are doing and agreeing that conventions need to be followed or we all devolve into wildlings.

Thanks ☺️

nostr:note1qffpcn5yd9p02cw8qgwjkrfzyg8exkqa66w6lw62wy8n9lg0qr3qaw3h7u

Replying to Avatar Silberengel

Another thing you could do is pay-to-play.

Our https://theforest.nostr1.com relay accepts all zap events, as those can be spammy, but so what. We can just let anyone zap and limit display of the zaps to a minimum sat amount _or_ write-access to the relay. You have to be whitelisted or pay at least 100 sats, for instance.

But, we can then allow them to include a message in the zap event (like Nostrudel does), and display that message in the feed, as a reply with a ⚡ icon or something (nostr:npub1636uujeewag8zv8593lcvdrwlymgqre6uax4anuq3y5qehqey05sl8qpl4 ?)

So, you can pay 100 sats to the pubkey, to have your comments show up, in our app.

And you can use anon zaps instead of private ones. Get away from encryption.

I don’t know if it’s possible to thread comments that are all zaps and wallets have their own rules about content length and such.

But design wise, it’s possible to go multiple ways with this. Even so far as to allow a publisher to include a min amount in the index tags and have it honored by the client.

Replying to Avatar Garbage nsec

Deletion is not a false aim, though. I feel the "nothing gets permanently deleted on the internet" has always been a flawed argument. This is emotional more than technical

There is a threshold over which most people will consider the deletion obligation to have been fulfilled, even though they will not be aware of the nuts and bolts (as technical people will). And that threshold is what matters.

ATProto does meet that threshold, with deletion at the PDS level, even though the relays make take time to delete or overwrite the event (ATProto relays are non-archival by design.) So on ATProto you can have a button that says "delete this post" and it'll be *accurate enough*. Or delete my account, the same, *accurate enough*.

Nostr doesn't meet that threshold, it's well under, and the result is that most average users will feel emotionally vulnerable. You have to have a button that says "request delete", which is a total freak-out phrase. The average user will become intensely aware that they don't really own their posts, someone else does and they have to ask that someone else politely to remove them if desired. Again, that's freak-out territory.

Also most cases of post deletion are deletes before anyone has seen the post, so the "things can be screenshotted" argument is also null. (Plus only 0.001% of users are screenshot worthy people.)

Basically for today's user you have to be over that threshold, even though of course you'll never get to a place where there is true and all-encompassing deletion.

We arrive in the same place. All deletions need to be honored by someone. The assurance of trust can be provided by a relay or a relay and client combo on nostr in a very similar manner than in other places in exchange for some decentralization (and you keep quite a lot of the decentralization on nostr compared to elsewhere). Someone who considers deletion essential to peace of mind would consider this a service. Hence, a business model.

But a business should be taken seriously and lots of things built on nostr are more showcases than services and barely any terms of service exist. The trust is low because we seem to be in a sandbox. The fact that the sandbox sits in an open square is indeed a dichotomy.

All of those are business opportunities.

Deletion is likely a false aim. Almost nothing gets permanently deleted on the internet if someone decides to keep it, except in a datacenter fire or a similar backup loss situation. Self-hosting your content on your own auth-protected relay and not broadcasting widely gives you deletion in the same scope as running your own website. Then you have a sliding dial of trusting some third party where you weigh the service pricing against your requirements in exchange for less expertise required of you.

DMs are solvable by a network of DM-specialized relays that maintain awareness of their peers and a client that knows how to talk to them.

Username/pass logins are not constrained by technical requirements but liability. The user base needs to be big enough to pay for the legal protection of such a service provider, who is in essence a password manager. The current attitude of ‘here you go, but we’re not reliable’ is especially cringe for such a service. In a business setting, this can be done by a central authority per business entity.

As for follower counts. I know they matter, but they don’t have to be global or for everyone. Need an accurate number? Get it from a DVM or a service that will count it for a fee, because it requires a targeted crawl.

I somehow expect people to know about this, but then it’s never mentioned, so I guess not 🙈

Replying to Avatar Geyser

Introducing LAUNCHPAD 🎈

The starting point for new Bitcoin projects and products. This is a new way to surface early-stage Bitcoin projects before they go live.

Projects now need 21 FOLLOWERS to officially launch.

Here’s how it works 🧵 https://blossom.primal.net/f73f33031405a09e97c1317e8e764e8dfa5eb1ef062e8625f533c7fb47c09d34.mp4

❓ WHY:

Most projects don’t fail because they lack funds.

They fail because no one knew they existed.

Before you raise sats, you need to rally people care about your idea.

That’s the purpose of Launchpad.

⛓️HOW IT WORKS:

Every project on Launchpad gets:

• 30 days to reach 21 followers

• A dedicated Launchpad section to grow early interest

• Once 21 followers are reached, all followers receive an email update

If you make it — you launch.

If not — it’s back to the drawing board...

Or, you can pay $21 to launch manually.

Yes, this makes things a bit harder.

But sometimes a small challenge is what triggers real momentum.

Launchpad helps separate signal from noise, and gives meaningful projects the visibility they deserve.

🔥Good luck!

What does ‘back to the drawing board’ mean?

On a personal level, my kids are definitely the coolest.

Beyond that, I still can’t quite believe I was in Argentina in 2011 when the volcano erupted in Chile and Bariloche was covered in volcano dust. The aftermath was what you’d expect from a natural disaster, but that first day was mind bending.

Sure. I’m thinking of monetizing the effort. I think there’s more value in curation, filtering, and selective processing that there is in raw data storage. The ‘global’ might become unwieldy and providers will drift into creating services tailored to a segment of users, countering the centralization. Smaller players can be competitive here if they have a creative way to surface a coherent subset of content.

It’s tempting to scrape and crawl everywhere because it is open and accessible. But sheer volume will surface as a problem. The whole point is that you don’t need to hold all the content yourself. Smart scrapers will only retain pointers to where the content was seen and not the complete compendium, and sort and process as they go. Keep this, dump that, convert to vector, save a summary, guess topics, feed to an agent,… then forget.

Key rotation doesn’t automatically include subkeys. The above proposal only solves for key rotation and it solves it with a soft solution that doesn’t require widespread adoption either from users or clients and is backward compatible. It defaults to separate identites for each npub, as they are now. A DVM could serve all the required data checks to clients and relays, so they are not required to run extra services or complete implementations for themselves.

I don’t have an equal solution for subkeys.