hm I don't think `channel` is the right terminology for this, ... • Aaron Parecki

Eddie Hinkle https://eddiehinkle.com/ • Dec 4
Also, thinking through this a bit more deeply, obviously someone could get data into their json file anyway they wanted, but the easiest way for most people would be a Micropub app that just allows you to snap a photo and upload it without asking for all the normal Micropub stuff. We would need some way to inform the person's server that the post is intended to be a "story". One option would be to send something like channel: ['stories'] or you could make a specialized Micropub app like that have a config screen where you define what additional metadata it sends and then people could use whatever method they wanted, a channel property, a tag property, etc. I definitely don't think a new attribute would be right, and I know channel isn't really used anywhere except your and my sites, but we also can't do tag as a default or else the posts would automatically show up on people's websites as a normal post (unless they configured posts with a specific tag to be routed somewhere else). So this is tricky, but I definitely think something like this would be required for me to use it routinely. My default for my site would probably be to use a 'stories' channel and then to be able to set an audience on each photo/video so that some things I could provide to a subset of people.

hm I don't think `channel` is the right terminology for this, also because stories exist completely outside of my own concept of channels.

Maybe it's just a new `mp-` command in the request?

Right now I have an iOS Workflow that just uploads a file to a specific endpoint. I guess that's the other way to handle it, create a new endpoint for it? Maybe the same endpoint that the story can be read from can also be POSTed to by the owner to create a story?

Los Angeles, California • 62°F

Tue, Dec 4, 2018 9:30am -08:00

2 replies
Have you written a response to this? Let me know the URL:
- Eddie Hinkle eddiehinkle.com
  
  Also, I think using the Media Endpoint is probably something you would want, so then you have to add a similar query style to the stories endpoint that Micropub endpoint has. Again, that workflow is already pretty clear but then it's like the stories endpoint is a half Micropub endpoint.
  
  Tue, Dec 4, 2018 4:08pm -05:00
- Eddie Hinkle eddiehinkle.com
  
  Yeah, you're right again! I did think "I'd have to tweak my channels" but thought it was the closest match.
  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.
  
  Tue, Dec 4, 2018 4:06pm -05:00

Posted in /replies using monocle.p3k.io