Imported but shows this regardless:

Reply to this note

Please Login to reply.

Discussion

The only use case I have for this is that I created private Twitter accounts for my kids to post the funny things they said. I downloaded backup archives of all of them and wouldn’t mind hosting them somewhere else but I’m not sure I want to go to all the trouble.

Yeah I don't see the issue with it if it still shows when it was first seen put on bluesky

Yup. And Nostr has the same issue (date of an event can be in the past) but showing such a warning on Nostr is much harder.

-A relay might not record the time it received an event

-A relay might record the time it received an event but this information isn't exposed to clients

-A relay might record the time it received an event and this information is exposed to a given client but that client might not care

-A relay might record the time it received an event and this information is exposed to a given client and that client might care but it is unable to determine whether something suspicious is going on (are the event date and receipt date out of alignment for THAT relay only, perhaps because the event was rebroadcast, or is something else at play, need more data...)

There's been lots of talk over the years of relays that check the timestamp. But I dont think we have that yet. It would be very valuable for certain use cases.

Wonder if you posted with a timestamp in the future how many clients would leave at the top of the feed?!