#GWGI posted the screenshots of a note posting form yesterday. Would you have any ideas to improve it? I always think of you because of your use of the Post Kinds plugin.
#KartikPrabhuI suspect that bridgy does not know that it has sent those (since G+ does not have URLs for them) and sends them again when it finds them in my G+ stream
#kylewmIt may be that the format changed when snarfed changed it to not have an e-content, and so it send them as "updates"
#KartikPrabhuaah I see. Not to worry, I replace the old ones whenever a new one is resent
KevinMarks, KartikPrabhu1, j12t, KevinMarks__, nloadholtes, KartikPrabhu, torrorist, fkooman, wolftune, loic_m, eschnou, indie-guest, catsup and frzn joined the channel
KevinMarks, KevinMarks__, alexhartley, wolftune and AcidNerd joined the channel
#rhiaro!tell aaronpk: re: the http/https stuff yesterday (last night?), as someone imminantly switching from http to https I second treating them as the same identifier. And also requiring https would have been a massive blocker for me earlier on; a warning and some friendly tips for getting started would be good though
#kylewmrhiaro: there's some competition between the UX and security there, I agree it would have been bad to lose all my accounts when i switched to https, but now that i have switched, I don't want my accounts to be accessible via someone logging in with http://kylewm.com
#rhiarokylewm: good point. Maybe accounts should be merged after the first https login
#rhiaroalso, related question: do I need different certs for subdomains?
#kylewmrhiaro: yeah I like that idea, "welcome https://kylewm.com, you have previously logged in with http://kylewm.com, would you like to upgrade your existing account to https?"
#GWGrhiaro: startssl is free if you want something basic.
#rhiaroI looked at startssl initially but then their pay-to-revoke thing seemed like kind of a jerk way to do business. But maybe I'll use that while I'm finding my feet and spend money when I have more idea what I'm doing
#GWGrhiaro: If they give you the certificate for free, they have to charge for something.
#rhiarooh turns out one of my domains (not my main one) came with a free ssl cert anyway
#rhiaroGWG: sure, I understand that, it seems like it would leave a lot of people unable/unwilling to pay and then left insecure
#Loqiaaronpk: rhiaro left you a message 1 hour, 5 minutes ago: re: the http/https stuff yesterday (last night?), as someone imminantly switching from http to https I second treating them as the same identifier. And also requiring https would have been a massive blocker for me earlier on; a warning and some friendly tips for getting started would be good though http://indiewebcamp.com/irc/2015-04-26/line/1430063947762
#KevinMarks__Hm, could do that with autoembed, like we do for images
#KevinMarks__Except it would need to call a service or something
#KevinMarks__(injecting the twitter embed iframe would be too much)
alexhartley joined the channel
#KevinMarks__So back to the meta tags thought. I noticed
#KevinMarks__That otherwise minimal sites spend the first precious ramp-up packets transmitting metadata cruft for silos. Could we put meta tags at the end?
#snarfedKevinMarks_: i kinda doubt that would make a big difference in end user latency
#KevinMarks__I suppose the actual question is "does fb parse meta tags not in head" which is testable
#snarfedtime to first byte generally far outweighs time to first 5KB
#KevinMarks__Certainly they should be after any things that queue other fetches, just wondering why the look most important of all
j12t joined the channel
#KevinMarks__The irony of single page apps who put more content in meta than in html
j12t_ joined the channel
#aaronpksnarfed: well I managed to track that down in case you were wondering
j12t__ joined the channel
#aaronpkapparently you need at least OpenSSL 0.9.8j to support SNI