#dev 2016-10-31

2016-10-31 UTC
KevinMarks, chrisaldrich_, KevinMarks_ and ChrisAldrich joined the channel
bret joined the channel
#
cweiske.de
edited /2016/Berlin (+37) "/* Participating */"
(view diff)
chrisaldrich1, tantek, KevinMarks and ChrisAldrich joined the channel
#
www.funwhilelost.com
edited /device-deaths (+661) "Adding notes about Apple's common iPhone obsolescence pattern"
(view diff)
#
ben.thatmustbe.me
edited /2016/MIT2/Guest_List (+234) "/* Participants */ RSVPs via eventbright"
(view diff)
KevinMarks, ben_thatmust, ben_thatmustbeme, KevinMarks_ and tantek joined the channel
#
KartikPrabhu
aaronpk: the links to individual lines in the chat logs seem to be messed up due to timezone issue i think
#
KartikPrabhu
tantek: I left you a message but can't link to it due to timezone issues. it should be at the bottom here https://chat.indieweb.org/dev/2016-10-27
#
KartikPrabhu
repeating "saw your post-type-discovery algorithm draft https://www.w3.org/TR/2016/WD-post-type-discovery-20161028/#algorithm . Any particular reason for the ordering of types as "rsvp > reply > repost > like" ? I understand "reply" getting precedence but don't understand the "rsvp > reply" and the ordering after "reply""
#
Loqi
[Tantek Çelik] Post Type Discovery
#
aaronpk
yeah, something about crossing the date barrier when viewing it in your local timezone
#
tantek
KartikPrabhu: reasoning is in the draft
#
Loqi
tantek: KartikPrabhu left you a message 3 days, 18 hours ago: saw your post-type-discovery algorithm draft https://www.w3.org/TR/2016/WD-post-type-discovery-20161028/#algorithm . Any particular reason for the ordering of types as "rsvp > reply > repost > like" ? I understand "reply" getting precedence but don't understand the "rsvp > reply" and the ordering after "reply"
#
Loqi
[Tantek Çelik] Post Type Discovery
#
KartikPrabhu
tantek: I don't see why "rsvp > reply" from that
#
KartikPrabhu
oh I see, because the author is expressing intent to be present at an event over simply online-replying
#
KartikPrabhu
gotcha, makes sense now
#
tantek
KartikPrabhu: an RSVP is richer than a reply since it contains a specific yes/no/maybe/interested piece of information in addition to a reply
#
KartikPrabhu
yup makes sense. i didn't think of that while reading the spec
#
tantek.com
edited /MediaWiki:Sidebar (+51) "this week's HWC"
(view diff)
#
tantek.com
edited /Events (+4383) "Nov and Dec HWCs"
(view diff)
#
tantek.com
created /events/2016-11-16-homebrew-website-club (+7644) "draft from 2016-11-02"
(view diff)
#
tantek.com
created /events/2016-11-30-homebrew-website-club (+7644) "draft from 2016-11-16"
(view diff)
#
tantek.com
created /events/2016-12-14-homebrew-website-club (+7644) "draft from 2016-11-30"
(view diff)
#
tantek.com
created /events/2016-12-28-homebrew-website-club (+7644) "draft from 2016-12-14"
(view diff)
gRegorLove joined the channel
KevinMarks joined the channel
#
tantek.com
edited /Events (-29) "/* November */ -PDX 11-30"
(view diff)
#
gregorlove.com
edited /Homebrew_Website_Club (+69) "/* Bellingham */ note holiday hiatus"
(view diff)
#
gregorlove.com
edited /Homebrew_Website_Club (-21) "/* Bellingham */ flatten li hierarchy a bit"
(view diff)
#
gRegorLove
tantek: ^ That look ok? Not sure we need the nested li since the city name is the heading
#
tantek
looking
#
tantek
one moment, queued
KevinMarks joined the channel
#
gregorlove.com
edited /events/2016-11-16-homebrew-website-club (+95) "Bellingham on hiatus through 2016 holidays"
(view diff)
#
gregorlove.com
edited /events/2016-11-30-homebrew-website-club (+95) "Bellingham on hiatus through 2016 holidays"
(view diff)
#
gregorlove.com
edited /events/2016-12-14-homebrew-website-club (+95) "Bellingham on hiatus through 2016 holidays"
(view diff)
#
tantek
gRegorLove: commas in headings result in ugly fragment links - can you remove?
#
tantek
also the headings make sense as shorthands, and then expand details in the content
#
gregorlove.com
edited /events/2016-12-28-homebrew-website-club (+95) "Bellingham on hiatus through 2016 holidays"
(view diff)
#
tantek
agreed re: nested li - artifact of how it used to be
#
gRegorLove
Oh, so it's a MediaWiki workaround
#
tantek
clean that up in general
#
gRegorLove
The nested li was one thing, but I guess what I was thinking more was: there's a lot of redundant information with the full city/region listed under the shorthand
#
gRegorLove
But yeah, nasty MediaWiki anchors
KevinMarks joined the channel
#
tantek
gRegorLove: shorter heading in general are better, hence why I was only using city name there
#
tantek
and then leaving details up to contents
#
gregorlove.com
edited /Homebrew_Website_Club (+20) "/* Bellingham, WA */ rm comma from heading, put city/state back in bullet"
(view diff)
#
gregorlove.com
edited /Homebrew_Website_Club (-23) "/* Regular Meetings */ flatten nested li, leave city/region names as first bullet"
(view diff)
KevinMarks and KartikPrabhu joined the channel
#
tantek
KevinMarks, did you create a FB POSSE event for your HWC SF event this week? I see http://known.kevinmarks.com/2016/homebrew-website-club-san-francisco-2016-11-02 says "Facebook event:" but no link after ?
#
Loqi
Homebrew Website Club San Francisco 2016-11-02
#
tantek
wants to RSVP to both
KevinMarks_ joined the channel
#
tantek.com
edited /2016/LA/Guest_List (+537) "add my project info!"
(view diff)
#
tantek
ok - going to RSVP just to the indie event for HWC this week - hopefully I can post an "update" if there's an FB POSSE copy eventually
ChrisAldrich and chrisaldrich1 joined the channel
#
www.boffosocko.com
edited /events/2016-11-02-homebrew-website-club (+137) "/* Details */ no HWC for LA this week in anticipation for IWC LA"
(view diff)
#
tantek.com
edited /Events (-51) "move Oct events to recent, no HWC LA this week"
(view diff)
#
tantek
!tell gRegorLove mind updating the home page indieweb.org with latest / next HWC / IWC event infos? Thanks!
#
Loqi
Ok, I'll tell them that when I see them next
#
tantek.com
edited /2016/LA (+18) "emojicon"
(view diff)
#
tantek
ChrisAldrich: do you have food sponsors lined-up already and food ordering/delivery plans?
#
tantek
(for IWC)
#
ChrisAldrich
Pivotal is taking care of the lion's share. They're a relatively large company of programmers, so they've got lots of snacks/drinks in their kitchen area and will be catering lunch for us.
#
ChrisAldrich
They've got a large open area in the front for the opening/closing/demos (with pingpong tables), and half a dozen or so individual highly connected conference rooms for breaking into groups of 3-15+ for sessions.
#
gregorlove.com
edited /2016/LA (+648) "/* Organizers */ +Participating section"
(view diff)
tantek joined the channel
#
www.boffosocko.com
edited /2016/LA (+994) "/* Where */ Parking and nearby entertainment"
(view diff)
#
sknebel
hm, rereading the webmention spec the security section focusses on the sender side in a few subsections (don't send WMs to localhost, don't send WMs to servers in private networks), but the same concerns apply similarly to webmention verification?
#
sknebel
(although it's GET requests there, not POSTs)
#
GWG
Examples?
#
www.boffosocko.com
edited /2016/LA (+319) "Gave Pivotal a sponsor spot at the bottom"
(view diff)
#
Loqi
[Aaron Parecki] Webmention
#
GWG
I implemented those for verification.
#
sknebel
me too, and we've talked about it quite a bit
#
sknebel
so I was surprised that it isn't mentioned in the spec
#
aaronpk
i think the concern is less important with GET requests, since normally GET requests don't mutate state. tho for really poorly designed systems i guess that could still be a problem.
tantek joined the channel
#
sknebel
on localhost, you potentially could talk to e.g. a database using a non-HTTP protocol, there have been weird vulnerabilities where creative HTTP requests then are interpreted as commands. especially relevant if you accept HTTP urls including port numbers
#
sknebel
and if verification results are displayed, you could leak info from internal sites?
#
aaronpk
that's a stretch but i suppose so
#
sknebel
I agree that you need quite odd circumstances
#
sknebel
but I'd err on the side of caution and recommend blocking ALL access to such resources unless explicitly whitelisted
#
sknebel
I guess in an intranet you might want working webmentions between local sites