@nora @ruby that actually makes sense. I’d still check if the instance software doesn’t do additional Weird Things with the text tho

@nora @ruby …wait, out of band tags are in the spec? I somehow did not know that, and now I’m wondering if we could do something with that (though it probably would require some integration effort)

@vision @froggebip same with my akkoma

@viv @bobskunk yeah, encountered that a bunch when trying to share post links with some friends

@bobskunk @viv yeaaa, I know, some types of instances handle that better than others (for example, firefish worked fine iirc)

@nora I really gotta grab that one

@viv @bobskunk it sure does work for me

@bobskunk @viv you can always try pasting the post link into the search bar fyi

@morine @girlcodedcreature @gcugreyarea ah, that’s probs a gts specific thing

@viv aaaand I don’t see any obvious place where it could be in the db. oh well, I guess I’ll live with it until I get around to looking at the source code to check where it puts those

@viv weird indeed. it’s just giving me a 500 in admin-fe and pretending the report was resolved until a refresh in akkoma-fe

@tenna update: I just made a test admin account and did it on my instance, it’ll just deactivate the account without any warnings, but you can reactivate it from another admin account (you can use the mix task to create one)

@viv seems like the whole report experiment from last time somehow left a bugged report in my instance that just doesn’t want to get deleted? time to dig around in the db

@froggebip …oh, you meant instance approvals lmao

@froggebip nah, mostly just me chatting with people for a while

@froggebip oh, I can relate lmao

@gcugreyarea @girlcodedcreature you generally don’t have to worry too much about public vs unlisted around here, unlisted just hides it from federated, local and tag timelines, and we don’t have the first one, only some instances have the second one and you don’t have any tags in the post anyways

#art #furryart

if someone hasn't already, i think i'm going to coin the term technoableism for stories like this one:

https://futurism.com/neoscope/paralyzed-man-exoskeleton-too-old

"After 371,091 steps my exoskeleton is being retired after 10 years of unbelievable physical therapy," Michael Straight posted on Facebook earlier this month. "The reasons why it has stopped is a pathetic excuse for a bad company to try and make more money."

According to Straight, the issue was caused by a piece of wiring that had come loose from the battery that powered a wristwatch used to control the exoskeleton. This would cost peanuts for Lifeward to fix up, but it refused to service anything more than five years old, Straight said.

stories like this remind me of the big IEEE Spectrum article from about two years ago about people with bionic eyes having the company that created them explode, leaving them to either get the technology removed, hope for the best, or DIY any issues for as long as possible. it's all kind of a super fucked up industry

@viv @EstrogenAndSpite @estrogenandspite could still delete and redraft if the issue is big enough