dshanske
https://github.com/dshanske
•
Apr 5
WeChat ID
aaronpk_tv
Sunday, April 8, 2018
| bicycle |
2 hr 19 min
|
|
22.3 miles
|
bicycle |
-
-
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. -
That was a great one this week! I really enjoyed the summaries of all the links added to the various wiki pages!
-
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 -
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.
-
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.
