jjuranI just thought of an idea. An image-based challenge, but instead of making the symbols nigh impossible to read, split the image into tiles, possibly using CSS to obfuscate their order.
@danyork↩️ @ambrwlsn90 - Thanks for writing that post. A question - how does Webmentions deal with spammers trying to add links to your posts? That was historically the big problem we wound up with both pingbacks and before that trackbacks. (twitter.com/_/status/1355905491197710339)
[Raphael_Luckom][tantek] one way I think about those things is to try to drive toward a contradiction. Like "If I imagine that the instance admin is 100% responsible for blocking / unblocking, can I think of an unambiguous-ish situation where that would fail badly?"
[Raphael_Luckom]the more interesting designs, like what you suggested, use more nuanced rules and them observe the dynamics that emerge. It's harder to predict what will happen in advance
ZegnatShould that in the great federated dream not mean that if your instance blocking thoughts do not align with your own, that you look for a different instance? Full disclaimer though: I am not sure I know what "blocking" means in this context. If my instance blocks yours, does that mean you can't follow me? But surely who gets to follow me (if I have no public feed) should always be decided on a per-account level and not per-instance?
ZegnatAlso possibly important context: I am not on the fediverse, I never left the blogosphere, so I was only reacting to [Raphael_Luckom] and do not know what prior conversations might have been like outside of indieweb IRC channels.
[tantek]not really KevinMarks, that was more of a wrangling organizer time/energy thing that burnt out the small set of us doing that. more on #barcamp in #indieweb-chat
[tantek]Continued on the obsession with figuring out "blocking": Also I'm starting to think that the "everyone is invited/allowed by default" position/attitude, whether to a personal site or "node" that you're hosting for folks, is a very entitled+privileged design attitude that ignores (or is naive to) the default harms that marginalized folks face
[tantek][Raphael_Luckom] re: "one way I think about those things is to try to drive toward a contradiction." I'm going to go out on a limb here and say while that's a good problem solving methodology for math, philosophy, and computer science, it's ironically *really* counterproductive (or missing so much of the solution-space!) for anything human-centric: UI/UX design, social interactions, politics, governance etc.
[KevinMarks]Well, it's also only a necessity when you have the kind of broken reply model twitter has now, where any reply is both sent to you and pasted on the bottom of your post unless you take action to prevent that.
[tantek]"only a necessity" ... "where any reply is..." <- this is precisely an example of what I'm talking about with "everyone is invited/allowed by default position/attitude"! (of Twitter's design)
ZegnatSame assumption is kinda build into webmentions and activitypub. These are all sort of publicly announced public inboxes. This makes federation/decentralisation possible because someone can spin up a new server that you do not know about, and they can then start interacting with you anyway. But public inboxes are hard to manage (see: email). How do I invite someone to my public inbox?
@GR36Now I’ve got twitter replies sorted as webmentions for blog posts. How are people displaying twitter likes?
Mine show up as. comment but noting appears underneath. (twitter.com/_/status/1355950269947908097)
Loqilikes are sometimes part of the information about a post displayed on the post itself, often in a post footer, like a total number like responses, icons of recent likers, or even a datetime ordered list of likes https://indieweb.org/likes