@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

I just built a poc search engine / crawler for Twtxt. I managed to crawl this pod (twtxt.net) and a couple of others (sorry @etux@twt.u53.us and @xuu@txt.sour.is I used your pods in the tests too!). So far so good. I might keep going with this and see what happens 😀

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 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

@xuu@txt.sour.is Are you interested in getting on Signal and swapping contact details and such so we can discuss some ideas in collaboration in more real-time? You have great ideas, I think we could benefit from a bit more real(ish) time 😀

@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

@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.

@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.

Breaking News
Shots fired at Nakatomi Plaza
Possible hostage situation unfolding in Los Angeles on Christmas Eve

@prologic@twtxt.net went over to watch this one in my home town last night. https://youtu.be/kUZB0_Jx3iE

#ChristmasLights #2020

Oooh I like this one! 👌

#ChristmasLights #2020

@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)

@xuu@txt.sour.is yikes the style sheet for blogs needs help.

@prologic@twtxt.net () 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.

@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.

@adi @prologic@twtxt.net I’ll give it a spin first thing in the AM

@xuu@txt.sour.is @adi@twtxt.net Private Messaging is finally done in the messages_poc_2 branch. If you have time to have a look and play with it locally and test it out that would be great. The plan is to release this as the first version which only supports “on-pod messaging” right now (cross-pod to come later).

btw my main feed is on gopher now too gopher://tilde.team/0/~dgy/twtxt.txt

@prologic@twtxt.net when its ready.. this is still in beta.

@prologic@twtxt.net yeah it would replace rice. best part is that it’s in the go build step so you don’t need to do any prep work with make.

@prologic@twtxt.net after stewing on it. I really like the idea of a wiki. throw it on the roadmap after DMs 😆

@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 found it!

2020-07-25T00:52:27.000000Z a new twtxt/weewiki feature: any word starting with ‘!’ will translate to an internal weewiki reference in my HTML renderer. Example: here is my !wiki_index

@prologic@twtxt.net https://txt.sour.is/twt/cwqmygq

@prologic@twtxt.net I see them is why I ask. like here #cwqmygq they use both hashtag and bangtag?

@prologic@twtxt.net 😁 that is me testing locally. does it notify you somehow when I follow?

@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?

@prologic@twtxt.net one.. kinda sorta option would be to tailor a workflow for each of the archs.. see https://github.com/JonLundy/twtxt/runs/1568071072?check_suite_focus=true

@xuu@txt.sour.is @prologic@twtxt.net oh.. you are.. maybe i don’t understand the issue with building?

@prologic@twtxt.net have you tried using the macos github build environment? looks like they have a windows one too.

@prologic@twtxt.net you think its time the version to get bumped? :)

@xuu@txt.sour.is @prologic@twtxt.net had to up my twt size a bit.

@prologic@twtxt.net

-----BEGIN CRYPTUTIL ENCRYPTED MESSAGE-----
l0GwFAQpx3ed+bZlcQ+pexbynFzZOm8EI/FivGbWQ16whyTkToVv8S2GSAjrsJoT
37MdaBDpoitli/f/aP130b6O6SnK/LdHHJ1DTvWgxB14sq9b4mRtk7HvYzA=
-----END CRYPTUTIL ENCRYPTED MESSAGE-----

@xuu@txt.sour.is @prologic@twtxt.net This? Fingerprint: 161c614f08e4ed4d1c8e5410f8c457e6878574dbab7c9ac25d474de67db1bdad

@prologic@twtxt.net I use https://key.sour.is/id/me@sour.is

I would need an out-of-band way to verify your public key’s fingerprint though 🤣

@prologic@twtxt.net Ok.. so using NaCL boxes. yeah its just a combo of using secretbox with a generated key/nonce. and then using the pubkey box to encrypt the key/nonce for each device.

@prologic@twtxt.net

Can we not have clients sign their own public keys before listing them on their Pod’s account?

Yeah.. we probably could. when they setup an account they create a master key that signs any subsequent keys. or chain of signatures like keybase does.

@prologic@twtxt.net def would be a wider discussion on preventing the pod from adding its own key to a users device list. Or using device keys to authenticate instead of user/pass.