Chubby cuddlebot Lemma!

gotta say that I'm inclined to trust facebook's assertion that this accusation is groundless given

a) I'm not sure what Secret Sauce for social media that twitter has but facebook (a company which operates at 5 times the scale) doesn't
b) elon dumped 20,000 engineers onto the streets of san francisco the instant he walked in the door and I'm sure recruiters at other companies were primed to go over people's noncompetes with a fine toothed comb
c) [pointing at twitter] c'mon

I assume the move here is supposed to be convincing a judge to issue an emergency injunction to shut threads down while facebook and twitter negotiate a settlement, but I got no idea how likely that is

<div /> is not an empty div in HTML5

saw some discussion on twitter about this blog post

and i haven't decided if i agree with the opinions but i am definitely having a hard time making my peace with this:

<input />This text is outside the input.
<input>This text is outside the input.</input>
<div>This text is inside the div.</div>
<div />This text is inside the div.

Why did anyone ever think this was okay? For what conceivable reason did anyone sign off on this bullshit?

I was just complaining earlier about worse-is-better, and this is the exact sort of worse that worse-is-better defends. If I let the brain worms take me and I forget that better things are possible, would I be able to rationalize bullshit like this? If I Nuance™ myself into thinking bad things are good, would I be happy?

1. HTML was originally (kinda) an SGML language. SGML was ridiculously over-complicated, so nobody actually implemented it properly, but it was also kinda a "formating commands" language. This whole tree structure bullshit is a modern invention, comparatively. Having null tags (those without children, like <img> and <input>) wasn't very weird.
2. Somebody squinted really hard at SGML and invented XML from what they thought they saw. Self-closing tags (<div />) came from SGML's "short tags" feature where you could write a tag like <div/ to imply the end tag. (Note the lack of >!)
3. XML IS THE FUTURE ALL MUST BE XML, Jake's article basically explains what went on here.
4. When you've got a trillion documents (not exaggerating that number) in some bizarre bastard syntax, "just document what's out there" starts looking really attractive, for good reason.

... i figured instead of being just whiny about it, i should write a feature request about it. you know, bare minimum effort to manifest what i want!

i even made a mockup although it is butt-ugly.

this one is in addition/conjunction with a previous feature request that is still one of the more popular ones: https://help.antisoftware.club/support/discussions/topics/62000183100

and i would also love something like this media gallery: https://help.antisoftware.club/support/discussions/topics/62000183148

but anyway, if you'd like for cohost to support audio uploads, i'd appreciate a vote up, and feel free to join the conversation as well (or make a nicer looking mockup lmao)!

context: this whole godforsaken issue

EDIT: i've spun up a place to organize the fork i talked about in this post

i think it's pretty clear at this point that the yari repo is compromised. if people with push access are going to actively ignore community criticisms and forge ahead with their own plans, i don't see how we can trust that it will be maintained in the best interest of it's users.

it seems to me that the content itself is fine - i haven't seen any evidence to the contrary, and dear lord i would hope we can still trust that content. luckily, the content and the platform seem separate enough that it looks like it would be viable to fork the platform while still consuming the same content. i think this is the best course of action.

now comes the tricky part: actually getting the ball rolling on a fork. i guess this is a call to anyone reading - is there interest in maintaining said fork? is this something that people want? i'd like to pick this up, but there's not much use in forking if no one else actually wants to. or maybe someone's already started an effort, and i've not heard of it yet - in which case point me over, i'd love to help out.

i feel like this is the point where a lot of forks struggle - initial community organizing/building. in the chaos, it's not very hard to plant your flag down somewhere - but it is difficult to get everyone to see it, especially if there's multiple flags and no one knows which flag to go to. and when the forking process relies on accumulating a critical mass of users/contributors to move over, it's pretty difficult to get a fork established.

i hope we can do it. the web needs a place we can trust to get information on how it all works. unfortunately, mozilla's pretty definitively demonstrated that they either cannot, or are not willing to maintain that.