i don’t remember whether i’ve posted these to fedi before but even if i have, You’re Welcome For The Reminder

today i am wearing this extremely powerful article of clothing

i like how this is saying Down With Property Rights without sayyyyying down with property rights https://www.newwaysministry.org/2022/09/18/shady-solidarity-a-god-who-lifts-up-the-poor/

neighbor came up to porch and i went scuttling into the bedroom.

(#ybjlgha) @darch@neotxt.dk Titles and subjects are two different things in my opinion. A title is a caption, brief summary or some description of a longer content that follows. A subject is a – in this case human readable – reference in a reply to some topic in order to group several twts to a conversation. Forks aside, the first twt starting a discussion typically doesn’t have a subject. But some article would have a title in most cases. You are right in that the subject mechanism could be abused for a crude title implementation. I wouldn’t do it, though.

it’s one of those things where you can roll some of it around and say that it’s nuanced and complicated and refer to its original context but also then, downstream of tolkien, you look at What The Culture Did With The Idea Of Evil Fantasy Races and….. yike

i feel like there’s probably some obsessive fan forum post rebuttal out there that would be interesting to read (“9 reasons why you CANNOT say that the siege of minas tirith represents the siege of constantinople”) but in sum… yeah https://onlinelibrary.wiley.com/doi/full/10.1111/sjp.12477

(#o34adwa) @prologic@twtxt.net I reckon there is a some kind of frame or hook tool for these loom bands.

i need a millennials-to-snake-people style extension to do something ludicrous with “virtue-signaling”

Not sure how my daughter made these but they’re really good 👌

(#ybjlgha) Agree with @lyse@lyse.isobeef.org here too 👌 It adds little value to the spec when we already have mechanisms to share titles by convention.

(#pk6tyua) @lyse@lyse.isobeef.org Hmmm

(#j6ldm5q) @darch@neotxt.dk Ahh I see

(#jdl5x5a) @darch@neotxt.dk Cool that’s much better 👌

(#oa6727a) @darch@neotxt.dk As I said in the issue, I’m guessing Simple CSS doesn’t have any styles for modal dialog(s)? 🤔

Also as an aside, I realied I can actually turn off Link Verification and Set my preference to Original Media, so at least there’s a work-around on per-user Settings until we fix this 👌

(#adrpwna) @darch@neotxt.dk You need to rebase it like I showed you.

(#ybjlgha) @mckinley@twtxt.net Even though I miss a title for general purposes, I’m not sold of cramming it into twtxt. It’s just not made for it. To only announce new articles, that format would work, though. It’s basically what some people already do, except a space rather than a tab is used between the title and link.

(#uft3kdq) @movq@www.uninformativ.de Ta, in my ~/.Xmodmap I just set my multi key to Caps Lock, which I had deactivated anyways. Now I can insert a non-breaking space with Caps Lock+Space+Space. Nice.

(#pk6tyua) @prologic@twtxt.net I fear that calls for even more trouble. But you can try.

(#uft3kdq) @lyse@lyse.isobeef.org Oh, of course,   … I’ve used that quite a lot, too. 😅 As for entering that stuff directly: https://en.wikipedia.org/wiki/Compose_key is great

(#sax4t6a) @eaplmx@twtxt.net Ahh, right, that’s it! 😲 🧓

(#oa6727a) @darch@neotxt.dk Try to click on the link above… It doesn’t work in the new theme 😅

Hello Google

(#wdu6cca) @eaplmx@twtxt.net I wasn’t making a criticism, I was just pointing out the difference in the format. I agree, there’s some great stuff on there.

(#jdl5x5a) @darch@neotxt.dk If that’s intention, that’s fine 👌 However it is visually different to tell apart the ‘In Reply To …” with for example an actual quote:

This is a quote…

Can we do something here?

(#xvx7mta)

(#xvx7mta) Ahh I see! I’ll jump on in 29mins 👌

(#zogehjq) @mckinley@twtxt.net In that case maybe we should adopt the GoldMark library which I think implements CommonMark?

(#xvx7mta) @prologic@twtxt.net $ nc kyoko-project.wer.ee 1234 in your terminal, it’s a remake of Among Us as a multiplayer text adventure.

(#zogehjq) @prologic@twtxt.net Referenced links also work on the Web client, but I tried both CommonMark syntax options for the horizontal rule and only one worked on Goryon.

This is exactly what I’m talking about. We should have a concrete specification so Markdown can be rendered consistently between client implementations.

(#xvx7mta) How do I play?

(#zogehjq) Probably yhe sanitizer doesn’t allow it 🤔 (for web)

(#zogehjq) @mckinley@twtxt.net It actually did work in the mobile app Goryon

(#rbkm6dq) @mckinley@twtxt.net So… What are you proposing exactly? 🤔 If not some kind of metadata field declaration?

(#xvx7mta) I think I broke it, though, because I started a game alone and then accidentally pressed ctrl+c. When I try to log back in, it says there’s a game in progress and I can’t start a new one. Sorry about that…

(#xvx7mta) @akoizumi@social.kyoko-project.wer.ee That looks fun. I’d play if we could get some more people in the game.

(#zogehjq) Nope, no horizontal rule. What about referenced links?

My website

(#rbkm6dq) @prologic@twtxt.net I don’t know if a metadata field is strictly necessary. I think there ought to be a defined set of syntax that all clients with Markdown support can be expected to handle in the same way. CommonMark maybe? It looks like Yarn supports most of CommonMark already, though I’ve never seen a horizontal rule. Let’s try it:

Some text here

(#y3bp7ga) @mckinley@twtxt.net Looks not too bad 👌

(#bqg2sbq) @akoizumi@kyoko.nerdpol.ovh Yeah there a few things that are broken but most things are okay 👌

(#y3bp7ga) Of course I pick the day before simple.css gets merged into main to get a new Ladybird screenshot. Here’s one post-merge.

(#j6ldm5q) In fact even in this Yarn, the whole Image Gallery feature that @ullarah@txt.quisquiliae.com originally did is not completely broken 😅 I’ll let you ponder on that for a while, but we should probably do something about this before cutting a new release for sure 👌

(#rbkm6dq) @mckinley@twtxt.net We’ve talked about this once before and in fact even tried to formalize it but in the end we couldn’t agree on a way to do it or even if it was a good idea… Worth revisiting this again? Like @lyse@lyse.isobeef.org I’ve also looked at JSON Feed and wasn’t entirely convinced either.

(#pk6tyua) @lyse@lyse.isobeef.org

We definitely need some feed normalization database, too many broken mentions out there

What if we use some kind of heuristics based on a client’s cache? Or some kind of similarity search? Hmm 🤔

@darch@neotxt.dk Also the pop-up when you click on external links in a Twt is broken. I tried to for example in the Twt (screenshot attached) and it didn’t work :/

(#xvx7mta) @akoizumi@social.kyoko-project.wer.ee Sorry man, I looked at this briefly last night when I went to bed (on my phone) but I “didn’t get it” 😅 Sorry!

(#ix64jaa) @lyse@lyse.isobeef.org Yeah I agree, and that does happen.

It’s also been merged and my pod upgraded 👌

@darch@neotxt.dk There are a few minor regressions. But maybe they were intentional? The “In-Reply-To” used to limit the text to some width and use an ellipsis via CSS to cut it off a bit.

👋 Hey all users of this pod (twtxt.net – I just merged @darch@neotxt.dk’s PR that replaces PicoCSS with SimpleCSS. You may want to refresh or clear your browser cache to get the new look 😅