Avatar
Viktor Vsk
8a699686811889186df398c7253e8c4417ce73fe814edeae7ecd81dbde9536ac
Building #saltivka 🇺🇦 Nostr Friendly Relay (https://saltivka.org) Building #Knowstr — smart Nostr events aggregator (https://github.com/viktorvsk/knowstr) Working to enable people have more activities through the word of mouth between friends, friends of friends and more 🤝 with https://recar.io and https://valent.network

> There is not a single jurisdiction without at least ANY restriction => EVERY operator MUST scan for illegal content unless they are uncatchable Joe.

No, it's a non sequitor, it depends on the law.

The fact that some content is illegal does not necessarily mean that the relay operator is liable, surely not for all illegal content.

You seem to believe that if willingly publishing something is illegal, then a hosting platform, to which relays are similar in practice, has the legal obligation to scan against it and is liable if it doesn't.

This is not generally the case. It depends.

> Also, relays MUST be for profit (if we are not talking about nostr in its today form no one uses just like right now) - because one has to pay for hosting and operation.

Bullshit.

Plenty of websites, which also have to pay for hosting, are run by non-profits.

This isn't a disputable matter of opinion, it's an objective matter of fact, there are *many* non-profit organizations running websites, often hosting them on their own servers, some of which are very large and have many users.

You seem to be under the impression that non-profits can't deal with money.

This is obviously not true. Many non-profit organizations handle money, sometimes massive amounts of money. That doesn't make them "for profit", because profit isn't their goal, or even part of their goals and money, to them, if they are run honestly, is nothing but, merely, a tool like any other, which they spend towards what actually fundamentally matters: the mission of the organization.

We already have several non-profits which operate in the software world, several non-profits which run widely used web services, several non-profits which have freedom of speech as an important part of their stated mission, all of which do what they do with no need to turn into "for profits".

You make many legit claims but mix it with incorrect ones which makes it very time consuming to argue with so sorry, I will only answer with a simple statement:

Yes, we have a lot of non profit media and journalists today and it works fine! Don’t even know why bothering with smth like nostr

You contradict yourself. I suggest you to take your advice :)

Again, I’ll try to put it simpler using your words. There is not a single jurisdiction without at least ANY restriction => EVERY operator MUST scan for illegal content unless they are uncatchable Joe. So your first argument doesn’t hold.

Also, relays MUST be for profit (if we are not talking about nostr in its today form no one uses just like right now) - because one has to pay for hosting and operation. So your second argument doesn’t hold.

Its great to have hopium at early stage project, but it has to be healthy balanced anyway

Anyone can curate and this can be almost free (spam)

But those who decide to train: they spend their resources, they bear responsibility, they get penalized.

So for me it looks like the only viable option for “decentralized curation, centralized training” is communism

How else could this be achieved?

P.S. also it seems to me it has the same vibes as “relays should grant free speech and forget monetization”

relays are not really web servers, they don't serve web apps or web pages, they are more like microservices attached to a database with a simple protocol

they *can* serve web pages, in fact i am in the process of adding some web service features on a secondary, local-only port for administrators to dump the event store and push events up to it without restarting the relay (dumping the DB was easy, adding events will be a tiny bit more complex) and i could easily add more web services to it if i could be bothered

the nostrudel client attempts to connect to the relay's listener as a simple webserver on its / route and it is possible to put a web app onto this port, for such things as serving up a statistics page or a subscription system, nostr wine and nostr.land i think both have little web pages for this that let you bump your subscription and suchlike

other big differences from a web server is these things called "ephemeral events" and the auth envelope is an example of one, this lets you identify yourself to an npub to the relay which can alter the data it will allow you to access or publish, this is all in a separate protocol from a standard web service, it is more like a microservice, microservices commonly use JSON protocols, but more usually actually JSONRPC2 or Swagger or similar protocols, it really is its own protocol and it's not and is not first class web server it is actually a websocket server

because it can auth in the socket and this can grant you different rights of access to data there is a lot more potential for mitigating attempts to surveill or stop the propagation of data, and this is the what the fuss is all about

websockets essentially let you run something that behaves like a webserver, but if you upgrade, or send other header fields, it can do other things, like the nostr+json which lets you access the relay's nip-11 metadata

calling relays "just a web server" totally misses most of the things that they actually do on a daily, minute by minute basis... and i run mine from my home, with the help of a reverse proxy and wireguard server, and it would be nothing at all to change that so the vps is in other jurisdictions and the actual relay itself is running anywhere, even probably (if i modified my reverse proxy) i could round robin it across multiple endpoints and have them quietly synchronising in the back end, which is just the beginning of the possibilities for making relays resistant to attacks from well equipped adversaries

🤦

Replying to Avatar franzap

"Relays should not be treated as databases" is silly and can kill nostr.

The relay query language was designed around a social notes client use-case. The "other stuff" that we love to talk about, as much as it's part of the nostr acronym, is an afterthought.

Other stuff clients do not work like social clients. They have way more specific requirements and hence need to use relays more like databases.

Since the query language is terribly limiting, this results in:

- Higher amount of requests

- More bandwidth

- More client-side processing

Do we want nostr to compete in terms of UX with other platforms/protocols or be forever lagging behind?

Worst of all, this leads developers to implementing hacks to perform queries (custom languages via NIP-50, for instance) which entirely defeats the point of a relay: to be easily swappable.

If we can't easily swap relays, nostr is dead.

The rationale for not treating relays as databases is based on the fallacy of simplicity. Since we want anyone (yes including your grandma) to create a relay we must make it as simple as possible – so we should not force implementation details such as requiring a database.

But guess what is the simplest way to build a relay? Using a database.

If we want nostr to succeed we must grow up, assume that relays will have a database backend, and reach consensus on a better query language that we're confident can be implemented in most engines (SQL, noSQL, graph, and so on).

Not perfection, not a highly complex language, but something that allows more flexibility than the archaic filters we have right now.

You mention that nostr “works” for social clients but not yet there for “other stuff”. Just keep in mind, its at the very least debatable if it works for social:

1. No likes

2. No followers

3. Broken profiles

4. No search

5. No private messages (yet)

6. No groups (yet)

7. No stats

8. No attachments

9. Single account for life

10. … list goes on

And the answer is usually “you don’t need it and hoy you will be happy”

The thought to change query language in future is interesting.

P.S. regarding “to database or not” I personally don’t have strong opinion but rather tend to believe “relays for transmitting, layer-2 for clients”

You asked a single question which I’ve answered in the simplest form possible. If you have another answer, ask it, this is how it works, when you don’t live hopium but real life

So what about them? They shutdown as soon as first complaint is filed. In reality they shutdown much earlier because actual traffic from a real social network does not fit into $5 vps

I’m just stating facts, sorry if I’m ruining your hopium, I honestly hope this outbox will fix this, btw, is it here with us in the room right now?

10 twitters running on the same protocol located in different countries/continents is rather decentralized

10 engineers running $5 vps for free will shut down with the first governmental subpoena (whichever govt it is)

So the answer is - “rather millions”