How much of this could we model in ActivityPub? Is it a limitation on the tools we already have? Or just that weโre not using our existing tools well enough?
I'll add these to my list, with some placeholders for "Proposed Solutions"
-- I can't stand when people sit on the sidelines and gripe about my work, but don't propose any way out of the problem, so I'm determined to not do this here.
I have plenty to gripe about, but feel like we should at least say what we'd do about it -- even if nobody else is listening :)
@CassandraVert Yep, great example. I think this is called something like "phantom replies" or "dropped replies"
And, I think the "Threaded Discussions Working Group" is working on something for this, but (as always) support may be spotty.
I've read several replies from people saying versions of "this is just because of the nature of 'Federation', so deal with it" but no other self-respecting social network would allow this behavior.
We're building ONE system, not many interconnected systems.
So, apparently I'm collecting a list of #ActivityPub pain points, now.
(shit)
What's your top ten list? I'd love to compare, and make sure I collect a complete picture, even if I don't have a good solution to the problem just yet.
Many here are so committed to โhow things wereโ that itโs hard to talk about โhow things could beโ
Iโll happily sign on to something AP-adjacent (strict mode?) that lets us talk to Mastodon and Threads for now, and provides a richer overall UX among the implementers of the new protocol.
Any new group would have to be small, and filled with actual implementers, not industry reps and armchair architects.
The deeper I dig into the #Fediverse, the more I realize that we aren't building a "federated" group of individual apps. It's a single, integrated system. Something like a digital hive-mind, and everything is connected.
Those once isolated websites and services are like individual cells in the body whole, making connections between (API's, protocols, etc) even more important than the individuals themselves.
Piece by piece, we're connecting #Bandwagon to every corner of the open web.
Today, we're improving how links to your songs and albums display when someone shares them on Mastodon, Facebook, and others. It's a small thing, but immensely valuable to the social web.
I'm planning to build the first (dozen? I don't know) profiles in the waitlist personally, with an email questionnaire and FaceTime follow-ups if necessary.
Once I'm confident in the UX, we'll open up self-serve signups for everyone.
I had an online discussion about a Federated-Yelp that raised some interesting points that might apply to SO as well -- How do you โfederateโ the features that DONโT fit into the standard social media formulae? Things like โaccepted answersโ might only work on a centralized server.
Also, this might fall under the threaded discussion WG. Iโd love to talk in more detail if youโre ever interested.
Sorry, I meant to answer this directly, but I'm still catching up.
In the original FEP, I tried to address the FEP namespace from w3id.org. There's a lot of good reasons to use it. But I'd hate to have to type `/fep/3b86` over and over. It's not very semantic, so I went looking for something else.
What do you think of using `w3.org/ns/activitystreams/#Follow`? Are those IRIs off limits for some reason? If not, it seems like a pretty good fit.
I'm working on "Remote Likes" and "Remote Shares" that help you jump back to your own home server to post when you find something cool on another website.
Imagine those "Share on Facebook" buttons, without all the ick.
I know it needs some work (that's what FEPs are for, yea?) so please read, comment, and help me get this over the finish line.
But, if you're not a software nerd like me, just send me a reply to this thread (or as a DM) and I'll do the rest.
Sharing, Directories, and Discovery are important parts to this, but I still have to build those out. LMK if you have thoughts/feelings about how that should look, too.
At #FediForum, @n00q discussed a Federated music service for #BandCamp refugees. After a few days of drawing up requirements and specs, and a couple days of code, something interesting is taking shape.
Here's a too-fast-tour of a hypothetical album page built with #Emissary. Custom skins, uploads, and transcoding music is still TBD, but so far this feels like magic.
Bands' profiles will be native citizens of the Fediverse to like, share, and comment. Excited yet?