Notices by Ben Pate 🤘🏻 (benpate@mastodon.social)

@pfefferle Done! Webfinger queries on emissary.dev and bandwagon.fm should now use the correct "template" argument. And I've updated the server-side lookups for #Emissary as well, so that they'll find the new (correct) value.

Here's a sample: https://emissary.dev/.well-known/webfinger?resource=acct%3Abenpate%40emissary.dev

Thanks Matthias!

@pfefferle

You’re gonna make me work, aren’t you? At 7:20 in the morning? Before I even finish my oatmeal?

With half-steeped tea!?!?!

You know what, I’m heading to my computer now…

😁😁😁

@pfefferle YESSSSS!

This will be awesome! Please let me know if there’s any way I can help make this happen.

My first implementation is 50/50 JavaScript and back-end code. In hindsight, I should have done 100% JavaScript. It would have been more portable.

But please take any of my code as a starter, or let me know if there’s other places I can help.

Super excited!

@pfefferle

Thank you! I think you caught something that drifted over time, but I didn’t go back to fix in my own code.

I really appreciate your help, and am excited that this is picking up momentum. Thank you so much!

@dansup That would be amazing. I would love to help you any way you need, and I can chat whenever it's good for you.

And, don't forget @Bonfire - they're also building to the same standard. #E2EE will be awesome for the #Fediverse.. but only if there's general #interop between different projects.

If you want some fun bedtime reading before we chat, I'm collecting all of my notes on the project here: https://emissary.dev/e2ee

That page includes links to the spec, Github, and other stuff.

I'm deep into refactoring the #E2EE code today. My goal is to reconstruct all of the server side code.

So, it's back to #Bandwagon roulette for today's coding music. It's simple: go to search, pick a hashtag (#Ambient for me, please), then play the top album in the results. They shuffle every time you reload, so there's always something new.

First up for me ~ Pathfinder by HCM: https://bandwagon.fm/678ec24cd84b0eb346b7a482

Yes, I think I like the idea of clients being able to store data on the server however they like. It reminds me of this description of ATProto that I found recently: https://overreacted.io/a-social-filesystem/

I guess my question is: once I store my custom stuff in custom places on my server, how do I publish this so other people can find?

And, object IDs are usually defined by the server. So how would it work to say "create a collection named XYZ and add this object to it"?

@silverpill @mariusor @trwnh

@silverpill @mariusor @trwnh

I e*love* this idea- especially in principle. I say that because I’m having a hard time wrapping my head around this and how it would be used in practice.

Do you think you could post an example workflow (or three) to demonstrate how this would work?

I get that objects could be added to client-defined collections (very cool) but if object/collection IDs don’t have predefined semantics, how will I know where to look to get the data I need?

@dansup awesome. Thanks. One more thing for the “to do” list 😅

@dansup well done! And congrats on another big update!

Are your starter kits documented somewhere? I’d love to follow on your work.

I'm a software developer working on a bunch of #Fediverse things: #Emissary, #Bandwagon, and bandwagon.fm - with several more in the pipeline.

It's a pretty strange mix that doesn't really fit today's Fediverse, but it makes sense when you see the end goal.

I got an opportunity at #Fedicon to explain myself, so here it is:

https://spectra.video/w/eod3ybLu7sHzAEMihej8km

It's not the greatest talk about Fediverse tech, but it's the best I've got so far, and I hope it inspires you to make great things here with me.

Thank you! I’ll make sure to get the listing updated.

And, thanks for taking a leap on this. I think we’re going to do something amazing together.

@rimu_piefed @webintents

Yeah, this is how I'd expect it to work (with the possible addition of *also* allowing cookie auth on the client side)

But yeah. Locally authenticated user from my client -> my server, then HTTP signature from my server -> your server

@evan @mariusor @thisismissem @steve @smallcircles

@thisismissem @steve @mariusor @smallcircles @evan

Just checking my memory.. this concept exists already, yes?

https://www.w3.org/wiki/ActivityPub/Primer/proxyUrl_endpoint

Are you just saying that the new API spec should include this? Or am I missing something?

There's a lot of energy on the #Fediverse right now to discuss/find a #Federated alternative to #Discord using #ActivityPub.

@strypey suggested that I put this out there to anyone who's thinking about it. We could probably rebuild most of Discord's features as an #Emissary inbox without doing a lot of back end code.

I'm too swamped to start on this right now. But if you're a great HTML+CSS designer, I'm able to give some time to a team who wants to take this on.

@evan @tess

I wish I had a hard number on what I though it'd take "to be a maintainer"

"It depends" *feels* like a cop out, but:

- Is the code stable & well written?
- Or is it spaghetti code that just mostly runs?
- Is it a niche app? Or super-popular that everyone uses?
- Or does Russia *really* want data off one of your servers?

The curve could easily go from negligible (0-5 hrs/week) to being 60 hrs+ for months

My work is 30-40hrs/week, but I'm still greenfield, not maintaining, sooo 🤷🏼♂️

I've been thinking a lot about #ActivityIntents and how to make it easy for people to find and join the #SocialWeb

Here's some ultra-low-effort drawings of the process I'm imagining. (criticism and refinements welcome)

1. embeddable widgets (follow, like, share, etc) for any site

2. pre-populate search fields to recommend a single server (with overrides)

3. pass extra data to that server on signup so the intent is honored

4. recommend additional accounts based on context

Yes?

Hey #FediDev gang.. Do you think this is the right way to guide people from personal/organizational websites into the #Fediverse?

Some of this is defined in #FEP3b86. Some of it exists today in #Emissary (and the #oStatus "remote follow") some is being built by @dansup as #WebIntents, and some is just scribbles on paper.

If there's interest, I'm happy to write up the rest of this as an additional #FEP

@silverpill
@rimu
@evan
@trwnh
@julian
@ricferrer

@evan Yes we do! It’s up in Boulder, and it’s a pretty big deal. If you’d like to go, I’ll happily drive you up there and drop you off at the door 🙂

@evan I work hard to experience Shakespeare as little as possible :)