@prologic@twtxt.net My account is @tanrax . Thanks!
@prologic@twtxt.net I can’t register with GitHub, nor make Pull Requests. Would it be possible to enable this? Maybe this repository could be on GitHub to promote it and increase collaboration.
@xuu@txt.sour.is Haha, that’s cool! Be careful with reporting or they might sue you to death.
@kat@yarn.girlonthemoon.xyz (they migrated their image backend from a deprecated third party plugin to a first party feature. which i did on the same codebase last summer with no knowledge of rails lol)
@kat@yarn.girlonthemoon.xyz sticker status!!!!! 
@kat@yarn.girlonthemoon.xyz I DID END UP PUTTING IT TOGETHER BTW AND I VLOGGED IT (https://memoria.sayitditto.net/view?m=fGvHAMJvq) AND I LOVE IT SOOO MUCH
@kingdomcome@yarn.girlonthemoon.xyz all me hahah! thank you <3
@kingdomcome@yarn.girlonthemoon.xyz hey irene!!!!!!!!!!!!! i’m vibing rn
I need an alternative news source… Something I can shove into feeds.twtxt.net that helps me keep up-to-date with Tech and other important news 🗞️ Hmmm 🤔 Suggestions? I can’t stand Slashdot anymore since they’ve decided to come down hard on ad-blockers 🤦♂️
@lime360@lime360.nekoweb.org Down at the moment due to hardware failure of one of my nodes. I have the spare parts to bring it back online, just need to find the time 😅 Sorry for the inconvenience, I just can’t afford to run the search engine right now on the remaining two nodes 😢😢
@arne@uplegger.eu Welcome! 🤗
Wussup twtxt I’m rolling cigarettes (I don’t smoke) (I think it’s funny) (it’s like crocheting a scarf when you don’t wear scarves)
@aelaraji@aelaraji.com Reading “The Book Thief” by Markus Zusak
@arne@uplegger.eu Uuhhhh, more twtxt clients, very nice! :-)
@prologic@twtxt.net you change something up on how markdown gets rendered?
Nun habe ich mir einen eigenen webbasierten TwtxtReader erstellt. PHP-basiert mit Phpfastcache, Fluid Template Engine und asynchronen cUrl-Requests für die abonierten Feeds. Inspiriert durch Timeline von @sorenpeter@darch.dk
@prologic@twtxt.net uhhh what happened to search.twtxt.net
@prologic@twtxt.net uhhh what happened to search.twtxt.net
@prologic@twtxt.net uhhh what happened to search.twtxt.net
@aelaraji@aelaraji.com @movq@www.uninformativ.de Damn, I forgot, too! And the clouds prevent me from catching up on that. But it’s really cool to hear that you were able to see something nice up there. :-)
@johanbove@johanbove.info Way to go! ✊ what will you be reading? Got anything planned?
@kingdomcome@yarn.girlonthemoon.xyz real shit
@prologic@twtxt.net Is it possible to make Pull Request on twtxt.dev ?
@prologic@twtxt.net It’s opensource. You can run the software in your localhost or server. Cloud service is a free option.
Of course @prologic@twtxt.net! Check https://streamlit.io/
@doesnmppsflt@doesnm.p.psf.lt It looks like it… Although they shouldn’t be empty since Timeline took care of sending those. I believe I have an idea as to why that happened, but will have to test before filing an issue.
v1.23.4 will there ever be a v1.23.45678? 🫠🤡
@lyse@lyse.isobeef.org HAHA! A forever stable major release eh? That’s brilliant 😃 …
@doesnm.p.psf.lt@doesnm.p.psf.lt I don’t know if you have already noticed, but your Twtxt/Webmention script outputs Timestamps from the future 🤔 I wonder if Timeline’s does the same …
@doesnm.p.psf.lt@doesnm.p.psf.lt Testing Testing… 123… Ouiiiiiii… 😆
@doesnm.p.psf.lt@doesnm.p.psf.lt Are you also using https://cabal.chat or just someone else with the same random username?
@sorenpeter@darch.dk Yes it works, thx: https://doesnm.cc/mentions.txt . I’m deleted html tags because my client do not support html rendering
@doesnm.p.psf.lt@doesnm.p.psf.lt Cool lets see if this works?!
@<url> form of mentions. Strictly require that all mentions include a nickname/name; i.e: @<name url>.
@prologic@twtxt.net I say we should find a way to support mentions with only url, no nick, as per the original spec.
- For
@<nick url>we already got support
- For
@<nick>the posting client should expand it to@<nick url>, if not then the reading client should just render it as@nickwith no link.
- For
@<url>the sending client should try to expand it to@<nick url>, if not then the reading client should try to find or construct a nick base on:
- Look in twtxt.txt for a
nick =
- Use (sub)domain from URL
- Use folder or file name from URL
- Look in twtxt.txt for a
v1.23.4 will there ever be a v1.23.45678? 🫠🤡
@aelaraji@aelaraji.com Reminds me a bit of TeX which approaches pi by adding a digit with each bug fix in its version number. https://en.wikipedia.org/wiki/TeX#TeX82
@movq@www.uninformativ.de @prologic@twtxt.net Yeah, you won’t be disappointed. :-)
@prologic@twtxt.net This is fricking amazing, congratulations! :-) \o/
@prologic@twtxt.net fuck yeah!!!
@prologic@twtxt.net <333 ty
@aelaraji@aelaraji.com i might give it a try soon!
@lyse@lyse.isobeef.org ahhh thank you so so much!!!! i’ve heard of shellcheck but haven’t checked it out properly - will try it for my scripts :D i really appreciate it
@movq@www.uninformativ.de Hmm yeah, you’re right. I should have checked for our location prior to getting too excited.
@aelaraji@aelaraji.com Yeah, a sore neck is always a win. :-P Here’s nothing really to see, all cloudy. And also a bit cold at -2°C. I don’t feel like standing still all that long outside at the moment. :-D
@lyse@lyse.isobeef.org /Me throws his keyboard off to the side, grabs his camera just in case and runs upstairs screaming “Yeah! Science B_ !”
Your code apparently works just fine. Until it @doesnm@doesnm.p.psf.lt’t. ;-) The shell languages are weird and having some strange properties that one is just not used to when coming from other languages.
@andros@twtxt.andros.dev I love how this is coming together! :-)
@kat@yarn.girlonthemoon.xyz To improve you shell programming skills, I highly recommend to check out shellcheck: https://github.com/koalaman/shellcheck It points out common errors and gives some suggestions on how to improve the code. Some details in shell scripting are very tricky to get right at first. Even after decades of shell programming, I run into “corner cases” every now and then.
E.g. in getlyr’s line 7 it warns:
echo -e $(gum style --italic --foreground "#f4b8e4" "'$artist', '$song'")
^-- SC2046: Quote this to prevent word splitting.
For more information:
https://www.shellcheck.net/wiki/SC2046 -- Quote this to prevent word splitt...
Most likely not all that problematic in this application, but it’s good to know about this underlying concept. Word splitting is basically splitting tokens on whitespace, this can lead to interesting consequences as illustrated by this little code:
$ echo $(echo "Hello World")
Hello World
$ echo "$(echo "Hello World")"
Hello World
In the first case the shells sees two whitespace-separated tokens or arguments for the echo command. This basically becomes echo Hello World. So, echo joins them by a single space. In the second one it sees one argument for the echo command, so echo simply echos this single argument that contains three spaces.
@prologic@twtxt.net Oh yeah, that’s terrible, yuck! Let’s not do it then. :-)
@prologic@twtxt.net As written in IRC, several things turned me off. I don’t have the energy at the moment to wrestle through. :-(
