They are a light year ahead of everyone else, this is the compute of the future.

And they are the only fully vertical provider that can execute on that with ease with the otherwise nightmare-ish hardware and software incompatibilities.

I havent read everything on it yet but from what I did its pretty damn beautiful.

I'll try to update the writeups on this that I've created because I have sketches of this entire product done the cypherpunk way that are at least 6months old 😅

Yup, users aren't capable of making explicit attestations (and don't want that overhead).

Looking at the activity at the community-level is the way.

I think this is the way... inferring amount/context!

What I was referring to are explicit attestations, I think it's hard to get a good UX for a user to define how much and which categories.

And I've seen alternatives mentioned like "oh no problem clients will deal with that" probably meaning that clients will sign events on behalf of users? If that is the idea I disagree

In what I'm drawing for communities UX, different types of content get surfaced first depending on how much they're used in that community.

There's no reason why that cannot be used the other way around to automatically have a default filter anywhere:

1. User opens random recipe app

2. App checks for the user's communities that actually write/interact with recipes (in descending order)

3. App surfaces high signal recipes

This def needs to be stated, and stated forcefully and stated often!

Proxy indicators of trust like the follows count have SOME utility but you are correct to say we should resist relying on them as much as possible. Which means we need replace them with something better. And imho, that means: explicit contextual trust attestations, where you can say exactly what you mean and mean exactly what you say. Attestations of this nature are harder to game than proxy indicators. Which is why I’ve been advocating for them for so long.

There’s a certain honesty about saying straight up “I trust Alice this much in this context.” No interpretation is necessary.

My next step at brainstorm.ninja will be to enable attestations like “I endorse (npub) to write wikis in Category XYZ” and to see that reflected in the category-specific Influence Score. Which will allow CONTENT DISCOVERY of creators EVEN THE ONES WHO HAVE ZERO FOLLOWERS.

The problem with follower counts is skewed incentives

Not only does it incentivize certain types of note formats (short, lacking nuance, provoking), but it also makes people regurgitate the same things over and over - leading to basically LinkedIn. People start using different clever ways of saying pretty much the same thing that doesn’t even need to be said in the first place. Of course, who decides what can be said? No one. So you get the enshitification of social media.

I firmly believe that follower counts should be resisted as much as possible and social dynamics more closely mimic real life. In real life our reach is limited, and if one person says something that thing becomes forgotten fairly quickly. People do not gain 100 followers by saying one thing. They may build up some social capital and eventually a following if they stay the course with their message, but those are few and relatively harmless. But when you have everyone competing for a superficial score, this ruins the social web. People start competing, making the rest suffer. I mean, it would still happen without a follower count, but to a lesser degree without the underlying incentive.

That’s all I have to say about that today. Maybe I’m saying the thing that doesn’t need to be said in the first place 🤣😯

Sure

Sounds controversial but would be cool to experiment with it. Client side at the moment, and especially on nostr, is quite terrible - particularly on websites. Sure I hope it gets better

What?! No way. Client side all the way. We’ve barely started to optimize all that we could on the client. Server rendering is a relic of the past.

how does one comment on highlighter.com? I click on the button and nothing happens

Websockets sucks.

The UX on nostr would be so much better if relays also had a rest API or something like that

Please look at heavily-formatted markdown files in both light and dark mode, when selecting client palettes. Thank you, in advance.

#devs