you are talking about muddling up the boundaries between presentation and delivery.
a curated feed is a presentation feature, something you can do with an app.
it simply makes no sense to put it in a relay, relays should be focused on delivering content that they are being paid to deliver.
it's a feature that belongs in the client, not in the server.
i'm not simply talking about mechanics, if you don't respect the ontology of a computer system, you will eventually break it.
i say this from experience having actually broken my own projects by mixing up where certain operations are done, and after the app gets to a decent number of features, having processing done in the wrong part makes it really hard to fix and/or extend the application.
You said it right here: "relays should be focused on delivering content"
That's what I'm talking about. Different relays delivering different content that mixes with a user's other content and whatever client/app they are using should be able to render all that content.
It's really no more complicated than that.
"should be able to render that content"?
this last 12 hours i encountered content, in the form of hyperlinks to DRMed spotify link previews, which caused my LIBREWOLF browser make it impossible to capture screenshots while said object was loaded in the visible page, and on top, because i had disabled DRM, i get a popup snack bar that distracts me and consumes screen space, on top of the fact i was now also unable to capture screenshots.
some content should be much more easily blockable too.
i don't want to render any DRM content, ever. the day that youtube starts using widevine, will be the last day i ever use youtube. spotify's garbage was chewing up CPU processing and memory and slowing down my nostr client "rendering that content".
not wanting to nit pick exactly, just to point out that some content is borderline malware.
I have none of the problems you are having so we are coming from 2 completely different paradigms.
i bumped into a bug before you did. maybe it was one you'd never bump into because you dgaf about DRM and you are ok with outside entities having total control over part of your computer. i don't think you would be if you understood it.
it's not a bug, in this case, it's a feature. but for this user, this is a bug. just because it's a bug you would not run into doesn't mean that it's not a bug that is a problem and has deeper roots than you want to acknowledge because it's too much new information for you at once to understand this principle of software architecture.
you'll understand what i'm saying in the future, for now, this is just a data point that you may or may not absorb and hopefully will, and later on, will make positive use of it.
Are kind1's DRM or otherwise inaccessible to you?
causing interference in my free use of my own computer is a partial inaccessibility to my own physical property.
the DRM embedded in the link inside a kind1 caused a string of seemingly unrelated problems in my use of my computer because the DRM takes over part of my computer.
it made screenshots unaccessible to me. it made my browser, generally, run a lot slower, and slowed down my nostr client web app.
it would be easier for you to acknowledge that DRM is stealing control of my computer from me and not to try and argue that i'm off topic, because anyone can learn that's what DRM does if they care to do a few minutes research.
just go to your settings on your browser and try to disable DRM and see if you don't have problems.
if you use brave or a chrome based browser, you won't have problems. but with firefox, there is huge problems.
i mainly want to point this out because mozilla virtue sigals hard core as being some sort of defender of freedom and they aren't, and i want people who believe in freedom to understand they are being lied to.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
