@prologic@twtxt.net would that need a NLP library? The lang would be great for a search engine to find language prefs.
@prologic@twtxt.net @darch@twtxt.net Like with many things that live in a diaspora there will be many names for about the same thing. Just look at e-mail headers!
@vain@www.uninformativ.de I have seen it pop up on a few feeds around and adopted it into the new parser I built.
The format I have followed has been '# ' :whitespace: :key-name: :whitespace: '=' :whitespace: :value:
keys can be repeated and accessed like an array of values.
@prologic@twtxt.net fixed.
@prologic@twtxt.net I know! it has 55 new emoji!! \u1F90C
@prologic@twtxt.net @jlj@twt.nfld.uk @thewismit@twtxt.psynergy.io https://gist.github.com/JonLundy/fb2a23c003be46c3a66e4b14e5971f13
@xuu@txt.sour.is @prologic@twtxt.net @thewismit@twtxt.psynergy.io ah.. probably a bug with the re parser. looks like i can do it without the <>’s with lex
@thewismit@twtxt.psynergy.io @prologic@twtxt.net Yo. wrap that naked link in some <>’s https://fosstodon.org/@/105673078150704477
@iolfree@tilde.club “I just typed in ‘censorship’ on pinterest and that is also completely banned.” https://i.imgflip.com/1ppi4p.jpg
@prologic@twtxt.net deedum for android.
Kristall for OS X
Elaho for iOS
though I can only vouch for the first two.
@thewismit@twtxt.psynergy.io @darch@twtxt.net @adi@twtxt.net @prologic@twtxt.net There is another: @hecanjog@hecanjog.com
@prologic@twtxt.net That is strange.. i wonder if there is another change that is causing it. Benchmarks are thinking the other way :|
BenchmarkAll/retwt-16 1 4940172200 ns/op 587319376 B/op 2587159 allocs/op
BenchmarkAll/lextwt-16 1 775764020 ns/op 9223088 B/op 197557 allocs/op
BenchmarkParse/retwt-16 1 591158277 ns/op 67539096 B/op 230841 allocs/op
BenchmarkParse/lextwt-16 1 716961837 ns/op 5450448 B/op 130290 allocs/op
BenchmarkOutput/retwt-html-16 1 8358103017 ns/op 918709168 B/op 4692292 allocs/op
BenchmarkOutput/lextwt-html-16 1 822033267 ns/op 14280112 B/op 261795 allocs/op
BenchmarkOutput/retwt-markdown-16 1 8114225415 ns/op 929928384 B/op 4693004 allocs/op
BenchmarkOutput/lextwt-markdown-16 1 806554306 ns/op 14332608 B/op 270905 allocs/op
BenchmarkOutput/retwt-text-16 1 8098215897 ns/op 923862192 B/op 4684739 allocs/op
BenchmarkOutput/lextwt-text-16 1 745064673 ns/op 12689784 B/op 252476 allocs/op
BenchmarkOutput/retwt-literal-16 1 4068799822 ns/op 409517880 B/op 2372471 allocs/op
BenchmarkOutput/lextwt-literal-16 1 754793627 ns/op 9834520 B/op 214931 allocs/op
@xuu@txt.sour.is @jlj@twt.nfld.uk @hxii@0xff.nu only if you look at the raw text file https://0xff.nu/blog.txt
@jlj@twt.nfld.uk oh dang the reply didnt add the reply. It was to @hxii@0xff.nu because Firefox shows his shruggy like ¯\_(ツ)_/¯
@prologic@twtxt.net @hxii@0xff.nu I’m certain that it is a markdown thing. Its that way on other markdown sites like Reddit. Because the underline is being escaped to prevent the underline style. Gotta double it up ¯\_(ツ)_/¯
FOLLOW: @xuu@txt.sour.is from @hxii@0xff.nu using picoblog/0.1.1
@jlj@twt.nfld.uk “Wow. I think much of what drew me to zettlekasten – and then letting it languish :-( – really belongs in Anki.” i have only used SRS for ~3 months now, so I’m not sure how long i’ll continue
@pbatch@pbat.ch “Writing a “tweet” is low-friction, and the medium forces you to chunk out ideas into (mostly) self-contained thoughts.” <3
FOLLOW: @xuu@txt.sour.is from @thewismit@twtxt.psynergy.io using twtxt/0.1.0@6379df1
FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@51889ee2021-01-26T21:02:50Z FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@0b6d6822021-01-27T18:29:57Z FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@bea2d23
@lyse@lyse.isobeef.org @prologic@twtxt.net @vain@www.uninformativ.de A penny saved is a penny depreciating at a rate of 1.4% per annum.
FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@174baf7
FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@174baf7
FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@174baf7
FOLLOW: @xuu@txt.sour.is from @asdf@0.0.0.0 using twtxt/0.1.0@9b57da3
@vain@www.uninformativ.de “I don’t know. But you got me.” <3
FOLLOW: @xuu@txt.sour.is from @alice@twt.nfld.uk using twtxt/0.1.0@0f0603f
@lyse@lyse.isobeef.org @prologic@twtxt.net I think lex will do that too currently. Should be able to lock that down.
@lyse@lyse.isobeef.org (#ezmdswq) Looks good for me!
@thewismit@blog.thewismit.com @prologic@twtxt.net I too wonder about this.
@prologic@twtxt.net @thewismit@blog.thewismit.com (#nicbdoq) possible, or a pod following any feeds it finds, if any one follows or not. So it has more twts cached
@prologic@twtxt.net (#ffxaisq) Should be ready to merge with lex as opt-in option. Need more eyes on it and some clean up.
@prologic@twtxt.net @thewismit@blog.thewismit.com (#nicbdoq) Ya I get that error a lot. I mostly use the web on mobile as a result.
@prologic@twtxt.net i think i finally suss’d out my hash issue.. now to figure out why im losing avatars on restart.
@prologic@twtxt.net @thewismit not sure.. im using Caddy instead of nginix
FOLLOW: @xuu@txt.sour.is from @thewismit@blog.thewismit.com using twtxt/0.1.0@b7f7c09
@prologic@twtxt.net lol.. sorry about the spam
@xuu@txt.sour.is @prologic@twtxt.net (#6jkpxzq) hmm from what i can tell its parsing ok.. something got broken in the markdown conversion…
@prologic@twtxt.net hmm this line seems to be tricky to parse. will need to look into it.
@prologic@twtxt.net test. Running new parser on txt.sour.is. :D
FOLLOW: @twtxt@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@6987434
FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@6987434
@prologic it seem to work just fine for the most part. http://darch.dk/twtxt.txt for refernce
FOLLOW: @xuu@txt.sour.is from @asdf@::1 using twtxt/0.1.0@90d1c09
@prologic@twtxt.net that would be an interesting idea. I think your current spec of using an SMTP proto is probably best for DM.
but having a federation of IRC servers would be interesting for realtime twt propagation.
@prologic@twtxt.net the meta info on the top I added manually. it’s following what I have seen from some other twtxt feeds. the new parser will read them.
@prologic@twtxt.net Veri soon. I have a experimental runflag that I am just about to deploy to my node. I have a few show stoppers holding me back.
Woohoo, #phpub2twtxt - my php interface for publishing to my selfhosted twtxt.txt is now online at GitHub
@lucidiot@tilde.town “nuclear realtor” I like this twtxt. [meta: I guess I’ll often just reply with “I like this” or , although perhaps liking could be a primitive. I’ll do it rarely enough to not clutter my timeline tho]
FOLLOW: @xuu@txt.sour.is from @jlj@ctrl-c.club using twtxt/1.2.3
@prologic@twtxt.net sometimes I think it would be nice to have a XMPP instance. then I remember it’s all XML and I think “nah.”
I am constantly in awe that IRC remains the only realtime chat that isn’t unnecessarily complex. name another that can run chatops bot with just nc and sh?
FOLLOW: @xuu@txt.sour.is from @adi@46.23.94.13 using twtxt/0.1.0@7098fcf
@adi@twtxt.net “@niplav What kind of thinking?” Leaning towards explicit abstract reasoning, though, if I would be pressed.
@adi@twtxt.net “@niplav What kind of thinking?” Nearly everything, I guess? More concretely: What falls into the category of whatever spans {deciding where to sit, deciding whether to blame someone else for something, catching a ball, picking a good career, proving a theorem}.
@prologic@twtxt.net @xuu@txt.sour.is Closer! Last bit to finish is a beast. FormatTwtFactory
@vain@www.uninformativ.dedd @lyse@lyse.isobeef.orgdd @prologic@twtxt.netdd Nope.. i have updated my gist to include the feeds listing. feeds.txt
@prologic@twtxt.net that seems to match my numbers. are you picking up the few gophers out there?
kinda makes me wonder about the ~300k you have cached. y’all got the library of alexandria over there.
FOLLOW: @stats@txt.sour.is from @xuu@txt.sour.is using twtxt/0.1.0@9d7b86c
@prologic@twtxt.net in theory shouldn’t need to let users add feeds.. if they get mentioned by a tracked feed they will get added automagically. on a pod it would just need to scan the twtxt feed to know about everyone.
@prologic@twtxt.net sounds about right. I tend to try to build my own before pulling in libs. learn more that way. I was looking at using it as a way to build my twt mirroring idea. and testing the lex parser with a wide ranging corpus to find edge cases. (the pgp signed feeds for one)
Well, my twtxt reader is a bit too simple; drops who actually wrote the message before it’s printed. 🤦🏻
@prologic@twtxt.net the add function just scans recursivley everything.. but the idea is to just add and any new mentions then have a cron to update all known feeds
@prologic@twtxt.net yeah it reads a seed file. I’m using mine. it scans for any mention links and then scans them recursively. it reads from http/s or gopher. i don’t have much of a db yet.. it just writes to disk the feed and checks modified dates.. but I will add a db that has hashs/mentions/subjects and such.
@prologic@twtxt.netd It is pretty basic, and depends on some local changes i am still working out on my branch.. https://gist.github.com/JonLundy/dc19028ec81eb4ad6af74c50255e7cee
@lyse@lyse.isobeef.org @prologic@twtxt.net very curious… i worked on a very similar track. i built a spider that will trace off any follows =
comments and mentions from other users and came up with:
twters: 744
total: 52073
curl https://raw.githubusercontent.com/jointwt/we-are-twtxt/master/we-are-twtxt.txt | grep -v '^niplav ' | field 2 | xargs curl ^/dev/null | grep niplav
here we go
@prologic@twtxt.net “What the hell does cartesianly mean?! 😳” Me inventing a new adjective for “there is only a one-way flow of information” ^^
Maybe I could write a script that trawls the we-are-twtxt list and notifies me when I’m mentioned–the name should be unique enough.
Disadvantage of twtxt: less incentives to reply to people since it’s not certain they’ll ever see it. My current solution to that is to follow everybody on the we-are-twtxt and only unfollow if they twt a lot of stuff I’m not interested in
@felixp7@twtxt.net “Yo, crypto-heads. Encrypted communication doesn’t protect your privacy. Laws …” I guess crypto-heads are often happy with acknowledging this, but also arguing that e.g. deniable crypto is a useful way out here (and, of course, just doing illegal stuff if it gets really rough).
FOLLOW: @xuu@txt.sour.is from @niplav@niplav.github.io using txtnish/0.2
Following with interest the developer activity regarding the twtxt spec at twtxt.net
Okay, my #twtxt reader works-ish. Need to properly deal with timezones (and, um, maybe do any error checking).
I have a working model for the reader portion of what I want this twtxt client to do.
@prologic@twtxt.net I am trying to cut costs, so I deleted all my Digital Ocean droplets. For a month I will be using a free s390x VPS, so I needed to adapt some of my Docker images, scripts and configurations for that architecture. Also took another chance with Traefik Proxy, I ditched it long ago for nginx-proxy, but this time I made it work. #h5nn5tq
@prologic@twtxt.net that I do. lol. I am xuu on hackint.org and freenode
@prologic@twtxt.net sure. I don’t use signal much because I have to disclose my personal phone. Telegram? https://www.t.me/xypheri
go run ./cmd/stats https://twtxt.net/user/prologic/twtxt.txt
@xuu@txt.sour.is @prologic@twtxt.net Your feed was great for catching edge cases ;)
@prologic@twtxt.net https://github.com/JonLundy/twtxt/tree/xuu/integrate-lextwt I made a stats command for the new parser that extracts a bunch of info about a twtxt file. run like: go run ./cmd/stats https://twtxt.net/user/prologic/twtxt.txt
FOLLOW: @xuu@txt.sour.is from @lyse@lyse.isobeef.org using twtxt/1.2.3
@prologic@twtxt.net yep!some of the lexer is directly copied from monkey-lang. love that book series.
@prologic@twtxt.net ah I need to add an edge case for naked urls with fragments.
@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
@adi@twtxt.net @prologic@twtxt.net using regex. which can be a rather inexact science ;)
@prologic@twtxt.net kinda.. It can parse the twts into an AST.. but most of the formatting out expects a string to do regex over rather then the parsed AST. thats what i am working out next.
@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.
the !zet I have written for my wiki is probably going to end up replacing what I’ve been using twtxt for these past few months. this means less spam here. you’re welcome.
@prologic@twtxt.netdd ooh I am adding that to my test suite
@prologic@twtxt.net @gareppa Tis fake.. that is the name of the tower in Die Hard. A movie that takes place on Christmas Eve. The actual name of the Nakatomi Plaza is the FOX Plaza.
@prologic@twtxt.net I agree, should have asked for help. Neither the bridge network nor any other bridge-based custom network allowed the containers to contact external servers, it might have been an iptables issue. #twflvza
@prologic@twtxt.net went over to watch this one in my home town last night. https://youtu.be/kUZB0_Jx3iE
@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)
WEBMENTION: @xuu@txt.sour.is on https://twtxt.net/twt/pcqworq
@xuu@txt.sour.is yikes the style sheet for blogs needs help.
@prologic@twtxt.net (#5jqioeq) Wrote up a blog post here: https://txt.sour.is/blog/xuu/2020/12/21/twtxt-auto-discovery
New Blog Post Twtxt Auto Discovery by @xuu@txt.sour.is 📝
@deadguy @prologic@twtxt.net been stewing on a discovery proto for twtxt. support for defining multiple ways to host/mirror a twtxt file. while being low tech enough to still be scriptable with basic Unix commands.