Responded to a bunch of Twtxt open issues across multiple repositories today 👌
@bender@twtxt.net You said:
as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
I think this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:
- Specifications (as they are now)
- Server recommendations (e.g: Timeline, yarnd, etc)
- Client recommendations (e.g: jenny, tt, tt2, twet, etc)
@bender@twtxt.net wut?! Who carries three grand worth of cash in their handbag?! 👜 Haha 😆
@kat@yarn.girlonthemoon.xyz Bahahaha so do it all the time 🤣
dm-only.txt feeds. 😂
@andros@twtxt.andros.dev Some good points here that I share and empathize with 🙌
@bender@twtxt.net I see hmmm 🧐
@andros@twtxt.andros.dev Zulu said:
what is twtxt for you?
For me Twtxt is just the underlying format that Yarn.social builds upon 😅
@andros@twtxt.andros.dev Ahh cool! I’ll try following it again 🤣 Mind @-mentioning/linking@twtxt.net the feed again? 🙏
Also what’s a, who’s the Pope? 😅
@quark@ferengi.one I know! I saw three Hacker News posts on it in a row 🤣
@andros@twtxt.andros.dev Haha 🤣 We’ve explored this idea in the past and we decided that it’s actually a good idea to have an “append-only” feed for various reasons. We’ve also explored the idea of using Range requests, but opted instead to just archive/rotate our feeds periodically 😅 There really isn’t much point in having a feed in reverse chronological order, except (maybe?) so a human read view the new twts at the top of the file?! 🤣
@bender@twtxt.net This is just a website that cycles through random Youtube channels? 🤔
I guess mentions with .(s) / dot(s) like @eapl.me@eapl.me are valid? 🤔 Or nicks even? 🤔
Fark Youtube is so utterly boring 🥱
@bender@twtxt.net Ahh yes you caught me 🤣
@bender@twtxt.net Not copy/paste 🤣 Hand on heart! ❤️ However it was a pretty nice article 😅
Getting Forked by Microsoft • Philip Laine 👈 Yet another pretty sad story of a megacorp (Microsoft) being total assholes 😢
Regex Isn’t Hard - Tim Kellogg 👈 this is a pretty good conscience article on regexes, and I agree, regex isn’t that hard™ – However I think I can make the TL;DR even shorter 😅
Regex core subset (portable across languages):
Character sets
• a matches “a”
• [a-z] any lowercase
• [a-zA-Z0-9] alphanumeric
• [^ab] any char but a or b
Repetition (applies to the preceding atom)
• ? zero or one
• * zero or more
• + one or more
Groups
• (ab)+ matches “ab”, “abab”, …
• Capture for extract/substitute via $1 or \1
Operators
• foo|bar = foo or bar
• ^ start anchor
• $ end anchor
Ignore non‑portable shortcuts: \w, ., {n}, *?, lookarounds.
@bender@twtxt.net No worries 😉
There we go. Restored all the old settings 👌
@bender@twtxt.net Lemme look at the old backup…
I am up to increase the length of a twtxt, though.
Recall what we had this set to for this pod? 🧐
@bender@twtxt.net Really? Wow! 😂
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
@bender@twtxt.net Hah 🤣
Just had a freak storm ⛈️ with lots of horizontal rain ☔️ that took out and tripped our internal RCD (again) 😱 Took out our Fibre too (servers were fine, good ‘ol UPS). Need to get a UPS for the Fibre box 📦 Haha 🤣
@movq@www.uninformativ.de So cool! 😎 Where’s the time lapse video you used to have of this tree? 🌳 Hmm 🧐
@movq@www.uninformativ.de Yeah I know 🤣 I found another bug in lextwt 🤦♂️ This whole DM / bang-mention thingy has thrown a spanner in the works 🔧 – Even if I wanted to implement it, I’m not even ready to try at the moment 😢
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
@kate@yarn.girlonthemoon.xyz (as I was trying to say…), Glad you think so👌 My goal with Yarn.social has always been to provide the best (best that I can anyway) truly decentralised (slow) social experience that uses the Twtxt format under the hood 😅
@xuu@txt.sour.is As I also mentioend on IRC I think this is a. bug?
Holy hell?! When I post this:
@<kate https://yarn.girlonthemoon.xyz/user/kat/twtxt.txt> Glad you think so! 👌 My goal with Yarn.social has always been to provide the best (_best that I can anyway!_) truly decentralised (_slow_) social experience that uses the Twtxt format under the hood 😅
Something is swallowing it.
@kate@yarn.girlonthemoon.xyz Glad you think so! 👌 My goal with Yarn.social has always been to provide the best (best that I can anyway!) truly decentralised (slow) social experience that uses the Twtxt format under the hood 😅
What if I do this…
Nope hmmm
What about here?
Okay they’re not here…
Why are my replies getting swallowed?! 🤔
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
Glad you think so! 👌 My goal with Yarn.social has always been to provide the best (best that I can anyway!) truly decentralised (slow) social experience that uses the Twtxt format under the hood 😅
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
@kate@yarn.girlonthemoon.xyz Glad you think so! 👌 My goal with Yarn.social has always been to provide the best (best that I can anyway!) truly decentralised (slow) social experience that uses the Twtxt format under the hood 😅
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
Hmmm?
Hmmm?
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
@kate@yarn.girlonthemoon.xyz Glad you think so! 👌 My goal with Yarn.social has always been to provide the best (best that I can anyway!) truly decentralised (slow) social experience that uses the Twtxt format under the hood 😅
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
This expands the usefulness of Twtxt / Yarn.social to:
- Sharing small posts
- Sharing links
- Sharing media
- Having long conversations
- Voting on topics, opinions or decisions
- RSVPing to virtual or physical events
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
The nice thing here is that any Ui/UX rendering for a “good user experience” is similar to what yarnd does for Youtube/Spotify/whatever embedding. Plus anyone can participate, even if they don’t really have a client that understand it, it’s just text with some “syntax” afterall.
#event:abc123 RSVP: yes +1
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
#event:abc123 Go Meetup – Sat Apr 27, 3pm @ Darling Harbour
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
#poll:xyz123 Favorite Go framework?
- Gin
- Echo
- Chi
yarnd UI/UX experience (for those that use it) and as "client" features (not spec changes). The two ideas are quite simple:
I’d have to write i up in full, but essentially looks a bit like this (contribived examples follow)…
💡 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@twtxt.net I think I could, but I haven’t bothered to do so yet… I’ll try that out later…