Nostr Web Client

nostr:npub1fjqqy4a93z5zsjwsfxqhc2764kvykfdyttvldkkkdera8dr78vhsmmleku Could replicatr be used as an inbox relay? I'm guessing it can and was going to try it out, but hit a build error

```

blee@litten ~/o/s/n/s/replicatr (master|✔)> git log -1

commit 2a8c80bef27fbb9c6274853c7149de26bb3a3a2b (HEAD -> master, origin/master, origin/HEAD)

...

blee@litten ~/o/s/n/s/replicatr (master|✔) [127]> go version

go: downloading go1.22.3 (linux/amd64)

go version go1.22.3 linux/amd64

blee@litten ~/o/s/n/s/replicatr (master|✔)>

blee@litten ~/o/s/n/s/replicatr (master|✔)> go build

...

go: downloading github.com/valyala/bytebufferpool v1.0.0

# mleku.net/nostr/envelopes

/home/blee/go/pkg/mod/mleku.net/nostr@v1.0.1/envelopes/process.go:29:25: undefined: sentinel.Read

```

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

ah, i saw this same kooky error in my colleague's VScode GUI, and it's complete nonsense, because if you go to the nostr/envelopes directory, you find this:

https://mleku.net/nostr/blob/master/envelopes/sentinel/read.go

package sentinel

...

func Read(buf *text.Buffer, match string) (env enveloper.I, err error) {

idk what the fuck this is coming up from, but it's wrong

we had this same shit appear in the VScode IDE when it was on the github repo too, i'm very curious to know why it flags this error because it's nonsensical