#GWGIt's a redesign of my Post UI. The last major one before the hammer falls. According to stats, the code has over 200 active installations. I always worry about, even though I'm doing it to improve my experience, that I'll get one of them upset
#[markmhendrickso@GWG Cool, if you want a second set of eyes, I'd be happy to give you my design feedback
leg joined the channel
#GWGI'm the WordPress person in the community, so this is inside WordPress. You are welcome to look though
#Loqi[dshanske] indieweb-post-kinds: adds support for responding to and interacting with other sites using the standards developed by IndieWebCamp
leg and tantek joined the channel
#[markmhendricksoI see under screenshots how the post appears to look now, for at least a like and video: https://github.com/dshanske/indieweb-post-kinds#screenshots. Is it this user-facing UI that you're redesigning, and if so, with what objectives?
#Loqi[dshanske] indieweb-post-kinds: adds support for responding to and interacting with other sites using the standards developed by the Indieweb Community
#[eddie][cleverdevil] thinking about the “Read Later” functionality. Initially I thought when using a desktop I could do something like add the Microsub Saved channel’s Micropub endpoint and token to Omnibear or some other Micropub client.
#[eddie]But I realized that would require the client to make the post be the existing page, not a “repost” or a “like”
#[eddie]That way when not using an iOS device you could essentially have a bookmarklet that will feed the current url into the system and then Indigenous’ server can parse the page you selected (if possible) and save the post into The Microsub channel
#Loqitantek: snarfed left you a message 22 hours, 52 minutes ago: thanks for the nudge on bridgy's github auth prompt. i was reluctant because i didn't want to move the repo, but realized i could just use the org for the app. prompt now says "Authorize bridgy"! https://snarfed.org/github_bridgy_org_auth.png
#Zegnat[eddie], what about using /repost for the read later? Not sure if any Micropub clients support it, but I could see a client parsing the current page to extract the main content and posting that to an endpoint as a repost.
jackjamieson, jjuran and tantek joined the channel
#Loqisnarfed: tantek left you a message 1 hour, 29 minutes ago: should I file separate (new) issues for handling img and hyperlink (a href) tags for Bridgy Publish to GitHub?
#tantek(if so I'd expect an explicit whitelist of which reacji as emoji since GH only supports a few)
#snarfedit's actually a minor interesting UX question. if a user intends to post a reaction, but typos it, a naive implementation will post it as a comment instead of returning an error. maybe that's ok? not sure what the right UX is.
#tantekI'd say a little bit of forgiveness, with a bit of future extensibility
#tantekon the forgiveness side, if someone doesn't get the exact right emoji, but it's close enough in meaning, then translate it. e.g. any of the heart emojis should probably work as a "heart"
#tantekany of the laughing emojis for laugh, etc. since GitHub gives them text meanings (on hover), that's probably sufficient guidance
#tantekbut for any other emoji, perhaps an error saying GH only supports ( insert list ) reactions currently, instead of posting a single-emoji comment
#LoqiHammerspoon is a tool for powerful automation of macOS that lets users perform actions using Lua scripts, including deep integration with the operating system https://indieweb.org/Hammerspoon
#[eddie]!tell Zegnat: my concern about using repost for “save later”. Most existing Micropub clients are just going to send the url under repost-of. But then Aperture doesn’t currently parse extra urls in posts. So my “save later” feed would end up with the repost url but no content (no title, content, etc) from the initial page I wanted to read later
#[eddie]So I would either have to build a Micropub client that would parse the page and put an embedded h-entry into repost-of. Which would be more time consuming than a web service that can do essentially that with a bookmarklet
AngeloGladding and [cleverdevil] joined the channel
#[eddie]I definitely want to get there. I’m also just thinking about like my work computer. I can’t install a Mac app on my work computer. But a bookmarklet would allow me to save stuff to read later
#[eddie]I think for your primary iOS and Mac the share sheet is definitely the way to go
#[eddie]But one thing I love about Instapaper is that I can get data in there 100 different ways
#[eddie]And my goal is to insta-quit-paper this year
#tantekthis is implications for Known: "Do not (and do not allow your users to) simultaneously post identical or substantially similar content to multiple accounts." - and perhaps any UI (Quill?) that allows you to check multiple POSSE destinations that are on the same silo
#tantek"Users of TweetDeck will no longer be able to select multiple accounts through which to perform an action such as Tweeting, Retweeting, liking, or following."
#[miklb]tantek, my argument is, anyone who has set up multiple Twitter accounts and signed up for an API key isn’t accidentally doing anything if they are blasting the same content to all the accounts at the same time. I’m sure I’m wrong, but I doubt they are going to go after someone with 2 accounts for some reason though. They are looking to crack down on heavy automation to a lot of accounts at once.
#tantekit's too easy for a user to accidentally check two checkboxes when they meant to switch from one to another
#[miklb]so yeah, I’d love to read a blog post on how posting the same content at the same time to multiple Twitter accounts is somehow good and related to indieweb because I’m from the other camp. 🙂
#aaronpki dont think there is a reason to *post* to multiple twitter accounts, but I have favorited or RT'd content from multiple twitter accounts which i feel okay about
#aaronpklike when i post somethinbg about indieauth from my @aaronpk account and then retweet it from @indie_auth and @oauth_2
#Loqi[tantek] also this: "Do not (and do not allow your users to) simultaneously perform actions such as Likes, Retweets, or follows from multiple accounts."
#[kevinmarks]“As an alternative to posting identical content, you can Retweet content from one account from the other accounts you wish to share that post from. This should only be done from a small number of distinct accounts that you directly control.”
#[kevinmarks]So I think the indieweb retweet mechanism is OK.
#tantekand the very next sentence: "Please note that bulk, aggressive, or very high-volume automated Retweeting is not permitted under the Automation Rules, and may be subject to enforcement actions."
#tantekwhich seems to align with [miklb]'s suspicions that "a few accounts" is likely ok
#[miklb]sounds like a fair trade off to me. I’m a small social media manager for a brand & have manage 8 Twitter accounts. I can post an original tweet on one and automate the other 7 as RTs. But I can’t connect 100s of accounts and bulk RT
#KartikPrabhuis this some misguided action to control fake/bot accounts?
#tantekI wonder if they already have the tools, and are identifying abusers already, or if they're giving themselves until March 23, 2018 to build and ready their tools
#aaronpkyeah it sounds like they're okay with small numbers of RTs from brand accounts is fine
#tantekfor duplicate posting / liking / retweeting that is
#tantekKartikPrabhu: to be clear " to have multple accounts and post from them" is fine for manual work, though duplicate content is still discouraged
#tantekand my use-case is different content for each of those accounts
#[miklb]yes, definitely I’d like to clarify that having multiple accounts act independently I don’t think should be an issue. It is once you start automating all of the activity that I do not have issues with rules on duplication
#tantekbut I'm really wondering if Twitter is readying all their tools to drop the hammer hard on March 23
#LoqiIt looks like we don't have a page for "Kuberbetes" yet. Would you like to create it? (Or just say "Kuberbetes is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "container" yet. Would you like to create it? (Or just say "container is ____", a sentence describing the term)