While everyone is fighting, I'm building (ideas).

What if a nostr client would substitute a "random" image in place of the intended one uploaded by user, some small percentage of the time? I often fear I'll upload and post something by hastily by mistake from my camera roll and have it live for eternity here. But with this, anyone could have plausible deniability!

Reply to this note

Please Login to reply.

Discussion

Have you been smoking🤔? Be off, with your silly ideas😜.

Dammit. Wasted 5 minutes of my life hunting down a clip I can't find. Sigh

Short answer, "a little high, from earlier...but that's got nothing to do with it!"

Build it and they will.......(Probably ignore it), ridiculous idea😬😂.

I have other ideas... pity you'll never hear about them 😤

No, please, if you're on a roll.....Shoot.

The well has run dry for time being...stay tuned though

Oh good idea! you know, the best way to do this would be if your client connected to some "caching" service instead of actual relays, then that cache could substitute and filter whatever it wants! ;) ;) ;)

It's not as dumb as it sounds, and it was the primal infighting thing that made it spring to mind.

I've also (can't recall if I posted about it, I have many, many ideas...) wanted a similar thing for my web traffic. Have a little random crawler visiting all sorts of sights, to pollute the data that might be collected about me

Oh no the idea itself is phenomenal. I was mostly joking making the point about the insidiousness of caching servers.

Since you're smart and I have your attention, what is the positive trade off you get with caching server? Speed? It's slower for me vs Damus...

I know Matt's no fool, so genuinely curious to know what he'd say but don't like to get involved in disputes I don't belong in (just watch from sidelines like a creep)

This has been mentioned in dispatches:

nostr:note1fea45tfldz9kxc6jx395k42lskmcwccv4z3jv8eksj4l7kyvdtkqmvuxq3

So it is speed. I then just wonder why it's slower for me when I test.

I don't wanna drum up any drama, not today for sure, but that's my experience

Yeh, I love Jumble on desktop, but it can be slow because it's directly talking to the numerous different relays used by the various npubs.

Talking to multiple relays isn't inherently slow, but you might come across a slow relay once in a while, or perhaps an unavailable one.

Caching or indexing relays can help, but you need to be careful how to implement them in terms of synchronisation or authority delegation.

Beyond this, my theoretical knowledge expires 😂

This sounds like real knowledge to me, not theoretical at all!

Thanks. Think the picture is clearer now. Learned the term "intelligent edge", it means pushing compute to device or "edge" of network. Still puzzled why primal struggles with speed just enough for me to be noticeably annoying, but moving on for today as my brain is full. Other clients I've tried are prob even a bit slower, and primal did seem to work best when I was traveling and getting such bad signal Damus wouldn't even load anything up.

I'm not extremely knowledgeable about this, so take this all with a grain of salt, but i'll write some nonsense that comes to mind (also, I pretty much respond to any notification i see - especially from npubs i've known for a while - and I don't get enough to not see them):

- wider reach without murdering the edge device. the remote caching server could potentially connect to hundreds of remote relays and your edge device only connects to this single remote caching server.

- this one is contentious, but: filtering. depending on whether you think this is good or bad, a centralized server can use a lot of user statistics and behavior to filter spam or otherwise "undesirable" content (personally not a fan)

- ordering/promotion: largely similar to above. the cache server can determine what order you see posts in, how often you see notes from a given user, etc. etc. (personally not a fan)

- heavy computation: like nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj alluded to recently, the "caching server" (really stretching this term now) can perform high-resource or long-running computations that your client can simply read "for free"

- probably other stuff but those come to mind are are probably most relevant to the wider discussion at the moment.

For the ones I'm "not a fan of", I think those general patterns are very good things, but I don't think we have the proper WoT and personal server infrastructure yet to achieve it in a way that doesn't move us backwards in terms of decentralization and content moderation/censorship. These are the sorts of features that everyone wants for good reason, but if "we give it to them" in a half-assed way, I believe we diminish the chances of ever achieving it in the full-assed way. (mostly due to user complacency. the internet repeats this cycle over and over)

Still reading remainder, but had to pause and laugh at first bit. Relatable

- reach: nostr.land aggregator can do this

- filter: nostr.land aggregator will be able to do this as the only relay, OR if clients add support for a filtering signaling NIP

- reordering: aggregator can’t do this

- precomputing stats: this will be supported via COUNT I think

these are the way(s)

Was wondering about how your super-relay model played into this. Or any relay now that I think about it.

Still digesting, so refraining from asking follow ups for now

Great answer! Thank you

in the embedded space there is a push for the “intelligent edge” with more processing on edge devices and less cloud reliance*

(*except for when companies want to milk you for $$)

in app land we are moving to the retarded edge

LOL yes.

Vibe code the shit out of that idea, now

Also, self zapping. I miss doing that 😂

Just zapped myself. Seems to have worked.

And it'd be easy as heck to code this, if I knew the existing code base at all... just skip to the final upload function in client, add a lil random "coin toss" (user selects desired weight, or leaves default of 1%). Only hard part would be selecting appropriate set of seemingly random and images to substitute in. Expect one could crawl Facebook for that easily enough.

On a serious note though, I find it interesting to consider how a nonzero built in failure might actually improve a product.

We'd all have something to moan about then.

Many of us enjoy a good moan 😂

Nothing like a good moan, or groan

We need more ideas like this

Glad you like it. It's not totally terrible, right? Like, oops that image is t the one I sent, must be the random algo 😅😅

Classy women could use it to have temporary relief from the tension of being classy. If you catch my drift

Oh snap! I do catch your drift. Whatever grows nostr 😏

Can we finally just start take responsibility and develop self host solutions?

Most of the internet seems like a mirage run on AWS, network illusion, like choice illusion.

Mistakenly shared image, revoke file access on your server.

This sounds too simple. Surely it wouldn't be so easy. I don't know how any of it really works 🤷‍♀️

No one told or taught you early internet lore, servers, domains, URLs, access permissions, vague high school computer class memories from the 90s?

You might find it hard to believe, but I'm not real bright when it comes to computers and networking.

What got you on Nostr?

A few people, like Gigi, were here and I decided to give it another try (came earlier but it was pretty dead and nonfunctional). I'm part of the early adopters, not the cypherpunk first wave, hence my lack of computer knowledge

You hang with the OGs you want to tell me?

Yodls is an OG

Was struggling to come up with answer. Definitely not. Not in BTC nor nostr. Just here to learn from the rest of you cypherpunk whales

Open water

Enigmatic

Give everyone a built-in “I was hacked” defense. One AI-generated post in your voice saying something random every month. Nope, wasn’t me that advocated to overthrow the government, was just the AI post. Why did the AI post it 100 times, was supposed to be once a month? Bad luck, I guess.

It's a decent concept. A slight decrease in functionality, but the benefit of plausible deniability. Kinda interesting imo