#tantekindiewebcamp.com was the primary site of the IndieWeb community from 2011 to 2016-07-03. As of 2016-07-04, we renamed the main site and identity from IndieWebCamp to IndieWeb.
#Loqiindieweb.org is a website in development to present indieweb ideas in a form more incrementally accessible to generations beyond generation 1 https://indieweb.org/indieweb.org
#gRegorLovemax-width helps readability, but looks weird on HD screen.
#LoqigRegorLove: tantek left you a message 6 hours, 23 minutes ago: I resolved the issue you added to https://indieweb.org/2016/homepage#Issues could you take a look? Also advocating using GH issues for new issues (link at that link). Thanks!
#gRegorLoveAlso, hm, what happened to my custom css...
#gRegorLoveActually, if the header bar stopped at 800px too and the right part of the page used the same bg color as the left sidebar (#f3f3f3), that might look better.
#LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indieweb.org/indieweb
#aaronpkneed to add css classes to the colored backgrounds and then change the link colors in common.css
#aaronpki only added inline styles on the home page just now
tantek, KevinMarks_, KevinMarks, KevinMarks__, KevinMarks___, snarfed and Loqi joined the channel
#tantek.comedited /indieweb.org (+4203) "document current use as of today (main site, 2016 camps, chat, etherpad, news), rewrite negative General Issues as instead primarily positive How Tos, with "avoids" only as specific exceptions" (view diff)
#tantekI've rewritten the negative General Issues with subdomains etc. into more positive How To brainstorms here: https://indieweb.org/indieweb.org#How - looking for review / feedback!
#tantekAlso I tried to do a big factual update to the top of https://indieweb.org/indieweb.org that just lists all the ways we are using indieweb.org now including subdomains
#tantekalso worthy of review - especially did I miss any *existing* (not proposed) subdomains that we're using? and why?
#colintedford"Join" & "Beyond" were a little hard to read b/c low contrast. I tried lighter shades but they didn't seem right for the boldness of the content.
#colintedfordTried white box for content on colored background -- not convinced it's the way, but it's mroe readable.
#tantekaaronpk, when you have a chance, please review https://indieweb.org/indieweb.org - there's more edits I'd like to make but I think this is a good enough improvement for now
#tantekin particular I'm looking for a review of the "How" subsection https://indieweb.org/indieweb.org#How - if that looks good to you (feel free to make prose edits / improvements as you see fit), I'd like to move to just after Why
#tantekwhich reminds me, the Why could go after the "Whats"
#aaronparecki.comedited /Main_Page (-70) "improve contrast of colored backgrounds by setting text and links to a lighter color and larger font size" (view diff)
#colintedford^ Larger font size in general would be good, but I imagine the newer Vector will take care of that.
#tanteknice work aaronpk. and it looked incremental enough that I figured it was some clever wiki hacking. and I checked /Special:RecentChanges before the logs ;)
#tantek(plus the section [edit] links give it away ;) )
#tantekonly think I would re-add to the header is a Search [__________] box to the right of "Discuss Events"
#LoqiThe indieweb is about owning your domain and using it as your primary identity, to publish on your own site (optionally syndicate elsewhere), and ownyourdata https://indieweb.org/indieweb
#petermolnar.netcreated /2016/Brighton (+1173) "Created page with "= <span class="p-name summary">IndieWebCamp Brighton 2016</span> = <div class="p-description description"> The importance of owning your data is getting more awareness. To grow ..."" (view diff)
#gRegorLoveYeah, the font-size is boosted inline in some of those sections
#aaronparecki.comedited /Main_Page (+66) "/* What is the IndieWeb? */ change icon background to a different shade of the background it's on top of" (view diff)
#petermolnartry this colour for the pink: background:hsla(30, 100%, 80%, 1);
#bearcan we get rid of the background of the part where "Join the IndieWeb" uses? or change it to the others - I'm having trouble reading the highlight text with that background
#tantekwaits for aaronpk to literally build his own bikeshed
#tantekaaronpk ugh, the horizontal icons are very bad for the first section
#miklbtantek fair enough. And trust me, I've been through it before. Habari went through more iterations of the home page than releases of the code I think
#tantekthought I already implied that in the issue as a DO NOT do
#aaronpkthe "join the indieweb" section doesn't have any text that can be used as headers
#miklbpetermolnar agreed, design without solving a problem is an affliction everyone's probably suffered from
#petermolnartantek that page from 2003, I think you might break a record there; most of the blogs you're linking from that page seem to be alive; that is extremely rare
#aaronpki think the three "principles" "selfdogfood" and "design" could work better as the 3-column bit
#tantekalright, let me try instead a smaller variant on the prev
#aaronpkafter we're done i'm making an animated gif of all the wiki diffs of the home page
#tantek.comedited /Main_Page (+31) "go back to nice subtle bg colors, and try a soft aqua for the calls to action. color complements orange-ishes, and stands out compared to informative texts" (view diff)
#aaronpkshades of *a* color would be okay. but the changing hue is awkward.
#tantekaaronpk - the other thing to do instead of the pastels is to go the other side and make them darks, like almost blacks, which would make the colors etc. in the photos "pop" more
#tantekand then you could get away with white text/links
#aaronpkyou can really only use dark backgrounds like that when there's very little text
#tantekaaronpk - feel free to finetune that yellow BTW, that was my eyeballing it on my Thunderbolt cinema display (which was pretty decent color representation / correction etc.)
#tantek(better than trying to do color work on a laptop screen)
#aaronpkMW seems to have a bunch of different ideas about links
#tantekbecause the footer stuff is not something to emphasize with such a stark contrast
#KevinMarksCheck contrast of teal though. (I have a laptop display and a sideways TV attached to mine that have very different gamma, so I see variations. Contrast on a best case screen is not the best test. Try it on your phone in bright sunshine
#GWGI have an issue filed against WordPress Micropub for the capability to set a post to draft status. Is there call for that in the specification? Or do you think it is too WordPress specific
#LoqiA draft in the context of the indieweb refers to a draft post, a post that an author has partially written, or otherwise does not consider finished https://indieweb.org/draft
#gRegorLoveI'm interested in safe-as-draft for micropub
#voxpelliNot sure if private and protected fits into the same property as draft in the h-entry world – there are thoughts on how to deal with private and protected posts already elsewhere and I think that's separate from the draft itself
#voxpelliGWG: it's a property of the post and I think that Micropub defines no properties of the posts but leaves that all to microformats to define
#voxpelliI would say that the problem would be solved by figuring out how one would express draft status on a h-entry
#voxpellimaybe tantek can add some thoughts there? since he apparently does so
#gRegorLoveGWG: I think since you want draft functionality, build it, then the micropub spec has real world examples.
#GWGI can build it into the server, but I am not working on a client.
#gRegorLoveProcessWire doesn't have "draft" concept built in, but does have a "published" and "unpublished" state. unpublished is only visible to logged in administrators. So effectively a draft.
#gRegorLoveYou can build unit tests that will ensure it works, sans client.
#voxpellip-x-status="draft" maybe? which in micropub terms would be just x-status=draft
#GWGGood point, but designing the property is something I would want some input on.
#gRegorLoveI don't think WordPress does, unless a theme does some additional handling. IIRC it uses the post ID in the URL instead of the slug, though.
#colintedfordYeah, Wordpress only distinguishes in the url -- I think it uses a query string there that makes it clear that it's a preview.
#voxpelligRegorLove: I think mp-* are free for other specs to add, but following similar practices as with experimental mf2 properties I guess
#voxpellibut maybe that needs to be clarified in spec?
#voxpelligRegorLove: I think "reserved for future use" just means: Do not ever have a property of the post itself start with "mp-" as those are reserved for micropub instructions
#gRegorLoveI may be thinking too specific to WP and PW, but for both of those, draft status is something outside the post. if an MP client creates a post and adds some mf2 to the post body to indicate it's a draft, it's something I would have to manually remove when I choose to publish.
#gRegorLovevoxpelli: Sounds right, just wasn't sure.
#gRegorLoveI think delete and update used to be mp-*
#voxpelli!tell aaronpk Maybe add some wording to the Micropub spec about what mp-* instructions are meant for and how other specs can add new ones and how one can add experimental ones similar to mf2's p-x-* (maybe mp-x-* ?)
#voxpelligRegorLove: mf2 properties doesn't have to be saved as part of the post body – they are probably rather rarely saved as part of the post body leaving the post body as only the e-content
#voxpellithat's how I save mf2 properties in my Jekyll implementation as well: everything in YAML front matter apart from the e-content data that's saved as the markdown file
#gRegorLoveNot sure I follow. Seems pretty implementation specific.
#gRegorLove"When creating posts, all other properties in the request are considered properties of the object being created." so they're properties of the h-entry
#gRegorLoveWhich can be invisible, but visible data is preferred
#gRegorLoveThat's why I was thinking of an mp-* property instead, perhaps
#Loqiaaronpk: voxpelli left you a message 26 minutes ago: Maybe add some wording to the Micropub spec about what mp-* instructions are meant for and how other specs can add new ones and how one can add experimental ones similar to mf2's p-x-* (maybe mp-x-* ?)
#aaronpkstarting with what's visible to the user for draft posts makes sense. i believe i usually see some indication that a post is a draft, or unpublished, etc
#aaronpkin that case it might make sense for it to be included as a microformats2 property
#aaronpkin which case it would translate easily into micropub
#Loqischeduling in the context of the indieweb, refers to the feature of setting a specific time for a post to be published in the future https://indieweb.org/scheduled
#voxpelliaaronpk: regarding the mp-*, I can't find a reference in the Micropub spec to where mp-syndicate-to is specced either – thoughts on whether the mp-* instructions needs be specced more? mf2-style or rel-registry style or such?
#voxpelli(not sure if non-working group members can add issues to the repo, so asking here)
#voxpelliactually recently had a real encounter with draft statuses saved as a date far far far into the future. Too bad they got published with that date later on. Siterusers were amused.
#Loqicolintedford meant to say: tantek: nice :) "helping people plan for their future [posting] needs"
#colintedfordI could see a micropub client UI having some sort of "draft/published" UI, and for drafts it would just leave out dt-published, and CMS would treat that as a draft (whatever that means in that CMS)
#voxpellitantek: it was rather that we didn't have a connection between publish dates and publish statuses – the two were completely separate from each other
#LoqiA draft in the context of the indieweb refers to a draft post, a post that an author has partially written, or otherwise does not consider finished https://indieweb.org/draft
#tantekI learned to avoid them in the CSS world, as part of methodology of designing new properties in such a way to minimize adding new properties in the future
#aaronpkwhich means status=draft makes more sense than draft=true
#tantekthere have been a few cases where people wanted a boolean, we picked non-boolean semantic names for the values, and then later, figured out that 3rd or 4th values made sense
#aaronpkstatus is really short for published-status
#aaronpkDoes Facebook have draft posts? I've manually done it on Facebook by creating a post visible only to me and then changing it to public when I want to publish it
#tantekI feel like auto-uploads to Flickr work that way too - app auto-uploads private as a "draft" hack, then you selectively set public
#aaronpkOh yeah I do that with my eye fi card al the time
#aaronpkWhich reminds me... That's going to go offline soon :-(
tantek, KevinMarks_ and KevinMarks joined the channel
#tantek.comedited /IRC (+5) "/* Under Consideration */ use indieweb-dev as place for meta until it seems it deserves its own channel (kind of feeling we might already be there)" (view diff)