@[email protected] to Fediverse [email protected]English • 1 day agoSnitches get stitchesi.imgflip.comimagemessage-square37fedilinkarrow-up1197arrow-down114
arrow-up1183arrow-down1imageSnitches get stitchesi.imgflip.com@[email protected] to Fediverse [email protected]English • 1 day agomessage-square37fedilink
minus-square@[email protected]OPlinkfedilinkEnglish11•1 day agoWhile that is very much true, but I find it debatable if you (as in the dev) want the user facing UI to show it.
minus-square@StovetoplinkEnglish25•1 day agoBut even if platforms agree to not make the data visible, anyone can spin up their own instance and browse through the backend data that is being sent. It’s the ActivityPub protocol itself, not the individual platforms that use it.
minus-square@[email protected]OPlinkfedilinkEnglish4•1 day agoThe main difference is ease, and if you have to spin up your own instance vs just press a button I’d guess most people wouldn’t do it
minus-square@idiomaddictlinkEnglish20•1 day agoMost people wouldn’t, but all the ones you need to worry about would.
minus-squareAwesomeLowlanderlinkfedilinkEnglish12•1 day agoYou’ve never seen how dedicated trolls and bad actors can get, I see.
While that is very much true, but I find it debatable if you (as in the dev) want the user facing UI to show it.
But even if platforms agree to not make the data visible, anyone can spin up their own instance and browse through the backend data that is being sent. It’s the ActivityPub protocol itself, not the individual platforms that use it.
The main difference is ease, and if you have to spin up your own instance vs just press a button I’d guess most people wouldn’t do it
Most people wouldn’t, but all the ones you need to worry about would.
You’ve never seen how dedicated trolls and bad actors can get, I see.