Looks kind of simple to me at first glance…

There are four properties in an accessibility tree object:

name

How can we refer to this thing? For instance, a link with the text “Read more” will have “Read more” as its name (find more on how names are computed in the Accessible Name and Description Computation spec).

description

How do we describe this thing, if we want to provide more description beyond the name? The description of a table could explain what kind of information the table contains.

role

What kind of thing is it? For example, is it a button, a nav bar, or a list of items?

state

Does it have a state? Examples include checked or unchecked checkbox states and collapsed or expanded states for the <summary> element.

https://developer.mozilla.org/en-US/docs/Glossary/Accessibility_tree </summary>

Typescript is an abomination. Been writing JS just fine for 30 years without it.

“if someone relies on this and uses it the wrong way”

The wrong way for you might be the perfect solution for someone else. Once things are being used, you have no idea how people will use them, and they will likely use them in ways you didn’t anticipate.

For some, C++ is the language they find most readable

I’m skeptical about that statement! lol.

what? how does that solve a double spend?

I agreed until the “fuck blockchain” comment in the article. How else would you solve the byzantine generals problem in computer science?

When NFTs were invented, people imagined them being used for things like titles/deeds. Instant transfer and verifiability would be a huge thing. especially in places that have real estate scams due to the slow/corrupt bureaucracy.

Here’s a python script that will do some of that. I think it’s mostly focused on syncing subscribed communities.

https://github.com/wescode/lemmy_migrate