@Edent Good writeup! To add: originating servers could orchestrate anonymous (on the poll author's side) voting by sending votes from a shadow account instead of the user's real account, moving the knowledge of who voted from the pollster's server to the answerer's. On the fediverse, identity is cheap anyway, so there's not much added potential for abuse. @rimu recently did just that in PieFed, in the context of link aggregator votes.
* It's instant, purely client-side, and has no ads or upsells. * It has a variety of color, shape, and logo embedding options. * There's PNG and SVG export.
The included logo selection is, let's say, "opinionated" and features lots of familiar faces if you enjoy federated social platforms. 😄
Here are a few example QR codes that all lead back to my Mastodon profile.
@evan An added dimension is that there are some fediverse implementations that are indeed server monoliths, even though most are not.
In a pitch presentation I've previously given, I tried to visualize the differences to closed social networks like this. A dot is supposed to represent one person, and Mastodon is more of a nebula than a single unit.
I'd be open to suggestions for improvement. 🙂
Edit: The next post in your thread has the improvement ideas. 😄 I'll take that on board, thanks!
@tchambers I've been working on multiple projects with it, it's enjoyable.
I don't know the whole Node / other server side TypeScript ecosystem very well, but Fedify with its documentation and examples makes it pretty easy to get started.
@evan I would love to try poutine in this lifetime. Apparently there used to be one single restaurant in this city that made it, but it closed down a few years ago. Gotta hope I can find an opportunity while traveling.
@hongminhee Does it assume that? I don't see it clearly stated in the documentation that the IDs themselves need to be numerically sortable, just that, when given a specific ID, the server needs to be able to retrieve newer or older posts based on it.
Of course sortable snowflake IDs make implementing this easier on the server side.
@gamingonlinux@rdnielsen The "Mastodon effect" is a real thing, but its impact will depend heavily on how a site is set up. I'm surprised a news site would struggle with it.
What am I doing this weekend? Learning #TypeScript, #Deno, and @hongminhee's #Fedify all at the same time, for a project which I'm hoping will be used by many people.
They say it's early in development but it's probably more mature than mine. 😄
It'd be nice to have a framework of sorts in Python that combines AP, WebFinger, HTTP signatures and all that stuff, without the fixed microblogging use case.
@PersistentDreamer Pixelfed is an ActivityPub-powered social platform that @dansup is developing. It's focused on photo and image sharing. It's interoperable with Mastodon, so you can follow Pixelfed users from here if you want to. https://pixelfed.org
The above screenshot documents and incident where a post on Meta's Threads was automatically marked as spam for mentioning Pixelfed. This is likely because Pixelfed is a competitor to Instagram and Meta is petty.
@aral@sarajw Going by his GitHub comments, I wouldn't be surprised if Ryan changes the plan to opt-in after sleeping on it. Making a protocol bridge 100% opt-in comes with some thorny interaction design challenges, but the "prompted opt-in" idea that a few people have brought up seems workable. I think that's what I would do in his shoes.
Of course I'm not in his head, but I empathize. He was up pretty late last night of his timezone replying to people, and in that time got the two puzzle pieces "move towards opt-in" and "how an opt-in process could work in practice" figured out, only missing the final commitment. I wouldn't have made a big statement at like 2:30am either, I would've gotten some rest and come back refreshed.
@scottjenson@Danc@edk Around 2006 some German HCI researchers investigated what makes an interactive system intuitive to use, concluding that it has more to do with familiarity (= ability to transfer existing domain knowledge into it) than simplicity. https://dl.acm.org/doi/abs/10.5555/1784197.1784212
One of the authors later taught HCI in Hamburg. It's where I picked up the notion that systems for professionals (of any kind) often look more like airplane cockpits than stove panels. Complex tasks beget complex tools.
@scottjenson@Danc@edk Their writing alludes to the responsibility of designers to foster capability growth instead of only aiming for the lowest common denominator, but stops short of making process suggestions.
@renchap I appreciate this approach, Renaud. 🙂 Is there anywhere people can follow the progress on this work yet, like a GitHub issue or an FEP draft? I get asked about this pretty often and I've been linking people your roadmap thread from a month back as the "latest update".
@aral Hey Aral, I gave you a shout out while talking to @fediversereport about the philosophy behind my recent weekend project Pinhole :fietkau_software: https://fietkau.software/pinhole and why I built it to be anti-scalable. Thanks for the inspiration! 🙂 If they end up using the full quote, your name should appear in their next newsletter.
Human-computer interaction #HCI, computer science & programming, home server & self-hosting, games and other fun stuff.Fediverse tool builder: @encyclia, @canary, FediRoster, Pinhole, ... see https://fietkau.software/tag/fediverse for more. I also help out with @fedidevs. If you do HCI-related research, check out https://directory.hci.social.He/him. Posting mostly in English, but you might see the occasional German boost.