A topic change by a local user takes the current time as the topic timestamp, and does not consider the situation where the topic timestamp is greater than the current time. This is fine for topics on local channels, but for global channels, the topic change is ignored upstream because the timestamp is smaller than the topic timestamp. For glines and jupes this problem is fixed by using lastmod+1 in that case. I think it would make sense to do the same for topics, to prevent getting stuck with a topic from the 'future'.
Log in to post a comment.