Aaron Parecki

@aaronpk

What would it take to get #IndieAuth working with #Mastodon / #NextCloud / #Peertube etc? Are there any major changes required in the way the various #Activitypub apps do things to be able to support this?

It seems to me that IndyAuth or something like it are badly needed in the #fediverse, as the more #decentralized we get, the more accounts users end up needing, compared to #gasm et al.

@aaronpk ouch, quite an expensive wash :(

That’s really interesting that you handle the videos differently between your stories endpoint and your Micropub Endpoint. Is that for size? Browser compatibility? What’s the thought behind that?

Makes sense, I’m good with starting the stories experiment with it being a separate endpoint.

I think I might be leaning towards an mp- command rather than a new endpoint. But there are some pros and cons.

The pros for a new endpoint that is at the same url as the GET for the data is that someone who hasn't built Micropub or wants to use an external service for their stories would make that possible. By de-coupling it, it provides more flexibility.

The cons for a new endpoint is that the authentication layer, the set up of a new endpoint can be a technical hurdle that might prevent more people form getting involved. For those that already have a Micropub endpoint, the addition of the stories feature becomes a pretty simple add on. It also means there's a new communication layer that people would have to understand, whereas Micropub with an mp- command is pretty simply understood.

Either solution would be pretty simple for me based on my set up, but I'm trying to think what would be more difficult for: a) Wordpress Users b) Static Site Users, anyone else that is building their own tech stack it's probably not a huge difference.

That said, I use an external Micropub library in my Node.js server that does the authentication against my token endpoint automatically. So if I were to add a new endpoint, I would have to write the code to handle the verification of my token endpoint. While my token endpoint is on the same server, for other people in similar situations, they might have juggling the authentication process.

The other thing is I’m wondering, do we just make the story JSON mf2 json since you all have experimented with that as a Wordpress side file?

Screenshots of stories (or Snaps, if you wanna trace the idea to the original) seems to be the intended workflow. So Stories being saved doesn’t seem to be a problem… I guess? And remember that if it got on the Internet, it remains on the Internet… forever.

The visibility of story content seems to be present on story-supporting silos, so that should be fairly logical to implement. Authentication would be required in this case.

I see it fairly often. Is there any API in p3k to make these stories available in readers? Maybe we could build something interconnected, so every person’s story was available in an IndieWeb reader!

I think stories are harmful for #IndieWeb, since they:

1. Are not visible from readers
2. Divert attention to silos
3. Disappear
4. Don’t have a universal share button outside of the silo