@prologic@twtxt.net (#https://twtxt.net/search?tag=tsvhqdq OK. Im upgrading my tools. twtxt works pretty well inside an Emacs shell window…
in the original twtxt your URL is your identity. No need for anyone outside your control to do account managment. One reason I’ll likely be sticking with command line. But, great work
What flavor or regexp? I tried here https://regexr.com/ with both PCRE and JavaScript and neither seems quite right. I’m relatively good with regexps, but they tend to be write-only :-/
yes. I read that. Nice post. Brave browser at least has trouble with formatting. The regexp got lost when renederd. Eww (emacs text browser) doees just fine with it :-)
@prologic@twtxt.net what is the exact syntax neeed for threads to work in the subject, e.g. will (#tsvhqdq) do it? The whole … (#tsvhqdq) thing seems like a bit of overkill. Too many characters.
as the person who motivated CompuServe’s USENET gateway https://www.chicagotribune.com/news/ct-xpm-1994-10-07-9410070309-story.html I’ve see what happens when the unwashed masses are turned loose in techie playgrounds
One very real problem to be aware of is “Eternal September” https://en.wikipedia.org/wiki/Eternal_September
one problme I’m seeing already is that the “micro” part is loosing out. Things are routinely getting longer than 140 characters
@prologic@twtxt.net I will probably stick with command line client just to make sure it keeps working
@prologic@twtxt.net and the fact that I just used /bin/ed to fix spelling before pushing :-)
@prologic@twtxt.net also the lack of a login and complete decntralization is a big win.
@prologic@twtxt.net twtxt is so simple one could read with netcat, cat and tail. I like that.
@prologic@twtxt.net For now I think I will stay with primitave tools.