It’s weird that we’re exploring an amazing new technology, but because Twitter is so disrupted, there’s no single place to report your discoveries. A pretty big handicap.
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.
@utzer@dansup Yeah. We could always just build a new network with special features that would require an account on a Q&A -style server.
But an emerging feature of "fedi" is that you can take your identity everywhere. I'd really like to support this somehow, too.
Perhaps it just means using main Mastodon (or whatever) account as a "universal inbox" for notifications. But then we link you back to a site with SSO, so you can interact more richly there.
Yes. Stack Overflow isn't magic. I think they succeeded because they focused heavily on SEO, which brought both ask-ers and answer-ers to the site.
Personally, the "accepted answer" is the killer feature. Dunno if NodeBB, Kbin, or others already support this.
There's potential in SO's gamification aspects, too. I'd love to let third-party sites to award badges or "endorsements" and display them on my profile page. This could work in all kinds of trust/credibility situations.
We're working to make a #Federated alternative to #Bandcamp where up and coming bands can connect with fans and share their music on the Fediverse.
The progress is really encouraging, so it's time to get some feedback from real #musicians
My goal is to have something you could actually use in the next month or two. So please get your ideas in so's I can squeeze them into my launch calendar.
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.
I have a few more “T’s” to dot, and “I’s” to cross, then I’ll probably open up a limited beta test. I’d love to chat once there’s something more tangible than my silly videos.
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.
Fantastic hack! And to think I just swapped between duplicate SVGs...
I’ll have to try this with icons, too. I’ve been dying to unload my webfont icons because the font file is soooo big. If this works with a remotely loaded SVG, I’ll be in hog heaven.
For years we've been using an alternate protocol between our own sites because ActivityPub wasn't capable of providing the services we require for federated communications. This is how we've supported things like nomadic identity long before the concept was even viable in ActivityPub. Now that I've got a usable framework for nomadic identity over ActivityPub, I went back and had a closer look at what else I might need to add to ActivityPub in order to finally put the Nomad protocol out to pasture.
I've mentioned transport encryption in the past; but that's only a big deal if you don't trust HTTPS security or your government. For true nomadic identity, we would also be sending sync packets so that your alternate identities are kept up to date with everything you do on other instances which share that identity. We'll also be offering a partially shared identity as mentioned in previous posts. This won't be a true clone but will instead be a way to link your various fediverse profiles in a cohesive way - like we do with our Fediverse Identity Manager. These are all pretty easy - just a 'Simple Matter Of Programming®'.
But I overlooked a real biggie. Permissions, permissions, permissions. A concept completely lacking in ActivityPub; and which can't be discussed rationally with other fediverse developers because folks raised on Twitter don't even understand the concept.
@mikedev I’ll agree 100% about the need for more granular permissions on the Fediverse.
So far, I’ve treated ActivityStreams as just one data representation (like HTML) not as the one core definition. I feel most permissions could/should exist somewhere separate from what’s published via ActivityPub.
Mike, could you expand on how you see permissions represented in ActivityPub itself? How does publishing this data benefit nomadic identity?
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?
@gribbles@n00q Sounds awesome. Yes, please stay in the loop on this. There are lots of things we can do with #ActivityPub that are more than "yet another micro-blog."
Not that you want to jump in and start coding, but to give you a ballpark estimate on the work required to make a custom app. Right now, its exactly 8 files - including the show calendar I'm working on.
Let's talk more once I have something ready to beta-test?
"...but I believe many UI developers prefer an API that's standardized across server implementations..."
This pretty much sums up the whole issue with ActivityPub.
Add to that: we're currently living in the world of "Mastodon-flavored-ActivityPub". If someone shipped a definitive C2S app, it could easily become the de-facto standard. I'll bet most devs (both client and server) would rather follow a well-defined API, and not have to greenfield their own design.