A little bit of spandex helps the financial basics go down! @ohmydollar #backerkitbond
WeChat ID
aaronpk_tv
-
at StreamPDXPortland, Oregon • Sat, March 10, 2018 11:37am
-
This is fixed in the current master branch. https://pin13.net/mf2-dev/?id=20180310151320713
-
at StreamPDXPortland, Oregon • Fri, March 9, 2018 5:24pmPreparing for moving the trailer tomorrow
-
Overdue, but yeah: Join us for @indiewebcamp Düsseldorf 2018 from May 5th-6th, right before @btconf. Let's put our heads together and work on our personal sites! 👉 https://indieweb.org/2018/Düsseldorf It's free, it's fun, it's @sipgate (🎉) and also on @colloq_io 👉 https://colloq.io/events/indiewebcamp/2018/dusseldorf/1
-
Took a solid 10 hours but better backcompat parsing rules in mf2py now https://github.com/kartikprabhu/mf2py
#python #microformats #indieweb -
Tomas Quinones
http://flyingsnailcreations.com
•
Mar 9
Thanks! My current Macbook has a iCore 7 and Thunderbolt ports, but my next Macbook will only have USB-C. I'm getting an AGPteK http://amzn.to/2oWWGsN on loan for the weekend but may order one of these solutions soon.
Only the 15" Pro has a quad core CPU so that's the only one the Elgato will work on. Can confirm it does not work on a 13" Pro. Your best bet would probably be to get a USB-C to Thunderbolt converter and the Blackmagic. -
Tomas Quinones
http://flyingsnailcreations.com
•
Mar 9
@aaronpk Any recommendations for streaming HDMI (Sony Handycam) to USB3.0 & OBS that doesn't cost more than $150? I want to stream paintings and other creative endeavors but the iPhone is too limited on focal range.
Do you have Thunderbolt? This is the best if so: http://amzn.to/2FvbepG Otherwise you're going to need a quad-core CPU and then you can use http://amzn.to/2oXJ0Oh
-
Colton Idle
https://twitter.com/ColtonIdle
•
Mar 9
OpenID != Open ID Connect?
Just learning about authentication, OAuth, and OpenID Connect and purchased your book!
Thanks! OpenID Connect is actually OAuth 2 plus an identity layer, and has nothing to do with OpenID 1. While useful, OIDC doesn't solve the same bring-your-own-identity goals that OpenID 1 did. -
My shareholders really don't like the idea of me speaking at @CollisionHQ without any travel expenses or compensation. https://kmikeym.com/questions/133
-
Add method to remove entries from a channel
Users may want to remove an entry from a channel for various reasons. Since #4 tracking read state means we now have referenceable entry IDs, we can use those to also remove entries from a channel.continue reading... -
Aaron Parecki
https://aaronparecki.com/
•
Mar 7
End of an era. StackOverflow is dropping support for OpenID. https://meta.stackexchange.com/questions/307647/support-for-openid-ends-on-july-1-2018
In related news, indieauth.com usage is steadily growing. However the vast majority of that is people logging in to StackExchange since it was one of the last remaining OpenID consumers 😂
-
End of an era. StackOverflow is dropping support for OpenID. https://meta.stackexchange.com/questions/307647/support-for-openid-ends-on-july-1-2018
-
Aperture consumes the
u-photoproperty on posts. All 3 current Microsub clients (Monocle, Together, and Indigenous) also consume the property to display photos in the reader interfaces. -
jameysharp
https://github.com/jameysharp
•
Mar 6
I'm writing an essay on what technology is missing for decentralized publishing of serial content (webcomics, fanfiction, podcasts, etc) and read-state synchronization is one of my topics. I'm hoping Microsub can be one good answer in that context.
For the kinds of serials that have ongoing plot/continuity, it's worth noting that
- entry order matters, and
- creators sometimes add or remove entries arbitrarily far back in the archive.
As a result, individual entry read-marks matter here because you'd like to know that there's something new even though it comes before entries you've already read.
Also: old entries can be edited. You may want to know that you read an older version of the entry so you can decide whether you care to read the updates, so I'd like to keep track of what the last-modified timestamp was for the version of the entry that you read. Note that this is not the same as the timestamp when you read the entry, because you might be racing with the publisher's updates.
I could picture it also being useful to record the timestamp when you read each entry for some kind of data analysis later—for example, predicting which feeds you like best, or clustering feeds that you like to read in close proximity to each other. But I don't think that's important for a first version of this spec.
Interesting use case!
I feel like it's worth pointing out that the spec only needs to describe as much as is required for interop between clients and servers, and servers are free to do as many additional fancy things as they want.
I could picture it also being useful to record the timestamp when you read each entry for some kind of data analysis later
Sounds like it might not hurt to also have the client send a timestamp of when the item was marked read, in case the client is syncing a bunch of these read-marks after being offline. Of course servers are free to ignore that if they don't support tracking the timestamp of reads.
creators sometimes add or remove entries arbitrarily far back in the archive
Issue #24 could help in this case, being able to retrieve only the unread items in a timeline.
-
Provide an option to return only unread entries in a timeline
By default, a call to retrieve the timeline will still return already-read entries. However, in certain cases, such as if there are lots of unread entries and you start reading them from newest to oldest, or if somehow an entry was added far back in the timeline, you might want to see only the unread items.continue reading...
