Follow

mastodon stuff 

so since you can get spinny text patched by just messing around with it enough that gargon goes "oh goddamnit"
how do i take that and apply it to
1. federated reports (#2176)
2. private accounts acting VERY WEIRD AND POSSIBLY UNSAFELY if they have no statuses visible to the instance you're on (#644?, i've seen more bugs than just #644)
3. deleted posts not being deleted if they were a retoot (#889)

mastodon stuff 

I just submitted a new, longer issue for 2. at github.com/tootsuite/mastodon/

Please note the fact that one of the things can happen is that someone who you didn't see a follow request from and didn't accept may be able to see your posts

(cc @Gargron pls fix)

mastodon stuff 

@shel theoretically yeah but also morally and logically no

mastodon stuff 

@boots feels like the messing around with it enough may be a way of trouble shooting though, no?

mastodon stuff 

@maloki i mean the issue with the css class thing was just "there's no whitelist"
it's just that nothing was being done for a while about it

mastodon stuff 

@boots Ah, I didn't know about it until just lately.
As well I'm simply not "caught up" with github, as I end up having to deal with other stuff.
feel free to poke me next time?

mastodon stuff 

@boots 1. is something i wanted to do until i realized it would require you to expose the reporter. because the mechanism for such things is salmon, it must always go from one account to another. so you would send a flag-as-inappropriate from the reporter to the author. the software could hide this from the author, but it still feels dodgy, thus i have no implemented this.

mastodon stuff 

@boots i have replied in the github issue for 2, but the reason 2 and 3 are hard is because federation is bloody impossible to debug with such things. like, i don't have any obvious clues as to why it would happen.

mastodon stuff 

@boots the reason the spinny thing was fixed quickly was 1) it was absolutely clear where the problem was 2) it was easy to fix 3) highly visible and urgent because it affected people with motion sickness

mastodon stuff 

@boots looking at #889: my response is wrong. RemoveStatusService removes a given status and all reblogs of it and sends out a PuSH/Salmon delete for each. So it's a mystery and I'm not sure if it's still reproducible or not.

mastodon stuff 

@Gargron @boots can still only delete the ones that the originating instance knows about tho i guess?

mastodon stuff 

@bea @boots I'm not sure I get this statement. If the instance doesn't know about something then it's already deleted?

mastodon stuff 

@Gargron @boots if the source of the toot A has it boosted by B to instance C that it does not federate with, then the copy on C will not be deleted

right?

mastodon stuff 

@boots @bea Oh you mean reblogs of reblogs, spreading out. Yes, kinda. Delete of the original will travel to followers' servers, if they reblogged it, the delete of the reblog will travel to their followers' servers, etc. Theoretically.

mastodon stuff 

@Gargron @boots k so

pretty sure this does NOT happen

mastodon stuff 

@bea @boots we can do some rubber duck debugging. author->RemoveStatusService->"delete"->follower->ProcessFeedService->RemoveStatusService->"delete"->...

mastodon stuff 

@Gargron @boots @bea Only propagated to followers?
So what if I reblog something from someone I do not follow (eg. by pasting a direct link in the search bar)?

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!