@bender@twtxt.net just a heads up im thinking of rewriting the database schema with hash v2 in mind >.<

@lyse@lyse.isobeef.org the problem is that i can not easily show both

it’s so satisfying clicking refresh and watching new posts appear 🥺

wait….so i’m like nearly done? it just works? and it’s fast? this feels like the end of the first all-nighter i pulled where i just got post creation done, unaware of the three weeks that would follow — like looking at the roadmap i’m definitely not done but bbycll is like actually kind of usable now o.o

@prologic@twtxt.net i just added timeline refresh to bbycll and it is so convincing i almost replied to you from there hehe, can i get a link pretty please :o

ok so i have found a genuine twt hash collision. what do i do.

internally, bbycll relies on a post lookup table with post hashes as keys, this is really fast but i knew i’d inevitably run into this issue (just not so soon) so now i have to either:
  1) pick the newer post over the other
  2) break from specification and not lowercase hashes
  3) secretly associate canonical urls or additional entropy with post hashes in the backend without a sizeable performance impact somehow

@prologic@twtxt.net wife is awesome 🙇‍♀️

@kat@yarn.girlonthemoon.xyz i think almost all of the code was written between 10pm-10am :3c

we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases….my friend’s feed with like four posts parsed correctly so i tried this account’s feed and well now im not going to bed on time

edit: remaking demo video

we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases….my friend’s feed with like four posts parsed correctly so i tried this account’s feed and well now im not going to bed on time

future sophia is going to have Fun cleaning up this mess

im a 1000x developer

remote.json | 3.4MiB

i hope testing this doesn’t get me ip banned from Everything

@bender@twtxt.net ty for attempting to test, though, it means a lot! lmk if u find any more silly things i need to clarify or fix :> be prepared for everything breaking during beta :p

@bender@twtxt.net i also recently discovered there was a bug causing new users to initialize wrong leading to their posts not being saved :p ..and made breaking changes to how the config and database files are stored so um, make sure to clear your local tree before updating!

@bender@twtxt.net as the host (eg twtxt.net) determines the canonical url of the instance in generated feed url metadata as well as every hash of every post made on the instance internally, i added this error message to make sure people don’t accidentally set up their instance on localhost :p for testing i set it to localhost:31212 and protocols to ["http"], it’s a recent addition that could definitely do with documenting in the getting started section

@lyse@lyse.isobeef.org retwts are a discovery feature! on federated platforms with no algorithm where you only ever see posts from accounts you explicitly follow, the element of “hey look at this!” helps users to find other accounts they might like organically

i agree quoting and replying forum-style is generally a much better way of doing things even though im a heathen and i revel in the dark patterns inspired by quote posts but when you have nothing to add and you just want to share a twt with your followers it’d be good to have a standardized way of linking to twt

@bender@twtxt.net @kat@yarn.girlonthemoon.xyz after implementing cws in bbycll (parsing them the way i described in op) i understand why <details> aren’t rendered. firstly they’re not actually markdown, and secondly they style weird — details are forced onto a new line as a block element but you can’t make the <summary> inline because it is inside <details>, and making <details> inline will also indent everything inside it

in the same vein, i think content warnings can be faithfully implemented by parsing CW: ..., tw // ..., etc. from the first line of a post followed by two newlines, like how they’re used on platforms that don’t have content warnings

at first i dismissed the idea of likes on twtxt as not sensible…like at all — then i considered they could just be published in a metadata field (though that field could get really unruly after a while)

retwts are plausible, as “RE: https://example.com/twtxt.txt#abcdefg”, the hash could even be the original timestamp from the feed to make it human readable/writable, though im extremely wary of clogging up timelines

i thought quote twts could be done extremely sensibly, by interpreting a mention+hash at the end of the twt differently to when placed at the beginning — but the twt subject extension requires it be at the beginning, so the clean fallback to a normal reply i originally imagined is out of the question — it could still be possible (reusing the retwt format, just like twitter!) but i’m not convinced it’s worth it at that point

is any of this in the spirit of twtxt? no, not in the slightest, lmao

search page, bookmarks page, improved thread view (that i will probably improve further), as well as a logo and a whole ui redesign. it is truly all coming together…were i to mark any items off the roadmap :p

is there someone (ideally not in the opposite timezone to me) who’d be willing to let me bother them with technical questions abt twtxtv2 and/or yarn’s inner workings? :3

beginnings of remote feed parsing..! the fact hashing just sort of works with the minuscule libraries i found for base32 and blake2b still amazes me (mentions are being eaten as html tags)

i wish the mug didn’t run out of coffee

@kat@yarn.girlonthemoon.xyz thank you!!!! just wait until you see what i have cooking :3

@lyse@lyse.isobeef.org hihi ^^ i did that at first, but i personally i don’t like it when websites don’t let me change my password when i am already authenticated — fwiw you can view and log out other sessions, if that diminishes this attack vector at all

@bender@twtxt.net ..if you read the post you would see those are the next planned steps, yes

replies and following implemented! next step is further parsing of post contents, rendering threads, and then maybe i can finally start adding remote feeds…! though i kinda wanna redo the whole ui ^^’

test reply please ignore

test edit please ignore

really proud of how bbycll is coming along!!

test post please ignore

@prologic@twtxt.net haven’t had too much time to really try it out yet ^^’ i’m um too busy staring at code i wrote while sleep deprived and wondering why i did the things i did, while sleep deprived \@.@

@prologic@twtxt.net hiiii o/