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?
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?
$ yarnd --help 2>&1 | grep 'max-cache'
--max-cache-fetchers int set maximum numnber of fetchers to use for feed cache updates (default 12)
-I, --max-cache-items int maximum cache items (per feed source) of cached twts in memory (default 150)
-C, --max-cache-ttl duration maximum cache ttl (time-to-live) of cached twts in memory (default 240h0m0s)
But you would have to supply insanely large values. Better solution would be to improve the search codebase and then incorporate those improvements (hopefully in a reusable way) into
yarnd itself so we can index and search the archive.
$ yarnd --help 2>&1 | grep 'max-cache'
--max-cache-fetchers int set maximum numnber of fetchers to use for feed cache updates (default 12)
-I, --max-cache-items int maximum cache items (per feed source) of cached twts in memory (default 150)
-C, --max-cache-ttl duration maximum cache ttl (time-to-live) of cached twts in memory (default 240h0m0s)
But you would have to supply insanely large values. Better solution would be to improve the search codebase and then incorporate those improvements (hopefully in a reusable way) into
yarnd itself so we can index and search the archive.
I'm not sure how to optimize this but I guess it depends on the demand for such a feature.
> 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.
I disagree with that. I always enjoy reading what people have to say about blog posts, and it's not uncommon for comments to be months or even years apart. Discussion doesn't have to be "alive" for a comment to be worth reading.
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.
> 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.
This βοΈ There will be zero ways to "moderate" or "filter" such content if one were to use teh soon and upcoming search of any given Yarn.social pod. The only way for a user to filter content or hide things is to have an account on said pod where things like "hidden twts" and "muted feeds" can be taken into account.
It _might_ be possible to do things like "exclusion matches" and such, but now that's getting into some tricky territory. Oh well, let's see how it goes π -- Google already indexes all pods anyway π€£
> 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.
This βοΈ There will be zero ways to "moderate" or "filter" such content if one were to use teh soon and upcoming search of any given Yarn.social pod. The only way for a user to filter content or hide things is to have an account on said pod where things like "hidden twts" and "muted feeds" can be taken into account.
It _might_ be possible to do things like "exclusion matches" and such, but now that's getting into some tricky territory. Oh well, let's see how it goes π -- Google already indexes all pods anyway π€£
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.
To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._
To really support this kind of thing, you'd really have to "dynamically" create a new feed for every user, uniquely identify them in some way so you can do this (e.g: with OAuth, IndieAuth, etc), then have an API or Form that they can enter content to and it write to "their" feed._
yarnd instance (a Yarn.social pod), embed a widget on the website that uses IndieAuth to your pod, dynamically creates a new feed for the user(s) and the widgets uses microPub to post to their feed on their behalf via some Javascript.Of course we're still missing microPub support.
yarnd instance (a Yarn.social pod), embed a widget on the website that uses IndieAuth to your pod, dynamically creates a new feed for the user(s) and the widgets uses microPub to post to their feed on their behalf via some Javascript.Of course we're still missing microPub support.
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.