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β¦
irc.mills.io running behind Caddy Layer 4. However I don't terminate TLS at the edge in this case.
@kate@yarn.girlonthemoon.xyz Youβre welcome π
http:// only and to keep hashes from breaking i added # url = http://... and now we are stock with it due to the curret specs.
@bender@twtxt.net Hehe, thanks for fixing this (was) broken thread π§΅ Haha π€£
MaxAgeDays configuration at the pod level, that now some profiles are rather empty. This is only because well, they're a bit "inactive" so to speak π£οΈ Not sure what to do about this at the moment... Open to ideas? π‘
@sorenpeter@darch.dk I really think you should fix the # url in your feed to be https:// π
irc.mills.io running behind Caddy Layer 4. However I don't terminate TLS at the edge in this case.
@bender@twtxt.net Sure! π
{
...
# Layer 4 Reverse Proxy
layer4 {
# Gopher
0.0.0.0:70 {
route {
proxy <internal_ip>:70
}
}
# IRC (TLS)
0.0.0.0:6697 {
route {
proxy <internal_ip>:6697
}
}
}
}