WeChat ID
aaronpk_tv
-
How Carob Traumatized a Generation | The New Yorker (www.newyorker.com)"As adults, we make hundreds of carob-like dietary substitutions in the name of good health. We shave summer squash into long spirals and deceive ourselves that it’s anything like pasta. We tip coconut creamer into our coffee, ignoring the way it threatens to curdle"
-
Portland, Oregon • Wed, January 31, 2018 11:33amEarly lunch 🍔 -
AsleepAwake7h 45mSlept12mAwake for
-
-
Did you find an instance of this? This shouldn't happen by definition, since any in-reply-to Microformats property in the post would cause it to appear in the Microsub post. This is in contrast to photos, where an img tag can exist in the content that does not have u-photo so does not get set as the photo property of the Microsub post
-
Portland, Oregon • Tue, January 30, 2018 5:36pmSetting up for #donutjs
-
"A photoblog is like Instagram, only it's harder to use, your friends aren't on it, and it's owned by you, not a megacorp." 😂 https://www.kickstarter.com/projects/davidfg/you-have-to-see-this-place -
EdwardHinkle
https://github.com/EdwardHinkle
•
Jan 30
My first thought is concerning potentially writing posts offline. I think I would like to be able to query my micropub endpoint and get an array of contacts, in the same way I can get an array of syndication targets. This allows the ability to be writing a post offline and to power either person tagging or @-mentioning.
Right now you can only have one draft post at a time (if you click cancel while writing a post, it will ask if you want to save you post as a draft, if so it will auto-fill the form when you open it back up again).
Eventually I would like if you are offline to click "Post" and to have it auto-post when it gets internet again. So in those cases I would want to be able to handle all nickname cache stuff on device after the initial login (and maybe periodically refetching the cache every couple of days or something).
I can see how it could be useful to query the server with the string so far in a situation where you know you have internet.
Yeah the offline case makes sense for sure. I guess i was just worried the list of names might get too big. So maybe the client needs a mechanism to sync the list and keep it updated. -
-
There's a Microsub issue about this: https://github.com/indieweb/microsub/issues/6
I think this would best be done on the server, so that it's consistent across all clients. It's also something that a particular Microsub server could implement on its own, just that clients would not have a way to configure the filters. -
There's a brainstorming issue for Micropub to have a way to query a site's nicknames cache https://indieweb.org/Micropub-brainstorming#Query_for_contacts
-
This begs the question of whether Microsub should provide a feed discovery feature like XRay has implemented. Monocle also uses XRay for this so you can subscribe from its UI.
-
ah jeez, Nest changed the mounting bracket and power adapter between their 2014 and 2018 models, so now I have to go rewire this instead of just swapping it out.
-
Priority follows
This might not end up being a feature of the Microsub spec, since any individual Microsub server could implement this, but let's document it here to see how widely this concept gets implemented.continue reading... -
I do like that feature of Overcast. Castro does it too. I'm not quite sure how to translate this into Microsub yet, but it'd be worth thinking about.
-
EdwardHinkle
https://github.com/EdwardHinkle
•
Jan 30
Yeah, exactly. On timeline can you provide both a before AND after token? You definitely would want to be able to specify both in the "timelineCounts" method.
Yeah right now it will actually work with both before and after tokens. I guess that isn't made explicit in the spec, but it was just as easy to have the code work that way. -
EdwardHinkle
https://github.com/EdwardHinkle
•
Jan 30
Excellent. I think the "unread counts" property is useful based on common reader approaches. So I think that is definitely valuable, I can see a lot of people wanting to use that. For my use-case, my unread status will likely be based on if the updated property has been "updated".
I'm gonna have to think about this further because there are three options I could do. Regardless of the option I use, Indigenous' default will always be based on if new posts have come in. However, there are some additional features I might implement:
- I could provide an account-wide setting that changes all Channel Unread indicators to be based on if there are any unread posts in the channel. This would be helpful for people that are completionists.
- One potentially interesting idea is instead of the above option, I could provide a per-channel setting of the "Unread Status" of the channel. This would be helpful because some channels I might want to read completely (more article based channels), whereas other channels I might want to be able to just scroll to the top and only have it be marked as unread when a new post comes in.
I think I'm leaning towards that last approach:
- All channels default to showing as read when the user has scrolled to the top and showing as unread when the channel has been updated with at least one new post.
- Each channel can be edited to have it's read/unread indicator be based on if there are any unread posts in the channel.
I like it. I'm definitely planning on having a few channels that I want to read 100% of the posts, and some where I want to skim them really quick, so I would definitely use that setting. -
Cappuccino
-
AsleepAwake7h 45mSlept17mAwake for
