If things don’t get anymore fishier regarding Pixelfed.social , the developer of the application who has refused to respond to me on the @pixelfed account and on their personal account @dansup during the past week has BLOCKED ME instead of providing any proof of why my account shows on federated instances after deleting said account (and deleting posts before deleting the account). I have no access to it anymore.
Please read first how federation works. How posts are federated, how posts spread on the federation and how posts disapear from federated instances after you deleted them.
@ButterflyOfFire@pixelfed@dansup@trumpet I deleted a handful of Mastodon accounts in the past and none of them had posts (or media or bios) after deleting them after weeks of deleting the account.
And these were ranging from small unknown instances to mastodon.social.
@intothetilian Even if you close your account on PixelFed or any other Fediverse instance, it will always take a while so that copies of your posts will be deleted on the other instances.
It depends on cache retention on every single federated instance too.
Blocking every user on it because they complained or assumed something. Maybe all my assumptions are wrong. Again, I don’t know all of these tech stuff.
@ButterflyOfFire@pixelfed@dansup@trumpet I don’t know but I remember a lot of users on Mastodon attacking me for Pixelfed being so sketchy and that I simply “don’t know” how federation works.
@intothetilian@ButterflyOfFire@pixelfed@dansup Your browser isn’t alerting you to an issue with Pixelfed, it’s alerting you to an issue with your password. Let’s say you used password ‘secret123’ on another site, which was compromised, and you also used password ‘secret123’ on Pixelfed. The password has been compromised, so your browser is alerting you to that on every site you use it on. I can almost guarantee that your Pixelfed password isn’t unique to that site.
Add comment