Going to try and few up a few more UX bugs today with yarnd
.
Problems are Solved by Method\" π¦πΊπ¨βπ»π¨βπ¦―πΉβ πβ― π¨βπ©βπ§βπ§π₯ -- James Mills (operator of twtxt.net / creator of Yarn.social π§Ά)
After 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?
Today I added support for Let's Encrypt to eris via DNS-01 challenge. Updated the gcore libdns package I wrote for Caddy, Maddy and now Eris. Add support for yarn's cache to support # type = bot
and optionally # retention = N
so that feeds like @tiktok work like they did before, and... Updated some internal metrics in yarnd
to be IMO "better", with queue depth, queue time and last processing time for feeds.
Interesting factoid... By inspecting my "followers" list every now and again, I can tell who uses a client like jenny
, tt
or any other client where fetches are driven by user interactions of invoking the app. What do we call this type of client? Hmmm π€ Then I can tell who uses yarnd
because they are "seen" more frequently π€£
First draft of yarnd 0.16 release notes. π -- Probably needs some tweaking and fixing, but it's sounding alright so far π #yarnd
Iβm thinking of building a hardened peering protocol for Yarn.socialβs yarnd
: pods establish cryptographic identities, exchange signed /info
and /twt
payloads with signature verification, ensuring authenticity, integrity, and spoof-proof identity validation across the distributed network.
π‘ I had this crazy idea (or is it?) last night while thinking about Twtxt and Yarn.social π
There are two things I think that could be really useful additions to the yarnd
UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
- Voting -- a way to cast, collect a vote on a decision, topic or opinion.
- RSVP -- a way to "rsvp" to a virtual (pr physical) event.
Both would use "plain text" on top of the way we already use Twtxt today and clients would render an appropriate UI/UX.
@bender You will be pleased to know that yarnd
now only consumes ~60-80MB of memory depending on load π€£ And bugger all CPU π