rm data/cache* and it's all good, things will just get rebuilt π
$ whois shortcircuit.net.au 2>&1 | grep -i creat
created: 1986-03-05
I _think_ this has to be the registrar's creation date no? π€
shortcircuit.net.au π
printf?!_)
The only part of this design I'm not 100% sure about is the Javascript-based challenge handling? π€ I'm also considering making this into a "proof of work" requirement too, but I also don't want to falsely block folks that a) turn Javascriptβ’ off or b) Use a browser like
links, elinks or lynx for example.Hmmm π§
yrand branch and run it up on say something like a yarnexp.mills.io or something π€
> Mentions are embedded within the text in either @
So the lextwt parser we use will simply call this an invalid mention, which it does.
> Mentions are embedded within the text in either @
main π€£ I'm fixing little things here and there. Also please report bugs π
* 101f3eb0 - (HEAD -> main) Fix a bunch of UX to do with following/unfollowing, bookmarking and unbookmarking (3 seconds ago) <James Mills>
Testing UI/UX is hardβ’ π
yarnd.
main recently? π€
q or a π€£
git checkout main && git pull, rebuild and redeploy: make build, and however you deploy. π Lots of fixes (_no more stalling_) and optimizations to the feed fetcher, smoother cpu usage, better internal metrics.
main. I merged the catcher branch already!
git checkout main && git pull && make build. Few bug fixes π
π Can I imply you're not interested in things like "LIke", "Report", etc?! π
yarnd v0.16 is released and the next round of specification updates are done and dusted, who wants me to have another crack at building Twtxt and activity pub integration support?
> where did this hash come from?
1. Replying to a Twt that has no initial Subject must itself have a Subject of the form (hash; url).
This way itβs a hint to fetching clients that follow B, but not A (in the case of no mentions) that the Subject/Root might (very likely) is in the feed
url.
It isn't that I've not considered all the other options on the table (_which can still be_), it's just that I've made a decision as the project lead that largely helped trigger a rebirth of the use of Twtxt back in July 1 2020. There are good reasons not to change the threading model right now, as the changes being proposed are quite disruptive and don't consider all the possible things that _could_ go wrong.