ben_thatmustbeme!tell aaronpk, kylewm we were so overthinking noting that a post was already liked by a user. It won't be up to the minute, but the post itself would "ideally" display the like, when its pulled in you would have that info
Loqikylewm_: ben_thatmustbeme left you a message 25 minutes ago: we were so overthinking noting that a post was already liked by a user. It won't be up to the minute, but the post itself would "ideally" display the like, when its pulled in you would have that info
Loqiaaronpk: ben_thatmustbeme left you a message 2 hours, 46 minutes ago: we were so overthinking noting that a post was already liked by a user. It won't be up to the minute, but the post itself would "ideally" display the like, when its pulled in you would have that info
cweisketantek, could we talk about the phorkie problem of yesterday a bit? my problem is that there are two use cases (working with the paste vs. embedding the paste) which require different information (working requires edit buttons, while embedding does not. embedding requires a style sheet that's as standalone as possible, the normal phorkie display does not). should this all be expressed in the same HTML code?
Loqiwillnorris: snarfed left you a message 3 weeks, 6 days ago: hi! quick question: bridgy is hitting the G+ API daily courtesy quota, and i'd like to request a bump, but i'm a bit scared to bring any attention to it. do you have any feeling for whether the G+ team would be ok with bridgy, or whether they'd ban hammer it? (i'll ask other friends there too, but you have the most direct experience. :P details: https://github.com/snarfed/bridgy/issues/22 )
willnorrisheâ€™s about 15 hours old, and already has level 6 security on http://indiewebcamp.com/https :) A little ways to go on indiemark, since he canâ€™t easily do indieauth without any profiles anywhere
ben_thatmustbemewell, i suppose there could be "user has not liked the post but it is displaying on the post" if a like was deleted, but i think for the current implementation we are leaving out removing likes
tantek"liked" - a reader for example can know that you *have* liked something, via its own cache, or a post claiming you've liked something, with a link to the permalink of your like post (verifiability of a like)
tantekif you retweet something, then click the colored in retweet button, it gives you the option to unretweet (confirm), which deletes the retweet post from your timeline, and resets the button to gray.
tantekthough the comparison to twitter is a good one, as wherever you display an embedded tweet, assuming you load/run Twitter's JS, the embedded tweet shows the webaction buttons in a state reflecting what the (logged in) user has done with them.
tantekwhether on their post permalink page, or when embedded inside another site (in a quote, in a reader etc.), if they have webactions buttons, those buttons should reflect the user's interaction if any with the post.
tantekBTW - ben_thatmustbeme - what NOT to do if the user clicks a fully red/gold heart/star - display an error like "You are not allowed to do that." or "An error occured" and "Try reloading the page". (i.e. what Twitter does if you try to favorite something that's already favorited)
snarfed!tell tantek,aaronpk just fyi, bridgy publish is now oauth protected (interactive) or requires backlink (webmention). i think that closes the outstanding security concern(s). let me know if you see any bugs!