@kat@yarn.girlonthemoon.xyz nope, not normal. Something birdy (because why to use fishy all the time?!) is going on.

good afternoon yarnverse i have done nothing productive so far. except edit my fandom site a little bit (i added tag pages!). does that count lol

@zvava@twtxt.net this is so cool…

@zvava@twtxt.net please be sure to get enough rest!!! you’ll be able to make something even better if you’re well rested :)

@lyse@lyse.isobeef.org that’s an amazing way to teach, and one many old school (I remember my father telling me “schools need to teach both theoretical and practical skills!”) people will agree with. The fact that graduates need to learn on the job after they graduate exemplifies the importance of hands on.

Woooooaaaahh, that’s bloody amazing! I wish I’d had a teacher like that.

English version: https://youtu.be/wi_q6IythMk

German version: https://youtu.be/2Lv1MMlFDBs

@kat@yarn.girlonthemoon.xyz The duck was in a darker spot, so my camera wasn’t all that happy with the lighting. Upon further inspection, you’re right, now that you pointed it out, I can see it too! The feathers do look like an oil painting. ;-)

@bender@twtxt.net Sadly, it’s super relevant. It’s a really good sketch. I’m actually surprised you know this German series. :-)

@zvava@twtxt.net Yeah, mentions are a great way to discover other feeds.

Regarding the “look at this, but I don’t want to add anything at all”, this never happened to me. Apparently, it seems to be a thing for others.

Woot, thank you! Using a config.json like this:

{
  "host": "localhost:31212",
  "protocols": ["http"]
}

Indeed did the trick! I know it isn’t production ready, but I wanted to see with my own eyes, locally, how did it look. :-) I like where you are going! It is looking very nice, and polished. Can’t wait for an alpha, beta, and release!

@zvava@twtxt.net it is amazing how much you have accomplished in such a short time. Take time to sleep, though! :-)

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

@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

such a good cover https://www.youtube.com/watch?v=49BQQ8OgDCM

@zvava@twtxt.net huh interesting!

@lyse@lyse.isobeef.org omg this looks like a painting!

Old, but as relevant as ever today.

https://www.youtube.com/watch?v=zvgZtdmyKlI

@bender@twtxt.net Believe me, I’ve never been more tempted to switch, than now, as Google is one by one, removing (or at last trying to remove) all the reasons why I chose Android, over iOS. In fact, many friends who were fellow “Android diehards”, ended up switching recently.

Sadly what I need is a headphone jack, ability to modify apps on device (decompile, change file, recompile), many specific mods, strong XMPP support, Pixel Station,… nothing switching to iOS, would give me.

It was nice to start a walk in the woods with sunshine. The last times it was all soupy. It was quite windy, autumn is certainly here. Soon, the leaves will begin to turn. https://lyse.isobeef.org/waldspaziergang-2025-09-11/

@zvava@twtxt.net I am getting [2025/09/11 12:56:01.816] ⇒ please set config.host when trying to run “bbycll”. How to bypass that tiny hurdle?

@zvava@twtxt.net I gave this, in my mind, a like/star/love.

Yes, I know, this is a “bad taste” joke. I appreciate you, @thecanine@twtxt.net!

@thecanine@twtxt.net or, you know, you could get an iPhone. 😂😂😂

@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

@movq@www.uninformativ.de Haha, that girl is good! :-D

@kat@yarn.girlonthemoon.xyz I reckon the original <details> need to have the open attribute set in order to expand it, so I cannot just define some custom CSS rules to do that in my browser.

But in regards to twtxt, my client won’t hide anything in that realm anyway. :-) It’s just more noise.

@movq@www.uninformativ.de I would call it “dark ambient”. It’s a broad genre, but one I rather like.

@lyse@lyse.isobeef.org i think if there’s an option to expand them by default (which can be done with <details> even) then i think it should be good!

@bender@twtxt.net ohhh oops! i will work harder then 🫡🫡

@kat@yarn.girlonthemoon.xyz it is not showing for me, on a validator. Missing something?

(Yes, she’s the one who did that Wisky bit: https://www.youtube.com/watch?v=1HDBSm2s18s

)

We’ve got a new feature!

https://www.youtube.com/watch?v=8-lgJX3npiQ

@lyse@lyse.isobeef.org Ouch 😲

@dce@hashnix.club Nope. 😃 What’s that genre called? Sounds like old horror movies from the 70’ies (or it could be a soundtrack to Salad Fingers, if anyone remembers that).

@kat@yarn.girlonthemoon.xyz I hope so 😅

@kat@yarn.girlonthemoon.xyz Ta. The only good use for <details> is to collapse long logs in bug analysis reports. Other than that, I find it rather annoying to expand sections manually.

As for spoilers, personally, I don’t care at all. Not the slightest bit. If there is something that I don’t wanna read, I just stop reading. ¯_(ツ)_/¯

But I’ve got the feeling that I’ve got an unpopular opinion on that matter. ;-)

@bender@twtxt.net I see, thanks. Well, I never found these warnings useful. To hide answers to conundrums or the like, ROT13ing or base64-encoding them is plenty sufficient.

Hahaha, I never heard of Poopgate before. :-D Poor passengers.

@kat@yarn.girlonthemoon.xyz all @prologic@twtxt.net has to do is to allow <details> and the subset under it. Granted, it could be implemented on the formatting toolbar too…

added opengraph to my blog :D https://bubblegum.girlonthemoon.xyz/articles/underground-soundcloud-remixes

Something like this, for example.

@lyse@lyse.isobeef.org a content warning is kind of like a forum spoiler cut, or like the <details> tag in HTML; it lets you write a sentence or so that someone can then click to expand to see the actual post. it’s called a CW because most people use it to warn for potentially triggering/harmful subjects, but you can really use it for anything, like spoilers in a TV show or even for joke punchlines

@lyse@lyse.isobeef.org a content warning is a way to tell the audience the content they are about to see is (or might be) shocking, or unsuitable, or unlikable. The audience can then chose to see it, or not. You know, akin of movies stating:

“Warning: The following film contains scenes that some viewers may find disturbing. Viewer discretion is advised.”

@zvava@twtxt.net i think CWs would be very cool here!

@lyse@lyse.isobeef.org yeah it’s not all that tall hahah! but yeah i am totally blinded to any sense of tall/short buildings lmao

@zvava@twtxt.net I never used any of the social media platforms, that’s why I’m probably ignorant.

I don’t understand the concept of a retwt. Just quote the (relevant) parts from whereever and comment on that. Or post a link instead of a quote. Sounds simple enough. :-) That’s also has the benefit that it works with every source, no matter what. Since it’s called retwt, I’d imagine this to only work (well) with whatever messages the system itself offers. But I could be wrong. What would be the benefit of having a dedicated message type or structure for “hey, look at that” messages in your opinion?

Hmm, what’s a content warning?

@movq@www.uninformativ.de Fun fact, inhabitants of this town are nicknamed „Brandstifter“ (arsonists). In the 19th century, a firebug caused a number of big fires here.

@kat@yarn.girlonthemoon.xyz Ten stories or more are already very tall in my books. Not sure at which height I would start calling high rise buildings sky scrapers, but Wikipedia suggests around 150 meters, depending on region.

Oh, I just found https://upload.wikimedia.org/wikipedia/commons/f/f1/Pier_17_2018-03_jeh.jpg and this really does not look all that high. I thought that this would be at least 50 or 100 meters up. I was completely wrong. :-D