@mckinley@twtxt.net I didn’t thought too much about it.

Personally I think that if a discussion is alive posts will be there, I don’t really mind if an old post/page lose its comments.

A solution might be a pod with an option to store twts forever?

@prologic@twtxt.net oh, I see.

I’m not sure how to optimize this but I guess it depends on the demand for such a feature.

@prologic@twtxt.net I’ll leave it to you, “Go” forth my warrior! 😎👌

@prologic@twtxt.net Great! And that would be the source of the data to show in a potential external page too.

@mckinley@twtxt.net You’re absolutely right, that’s why I kept mentioning it as a personal preference. 😁

When I browse the web I almost entirely look for information with an “expiration” (tech and code related stuff tends to get old fast) and quite often if the topic is too outdated the only useful comments are the ones like “Hey! It’s been two years now, here’s a better way.” with some links to a newer page of some kind.

Of course I’m open to both cases to allow freedom of choice for everyone on how they want to handle that.

Another risk on a persistent comment system is to remember to have a way to moderate the posts, since you need to control what gets on your page and can potentially stay there forever.

@prologic@twtxt.net Better not, it’ll become a mess.

I think it can be managed with something like a dedicated system that interact with yarn or twtxt in general and act as a specific system for comments and discussion to embed in the hands of the site owner.

@prologic@twtxt.net Yes, the way I can think of, by using the @darch@neotxt.dk way, is to have a feed with a user annotation within the twt and post everything on a single feed controlled by the owner.

It initially was a simple idea thrown there and so much has been built for it, it’s amazing. 😲

Also some feedback from other people on the matter might help us find some other great solutions.