Anyway... figured i should have made an account for cardboard.NET related things so @CardboardNet@kitsunes.club exists now. I'll still post dev stuff here but for announcements, milestones and specific to cardboard.net dev stuff i'll probably move it all over there.
Remote
Amber
@puppygirlhornypost@transfem.social
Please view @puppygirlhornypost2@transfem.social This account is now a read-only archive. I am unable to use it any meaningful capacity
0
Followers
0
Following
12
Posts
Posts
As a result of this experiment and several others (figuring out that the *key api does not have protections in place) Cardboard.NET is going to prevent footgunning here.
https://activitypub.software/TransFem-org/Sharkey/-/issues/625#note_5155
Mainly, I am going to make DeleteAsync() and other actions you can take on a user account virtual so RestInstanceActor can override them. There will also be some checks for GetUserAsync() and various other parts of the library in which you can fetch the instance actor as type RestUser instead of RestInstanceActor to prevent instance actors from being treated as normal users. The library does not allow you to instantiate RestUsers from a pure model or anything like that (all of the stuff for that is internal only) so it shouldn't be that hard to encapsulate.
RE: https://transfem.social/notes/9xrrrrj7jekd0107
Replying to
@puppygirlhornypost@transfem.social
It's a lot less... explosiony. I mean, it depends? Yeah everything breaks but only when it comes to authorized fetch and federation. Other than that your instance is ok... you can restore the actor to get some of that back but once it deactivates the instance actor *oma instances will not be able to get it again. @Seirdy@pleroma.envs.net look at me I committed crimes against AP again
the results are in... It turns out that you're really not supposed to delete your instance actor. No really, what is wrong with you? Don't suspend it either. 
Replying to
@puppygirlhornypost@transfem.social
also written by me lmao. Yes, thank you guinea pig. delete your instance actor.
Replying to
@puppygirlhornypost@transfem.social
I love how right above it is the following To add to this conversation, the consequences of deleting the local instance actor cannot be overstated. I am unsure if deleting an account causes the instance to issue a deactivation on the actor's keys (it does this for suspensions). I do know that considering how suspension of a local account ends up "deactivating" the actor and federating that deactivation if one was able to suspend the local instance actor (no, I am not doing that, even for testing purposes as it will burn the domain - I know we can suspend remote actors).I have not seen how misskey does instance <-> instance federation; however, I have watched akkoma <-> mastodon-glitchsoc, the first thing it does to establish federation is a GET @instance.actor@transfem.social, exchanging keys. If this process is interrupted neither instance is able to federate. In my specific case, I was debugging a wireguard issue (MTU size ended up snowballing into an HTTP timeout on this specific fetch). Authorized fetch is not that big of a deal (instances have it disabled all the time) but not being able to establish an instance's "identity" because it's tied to the key of the instance actor?That obliterates federation and there's no recovery from that. Other Misskey (and forks) instances might be able to reactivate the instance.actor user, but akkoma and plemora will not. I have seen this time and time again when issuing suspensions for local instance users, the second they get unsuspended all of the sudden accounts from *oma instances such as labyrinth.zone are unable to interact or engage at all until a manual override by the remote instance administrator.
Replying to
@puppygirlhornypost@transfem.social
blessed instructions
me in the gitlab issues going
Doing this will allow you to log in as the instance actor, what you can do from there is up to you but I have a couple of recommendations.
3) Delete the actor again (after backing up preferably)
Replying to
@foone@digipres.club
@foone@digipres.club good, I’ll make popsicles out of it. Thanks again foone for pissing in my sock drawer. The amount of money saved really shows I no longer buy those expensive popsicles from the store for an afternoon snack.
eventually computer touchers reach a point in which all computers around them will display weird characteristics that are specific to them and they just end up with super specific issues only they encounter