Avatar
semisol
52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd
👨‍💻 software developer 🔒 secure element firmware dev 📨 nostr.land relay all opinions are my own.

well to be honest they practically don’t exist for 99.99% of nostr users either

You don’t own your data nostr:note1jfkf8husy0juz8g2fwt6dnt7q2dlmq3q3ega3h4sawj2ge84snnsaanrm0

Go is a great programming language and you cannot convince me otherwise

one thing you may want to do is separate the actual DB logic and what I call the index provider

that basically allows you to swap the query planner and index generation logic, and allows making search very easy (tokenize => save as individual index entries)

index changes become easy too, as all you need to do is reindex all events in place, with no interruptions, and after that’s done enable the new indexes

also I am considering using a good amount of the realy code, which looks good, just with a different event store and some other changes

will contribute back those changes if possible

I can however confirm I did move the relay from my test environment and didn’t move the data, and there was some downtime

The error is not you but your network

Anyway, since the relay is experimental and was moved to a new server, you will need to re-broadcast events (DB was not moved)

DNS resolution failure. The relay is fine and it works for me.

Often what I experience is DNS resolution fails due to packet loss.