Everything is compatible with a timeline. That's why everyone is afraid to break with the timeline concept. It's the easiest and the simplest to explain.

They also mix "timeline" up with "appears in a vertical, scrollable list, even though you can put things in a list in a non-timestamp order.

For instance, if I open up my notifications app, do I absolutely have to see everything in the order it was sent, or should I see more high-priority items first? If I open my communities app, do I have to see everything in the timestamp order, or could I see threads my best frens are in, or that focus on my favorite subtopics, further up in the list?

And why do I need to tell the app whose stuff I'm going to be most interested in? Is it not obvious who they are, from the open data set? People are so afraid of smart code that the clients are kept willfully retarded.

At the same time, I might want to only lurk on some stuff (leaving less of a data trail) or I want to specifically avoid someone that I'd been speaking to regularly, without having to mute them. Can the client figure out a way to help me do that?

Reply to this note

Please Login to reply.

Discussion

Not sure how that is a protocol flaw. Can't you build a client that ignores timestamps?

I didn't say it was a protocol flaw. It's a flaw in our attempt to just rebuild what we already know, instead of putting more thought into the workflows.

My point is the opposite:

The protocol and other innovations make a lot of complicated stuff bizarrely easy, and we haven't even begun to scratch the surface of it because we've been caught up in rebuilding stuff we're used to.

There are entire use cases that are only feasible, now, and they suddenly became feasible for everyone, everywhere, at almost no cost.

Like, someone on here was recently talking about real estate data.

You know who has the best real estate data? The old lady on the street the houses are on. Think about what that means.

We should focus on onboarding?

I mean, to ask the question is to answer it.

Why do the clients all have timestamp order?

Because Twitter does.

Why do we have follows?

Because Twitter does.

Why do we have mutes?

Because Twitter does.

Why are we against deletes?

Because we've seen people try to rewrite history on Twitter.

If every decision you make is based upon "do Twitter better", you will end up with 50 variations of Twitter and little else.

But we want the OtherStuff.

agree

A protocol scrap-n-rebuild would be a breaking change, like we just pushed through with Asciidoc. I think we're going to need some serious breaking changes, soon, or it will inhibit innovation.

We seriously need to fix generic replies. It's a mess.

Perhaps a nostr client could emulate Google’s PageRank system i.e. before Google went from Do No Evil to Do Mostly Evil:

Quality of note X (total zap value, WoT) * number of other high-quality notes interacting with note X.

Unfortunately, zaps are not a signal of quality, but I like the idea. For me, it was also just the idea of what is important to me, personally. What I would consider high-quality. AI can analyze the actual content, after all.

Yeah zaps can be faked and are subjective, WoT does help here

I think zaps can give information about the relative quality of posts from one npub, but not between npubs.

But even then, there are weird, unexpected dynamics.

For instance, pictures of my person tend to receive more reactions and replies than pictures of my dinner, but the latter gets lots of zaps and the former gets none or only a couple very small ones from some people doing OnlyZaps.

Should I respond to the financial incentive and never post pictures of myself and post lots and lots of pictures of food? Probably not. There's some weird effect on display here, but I know not what.

The zaps, and lack of zaps, are providing information, but how to interpret it?

Start a community and charge for replies 😆 .

That said, paid replies probably contain more information than zaps of similar amounts (especially if only members can reply).

Micropayments are great for machines, but lousy for humans. Humans love membership. I think there is a possibility to combine membership (paid-up npub) with the ability to disburse micropayments along the way.

I was doing read-aloud-by-request on Twitter, for fun, and some guys were like, is there an OnlyFans where we can get private read-alouds?

They were serious. 😅

Like, you'd pay me to sit in front of a camera and read aloud from classical literature?

Yes, apparently. Especially if I wear my tweed retro dress and my nerdy glasses.

Zaps often seem so random. And there are a few mega-zappers that completely skew the statistics. And someone who leaves and comes back, after a long hiatus, gets rained with zaps. Has nothing to do with the content of the note they posted.

I'm here so much, that people think of me as part of the infrastructure, so they take it for granted that I'd remain. I'm now the wife, not the new girlfriend, so nobody is flashing cash, anymore, cuz they figure I'm a permanent fixture. I'm like Nostr background noise, but I don't actually have a Nostr income, so I'll be going a bit radio-silent, soon, when I get my new job.

The problem is obscurity, not smartness of code.