monlovesmango

> on first start query all events (until EOSE), then store timestamp, then query events with since = timestamp - 1h (or some amount of time to account for client...

this would require finding all the ancestors for any particular event in order to create a reply which adheres to this standard. since there are already many clients not adhering...

@arthurfranca >It would be enough to turn the previous id that has "reply" marker (or the last one, if deprecated way) into an ancestor e tag. if you do this...

I like these changes, much clearer. >Clients MUST NOT include multiple "e" tags with the same marker in an event. Shouldn't you be able to have multiple 'mention' events tagged?

@alexgleason from the looks of your example the problem is nested mentions are pulling in, not that there are multiple mentions This PR initially was created to just clarify wording...

not opposed to bringing back kind 6, however kind 6 is only for reposts to my understanding. quote posts would still need to be able to use the mention 'e'...

not opposed to that. but we would still need `root`, `reply`, and `mention` markers then for kind 6 then.

in astral I just created a warning every time someone creates their first follow to confirm that they don't actually have any follows. my gut feeling about this pr is...

at first glance, I really like this idea @vitorpamplona . making an individual follow event for each person you follow seems pretty straightforward and eliminates the possibility of wiping existing...

I think this happened if you didn't already have a permissions object saved and you try to set permissions for new host. just ran into this and making pr now....