@prologic@twtxt.net damn, your reply got me an idea…
What if you can use a thread as discussion externally?
I was actually searching for something similar around for myself for curiosity.
Think of it like a widget similar to Disqus.
You can embed a discussion on your site like a comment system.
It might even help spread the use of twtxt with people who don’t know of it.
@prologic@twtxt.net I see, what I imagined was simply reading a thread embedded in a page, especially on a static site.
I’m not too aligned on the whole IndieWeb features, I’ll have to check it out deeper. 😲
@prologic@twtxt.net I’ll look into those! 😎
@justamoment@twtxt.net I kinda had the same idea for using a twtxt file for incoming comment on a blog and the people could follow that feed to see the comment.
A way to implement it would be like I did at http://algorave.dk/bbs where everyone can comment if they know know the password
@prologic@twtxt.net Mine was just a simple idea, nothing more, your analysis of the process is just perfect, I haven’t really thought about it that deep, if it’s possible it would be amazing.
Just a note from me, I love working statically in general (no servers, no databases, no worries) so my motto is to rely on a external services to handle the moving parts or to push the dynamic parts to the code, like how Netlify CMS does it. It might help further analysis. 🥸
@darch@twtxt.net A BBS is nice but I don’t know how to handle that on a public site, does it use an invite system?
The twtxt concept always amazed me, so many possibilities. Even in such a small scale it can really handle something like Twitter does with just plain txt files, I can’t wrap my head around it yet. 😲
@justamoment@twtxt.net if you can guess the password you are in. Not very secure, but maybe it does not need to be
@darch@neotxt.dk it might be fine in some cases but it might be accessible to spam bots too I think? 🤔
Maybe an approval system to cover it, but it seems too much in my opinion.
Meanwhile I ended up putting together a Proof of concept for the widget I mentioned.
Here the repo https://git.mills.io/justamoment/yarn-conv-widget
Published without the link, here again: https://git.mills.io/justamoment/yarn-conv-widget
Live demo: https://sunetraalex.gitlab.io/yarn-conv-widget/
Note: you might want to try with a proxy since CORS is not enabled, like I did in the screenshot below.
@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?
@mckinley@twtxt.net does it happen? 😮 Didn’t know
@eaplmx@twtxt.net yeah, the posts goes but the txt stay.
Am I right @prologic@twtxt.net?
@prologic@twtxt.net for me not seeing a couple of old twts is no big deal, but if more people would like it that feature then we can consider a way to fix it.
@prologic@twtxt.net that exactly my logic in why I don’t care.
As time progresses people opinions and everything else does too, even I could find one of my own old posts disappointing and then think: “Why did I say that?”
What can be done instead could be something like, “This is a good post! I wanna pin it for storage manually”.
Like when someone gives a better alternative to a problem in a comment but, even there, if it’s this good of a comment I would take care to grab it and update my own content to share it with everyone even with who might or might not read the comments.
After all, the only comments that tend to be remembered, from what I’ve seen, are the bad ones. 🫣
@prologic@twtxt.net yes, I know about the bookmarks and I use them too, what I meant is a way to store important bits in the context of a comment system, as the related content owner while thinking of people who might read the content and ignore any comments regardless of the posts age.