@matigo Ah. I like the Client info for a way for people to discover clients, of course. ;)
I noticed that the account info embedded in posts looks slimmer now. Makes sense.
@matigo Ah. I like the Client info for a way for people to discover clients, of course. ;)
I noticed that the account info embedded in posts looks slimmer now. Makes sense.
@matigo See, those are the sort of edge cases I can’t predict.
How would elsewhere-posts (YouTube/T) even wind up in Global?
How does someone reply to a blog post? (I see them in Nice, so probably I can figure this one out on my own - it’s not uncommon.)
@joanna Macchiato is recovering from the cutover. Loading older posts in a stream is definitely on the list of things to make work again there.
@matigo In general I have a lot of questions about how federation plays into things. If that’s indeed where the “get channel guid from homepage meta” and such are heading. Is that still embryonic, or are there do’s and don’ts for clients in order to play nice with federation when The Open Sourcing arrives?
@matigo In terms of docs, an “example zoo” would be hugely useful. I bet there are edge cases around post visibility or expiry that I’m not handling, because they are rarely encountered.
@matigo Is client information intentionally absent from the logged-out stream’s posts? That and channel being gone surprised me. (Missing the attributes, not so much, since those all take a logged-in user to set.)
@matigo I saw that. It looks like to get the replied-to post ID, you’d need to yank it out of the reply_to URL?
@matigo This one took some squinting to catch:
// (2019-04-12)!!!: Likely bug: "Post.mentions" can be an object, not an array, when there's just one
I try parsing as both array of mentions and single mention object now. If it ever gets fixed, the fallback single-object attempt will be redundant, but it won't break anything.
@phoneboy Yeah, I'm not expecting the posting to be too bad. I'm probably over the hump. There was a good bit of change from v4 to v5 in the post/account/etc data needed to understand the stream.
Huh, my image attachment didn't show up.
ETA: Oh, because the file upload returned an error. :\ That the UI didn't show me. Out of space in a bucket, maybe?
\"errors\":[{\"name\":\"Behold 10Cv5 Global - Simulator Screen Shot - iPhone X - 2019-04-12 at 23.31.57.png\",\"size\":900917,\"type\":\"image\\/png\",\"reason\":\"Could Not Record File Data\"}