Heading to @CocoaBoston in a few. Hope to see some of you there! cocoaheadsboston.org
WeChat ID
aaronpk_tv
-
Nice! Do you know the organizers? I'd love to come out and give a talk on OAuth for iOS apps at a future meetup! -
That would be so great! I would definitely use this!
-
manton
https://micro.blog/manton
•
Apr 11
@frankm It's easy to forget, but I think there were quite a few around 2007-2008. I remember trying to convince people to use Twitter. Many people didn't get it.
Not even that long ago! https://www.wired.com/2016/05/twitter-onboarding-tips-for-new-users/ (2016) https://www.lifewire.com/tutorial-intro-to-using-twitter-2654622 (2018) -
danielpunkass
https://micro.blog/danielpunkass
•
Mar 25
@aaronpk I intend to support it natively when I can. It’s would be helpful to know if an equivalent of “getPosts” is standard yet? Can I list the contents of a blog?
Not yet, but if that's a requirement for you then I am interested in solving it! -
Excited to see what's coming!
-
jeremycherfas
https://micro.blog/jeremycherfas
•
Mar 25
@JohnPhilpin @sumudu I'm waiting until it is a little more robust before trying to get @aaronpk's bridge from XMLRPC to MicroPub working with MarsEdit. That will be fun.
fyi I'm not planning on making any changes to that project unless prompted by someone who is actually going to use it with another tool. I would also rather see MarsEdit add Micropub support so that it can work natively with more sites! -
dgold
https://micro.blog/dgold
•
Mar 25
@aaronpk Wow! That's an incredible thing to put out there & available, aaron, thank you.
The nice thing is it doesn't require that the bridge store anything, even user credentials, so it doesn't take a lot of server resources to run! I am curious how many people will find fun edge cases from various blogging apps tho! -
This is incredible! I used to love this game
-
Matt Biilmann
http://www.netlify.com
•
Apr 8
I would recommend adding it as an env var in the Netlify UI - there it will only be exposed to your build environment and any Lambda functions you run.
That's probably a better idea :-) In any case the token only provides read access so it's not a huge deal. -
ah, if you don't mind everyone having access to query your webmentions on https://webmention.io then it's fine to make that public, either in github or in Javascript on your site.
-
Frederic Hemberger
https://frederic-hemberger.de
•
Apr 8
@aaronpk Hi Aaron, I'm trying to implement webmentions on my site. Unfortunately, @netlify doesn't support encrypted env vars, so I'm not sure if pushing the API token to GitHub in clear text is a good idea. Any thoughts?
Which API token are you talking about? Also might be easier to come chat about this in IRC/Slack: https://indieweb.org/discuss -
That was a great one this week! I really enjoyed the summaries of all the links added to the various wiki pages!
-
Agreed on removing the filter. Until there is a good use case for a plugin modifying the behavior of the plugin that also wants to provide finer-grained access, there's no need to make that part extensible. Supporting the primary list of scopes create/update/delete/undelete is good for now, and you could also accept "post" if it's requested for legacy clients.
-
Eddie Hinkle
https://eddiehinkle.com/
•
permalink
How did you do this??? I need to know! That looks like you edited the global items???
A clever app using probably not allowed system APIs to mess with it! Here's a pretty good writeup: https://medium.com/productivity-freak/what-if-you-could-really-customize-your-new-touch-bar-ea42ec66f42c -
Jeff Atwood
http://blog.codinghorror.com
•
Apr 6
One thing we don’t do but I would like to is tombstoning a forum as static HTML pages (no vulns)
Totally! I did exactly that for all my old startup's websites. Forums, event calendar, blog. I want the content to stick around, but there's no way anyone would keep all that software updated. Flat files ftw. https://github.com/aaronpk/spiderpig http://community.geoloqi.com http://geoloqi.com/blog/ -
singpolyma
https://github.com/singpolyma
•
Apr 6
We wanted to avoid needing to spell out diffing mechanisms for every conceivable format in the core spec.
I get this, but why not just allow for format-specific diffing without specifying it? Show the atom one as an example and leave the specifics up to implementation.
I don't remember the exact reasoning anymore, but believe me there was a *lot* of discussion about this. You can probably dig up some of the past threads here if you're so inclined https://github.com/w3c/WebSub/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed+diff -
We wanted to avoid needing to spell out diffing mechanisms for every conceivable format in the core spec.
The trick around this to technically remain spec compliant, while also not surprising consumers of the WebSub API, is to say that your WebSub-enabled URL returns only the latest item. That way you can send just the one
<article>or whatever, and it still counts as "sending the full contents of the URL". In practice, it's fine to do this as long as the page you're sending has a concept of multiple items in a list, and if your consumers are ready to handle arbitrary numbers of items. -
indieauth.com should never have been involved in that flow if both wordpress plugins are set to use the internal authorization endpoint. I think your idea that an old options entry is being used is right.
-
Which site was this plugin installed at? Both? And which site was configured to point to indieauth.com?
Technically we shouldn't need to end up on indieauth.com for this use case, though that might need to be a separate set of changes to the plugin. -
So to clarify, you installed this plugin on both sites, and you were trying to log in to one as the other? It would be nice to get more information about the error you're having so we can try to reproduce it.
