"an overeducated engineer and programmer who used to be a designer"
1. [(visual computing) research https://graphics.social/@daridrea
2. (security, ML/AI, apps/web, prodmgmt) side projects]
3. she/them đŤ
| Hellbird | https://twitter.com/daridrea |
| Cohost | https://cohost.org/daridrea |
| [email protected] |
Announcing #cubiti
A toy #fediverse server for #ActivityPub and #MastodonAPI
Run server, connect to it with Mastodon client (#Pinafore works, #MetaText just about works), do federated stuff.
ActivityPub in the back, Mastodon API in the front, sqlite and node.js in the middle
There's going to be a massive land grab of all these big instances. There will be lots of merging and acquiring too.
My advice is that you all become *very* aware of who owns your instance and why.
Get to know your adminsâmake sure their values align with your own.
If you don't want to put your social media life in the hands of strangers, then self-host your own instance.
Itâs here!! My new zine âThe Pocket Guide to Debuggingâ is out now!! It has 47 pages of my favourite strategies for solving your sneakiest bugs. đ đ
Get it here for $12: https://wizardzines.com/zines/debugging-guide/
A kind observation that exclusively calling this place "Mastodon" has a bit similar energy as saying "I just sent a GMail."
"Fediverse" (or "fedi") is a more inclusive, general term.
Mastodon is just one of many software projects that talk to each other to create this multi-instance social network:
https://axbom.com/fediverse/
(kudos to @axbom for this fantastic infographic!)
There are blogs, Reddit-like communities, video instances and many more, all part of fedi.
As more and more people are asking me about Mastodon I felt a need for a picture to point at, showcasing how the software known as Mastodon fits into the much larger concept of the Fediverse. I made this infographic to help myself and others explain the many different use-cases
On responsiveness and quality interactions, in #WebXR and beyond :
FWIW I'm not a game developer but still program VR prototypes professionally. I do that on the Web not just because I know it but rather because of the potential for, when done right, responsiveness and accessibility.
Using WebXR one makes a single Web page that works on a VR headset, including standalone like the Quest, but also on a mobile phone (using the IMU, or not) or desktop. The single same Web page. That can also include networking and federation. So... yes indeed I believe if someone wants to build something social, something to use with others, it should go beyond "just" VR.
That being said, responsiveness and accessibility, must not come at the cost of "flattening" the experience. It's not because an experience can also be done on an entry level mobile phone that roomscale and handtracking must disappear, rather one must rethink of quality interactions both per device and across device. What does it mean to manipulate a thing, e.g 3D model or even text and code snippets, while moving with hands (in VR) versus just 2 thumbs (on mobile) statically? That is the harder part, when we can find ways to both compete and collaborate while leveraging the best of interactions across totally different devices.
I have students in my Software Design & Development course listen to that episode as a reading assignment, and then we do a kind of â5 Whysâ exercise around the question âWhy did Atari collapse?â The rules:
⢠Ask why
⢠Stick to proximate / direct causes
⢠Be specific
⢠Keep asking why
Hereâs a screenshot of the virtual whiteboard from that discussion when the class was remote. Comes out a little different every time, but similar themes always emerge:
Toby Jaffey
Chris Trottier
Julia Evans
MichaĹ "rysiek" WoĹşniak ¡ đşđŚ
Utopiah (Fabien Benetou)
Paul Cantrell
Vicki Kyriakakis
David Carroll
Oliver Darcy
Mark Jardine 