#tantekso if you take / post photos of similar things/events (group workouts, HWC meetups, etc.) then person-tagging gets more automated with each post
#tantekno need for any fancy/trendy machine-learning / AI hoo-haw
nitot joined the channel
#tantek3. implement receiving "tag-of" responses and incorporate them as person-tags, using the person-tagging features of silos that I POSSE the photos to as a UI instead, and then have Bridgy backfeed those person-tagging as synthetic tag-of responses.
#LoqiA fragmention is an extension to URL syntax that links and cites a phrase within a document by using a URL fragment consisting of the phrase itself, including whitespace https://indieweb.org/fragmention
#KevinMarksIt is tricky because of the tension between the selected text being long and coherent versus being just enough to identify that paragraph
#KartikPrabhubut the selected text can be coherent and across mulitple elements
#tantekKartikPrabhu: you can either <nowiki> it and document when it was noticed that the link died, or (more work) dig up an archive.org link to the last functional version
#ZegnatKartikPrabhu, so should a spec bug be filed before browser bugs? Or browser bugs before spec bug?
#KartikPrabhudon't ask me! I just filed my first bug report today!
#KartikPrabhuthese are times I get reminded that I'm not a "proper dev"
cuibonobo, friedcell and rrix joined the channel
#ZegnatKartikPrabhu: not a proper dev? Anyone who detects browser implementation differences and then writes succinct tests for them is a proper dev IMHO
#KartikPrabhuI guess, that does count for something! :)
#sknebelRegarding the fragmention examples, just for my understanding: the entire document is selected in the first example because it highlights the element that contains the entire selected text?
#sknebeland the document is the parent of the two <p>?
#KartikPrabhucweiske: but it does scale with browser zoom so...
#sknebelKartikPrabhu: sounds like for that case you'd want to highlight all the children of that nearest ancestor that contain parts of the selection instead?
#ZegnatIt's not really aboout highlighting though, more about where to put .focus()
#ZegnatAnd that's limited to a single element, by definition
#KartikPrabhusknebel: that is a valid expectation, please add to wiki
#KartikPrabhuZegnat: I don't think the fragmention.js script switches focus at the moment; but that also is a valid expectation, please document it on /fragmention
#KartikPrabhucweiske: what I meant was you could always change the scaling in your own browser
#KartikPrabhuthere is no real metric for how big a font size should be
#cweiskeoh. my browser lets me specify the default font size
#ZegnatWait, it does not put .focus()? I thought that was what it was for :o
#cweiskebut they seldom do, and most people don't know about that setting
#KartikPrabhuZegnat: fragmention.js does detect the element and put a special attribute "fragmention" on it, I suppose putting focus would be a good enhancement
#KartikPrabhucweiske: if CSS is used it should be respected by the brwoser settings no?
#ZegnatIs there a reference fragmention implementation? E.g. a repository for fragmention.js?
#KartikPrabhuor why not? what is incorrect about rem for font-size?
#ZegnatKartikPrabhu, thanks. So it does element.scrollIntoView(), but as soon as I were to start TABing around I go to the top of the page again because focus was not set to the element
#sknebelZegnat: can you even set focus on e.g. a <p>?
#KartikPrabhuwould really like feedback on this since I am trying to improve the UX of fragmentions in general
#Zegnatsknebel, in some browsers I believe you can. Or you can make it focusable. I am looking to see if I have the code left. Pretty certain I wrote something for it
#ZegnatKartikPrabhu: can't currently update the wiki or post to GitHub. Don't have my password vault on my work PC
#KartikPrabhuZegnat: anytime you are free would work. I think fragmentions is a great idea and so would like to see it tested and improved up on
#ZegnatI also wonder where screenreaders would expect to be dropped into the document. Probably on the nearest ancestor P. That's also something to think about, if you always grab just the nearest ancestor you might end up on a STRONG in the middle of a sentence. While I would expect to be put on the P, i.e. at the start of the sentence the selection fall
#KartikPrabhuonce it is documented on the wiki we can try to get the developer's eyes on it
#ZegnatSo if the nearest parent is of the category phrasing content (https://html.spec.whatwg.org/multipage/dom.html#phrasing-content-2) go up the tree to find the next parent. That would get you to LIs / Ps / etc. There are probably problems with that. (E.g. SPAN childs of BODY will focus BODY. So this only works if you use proper semantic sectioning ele
#KartikPrabhuZegnat: glad you know more about these "semantics" that I do
#ZegnatKartikPrabhu, I sometimes get a bit obsessive over specs. I don't often see people refer to element categories, which is too bad, because they can be very helpful in conversations like this one
#SebselHaving your own website is hard if you want to do all the things 'right' and by yourself
#petermolnarnah, there's got to be a WordPress plugin for that /s
#ZegnatThat's probably why people see a barrier to entry here. The real thing to understand is that there is no "right". Publishing HTML is all you need to do to do it right.
#petermolnarthat soon results in too many choices, too many technologies, what is trendy, what is lame, and some will just walk away instead
#Loqi[aaronpk] well you don't need microformats if you just want to publish something! you need microformats once you want someone/something else to consume it!...
#aaronpkpetermolnar: sebsel: I'd say just start simple. it's been surprisingly fun to build my new website by just writing plain HTML files, then slowly adding php includes, so that I focus on actually writing things instead of worrying about the tools https://w7apk.com
#aaronpkh-review is one of those funny ones where it actually shares most of the same properties as h-entry so maybe shouldn't have been its own top-level item, but came from a long history of microformats1 where it was a top-level item so here we are
#aaronpkit does have a little more semantic difference between h-entry compared to something like an h-entry with a photo, plus the name is catchy (as demonstrated by the surprising number of tweets about it still), so it's not too bad that it's a new object type
tantek, awolf and rrix joined the channel
#Loqi[indieweb] "Currently debating between #100DaysOfMusic or #100DaysOfIndieWeb for my #100Days project. #100DaysOfMusic - The goal..." on 2016-12-21
#aaronpkoh hey superfeedr is picking up my notes now
#bearyea, I need to stop posting - later I'll explain why hearing anything from some folks in the nodejs community sends me straight to rant/rage
nitot, ehlovader, snarfed1 and KartikPrabhu joined the channel
#petermolnaroffline first: I'm with bear on this. offline web apps is a waste in it's current state. ( os layer, gui layer, browser layer, web layer, and I'm wondering why my CPU is baking plastic. )
#petermolnarthere are these things, like Thunderbird, text editors and stuff, out of the browser, which are, be definition, offline
#petermolnarjust add an api to those, to connect to remote stuff
#petermolnaryou don't need the whole js sandwich for this
#bearmy take on the type of offline reading your describing above is that it's a solution that is required only because phones don't have a well defined api to store content
#bearmy gripe is this in a nutshell - why can I not view a web page, have the browser store the html, css and even some js
#bearand make it so if I visit that web page when offline I just get a small icon that says i'm viewing an offline page
#bearinstead most sites won't even have visible text
#bearand yes, service workers "solve" this - but really i'm asking why doesn't this already exist as a solved item in browsers
#bearthat's why i'm such a huge fan of static with a bit of js added for +1 features, but always have the core fallback of static
#KartikPrabhuof course the browsers could do this by default, but service worker type things are a good start
#bearI view service workers as another layer in the progressive stack really
#bearstatic html - css - js for events - service layer to cache forms and the like - fully online
#petermolnar"> always have the core fallback of static" we're relics from ~2006 when progressive enhancement meant static html first, then styling and just after that JS
#KartikPrabhubear: yes! they are another layer in the progressive enhancement stack
#KartikPrabhupetermolnar: that is what progressive enhancement means today too
#bearit's all dynamic html stuff that *requires* some javascript dom manipulation that is then sent to a backend using something other than a POST
#petermolnarthat bothers me as well, when I see a button but it's not a clickable action handler
#bearheck, I would even remove that complaint if the data to submit was at least doable over a REST api
#petermolnarbecause the js is a third party pull which I block
#KartikPrabhui agree that most of this JS stuff has been over-used but that doesnot mean that the JS tech is bad
#bearand i'm not ranting against that because I'm stuck in 2006 either - entire swathes of internet communities cannot access those items because they use assisted devices to view pages
#petermolnarno tech is bad on it's own, I don't blame hammers either
#bearKartikPrabhu - completely agree, most of my ranting is targeted to the echo chamber that is "modern" web devs
#bearwho build things because they can and then toss them onto the internet and then yell back at you when you ask for it to be accessible
#bearwow - I'm really in a grumpy mood today - I think i'm on my 10th rant
#KartikPrabhuhaha go build something on your own site to cool off