Just created a Lambda function that looks at my website's On This Day page, and publishes the memories to a special channel in my Microsub server. #IndieWeb #OwnYourMemories
WeChat ID
aaronpk_tv
-
This episode marks a full year that I’ve been creating weekly audio summaries of the IndieWeb newsletter! Thank you for listening!
I’d love any feedback that you have. Also, if you’d take a moment to leave a rating and a review wherever you get your podcasts, that’d be 💯!
-
Streaming API
Clients should have a way to tap in to some sort of streaming API to get updates from the server in realtime.continue reading... -
Tickets are STILL AVAILABLE for the Portland show on 3/30 and Seattle show on 4/1! I requested that the venues not advertise these shows until the end of the day so that my fans can have first dibs! #CrazyExGirlfriend
-
I don't like running things in Docker so I won't be tackling this, but I'm open to accepting a PR if someone puts it together. -
Zegnat
https://github.com/Zegnat
•
Feb 16
It doesn’t return the Microformats JSON, it converts it to its jf2 format first.
It might be worth opening an issue on jf2 to see if they want to keep an explicit
nameproperty. Their “author” syntax says it “consists of a name” and more, but that’s not marked as a MUST. For a jf2feed on the other handnameis a SHOULD.The real question is, do you see any reasons for postponing this change because of your use of a mf2 parser as a service? I think not?
Nope, wasn't intending to hold things up, just wanted to put that there for the record.
I agree with the current proposal of having
p-*ande-*andh-*stop the implied name. -
Zegnat
https://github.com/Zegnat
•
Feb 16
Documenting from yesterday’s chat, because nobody could remember this and I can’t find it elsewhere:
- @tantek would like to keep parser changes conservative but is “amenable to expanding to any p- or e- = no implied p-name”.
- I have not been able to document any cases where more than this is necessary either.
So I think the (as of now) latest proposed spec change would be:
p-nameMUST NOT be implied if there are any explicitp-*ore-*properties, or any nested microformats.
Currently all mf2 items have a name property, because of implied name. If we change this, some code using the parsers could fail if it assumes a name is present.
Here too I will just document an answer given in chat, this time by @aaronpk:
may just mean it has to be released as a major version number [of the parsers]
Assuming something like semver is being used, any major version bump should signify possible API changes to the user. I too don’t think that would be an issue.
There might be an issue if someone is using parsers-as-a-service, e.g. always getting their mf2 parser output from
php.microformats.io. But I don’t think anyone ever advertised their online parsers as a service?
I (and likely others) use xray.p3k.io as a service, so I will have to consider what to do in that case. It doesn't return the Microformats JSON, it converts it to its jf2 format first. I may just return an empty string for
nameif there is no mf2nameproperty. -
A lot of progress is happening on the Together project. Its shaping up to be an amazing Indie reader! New features include responsive design, read/unread tracking, "classic" view, and more. Great job, @grantcodes – https://cleverdevil.io/s/rbTFxamOAH.mp4
-
I just updated the text to hopefully be more explicit about this: https://indieweb.org/Microsub-spec#Set_Channel_Order
-
No, that's not what I meant.
Only the order of the channel IDs specified will be changed
In your example 1,
chas moved as well, even though onlydandbwere given.To move a channel up or down...
This is equivalent to swapping two adjacent items.
I didn't give an example of setting the order of three items because I couldn't think of a UI where it would make sense, but it is still possible.
The nice thing about this approach is that the same update logic works for all the use cases, and doesn't matter how many items are in the list, and is atomic.
-
at StreamPDXPortland, Oregon • Tue, February 13, 2018 5:48pm
-
grantcodes
https://github.com/grantcodes
•
Feb 13
Working on implementing this in together now, I'm sure there is a valid reason, but I'm just wondering why the
_idis different from the paging before and after values, could they not be the same?
The
beforeandaftervalues are meant to represent pages of data, not necessarily individual records. In my case, theaftervalue refers to an item that isn't in the current page. I could return a string for_idthat looks more like thebeforeandafterstrings, but that's just an implementation detail of my server. Alternately I may switch mybefore/afterstrings to look more like the current_idvalue. Either way, this difference doesn't seem important to the client. -
That would be an interesting feature that the microsub server could provide to clients. It does seem like this will always be a problem.
-
Channel icons?
I just added emoji in the channel names, and now I'm wondering if there should be a way to choose/upload an actual custom icon for channels.continue reading... -
Aaron Parecki
https://aaronparecki.com/
•
Feb 12
I'm implementing a draft of this in Aperture right now. Here is the current API...
I should add that the `_id` values are meant to be an identifier for this instance of the entry in the channel, not an identifier for the entry across channels. This means if you're following the same feed in multiple channels, entries may have a different `_id`. -
EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 12
Not that it has to be implemented right now, but I do want to make a case for the “updated” field of a channel. In order to reduce “high noise signal”, for most of my channels, I’ll want the channel’s “unread indicator” to disappear when I reach the top of the timeline (even if things are unread). When a channel is updated (receives new posts), I would want to be able to re-enable the unread indicator. Essentially saying “there are new posts here” rather than saying “there are unread posts here”. In fact now that I say it, I might make the indicator a different color as well. That said, the purpose of such a channel is, I want to be able to know what I have and haven’t read, while only being prompted to open the channel if there are new posts. The “new posts” indicator essentially upping the priority of time looking at that channel than one without new posts. That said, when I have more time, to be able to go back to an existing channel and still know what I haven’t read (which is why this can’t just use the “last_read_entry”, even though that is a useful method).
(Originally published at: https://eddiehinkle.com/2018/02/12/7/reply/)
Here's a question. Do you imagine this additional state being something that only individual clients are aware of, or should that be synced to the server as well?
If the server returns the "updated" date, then the client has enough information to show the indicator itself. But as far as other clients are concerned, they wouldn't know about whether you've seen those posts in another client.
I'm kind of leaning towards it being a client-only thing, at least for now.
If that's going to end up getting pushed to the server then I think we need to better define the different kinds of states. Maybe "read" vs "seen", where "seen" is the soft indicator that the client has displayed the post to the user, and "read" means they've opened it up (or maybe even explicitly marked it as read). -
Add option to remove entries when unfollowing a source
When removing a source from a channel, Aperture provides an option in the UI to either remove all the existing entries or just stop adding new entries. It may be useful for this to be an option for Microsub clients as well.continue reading...
