#ben_thatmustI don't see that as so much of an issue, when you pull the mention to see if its a like or just mention, you can see if there is a u-tag-of your site
#KartikPrabhutantek: i haven't seen any but wouldn't be hard to do. You use your JS code to pull in from webmention.io and then run marginalia.js after it. The trouble is I don't think that webmention.io does fragmentioned webmentions
#KartikPrabhuyeah. but independent libraries so to speak
#bretbrowserify is pretty cool. it brings the var module = require('module') to front end
#KartikPrabhulike if you wrote a code that pulls webmntions from webmention.io and want to use marginalia to display it. How would I give you access to the 3 functions in marginalia?
#bretdepends how you are getting the data off of webmention.io. my perpetually not working implementation gets data off via jsonp
#bretit would be better to use CORS and XMLHttpRequest();
#bretthe idea is to write smaller single purpose modules with an actual module loading system (like in python or ruby) rather giant do everything libraries like jquery, that expose themselves as global window variables
#KartikPrabhuwell I changed some fields and the db migration croaked. then I fixed it but the migration code does not know about the fix so now my dbs lost the original field and don't have the new one
#colintedfordgRegor`: Huh, that setting is set correctly but seems not to work for me on the default IWC theme.
#gRegor`colintedford: I think when it's unchecked it puts a question mark after broken links. Does that work? It's possible the themes are just broken.
#KartikPrabhugRegor`: i think it is the themes. a broken link also shows up in blue in my expereince
#colintedfordgRegor`: Yeah, I "jiggled the handle" (unchecked, saved; checked again, saved). Neither changes the link appearance.
#colintedfordThe Simple theme works, but IWC & Teahouse don't.
#gRegor`There's still several JS errors with the theme, so I'm guessing it's in there.
#colintedfordIWC looks like it has formatting set but it doesn't get applied. Teahouse seems not to have separate formatting for broken links.
lukebrooker joined the channel
#colintedfordSorry to hear about the db, KartikPrabhu.
#KartikPrabhucolintedford: yeah horrible and frustrating. which is why I want to move my own site to a file-based storage ASAP. but that is going to take some dedicated coding
#KartikPrabhumaybe at some point in the future I can have a system that others can use. I did see your call for a file-based static site
#tantekKartikPrabhu: ugh - sorry to hear that about the local db dataloss :( if there's some way you can write up a warning about what you did, perhaps we can help prevent it from happening to others
#KartikPrabhutantek: yes. I was planning to write it up when I get my file-based system up but that seems to be a long way in the future. Maybe a preemptive post about "why" I am swichting to file-system.... so much to write and no local site to test it
#tantekKartikPrabhu: braindumping a few notes on the wiki would be fine too - perhaps on the page related to the specific db you were using
#KartikPrabhuyes possibly. will get to it soon. too much stuff to do this week
LauraJ, michielbdejong, mdik_, DanC_, loic_m_ and michielbdejong1 joined the channel
#KartikPrabhumichielbdejong1: you missed an important situation: when your javascript fails e.e.g a misplaced smeicolon is enough to cause trouble
#michielbdejong1KartikPrabhu: that's no different from a misplaced tag in your html?
#michielbdejong1I don't think that's a valid criticism of javascript as such.
#KartikPrabhuit is. a misplaced tag still "evaluates" the rest of the HTML, but a javascript error just stopd the code cold
#michielbdejong1But you would immediately see that, right?
#michielbdejong1Also, that's assuming you're writing your own javascript, most people would typically use a CMS?
#KartikPrabhuthe problem is exactly trusting others JS. I can trust the browser to render faulty HTML written by others (like templates) but not faulty JS because it just stops
#michielbdejong1I guess you could say that a criticism of javascript could be that it's hard to write code that works (harder than writing html code that works)
#michielbdejong1So if you feel that is a relevant criticism of javascript as a technology, then you should add that as a second criticism. I just edited the "Sites break without Javascript" point.
#KartikPrabhuyes. HTML has a safe fallback in case or errors, but JS does not ( which is good for programming ) but not good enough to rely on it
#michielbdejong1do you know if anybody already wrote this criticism of javascript being hard to get right, somewhere?
#KartikPrabhumichielbdejong1: sure. I'll add that sometime. not to say your points are not valid :)
#michielbdejong1i guess as a wiki, you should not add original research
#KartikPrabhuagain not disputing anything you wrote. I agree with those, but "no one has their JS turned off" and "Google now render JS" has been used as an argument against progressive enhancement before. Just on the indiewebcamp wiki
#colintedford"No original research" is a Wikipedia thing because they're an encyclopedia, not a general wiki thing.
#KartikPrabhucolintedford: still a good practice. and I can not disagree being a scientist
#colintedfordYeah, supporting evidence / citations are always good.
#KartikPrabhuare always important I would say. So michielbdejong1 was right to call me out on that
#KartikPrabhujust that I can't produce the citations right now :)
#KartikPrabhumichielbdejong1: exactly the reference I would have cited :)
#KartikPrabhumichielbdejong1: yes Google now parses JS
#michielbdejong1ok, i'll do the edit as i'm there now.
#KartikPrabhubut again one misplaced semicolon and the rest of your JS fails
petermolnar and Sebastien-L joined the channel
#KartikPrabhumichielbdejong1: just to get this straight. we are not disagreeing just the degree of agreement :) you seem to be in a bteer timezone to find citations and also spell :P
#michielbdejong1:) yes, I'll try to put the arguments there with their citations, in the right order.
#KartikPrabhualso note that the error handling extends to dependencies. so if you have a JS that depends on JS that depends on JS, the some error in the last one might cause the whole chain to fail
#elf-pavlikhi xtof, yes i still look at a way to get there from paris
#xtofelf-pavlik: think I’ll join tomorrow morning by train from Montparnasse
#elf-pavlikdo you know if people tend to check tickets often here? which doesn't matter that much since i can always hitchhike the rest of the trip if get kick out of the train :D
#xtofelf-pavlik: no problem. Let’s go together if you’re free tonite. Awating an opportunity of dinner tonite + co-voiturage tomorrow morning ?
#elf-pavliksounds good! i have call with Lloyd from Social IG Vocabulary TF at 7PM to discuss describing *skills* in online profiles, maybe we could meet sometimes after 8PM?
j12t joined the channel
#xtofelf-pavlik : great. could you come at home ? And we’ll improvise. I’m awating news from a friend hitchiking from Germany…
#kylewm.comedited /JavaScript (+187) "/* Sites break without Javascript */ make discussion a bit more direct, add a 3rd reason for graceful degradation without JS" (view diff)
#kylewmsnarfed: hey what do you think about that out-of-date BeautifulSoup github mirror? i'm thinking we could 1) ask them to update it, 2) make our own mirror, 3) use the launchpad.net repository directly
#kylewmtantek: re single-page-antipattern, where do you fall on sites that do client-side rendering but have normal-looking permalinks (like ember.js apps)?
#kylewmdoes anybody else have the problem where clicking on wiki links (like above) takes you to a logged out session?
#kylewmif i change it manually to https, then I'm logged in again
#colintedfordkylewm: I don't seem to have that problem.