Doug Hoyte

My issue wasn't with the ffff, but that it was missing a `::`, see this website: Bad: http://v6decode.com/#address=ffff%3A123.83.123.203 Good: http://v6decode.com/#address=%3A%3Affff%3A123.83.123.203 But probably you're right and it is just github mangling...

Hi! Sorry about this, but yes, the `sync` functionality is currently broken. I was working on a big overhaul that will fix this, but then I got pulled away for...

The only thing about using plugins for read is that calling into another process would add a lot of extra latency. My instinct is that this latency would be too...

If it was 0 impact when disabled, yes, most likely I would merge it unless it required really invasive changes to the code-base. I suggest once you have a design...

Getting it into Debian is a big pain, I don't really want to bother with that now. Precompiled binaries could work, but we'd probably need to compile them statically, which...

Neat idea! I would definitely be open to proposing this as a NIP. My only worry is that maybe with some more applications we might come up with some improvements,...

A sad day for the internet...

Thank you! You're completely right about the `d` tag being useful for querying. Especially if the user has a large number of PREs of the same kind. I'll edit the...

> Also expiration being less than created_at should automatically imply the event is treated as ephemeral? EDIT (mis-read this). This could work too. What would the different possible values for...

> One potential source of conflict is if people put d tags (with different values) on events which were historically considered replaceable like 0, 3, 41, 10000-19999 I think it...