[Ramiro_Ruiz]I want a better way to run specific shortcuts than just have to wait netlify to deploy (30-45sec) to then run the last part of the shortcut. I’m out of ideas so maybe someone with a fresh perspective can help me to come up with a work around.
jjuran, dopplergange, chrisaldrich, gRegorLove, jacky and [Rose] joined the channel
[Rose]As in, when Netifly deploys have it also ping Pushcut (assuming that’s possible), and then you tap the pushcut notification on your device to run “part two”
sknebelhaha, reminds me a bit of ballistol, which is a German brand of paraffine oil (originally gun oil). They have products specifically for use on humans, on animals, and for technical purposes, but their basic product is "universal oil" which is recommended for use on all 3
beko[m]content with another party in this way, you may only share up to 50,000 hydrated public Tweet Objects and/or User Objects per recipient, per day, and should not make this data publicly available (for example, as an attachment to a blog post or in a public Github repository).` - what is hydrated anyway?
beko[m]til: TW want's tweets to be embedded and if not embedded at least styled in a very specific way https://developer.twitter.com/en/developer-terms/display-requirements.html - this kills any free design for backlinked responses. Uncertain to what extend `Redistribution of Twitter content` applies: `We permit limited redistribution of hydrated Twitter content via non-automated means. If you choose to share hydrated Twitter
[snarfed]...having said that, it's worth distinguishing between principle and practice here. in principle, you're both right. in practice, pretty much all indieweb personal sites are too small for twitter to notice or care about. eg bridgy and twitter-atom, maybe. your sites (and mine), probably not.
[snarfed](this comes from experience inside big silos and seeing how they actually manage and enforce these kinds of ToSes. others like [KevinMarks] and [tantek] can confirm)
[snarfed]on a related note, big publishers have struggled with this exact rule of twitter's for a long time when they want to include a tweet in an article. same "own your data" concerns we have. embeds may look nice, but they're brittle, dependent on twitter's servers, etc.
Loqihydrate is web developer jargon for the process of client-side JS taking over a DOM that was generated on the server, adding it to JS data structures, adding event handlers, … instead of generating page elements only on the client or entirely replacing those sent by the server https://indieweb.org/hydrate
[tantek]there's a fair use / citation exception that they can't really claim any control over, so IANAL IMO it's fairly ignorable as long as you act in good faith
[snarfed][jgmac1106] probably! with good reason. and many of them will be "big enough" that twitter notices them. one key difference may be that they're (probably) not using the API for that, and the terms we looked at are for API usage specifically.
[manton]I was curious about this so just confirmed that Twitter's embed is a blockquote + script tag. (I personally use blockquote manually when quoting anything, so that it looks consistent whether it's a blog post, tweet, news article, etc.)
[manton]By embedding a tweet with Twitter's script, it's kind of reinforcing that 280 characters of text is something special that only lives on Twitter's platform. End mini-rant.
[snarfed]yeah i expect both the terms and especially the enforcement differ somewhat between embedding individual tweets and using the API, since the latter is often larger scale
[fluffy]okay so: webmention.js is a quick single-file javascript library thing I implemented as a quick hack that other people started using, which is great
[fluffy][tantek] suggested I start actually providing version numbers for it, when in reality each “release” of it is just, hey, I checked in another quick fix to it
[snarfed]depends on what people need the version for, if at all. commit hash is one lightweight way people do this, eg in a query param for cache busting
aaronpkyeah i've been getting in the habit of semver tagging via github. the workflow is pretty minimal for it and has a bunch of perks built in like [snarfed] said
[snarfed]heh. expecting head to always be usable is reasonable for small projects, less so for bigger ones. nice goal, just not always realistic or doable.
[tantek]agreed. though my workflow makes it workable for CASSIS (I deploy versions to test them on my own site in production *before* checking them in to head on github)
[tantek]re: Twitter publishing guidelines thread btw, see /display-guidelines and feel free to add to it, especially concerns, issues, brainstorming etc.
[Ramiro_Ruiz] Anyone with advance iOS shortcut knowledge?
[tantek] design << Beware of meaningless consistency in design: https://twitter.com/jmspool/status/1193719439772078080
@jmspool The downsides of design systems. https://twitter.com/SharonG/status/1193660560526594048 (twitter.com/_/status/1193719439772078080)
Loqi ok, I added "Beware of meaningless consistency in design: https://twitter.com/jmspool/status/1193719439772078080" to the "See Also" section of /design https://indieweb.org/wiki/index.php?diff=66828&oldid=64471 
jeremycherfas I've done mine personal challenge for today. If I get enough paid work done, I might cheat and do tomorrow's.
beko[m] content with another party in this way, you may only share up to 50,000 hydrated public Tweet Objects and/or User Objects per recipient, per day, and should not make this data publicly available (for example, as an attachment to a blog post or in a public Github repository).` - what is hydrated anyway?
gRegorLove I feel like I still see publishers with tweet screenshots instead of embedding
[KevinMarks] Spa hydration? That sounds like something else
[jgmac1106] I have no hard data but I feel like most publishers and news orgs have been quoting rather than embedding tweets much more often.
