Lady of the Land @Lady@cat.family

it's nice when a group of humans who are passionate about a thing get together and make a proper art about it

it's unfortunately rare to see on any kind of scale but it's nice

i feel the same way about the animated hobbit feature by rankin-bass but this is more contentious

say what you will about fantasy and fandom, but a world without the lord of the rings movies would be a much shittier world

https://blog.ladys.computer/2023-12-17/programming_resolutions_24/

#prrgrrmmng

@wallhackio if you want better type detection (not dependent on instanceof), most builtins have methods which will throw if not called on an instance and you can use those as a brand check

i think assuming that people haven't done weird things with inheritance is a fine limitation tho

@jdp23 you have no guarantees about whether the content gets there. it can’t be FETCHED or VERIFIED by the receiving server if your server has them blocked; this comment by claire implies that this also takes effect for individual blocks <https://github.com/mastodon/mastodon/issues/18345#issuecomment-1120176872>.

mastodon does not appear to include the contents of boosted posts in boosts, so this is enough to prevent them from federating from a Mastodon server. however, other ActivityPub implementations could conceivably include the contents of the post being boosted. in this case, the content would be leaked, and just not verifiable.

on mastodon, every post is verified to protect against other instances lying about things that you said. this means: if you have AUTHORIZED_FETCH and a server is blocked, and it gets word of a status by you, then it will check to see if you actually posted that status. it won’t be able to confirm that, so it does the reasonable thing and assumes it may have been deleted. consequently, it does not record the status or show it to its users.

however, there is always the possibility that (a) a different ActivityPub implementation includes the full contents of your post when it boosts it, and (b) Threads accepts this content as true, even though it can’t verify it. there is nothing technologically which can be done about this sort of information leak, aside from not federating with instances which might fall into the category of (a).

i don't know but i haven't hit the limit yet

@aschmitz wait i cam get your posts from here? since when?!

wario doesn't have a butt chin. it's just a butt. wario is mario upside down

yep it’s a cache issue; it’s working for me now

i wonder if my browser is cacheing something weird (i really need to set cache-control headers)

this seems to work, but interestingly not in the in-app browser on iOS (works fine if you open the link in safari normally)

This is a test of crossposting functionality between <https://status.ladys.computer> and Mastodon (via the Shortcut that I use to generate statuses).

If everything works as intended, this post should appear in my Mastodon feed with a permalink to the original at the bottom.

(If it doesn’t work as intended, I may delete and remake this post until it does.)

Permalink: <https://status.ladys.computer/urn:uuid:018c74a5-da0c-71eb-b017-2b896350e3a7>

source code is here <https://git.ladys.computer/Status>, naturally

you may have seen me do this before but what distinguishes this from previous attempts is there are now atom feeds

okay this is live and works
<https://status.ladys.computer>