PEP 656: Platform Tag for Linux Distributions Using Musl ⌘ Read more…

@prologic@twtxt.net Vim, and it’s really not that awful.

@prologic@twtxt.net 36 characters left makes it rough.

@darch@twtxt.net Just inline images, they wrap like text.

@adi@twtxt.net I can’t find it now, keep an eye out for it.

Code: new version of oppinionated Ansible role to install Golang ⌘ Read more…

@adi@twtxt.net Thanks, man. I’ll take a look.

@prologic@twtxt.net Logs say it’s just you :)

@prologic@twtxt.net 36% of requests since I enabled logs

@prologic@twtxt.netYes, I think tags should just be #foo, and let the client figure out searching if it cares.

@lyse@lyse.isobeef.org Yes, I often read the raw messages. But more to the point, the simplicity of the format is the bulk of the appeal.

@movq@www.uninformativ.de No argument that threading is an improvement. But I think (#hash) does that, and I think figuring out how to search should mostly be up to the client.

I don’t have any issue with the (foo) subjects, it’s the proliferation of the (foo url) tags. They’re just too long and ugly.

@jlj@twt.nfld.uk “@niplav (#4qeibma) Hadn’t heard of this; thanks for the tip! Been getting lost in your text reviews; the Benatar piece piqued my interest: I’d been reading a critique of his earlier work – in Overall’s Why Have Children? – that really wasn’t up to scratch. Now I’m reading about pure replicators, which is a new concept, to me. :-)” -> Nice :-) Looking over my text reviews, they’re not quite finished (especially the Benatar one), so take it with a grain of salt

@prologic@twtxt.net I’ve just never had it be a rewarding experience.

@prologic@twtxt.net rc, the Plan 9 shell.

Stacy got the heels and the brand new tags 😝 ⌘ Read more…

Code: new version of opinionated Ansible role to install Golang ⌘ Read more…

@prologic@twtxt.net Wow! Really interesting perspective! Thanks for sharing. :-)

@prologic@twtxt.net Wow! Really interesting perspective! Thanks for sharing. :-)

@prologic@twtxt.net I see Consul service mesh everywhere these days, X-D thanks to a 180 career change and major upskill.

@prologic@twtxt.net I see Consul service mesh everywhere these days, X-D thanks to a 180 career change and major upskill.

@prologic@twtxt.net Really helpful context: was definitely over-engineering. Cheers!

@prologic@twtxt.net Really helpful context: was definitely over-engineering. Cheers!

@prologic@twtxt.net The favicon in particular! :-)

@prologic@twtxt.net The favicon in particular! :-)

@prologic@twtxt.net lol. quitfacebook.org is still up. twt is set to be on more radars, though. ;-)

@prologic@twtxt.net lol. quitfacebook.org is still up. twt is set to be on more radars, though. ;-)

@prologic@twtxt.net Yeah, a completely-unsolicited surprise! :-) And, sweet! To IRC then!

@prologic@twtxt.net Yeah, a completely-unsolicited surprise! :-) And, sweet! To IRC then!

@prologic@twtxt.net yep. it actually extracts everything at parse time. like mentions/tags/links/media. so they can be accessed and manipulated without additional parsing. it can then be output as MarkDown

@prologic@twtxt.net as promised! https://github.com/JonLundy/twtxt/blob/xuu/integrate-lextwt/types/lextwt/lextwt_test.go#

the lexer is nearing completion.. the tough part left is rooting out all the formatting code.

@oevl@twtxt.net @prologic@twtxt.net (#) for the most part a subject is just the content in the perens. Usually it’s a tag. It appears near the start after any mentions. It can also contain text like (re: subjects)

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.

@prologic@twtxt.net Txtnish adds a 28 character timestamp to the message, so in Bash: tweet=tail -1 the current twtxt.txt file and then pipe echo body=${tweet:28} to twt.

@prologic@twtxt.net (#keh22ka) maybe a custom linking method on a pod level? like can pass a template that gets translated. ex https://{domain}/wiki/{nick}/{tag} + !somepage -> https://sour.is/wiki/xuu/somepage

@prologic@twtxt.net do you have any info on how the ‘!’ tags are supposed to work? are they just a different kind of hash tag?

Code: new version of oppinionated Ansible role to install Golang ⌘ https://github.com/sascha-andres/ansible-role-golang/releases/tag/v1.15.6

@prologic@twtxt.net I have some ideas to improve on twtxt. figure I can contribute some. 😁 bit more work and it will almost be a drop in replacement for ParseFile

Kinda wish types.Twt was an interface. it’s sooo close.

@xuu@txt.sour.is Not too happy with WKD’s use of CNAME over SRV for discovery of openpgpkey.. That breaks using SNI pretty quick. I suppose it was setup as a temporary workaround anyhow in the RFC..

Code: new version of my opinionated Golang role for Ansible ⌘ https://github.com/sascha-andres/ansible-role-golang/releases/tag/v1.15.5

i just realized i have no idea how to tag/mention someone else on this thing. i tried but i don’t think it worked?

@prologic@twtxt.net (#https://twtxt.net/search?tag=tsvhqdq OK. Im upgrading my tools. twtxt works pretty well inside an Emacs shell window…

and then ignore it “notmuch search not tag:unsubscribe and date:yesterday..”

tag anything with the word “unsubscribe” by “notmuch tag +unsubscribe unsubscribe”

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

FWIW, I put up a quick blog last night about using twtxt command line https://eludom.github.io/blog/hello_twtxt/

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.