#KartikPrabhubear: turns out "six" was not installed because I have to do "pip install --user six ".... who the F#%@ is supposed to tell me that!
#tanteksalanto also agreed about "stuff I post on the internet I don't want on twitter" - or rather, I'd like to get to the point where I can trivially post little things on my site as much as I like, without feeling the burden to self-censor/self-rate-limit due to cross-posting to Twitter(&FB).
#tantekbut for now, since my posting UI is crap, that slows me down enough to only post once in a while and thus not too bothersome for those that follow on Twitter/FB
#salantoMy indiesite is hosted on my laptop. My view is that it's my data that im giving people permission to view. Not some server that I have permission to write to
#salantoI only POSSE things I want people to see when I close my computer
#tanteksalanto - sure, your local copy of your site as the "truth" and some server on the web as a "cache" of that :)
#tanteksalanto - do you have more than one device you write on? or browse/favorite/comment on?
#salantotantek: Write on as in create the post content, or store the content?
#salantotantek: My laptop is publicly accessible from the internet
#salantotantek: .club domains are only like 2 dollars a year from namecheap
#salantoICANN went balls out. They even have .ninja now
#tanteksalanto next I'm imagining you having an always on (and on the internet) raspberry pi tiny box in your back pocket that has your true/canonical data that you post to.
#salantotantek: Actually I have a publicly accessible native ipv6 address on my rooted android phone that I am tempted to setup an indie site on, the only problem is that most people don't have ipv6 access from their isp yet
#salantoThey could use the sixxs ipv6 proxy to get to my site I suppose
#mkotantek: I don't think benwerd has implemented recursive inreplyto (aka tweetstorms) like Twitter has.
#tantekmko - I don't really care what the underlying technique is (recursive whatever), but rather, the user visible difference between screenshots of those two URLs.
#Loqitantek meant to say: mko - I don't really care what the underlying technique is (recursive whatever), but rather, the user visible differences between screenshots of those two URLs.
#mkoYeah. Agreed. I was just letting you know what the disconnect between the two was.
#tantekmaybe, I mean, do you know how Twitter is actually coded? because I don't. hence I prefer to speak only at the user level for such things.
androtest and indie-visitor joined the channel
#LoqiWelcome, indie-visitor! Set your nickname by typing /nick yourname
#TeddyJIf I have a domain: example.me, How do I register the subdomain: name.example.me?
fmarier joined the channel
#mkoTeddyJ: The subdomain just needs to be added with your DNS provider to point to the relevant hosting provider IP address or folder. It varies from provider to provider.
#TeddyJIs there a FAQ or wiki entry having to do with children on IndieWeb?
#salantoyou can get a free tunnel to enable ipv6 from tunnelbroker.net
#salantothe computer im on right now is through a tunnel
#mkoI'm actually just waiting on Comcast for a new modem/gateway. IPv6 is supported on my line, but apparently the gateway they sent me when I signed up originally doesn't support it.
#salantomko: I have the same situation for this router I'm on now
#salantoIronically my modem has ipv6 support it just doesn't work with comcast's ipv6 network
#snarfedhey kylewm, I'm afk and saw a error spike on bridgy soon after the deploy. would you mind taking a look if you're around?
snarfed joined the channel
#snarfedkylewm: actually nm, looks like it was transient. I'll look later
#snarfedkylewm: saw the logs, looks like it's missing an index that's probably in your index.yaml. feel free to push that to upstream and deploy if you want! otherwise I will soon
#kylewmsalanto: the open source question is one i asked too. i think the idea is basically: it's rEAlly hard to release and support a full product, and aaron et al feel they can serve the community better by experimenting with their sites and then releasing battle-tested code in small libraries
#snarfedthere definitely are full open source stacks though
#kylewm"Why can't I just have p3k/taproot/Falcon?"
Jihaisse joined the channel
#mkoI'm planning on releasing Indie.js (http://indiejs.com) as soon as I have a single working instance and then updating it as I go.
#mkoMy goal is to have a single app that can be downloaded, dropped on a server, and then started up via an install script.
jsilvestre joined the channel
#mkoI only started on it about 2 weeks ago, though, so I'm not sure how long it'll be before it's out. Hoping to release my personal site at the end of this week as the "alpha" of it, then make some of it a bit more generic, then release v0.0.1-alpha on GitHub.
glennjones, petermolnar1 and petermolnar2 joined the channel
#tanteksalanto: wordpress is currently the easiest initial install though I think Known is getting better and better. Pretty sure they are testing a version that runs on MySQL (not mongodb)
#salantoubuntu is a bit too brittle on my phone to play nice with a complicated setup
#tantekTwitter has poor block/report spam handling, poor even by silo standards
#tantekon Flickr, Facebook, blogging platforms in general, if you block an author or delete a comment, it's gone from your post. On Twitter, it's only hidden *from you*. E.g. I blocked that spammer bear saw, and if you view this: https://twitter.com/t/status/490312706650431489 you will see it still has two comments from that spammer (I can see it on a non-logged-into-twitter browser)
#petermolnarI was asking for Known debug options :)
#bearhow are you calling php5 from nginx? php-fpm or ???
#petermolnarPHP-FPM, yes, the PHP log therefore shows up in nginx error log
#bearnot always, i've seen some php apps where the app log is in the root dir, in /usr/local/.… - but i'm also not a php5 dev and was just trying to help
#tantekgood morning all - the call for participation in the W3C Social Web Working Group just went out to all W3C Advisory Committee members (member-only list), and I'm happy to report that the home page of the group is a wiki page :) http://www.w3.org/Social/WG
#tantekI want to encourage everyone in #indiewebcamp to consider participating (I'm a co-chair), whether officially or unofficially
#tanteksince you're on IRC, please feel free to jump on the #social channel on irc.w3.org:6665
gRegor` joined the channel
#barnabywaltersI never understand W3C call minutes. what’s timeboxing?
#tantekcuibonobo: agreed. I think a lot of the "real work" will happen here frankly, and I see my role as chair to attempt to bridge communication with that broader audience, pointing / referencing the good work done in #indiewebcamp
#cuibonobogRegor`: yep! i’m actually taking ideas from several places. indiewebcamp is my primary resource for getting my website display app to play nice with other sites. i’m getting ideas for how to actually store my stuff from the tent.io community
#tantek(as opposed to W3C going off an inventing a bunch of new complex enterprise stuff that no one implements)
#gRegor`tantek: the archive link "public-socialweb-comments@w3.org (archive)" is 404
#barnabywaltersin other words, it’s a way of getting the W3C official stamp of approval on indiewebcamp stuff, which is important to a lot of people
#cuibonobogRegor`: the idea is to have a RESTful API of the data itself in JSON format and then have apps to consume that data in different ways. apps could range from scrobblers to the app that actually renders your website.
#tantekbarnabywalters: that and having W3C efforts reference (rather than duplicate) indiewebcamp work
#cuibonobogRegor`: however, i’m not subscribing to tent.io wholesale because they’re very focused on the protocol and have left actual real-world stuff behind
awolf joined the channel
#barnabywalterscuibonobo: that sounds like a sensible approach — reuse the useful work they’ve done and ignore the unproductive bits
pfefferle_ joined the channel
#tantekcuibonobo: "the app that actually renders your website" is an interesting viewpoint, since we're taking the simpler approach that your rendering of your website is your data (i.e. for interaction with webmentions etc.)
#tantek10 years ago people were building "RESTful API of the data itself in XML format"
#cuibonobotantek: i don’t subscribe to the idea that the HTML is simpler. for instance, i feel like a plaintext JSON file is easier to digest than plaintext HTML. but more than that, my goal is my data, not my website. my site is just a way to render my date.
#tantekcuibonobo: over time I'd assert that the HTML is actually the most stable reliable "form" of your data.
#tantekfor the "easier to digest" need - that's why there's a canonical JSON representation of microformats2, and parsers that produce it
KartikPrabhu joined the channel
#tantekthe idea is that longevity, reliability, stability is the most important thing for your data. And historically so far HTML has been better at that than XML, or JSON
#tantekdespite supposedly being a "presentation" format
#tantekbut I understand the current fashionability of JSON. Also good to have different folks pursuing different approaches.
#tanteksome folks are using Markdown as the canonical form of their data, which has some good long term usage experience as well
#tantekwith actually more well defined rules than before
#tantekthus original microformats now have a canonical JSON representation that they never did when originally published
#tantekwhich HTML tags have shifted in particular?
#barnabywalterswell marked-up classic microformats are parsed seamlessly by commonly used microformats2 parsers
#tantek(we've known to ignore presentational HTML markup for a *very* long time)
#cuibonobotantek: back when i first started using HTML, presentational markup was still a thing! and i’m only 32
#tantekbut to your point about original microformats - HTML+microformats have outlasted *all* the XML formats that were being pushed at the time. Even by big companies like Google and Yahoo.
#tantekoriginally XML was supposed to win over all this stuff
#tantekmicroformats was a scrappy simpler alternative
#mkoI don't have time to get into a discussion right now, but I will say this: from my own experience, microformats parsing isn't consistent right now except across a limited subset of parsers. For example, mf2py, hkit, microformat-node, and sumo all produced different parsing results when I was trying to figure out why one of my articles wouldn't validate as an h-entry in my webmention module.
#tantekcuibonobo: when I first started to also (~1995), but by 1998 I'd been properly educated about it ;)
#cuibonobotantek: my perspective is: what is this data for? if my primary use-case is to have a searchable repository, it doesn’t make sense to spend my time creating / maintaining HTML parsers that will then populate an index. databases already exist, so i’ll use that.
#cuibonobothe longevity of my data is a different problem entirely
#mkoI've already filed issues with the others that didn't work with <article>
#cuibonoboi can’t expect to have data that is useful now and data that i can put in cold storage
#tantekcuibonobo: databases seem to transfer less well from system to system than flat files, hence a lot of us have rejected databases for any canonical storage.
#barnabywaltersmko: IIRC hkit is no longer maintained, and is a classic microformats parser anyway
#tantekhkit is php right? perhaps it should be updated to just use phpmf2
#barnabywaltersit’s only really meaningful to compare microformats2 parsers
#cuibonobotantek: you’re right. databases are a pain to transfer. but am i going to delay the storage of my stuff while i implement a proper parser? i’d rather store my stuff now and figure out how to translate when the new hot thing comes along.
#tantekright, and the point is they produce consistent results, even with classic microformats (or rather they all should, modulo some issues / bug fixes)
#tantekcuibonobo: I guess enough of us have gotten bitten enough times with data loss from database hassles that we've given up on them
#tantekand decided to eat the upfront dev cost of using flat files instead, for the sake of being free of future database-tax
#tantekbut your're right, databases can be a good bootstrapping mechanism. it's how Known advanced so quickly in its feature set (IMO)
#cuibonobotantek: i’m very new to this community, but it seems like the up-front cost is *much* too high compared to `brew install mongo`. plus: what if everyone moves to blockchain storage and namecoin as DNS within the next 10 years :D
#tantekso yes, it's still good to see different people pursuing different approaches.
#tanteklol blockchains. I think that's another fashion thing that will pass. :)
#tantekfair enough about up-front cost is *much* too high
#tantekwhich is also why those of us using flat files for storage have yet to open source that code AFAIK - storage is hard enough to get working for yourself, nevermind something others can depend on
#tantek(myself at least, I'm implying for aaronpk and others)
#tantekthough … barnabywalters doesn't Taproot use flat files for storage?
#barnabywaltersandrotest: there are plenty of valid use cases — essentially anything where you need to be able to know that one thing happened before another
#tantekso that's my general point. a bunch of us are using flat files for storage, but yes, it's hard, so none of that code is not open source yet
#barnabywaltersbut it’s just moving the trust to the network rather than a trusted third party
#barnabywaltersI have recently (places) run into cases where using my CSV indexes has blocked adding useful features, so elasticsearch has moved up a little in my priortity list now
#tantekif I came up with a decent abstraction for my flat file storage (in HTML+microformats) in Falcon I'd likely open source even just that bit in the hopes that someone else would find it useful.
#barnabywaltersI think glennjones’ transmat storage is the closest thing to this so far — give it flat files and you get an API
#tantekcuibonobo++ for pursuing what's #selfdogfood productive in the short term. :)
#tantek(though some aspects of storage, like backup, restore, recovery are user-exposed features, and I think that's where some of the flat file vs. database tension comes from)
#tantekas a user I sleep better knowing my "data" is all in a simple folder I can copy around, rather than a series of exports/commandlines that talk to a database server somewhere
#tantekbarnabywalters: interesting about Transmat - care to start a /Transmat stub?
jschweinsberg joined the channel
#barnabywaltersI would if I could find or remember the link to the API demo
#gRegor`cuibonobo: Are you using an existing /project to run your site, or setting up something custom?
androtest joined the channel
#cuibonobogRegor`: since i like the *idea* of tent.io but it’s becoming apparent that it’s not gonna be ready for at least a year, i’ve decided to roll my own thing. i’m using a lot of ready-made components though: Eve for the API, Flask for web apps, Mongo for storage
#bearIMO a good interface is the one that changes the result based on content-type
#barnabywaltersthe term REST is also almost as abused and misused as HTML5
#cuibonoboyeah that’s really it. you’re bound to HTTP verbs rather than trying to make up your own API, and the server shouldn’t save sessions. full stop.
#bearyes! html5 definitely muddied the waters when folks who didn't quite grok REST started to make sites
#KartikPrabhubear: that's what I thought people did. apprently not
#barnabywaltersso when people say they want a REST API rather than a website it’s worth digging down to see what they actually mean
#KartikPrabhubarnabywalters: most of my investigations ended up with "they got JSON data rendered with JS client-side"
#KartikPrabhuthose are not actual quotes from someone
#KartikPrabhu<shrugs> this mostly sounds like HTTP is coming back into fashion
#KartikPrabhufor instance, there is Django and there is the django-rest-framework... which led to my confusion
#bearall big frameworks have tools/modules to enable REST(ish) routes to be defined
#bearheck REST got it's big push from the ruby-on-rails folks
#bretoliusjohncash i think elgg was used by a lot of non profits… known would likely be of interest there. but I think the idea is that it would be useful to many more people
#bretoliusShaneHudson what software do you use to run your site?
#ShaneHudsonYeah, and a way to easily host elsewhere.
#tantek(ok so I thought the IndieWebCamp / camping / tent.io joke was funny ;) )
crossdiver joined the channel
#ShaneHudsonI use Wordpress at the moment, having a lot of troubles with it but has been too much work trying to move it elsewhere. I will probably use Known, as it has a lot of the extras I need (content types nicely done etc)
#bretoliusShaneHudson ah cool. it looked like it might have been done in jekyll or something similar
#ShaneHudsonAh nah, there are thousands of private posts etc :)
#Loqitantek meant to say: I mean, have you *talked* to the guy? ;)
#cuibonobothe problem with the “these youngsters will find out one day” argument is that when the day comes, I won’t remember your argument. what’s good about the indieweb *right now*?
#tantekcuibonobo: when the day comes, the old arguments won't matter.
fmarier joined the channel
#tantekcuibonobo: the latter adopters will adopt because their friends and people they respect (or want to be like) are adopting.
#tantekEv, Blaine, Jack are all very much more GenX like than Millenial like (re: Twitter)
#bearyour all young'uns - get off my world-wide-web lawn!
#cuibonobotantek: yes. exactly. so “they’ll come around once those websites go down” isn’t very attractive. if i recall, there’s a similar argument about databases on the wiki ;)
#bearstarts a "bring back gopher and wais" campaign
#tantekno no that's different, that's more like, our databases *have* gone down, so we've abandoned them and going with what's not gone down - flat files :)
#tantekbear - gopher lost its chance by not open sourcing.
#tantekwas a fan of gopher back in the day, so much more "organized" than the messy "web" thing.
#kylewmsnarfed: is it true that the Loqi bridgy mentions are always going to be someone replying/liking/retweeting a silo post that links to an indiewebcamp.com page?
#bretoliusit does but its crappy. i get like 4 hours a week to work on my indieweb projects and 2 are spend trying to track down stupid bugs in my code
#aaron_pk"Email and phone verification is required in order to ensure that you are complying with the Respect Network One-Person-One-Account rule." from the Respect Network registration prompt
#tantekthe likes came from identi.ca accounts to a reply posted on microca.st which itself is a comment on e14n.com
#kylewmpump.io speaks activitystreams, i wonder whether Known's json could talk to it
#tantekso the question is - does this all only work because it is a single piece of software (pumpio) - thus monoculture? or is something more interesting going on?
#tommorrisRespect Network can safely be completely ignored. The combination of Google+ style identity verification horror show + XDI silliness made me have to check I had only had one drink.
#kylewmwhether or not there is something more interesting going on, all those servers run the same software (pump)
#tantekkylewm: so monoculture once again. well, interesting proof of concept for the UI at least
#aaron_pkI would hope that there's nothing preventing other sites from integrating like that
#tantekaaronpk - I wouldn't presume that - as usually when it's the same piece of software, it means it's depending on software-specific behaviors (above beyond or excepting from any "standard" protocol/format)
#tantekas happened with identica/statusnet, then diaspora, now also tent
#tantekall of which can be deployed across sites to talk to their own software, but none with each other.
#tantekjohncash, webmentions will likely show up on my site as a side-effect of me implementing /event posts: http://indiewebcamp.com/Falcon#event_posts (which is fairly down the line of priorities of what I'm working on)
#Loqisnarfed meant to say: bnvk: do you do your own backfeed? bridgy is definitely careful to only backfeed fully public responses. https://www.brid.gy/about#missing
#kylewmactually I wonder if I should add something like that to the BY-CC bit at the bottom of my site ... "Comments are copyright their respective owners" or whatever
#johncashis there an indieweb equivalent of direct message?
#tantek.comedited /likes (+485) "put a thumbs up as likes are displayed that way in FB, add explicit IndieWeb and Silo examples sections" (view diff)
#gRegor`Related to people possibly being surprised their comments appear on my site, there's no easy way to remove it from my site if they remove it from FB, is there?
#Loqibenwerd: tantek left you a message 3 hours, 39 minutes ago: yes I'm giving you a hard time for reading and linking to a *CNET* article instead of a better, more indie source. ;)
#Loqibenwerd: johncash left you a message 2 hours, 18 minutes ago: do you have a business model for known?
#ShaneHudsonWhat Twitter clients do you all use? I've got POSSE working (to some extend) on my site, not activated yet, but I know I won't use it unless I'm using a client to reply to other people.
#benwerdtantek: congratulations again about the working group - really an awesome step
#tantekwhile that's still only a single piece of software doing it (pump.io), it is happening across *three* sites. the likes are on identi.ca on a comment on microca.st which is commenting on a post on e14n.com
#benwerdtantek: yes. Full context including context of replies / surrounding thread is definitely on the roadmap.
#benwerdWe're changing the way that whole piece gets displayed and implemented over the next few weeks
#tantekcool - will be interesting to see where the boundaries are
#benwerdPart of ownership = fully understanding the interactions on the things on your site
#benwerdsitting on a Bolt Bus so Internet may come in and out btw
#tantekI see it as a goal as not having to click through to a POSSE copy to see *more* interaction.
#tantekthat is, having your own site have a proper superset of the interactions across POSSE copies
#tantekand then I think it's reasonable to always include a permashortlink with every POSSE copy
#tanteksince you're stating that yes, my original post will have *at least* as much information as this POSSE copy, and likely more, since it will included Indieweb interactions and *other* silo POSSE backfeed interactions
#tanteklooks forward to seeing permashortlinks on benwerd's POSSE copies
#cuibonobopermashortlinks seem a little… pushy to me
#tantekcuibonobo: they're like watermarks for your copies
#benwerdI originally turned them off because of complaints - contemplating checking referer and adding a "what is this?" note. And possibly some other rough prototypes of the reader experience.
#tantekso if/when people copy your content, their copies point back to your original
#benwerdooh, Bolt Bus adds ads all over my site without asking me. My favorite
#tantekhas had some experience with random sites / feeds / Twitter accounts copy my tweets without attribution or linking
#cuibonobotantek: i get your justifications for them. still, they skew a little bit religious fanatic for my taste
#bretoliustantek re https://e14n.com/evan/note/s4sLsySKS_C9Ac1Mu80k3Q lots on AS and JSON-LD. I know pump.io builds around AS and has quite a few users/instances… where does indieweb stuff (Webmention, microformats, indieauth and micropub) find its place in the WG?
#kylewm.comedited /pump.io (+6) "/* Rejected pull request for microformats */ clarify close intention" (view diff)
#bretolius"In the same time, I'm going to deal with the long list of pull requests and open issues with pump.io. The PRs will either get a reply, get pulled to 0.4, or closed. The issues will get put into milestones for 0.4 or "maybe later" or "probably never"
#bretolius"Finally, I'd very much like to do a Kickstarter for the home pump server I discussed last year. I think it could be a lot of fun, and really help people get onto the network." Johannes? you there?
#bretoliusjohncash you can grab rss somehow i forget
#bretoliusor there is a pump to to rss bridge somewhere
#Loqijohncash meant to say: why have data and styling in one stream and data only in another stream. might as well put all the data in the stream that already has data
#bnvkI've been wondering about the idea of @usernames inside of email content so to enrich the experience of when one is mentioned in an email. Has anyone come across that sort of thing?
#bnvkit would also work well for email threads that are publicly viewable, as @username could be parsed to then show relevant user context data
#kylewmbnvk: wouldn't you need some centralized arbiter of who is which @username?
tantek joined the channel
#tantekDoes "email" imply SMTP or is that just plumbing?
#bnvkkylewm: well depends, one approach could be in an address book within a users given email client
#bnvkanother could be a browser extension pulling from one's IndieWeb side address book
#tantekAssuming we get /messaging working well, could we simply call that "email"?
#bnvktantek: tricky question, I think of email being both the message data format + SMTP transport
#tantekThen an "email on the public web" is just another post
#tantekIf I ever started a silo I'd be tempted to call it sandcastle.something and once in a while a big wave would crash and wipe out the sandcastle a that people had built there.
#Loqitantek meant to say: If I ever started a silo I'd be tempted to call it sandcastle.something and once in a while a big wave would crash and wipe out the sandcastles that people had built there.
#tantekThis is what I mean by those that redesigned don't actually use / edit the wiki day to day
#tantekGregor the problems were so numerous and seemingly obvious To a daily user that I didn't bother. It smelled like no one that worked on it was bothering to dogfood daily.
#gRegor`I ask because I use the new theme and am going to tweak it.
#tantekGood way of seeing what's new since I last looked at this page
#bnvkPersonally I have always found the wiki relatively obnoxious- the underlying technology, syntax, and sites information architecture. I wonder if we'd be better off with a WordPress site for public "new user" information and such and an instance of Gitlab for actually working on things
#tantekI like to look at several diffs at a time which the history page let's you do.
#bretoliusyeah… it may just be that I dont know these trix
#gRegor`Are we referring to a mousever as a click? Re: Edit and History?
#bnvkboth have relatively structured data input forms and such
#bnvkthe current site is definitely not alluring to new users- many ppl at camp in Berlin found it challenging to engage, navigate or gain any value from
#GWGsparverius: You mean like every popular platform?
#aaron_pkcomplaining that "new users" find it hard to navigate the wiki is not sufficient reason to suggest replacing it with something else. I guarantee whatever would replace it would be harder to put content into
#bretoliusgRegor` aaron_pk Ill start using it day to day and see what bothers me
#tantekNo for personal I can see that it works for some
#tantekAs in bnvk , I challenge you to show me a public community effort that works like that where the public home page doesn't just go stale in months.
#tantekAs for my own anecdotal I will offer microformats.org where we basically tried the split bnvk is suggesting and all the WP "public" pages went out of date while the /wiki media wiki is what everybody updated.
#aaron_pkbretolius: cool. I tried that but then switched back because I actually wanted to get stuff done :(
#tantekEventually we've been migrating more and more of the WP public content pages to the wiki.
#bnvkI also find the wiki hard to engage with. Right now "create a stub" I don't have this mental processes of what that process is. I have to hunt and peck between existing pages
#tantekSnarfed the hate (in this case) is only for the misconception of using it for a collaborative community site.
#bretoliusit would be cool if there was like a Ghost style wiki editor
#snarfedtantek: agreed in this case. there's some low grade ongoing hate for it as an indieweb platform too though, hence the previous negative karma. i'd guess some of that is just because it's big, but probably not all
#bnvkand overall it just lacks structure of how to easily go publish / edit a given type of content… but you all are much bigger users than I am, so do what ya will, I just wonder how much more myself (and others) would use something slightly easier ;)
#snarfedtantek: not a big deal though, not worth doing anything about
#tantekbnvk: Wordpress is not easier for collab editing, that's your mistake
#tanteksnarfed: Clearly WP has proven itself as a flexible indieweb publishing solution, if only by the adoption numbers.
#gRegor`My "go to" demo of why I dislike WordPress is this function. WP adds magic quotes regardless of server settings, or the fact that PHP is getting rid of the "feature." http://codex.wordpress.org/wp_magic_quotes
#tantekAnd generation penetration too. I think WP is the only solution that gen 2 folks have started using so far for indieweb functionality.
#tantekSuch external measurements are an important metric
#snarfedbut agreed, self-hosted wp is probably be the most important
#gRegor`tantek: Using this page as a comparison, http://indiewebcamp.com/User:Gregorlove.com/redesign, line lengths are actually longer on the current wiki theme vs the new. Not usually by more than a couple words, but yeah.
#tanteksnarfed: Blogger and tumblr are a different camp since they still have silo TOS
#snarfedtantek: hmm. i expect all of our hosting providers and ISPs have TOSes. if you bring your own domain, are blogger/tumblr materially different?
#tantekEven just the home page looked uglier in the new theme
#bnvktantek: yah readable / accessible information that is up to date- that makes sense, I just don't understand why you think a WP page is somehow less easy for multiple people to edit at different points in time
#gRegor`New theme is: "Helvetica Neue", "Helvetica", Helvetica, Arial, sans-serif;, old is just: sans-serif. Hm
#gRegor`"It looks uglier" is harder for me to act on :)
#bnvkfurthermore, there are all sorts of WP plugins for things like events that give data (and the input forms) structure and order. The current events page in wiki syntax feels like an ad-hoc jungle
#snarfedtantek: understood in general…but for blogger and tumblr specifically, you actually know that they claim to own your content? or something similar? hard to believe, but if you say so, i'll believe you
#gRegor`bnvk: I have a template in progress (practically complete) that will make events much easier. /Template:one-day-event
#johncashtantek: i deleted my facebook because of the creepy experimentation stuff. so i hear you on the silos overstepping
#bnvkonce I get a bit of free time (after sept) I will definitely step up to the plate to help redesign the site if it's not done by then (even if it's still on wiki) :P
#snarfed(for the logs: Tumblr and Blogger's TOSes both explicitly say that users retain ownership and copyright over all content they post. both are obviously limited in other regards, but it's good to know at least that part won't prevent people from using them as valid indieweb sites.)
#gRegor`There's some weird things in Foundation. Like h4 is text-transform: uppercase
#gRegor`for no apparent reason. All other headings are normal case.