Big thanks to @thisismissem for walking me through some of the nitty-gritty details of ActivityPub and the Fediverse.
Her help is already making a positive impact on my work on #Emissary -- so thank you very much. Please support her work!
Big thanks to @thisismissem for walking me through some of the nitty-gritty details of ActivityPub and the Fediverse.
Her help is already making a positive impact on my work on #Emissary -- so thank you very much. Please support her work!
@subclub Congratulations on this roll out. This is a big step forward for the Fediverse.
Ok kids, here we go:
#Bandwagon, the open #Fediverse alternative to #Bandcamp is ready for its first steps into the light.
I have a waitlist online at
https://bandwagon.fm if you'd like to try it out.
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.
@dansup Yes. After Bandcamp.
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.
@silverpill Yeah, I knew I was probably going to get bit by web standards. And I *DO* want to follow the best standards.
What do you think would be the best approach here? I think it's important to keep it short, and as semantic/descriptive as possible.
Woo Hoo! Check out Baby's first FEP...
If you're a #Fedidev developer, please check out FEP-3b86 at https://codeberg.org/fediverse/fep/src/branch/main/fep/3b86/fep-3b86.md
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.
I owe you all some links:
I'm building all of this in the open on GitHub.So I'd love to collect suggestions as GitHub issues, if you're able to post there:
https://github.com/EmissarySocial/app-planetary/issues
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?
@steve @dansup -- Having only dug into the S2S API so far, I will 100% believe this.
Has anyone ever mapped out the gaps between these two? Or, would doing a diff between Macedon and C2S be the best way to figure that out?
perhaps that is the prerequisite to boot strapping this whole thing.
@dansup Go for it! Itโs always seemed like a chicken-and-egg problem: nobody builds C2S servers because thereโs no clients, and nobody builds clients because thereโs no servers.
If you could get even one good client off the ground, it might bootstrap the whole C2S ecosystem.
And I, for one, will absolutely follow you there. Iโd much rather build a solid C2S server instead of implement the Mastodon API.
Thanks for the feedback and boosts, everyone. You're all awesome. Are there FEPs out there that I should really consider to be "mandatory"?
It's hard to tell from the list which ones are just brainstorming ideas and which ones I should really get into.
I'm happy to start listing out the "best" FEPs, if that would be helpful.
In one session of #FediForum, I said that I really needed "a map" of the tools and communities for building apps on the Fediverse.
To follow up on that, I've posted a first draft of what this looks like to me.
If you know more about the Fediverse than me (that's most of you) please take a look and let me know how I could make this list better:
https://emissary.dev/fediverse-resources
Hopefully it's a starting place that'll help other #FediDevs to get their projects moving.
@aral Well keep it up. It looks super fun!
@aral Kitten looks pretty cool. Aimed mostly at JavaScript/HTML developers?
@risottobias Yes, yes, yes.
Honestly, my head is spinning right now from everything that came up and #FediForum. So, I think Iโm gonna go take a nap, do my taxes, and then come back to try to figure out how to organize all the great ideas swimming around in my head.
Let me know when youโre in Denver, and Iโll try and see if we can meet up.๏ฟผ
@ricmac Thanks, Richard! I'm pretty excited about this, too (and a little scared, tbh)
#Emissary is a personal / small group server that sends and receives ActivityPub, RSS, and IndieWeb (MicroFormats, WebMentions, etc)
It's also a programmable toolkit for others to build their own Fediverse apps. To anyone who's interested: I'm looking forward to helping you build cool stuff with Emissary. :)
@risottobias #Emissary handles all of the ActivityPub / WebMention integration under the hood. Your apps integrate with it with this json:
```{do:"publish"}```
In the (near?) future, I'm hoping to let developers define custom JSON-LD, and even handle JSON-LD messages, too. We should talk about your distributed wiki -- maybe at #FediForum Session 6? -- to see how much customization is actually needed...
I'm (gently) starting to post from my @ben account to see how well #Emissary works on the live Fediverse.
Eventually, I'll migrate this account over to Emissary permanently. But for now, I think I'll start boosting my posts there as a first step.
If you've ever wished there was some custom Fediverse app that served your *specific* community, we should talk.
#Emissary is new, and still needs some work, but it's ready for devs and other bleeding edge radicals to start building the next:
music sharing...
workout tracking...
garage selling....
location posting...
neighborhood gossiping...
Fediverse app.
Thoughtful comments on at least one irrelevant topic. #writing #software #democracy #pirates.
GNU social JP is a social network, courtesy of GNU social JP็ฎก็ไบบ. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.