WeChat ID
aaronpk_tv
-
gerwitz
https://github.com/gerwitz
•
Apr 2
I have no strong opinion here, 501 arose from discussion on the IWC Slack.
My API experience falls into REST and deep-stack buckets. Micropub is lighter weight than any non-REST protocol I've used or implemented over HTTP, so it "feels" right for it to act RESTy.
To defend my recommendation, if it's not appropriate to use HTTP codes, why does the spec call for the use of 4xx codes, rather than replying with a 2xx that includes error details?
The 4xx codes were inherited from OAuth 2.0, which defines a few 4xx codes when using access tokens, https://tools.ietf.org/html/rfc6750#section-3.1 and using 400 as a catch-all for any client errors. -
Add option to deduplicate entries within a channel across sources
Currently each source is treated independently, and if two sources end up having the same entry, the entry will appear twice in the channel. This is only a problem when for example I add a Twitter search from granary.io as a source, as well as have my streaming search script running, and a tweet matches both.continue reading... -
-
Eddie Hinkle
https://eddiehinkle.com/
•
permalink
That’s funny, I have that tag query support on my list both for my site and for Indigenous as well!
Out of curiosity, how long has it been on your list? Cause it's been on mine for a long time but I guess I haven't quite felt annoyed enough by having to type out the full tag to go implement this. -
Chris
https://chrisbeckstrom.com
•
Apr 1
Replied to reply to https://aaronparecki.com/2018/01/06/13/code-snippetsThis is great, thanks for creating such a useful tool! Do you also host your own git repo, and if so, how do you integrate that into your website?
I use gitlist (https://github.com/klaussilveira/gitlist) but it’s not integrated into my site at all.
Also on:
Thanks! My code snippets aren’t backed by a special git repo like gists are. They’re just stored with my regular posts. Those are part of the git repo storing my full site’s content, so I do have versioning if I try hard enough, but version control isn’t specifically a feature of this yet. -
add geofencing support
I'd like to be able to define geofences and rules that will run whenever a fence is entered or exited.continue reading... -
create meta-channel with h-events for upcoming birthdays
Given your (or a channel's) following list, find birthdays, then create h-events for upcoming birthdays. A microsub client that shows events will be able to show upcoming birthdays without understanding birthdays specifically. Could also index your website's nicknames cache to find birthdays there. or maybe provide a way to sync to Google Contacts even.continue reading... -
Store feed metadata
Feeds include additional data such as a name, image and description. In the case of podcast feeds, the podcast artwork is a critical component of the feed and should be presented when viewing entries from the feed.continue reading... -
-
provide a UI to move a feed into a different channel
should move all existing entries from the old channel to the new channelcontinue reading... -
add IndieAuth login to channels
Currently you can add an "API Key" in order to write content into channels. This is actually Aperture acting as a Micropub endpoint. It should be possible to log in to existing Micropub clients as one of these API keys, doing the IndieAuth flow and resulting in providing the client with the API key. This would provide a way to set up fancier integrations without copying and pasting tokens.continue reading...
