#@timoniHm. As I debate replying to one of my tweets with another just to make a digital connection, I realize I’ve started to use Twitter as a public memex. Other than actually building one (@TrevorFSmith) have folks tried this? Probably you, @t? (twitter.com/_/status/1000928081215868928)
#Loqi[kartikprabhu] Here are the proposed changes to the spec to account for `alt` attribute.
Add a new section 1.5 with title "parse an `img` element for `src` and `alt`" with the steps
- if `img[alt]`
- return a new `{}` structure with
- `value`: the `src`...
loicm and tantek_ joined the channel
#tantek_eddiehinkle's idea for embedding subscriber specific links in an email version of your posts makes a lot of sense - wondering if that idea is documented anywhere
#tantek_and even just the MailChimp feature of RSS to email
#LoqiIt looks like we don't have a page for "RSS to email" yet. Would you like to create it? (Or just say "RSS to email is ____", a sentence describing the term)
gRegorLove, cweiske, AngeloGladding and maingo joined the channel; mblaney left the channel
#[jgmac1106]If you get a chance can you note it here: https://github.com/jgmac1106/wp-dimension/issues want to get it set before the PR, have'nt decided how to handle all the h-entries on the same single page but like you said will jsut mark it up correctly and nopt worry about parser behaivor
#sknebel[jgmac1106]: you probably meant me. you have the u-urls on the wrong element, they have to be on the <a> tag with the link, not on an element around it
#[jgmac1106]and oops it was @sknebel who looked at it, have no idea why I think you two are the same person
#LoqiA token is an identifier that apps use to authenticate between each other and sites; IndieWeb software often uses an access_token obtained via IndieAuth https://indieweb.org/token
#LoqiIt looks like we don't have a page for "expiring token" yet. Would you like to create it? (Or just say "expiring token is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "scheuled token" yet. Would you like to create it? (Or just say "scheuled token is ____", a sentence describing the term)
#ZegnatI am not sure if those terms are actually in use else where...
#ZegnatBut let me define them how I was thinking about them
#ZegnatAn expiring token is a [[token]], probably an [[access token]], that automatically expires after certain use or after a specified amount of time
#LoqiIt looks like we don't have a page for "scheduled token" yet. Would you like to create it? (Or just say "scheduled token is ____", a sentence describing the term)
#ZegnatA scheduled token is a [[token]], probably an [[access token]], that is only active between two specific points in time.
#ZegnatI meant that I think these things are existing systems that must have a name. But the names “expiring token” and “scheduled token” are names that I just came up with in context.
#snarfedschedule/expiring tokens are fine, but seem kind of orthogonal to future vs present post date
#ZegnatSo might turn out somebody swoops in and tells me they have a specific name established in some RFC later
#snarfedseems like if you really want to control token lifetime, you do that in the context of your session with the client app, not per post
#tantek_expiring token << Use-case: if you want to give a 3rd party site or service a token to post on your behalf but not worry about that site holding onto the token longer than they should, or using it more often than you want them to.
#Loqiok, I added "Use-case: if you want to give a 3rd party site or service a token to post on your behalf but not worry about that site holding onto the token longer than they should, or using it more often than you want them to." to a brand new "See Also" section of /expiring_tokenhttps://indieweb.org/wiki/index.php?diff=48038&oldid=48036
#loqi.meedited /expiring_token (+232) "tantek_ added "Use-case: if you want to give a 3rd party site or service a token to post on your behalf but not worry about that site holding onto the token longer than they should, or using it more often than you want them to." to "See Also"" (view diff)
#Zegnattantek pretty much summed up the usecase, e.g. with Futurepub, that would want to make me use them
AngeloGladding joined the channel
#tantek_scheduled token << Use-case: if you are using a 3rd party [[scheduling]] service like [[Futurepub]], you may want to give it a token that only works during when you expect that service to post on your behalf in the future, so you don't have to worry about the service using it too soon, or holding onto it.
#Loqiok, I added "Use-case: if you are using a 3rd party [[scheduling]] service like [[Futurepub]], you may want to give it a token that only works during when you expect that service to post on your behalf in the future, so you don't have to worry about the service using it too soon, or holding onto it." to a brand new "See Also" section of /scheduled_tokenhttps://indieweb.org/wiki/index.php?diff=48039&oldid=48037
#loqi.meedited /scheduled_token (+307) "tantek_ added "Use-case: if you are using a 3rd party [[scheduling]] service like [[Futurepub]], you may want to give it a token that only works during when you expect that service to post on your behalf in the future, so you don't have to worry about..." (view diff)
#ZegnatIf the token is only good for one post (auto expiring afterwards), I would feel a lot safer handing it to Futurepub. If it leaks, the worst that can happen is 1 spam post being created and my scheduled post neve being posted.
#tantek_Zegnat, if you like, you can edit those pages to move those Use-case: statements into a new "Why" subsection on each
#ZegnatOr, to give it a better chance of only being used by Futurepub, for the token to only be valid around the time I expect the post to be made. Say ±5 minutes from my scheduled post date.
#tantek_It's quite a clever improvement to the problem of trusting 3rd party services, or rather, of reducing how much you have to trust to them in order to use them
#Loqizegnat has 66 karma in this channel (220 overall)
#ZegnatSo, snarfed, I am thinking of it in connection with “giving a token to Futurepub”, not really “using separate tokens for each post”, if that makes sense?
#Zegnat(Futurepub just as an example, as it is the first Micropub proxy I have seen.)
#tantek_Zegnat, Silo.pub is a Micropub proxy of sorts
#LoqiIt looks like we don't have a page for "Micropub proy" yet. Would you like to create it? (Or just say "Micropub proy is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "Micropub proxy" yet. Would you like to create it? (Or just say "Micropub proxy is ____", a sentence describing the term)
#tantek_Micropub proxy is a service that acts as Micropub server to receive Micropub requests, then passes those requests onto another service to handle the actual publishing. Examples: [[silo.pub]], [[Futurepub]]
#skippysomeone, somewhere, has to manage all this stuff. if i'm doing it for myself, i have skin in the game. if i hand it all off to someone else, how is that not a different kind of silo reliance?
#snarfedthe "how much do i have to self host to be indie" question is *very* well worn here, and captured in at least a few places on the wiki
#snarfedconsistently the answer has been, you don't have to self host *anything* to be indie, you just have to own your own domain
#aaronpkthe important part is that you *can* self-host if you want
#skippyit's not a matter of "how much makes me indie" but "eventually the guy who hosts the stuff on which i rely will get bored and stop hosting that stuff" leaving me in a lurch
#aaronpkas in, we need to make sure the systems and protocols we design both don't require you to self-host, but also don't prevent it
#snarfedif we had to do everything ourselves, we'd all live in shacks, growing potatoes and roots and breaking our back harvesting them, and die at 35 of rickets or scurvy
#snarfedat this point in my life, increasing my personal sysadmin tax directly reduces my quality of life and overall happiness, and i'm pretty tolerant. it's absolutely a non starter for gen 3/4
#aaronpkand we need to make sure we have the ability to swap out the infrastructure for something else without losing all our data and connections
#aaronpkit's not about self-hosting or not self-hosting
#skippyi dont give a wet slap about meeting some collective definition of "generations" or "indiemark" or anything. I do care about not relying on some service that next month becomes abandoned.
#snarfedright! also choosing vendors carefully, paying instead of using free services
#snarfedright. no matter how much you do yourself, you won't do some things - datacenter, network, OS, etc - and those will change too. you need to be able to handle that ok
#skippyManton could eventually stop doing micro.blog. brid.gy could go away tomorrow for any number of reasons. quill could shut down, and micropublish.net too; and tokens.indieauth.com.
#skippyso yes, i understand the sysadmin tax. I am a sysadmin by day, all day.
#snarfed...and your OS, and your hardware vendor, and your datacenter. nothing is forever
#[cleverdevil]This is one of the main reasons I am working on serverless solutions now.
#skippythe build/buy debate is ancient, and on-going. it's a spectrum, and different poeple have different motivations for where they live on that spectrum.
#petermolnarthis is the reason why I run my own server - fascinating to see the different reactions to the same problem :)
#skippyironically, there are so many servers involved in any "serverless" solution. :) Amazon pays armies of human beings do manage them.
#aaronpkskippy: again this is what i was saying about it's not a build vs buy or self-host vs not-self-host question
#aaronpkfacebook is not a problem because you can't self-host facebook. it's a problem because there's no interoperability with other tools and no portability
#snarfedwater services is an awesome analogy btw. absolutely essential, but i expect very few of us are on well water, and none of us run our own public water utility :P
#LoqiCall for Presentations
The 2018 Ohio LinuxFest is looking for presentations on Friday and Saturday, October 12 and 13, 2018 at the Hyatt Regency Columbus. Please submit your talk proposals by the deadline of July 31, 2018 to make sure you’ll be con...
#tantek_aaronpk, I haven't heard back either. I'm assuming if you have (bought) a ticket, you're in, and whether or not you get to speak is up to time limits
#LoqiIt looks like we don't have a page for "IWC Nurnberg" yet. Would you like to create it?_ (Or just say "IWC Nurnberg is ____", a sentence describing the term)
#aaronpkfor all I know, the Facebook AI is organizing that event as an attempt to consolidate all humans working on decentralized networking things into one place to take them all out </dystopia>