#[Rose]1Me! I use Zapier to auto post things to Twitter and LinkedIn in specific formats.
#GWG[Rose]1: It's the reasoning people use to make that decision I am curious to hear a broader set of opinions on. So, for example, how do you decide what automatically posts to LinkedIn, or is it everything?
#GWGI may want to add some notes on this to /POSSE
#[Rose]1Only blog posts and podcasts post to LinkedIn for me.
jgmac1106 joined the channel
#[Rose]1So I do it based on post category for those. Kind dictates what goes to twitter though.
[davidmead] and [jgmac1106] joined the channel
#[jgmac1106]reply contexts get hard, I would like buttons or radials to decide on per post level, but also be able to decide what is checked by default
[grantcodes] joined the channel
#[grantcodes]Always auto posse with a bit of intelligence. Twitter always, Instagram + twitter if it's an image, replies / likes only if they are to the specific silo
KartikPrabhu joined the channel
#sknebelnot sure if that integrates well, but maybe this would be something where a hook for custom code is a good starting point, and then see after a while which options community members have implemented, and then polish those as full features, if you aren't sure what's good options right now
#@NmVAsonPSA: TIS THE SEASON TO CHECK YOUR FORMATTERS, PEOPLE TIL that Java's DateTimeFormatter pattern "YYYY" gives you the week-based-year, (by default, ISO-8601 standard) the year of the Thursday of that week. 12/29/2019 formats to 2019 12/30/2019 formats to 2020 (twitter.com/_/status/1207820284268597249)
#@bradenslenThis is cool. With https://b2evolution.net/ as a blog script you get as many blogs as you want with webmentions on one install. As a CMS you get the mentioned blogs, plus photo gallery, forums, a manual publisher and a group projects tracker in one install. (twitter.com/_/status/1208047894663700480)
#[tantek]GWG, did you find any documentation on automatic POSSE? I think most of it assumes automatic POSSE, and "manual POSSE" is the exception that is called out
chrisaldrich joined the channel
#GWG[tantek]: So far, didn't see any discussion of it on the wiki...so I may be searching the wrong term
#[tantek]bad UI to make it extra steps, bad UI to give lots of extra checkboxes that a user has to waste time reading and understanding before they can take their action
#GWG[tantek]: That's why I want to improve mine now that I added another one
#[tantek]good design makes choices that benefit the user and the user's intentions
#aaronpkI like being able to choose whether/where to POSSE my posts
#GWGWhy does Micropub not have a setting to check by default?
#[tantek]"lots of checkboxes" is one reason why people call things "complicated"
#[tantek]aaronpk, I understand your personal preference, but I think folks (GWG) are assuming that's good UI design in general, which frankly, it's not
[schmarty] joined the channel
#[schmarty]haha i'll wrinkle this up a bit and say i would like the option to put a syndication link on a post when i create it on my site 😂
#aaronpkhowever if i'm replying to something on twitter, then I always want that to POSSE to twitter and it would be annoying if I had to check that button
#[tantek]it's good for your preferences, but not for users in general who are actively *hurt* by each additional step and option
#[schmarty]sometimes i have already posted it to whatever silo and am manually re-creating the post on my site
#[tantek][schmarty] that sounds like a backend issue that the backend should intelligently handle, not something to burden the user with posts-vs-POSSE-accounting to keep them balanced
#GWGBut I am asking why the endpoint can't say check by default
#Loqimanualuntilithurts has 3 karma over the last year
#[schmarty](i don't have time to build "check my twitter to see if this new content matches my latest tweets" into my site)
#[tantek]GWG, right, this is why people use IFTTT, they set it up to automate something and then just let it run. it doesn't bother them with checkboxes every time
#[tantek][schmarty] that's fine to admit it's patching over a backend weakness, rather than actually intentional UI design
#[schmarty]i don't concede that it's a backend weakness. who wrote that into my requirements document? 😂
#[tantek]I mean you did in your statement "sometimes i have ..."
#[schmarty]tantek: i don't follow your reading. i described a situation where i have posted something on a silo and want to copy it to my site with a syndication link. my micropub endpoint would happily accept a post like that, but i am not aware of any clients that will construct that post.
#chrisaldrichI'll stay away from the larger plumbing questions/issues, but I will say that the way Known implements syndication buttons for silos is much more elegant UI than checkboxes.
#aaronpkthe micropub endpoint tells the client which syndication options to show to the user. he's talking about adding a property that tells the client to enable an option by default
#GWGIf the Micropub endpoint wants to handle syndication entirely, it would show no targets and just posse itself
#chrisaldrichQuill is a solid experience too, though it might be better on desktop if they were horizontal buttons (to take up less screen space/scrolling) instead of vertical (which is a better experience on mobile).
#LoqiFoursquare is a venue reviews, recommendations, and lists silo based on its previous location-based checkin support, a feature that was spunout to the separate Swarm application which still shares some data back & forth with Foursquare https://indieweb.org/Foursquare
#chrisaldrich[tantek] I'd looked and it was all checkins related (from before Foursquare pivoted to Swarm branding)
#[tantek]GWG, this is one of the big challenges of good UI design
#[tantek]if you ask people if they want lots of options, they say YES
#GWG[tantek]: Yes, but I refuse to do checked by default for posse without more intelligence as to post type
#[tantek]however if you actually *user test* people with simple UIs with fewer options, vs more complex UIs with lots of checkboxes etc., and measure *did they get the task done* and *did they feel good about it*, the simpler UIs with fewer options always win (as in overwhelming majority of users)
#[tantek]so saying "different people have different preferences" avoids doing the hard work of what preferences actually make sense to just decide on by default and implement that first
[davidmead] joined the channel
#[davidmead]Chiming in quick (as I have UX i my title) - beware sing buttons, especially lots of them, as this can be confusing for users. buttons are usually only one or two and mean an action, like submit.
#[davidmead]expectation is usually “i push/click this and I’m done”
#aaronpkI like the toggle switch control that known and adactio use for that reason
#chrisaldrichAlso in thinking about a broader IndieWeb future, there's a liklihood that there are more syndication targets (like IndieNews or IndieWeb.xyz), which means many more toggles over time.
#[davidmead]asking a user if they “always want to send posts to…” when they toggle can be a good way to change preferences with them having to think about it and hunt around for it in the settings
#[tantek]and they're sticky too, that is the toggled state sticks across checkins
[asuh] joined the channel
#aaronpkinterestingly swarm's syndication buttons are nearly the same as the "cancel"/"check in" buttons below. they're just circular instead of ovals
#chrisaldrichI like the idea of having a sticky toggled state, but GWG is also dealing with a dozen or more post types (notes, likes, replies, etc) and far more targets which complicates the plumbing and choices combinatorially.
#chrisaldrichSwarm has the benefit of being a checkin unitasker with only a couple of syndication targets. That level of simplicity makes the UI an easier thing on both sides of the dev/user equation.
#chrisaldrichAn example closer to what he's talking about is the massive plumbing involved in setting up /SNAP, which couldn't have been fun to code, isn't fun to configure as a user, and even when done well isn't much fun to use on a day to day basis.
#[tantek][chrisaldrich] I feel like you just described the average/typical WordPress Plugin UX
#chrisaldrich[tantek] It's not far off, but I'll also note that /SNAP is one of the most massive and ugly ones that I've seen, particularly if you're attempting to syndicate to more than one target.
#[tantek](from having observed many WordPress users struggling with many WordPress Plugins, both in setup/config, and in use)
#chrisaldrichNot far behind that are some of the big SEO plugins, which might also make some good UI case studies.
#[schmarty]aaronpk's talk about home automation with NodeRED has me thinking about visual flowchart-like tools for POSSE/PESOS
#[schmarty]bridgy publish is the only service that needs to be bridgy publish :}
#chrisaldrichGWG, another way of looking at the solution is to offload some of these decisions to the UI that micropub clients want to build in or support. Just provide the minimal basics in WP or your platform of choice and let the variety of micropub apps sort out what users may or may not want?