mblaney!tell eli_oat re: empty reader entries, you have your content in <p class="meta-data reply"> followed by an empty <div class="e-content p-name">. If you can combine the two (ie put all those classes on the same <p> or <div>) then things will work the way you want.
mblaneyno worries :-) personally I leave likes out of my feed, but of course everyone is free to do their own thing. I just don't see the difference between likes and reposts when the two are combined.
eli_oatgenerally speaking I like that using my website as a single point of truth as opposed to FB, or something, limits my response types. I use the likes for the self-serving purpose of not wanting to loose a certain link
sknebelgRegorLove: since you do a lot of wiki gardening, I'd be interested in your thoughts on automating some of it. I got the basics to edit the wiki programmatically working, so if you have an idea for something useful, say something
[miklb]so in the spirit of “can’t beat them, join them” I’m testing out using Chrome & an Atom extension to edit in my editor of choice. Also using pandoc to convert from markdown to mediawiki syntax.
[sebsel]!tell aaronpk Seems like my multi-photo-checkin problem is actually a OwnYourSwarm bug, because your site does not have multiple photos either! https://aaronparecki.com/2017/06/18/35/ (because of the +10 coins I suspect you posted both pictures on Swarm at the time of checkin, right?)
[sebsel]Hm, and when someone else checks me in (you did, https://seblog.nl/2017/06/17/15) and I make that same checkin, tagging you, adding a picture, I get the picture, but not the text / tag!
ZegnatThat seemed to be something that was OK. If we can establish a pattern (pro/con comparisons) make it a template for consistency and editability throughout the wiki.
ZegnatI also considered side by side lists, possibly restyle the bullet point to a plus on one hand and a minus on the other. But that was more design work than this ?
sknebelside by side is on https://indieweb.org/wiki/backup. templates AFAIK don't have a nice way of dealing with variable numbers of params, but if you figure one out ;)
ZegnatOh, and what is pretty nice about template arguments is that order does not matter. So when you want to add a con or pro you can add it at the bottom. You will still need to find the correct number yourself though :(
[miklb]seems worthy to add to the discussion for leader summit. Tantek made some comments about effort required for maintenance & upkeep, etc when discussing other options, I’m not sure the amount required for the wiki is really taken into account.
Zegnatsure, but are you going to ask people to learn wiki table syntax instead, which might also require you to add extra styling? Or encourage HTML blobs?
Loqi[Zegnat] I also considered side by side lists, possibly restyle the bullet point to a plus on one hand and a minus on the other. But that was more design work than this ?
ZegnatI am more interested in the syntax for the template for now, as that is to address editability. We can change the output HTML at any point and that would update all pros/cons lists
tantekfor tiny little building blocks like that, there is little advantage, and as cweiske pointed out (I think), it becomes one more syntax to have to learn
ZegnatI think this is less learning. My argument is that, if we want to encourage people to edit pages who do not like working with wiki syntax, it is easier to ask them “add your pros/cons to this page” where they can instantly add a pro=this or con=that to the list than asking them to edit other wiki syntax
[miklb]Zegnat, right now I’m working on just feeling more comfortable in the editor, and will use pandoc to convert to mediawiki if I feel the need to have a lot of formatting
tantekwe have more one person come along and insist they could redesign the whole wiki for us with much better design. and we asked, great, show us an example of your great design on your own website.
ZegnatI can not reimplement MediaWiki template syntax, that is just silly. Neither does running an entire MediaWiki instance make any sense. Instead I tested this out on a Sandbox page under my user page on IndieWeb and converted a single “real” page to see if the syntax could stick. I feel that is a perfectly valid process.
LoqiA wiki page is a type of web page that many in the IndieWebCamp community either want to or already host on their own personal site https://indieweb.org/wiki-page
ZegnatAnd I do run a wiki (wiki.zegnat.net) where I do document new things (e.g. my pronoun microformats research). That wiki is Markdown based though, so syntax doesn’t cary over to IndieWeb.
ZegnatWhat I am wondering specifically is if people like miklb, eddie, and chrisaldrich who voiced concerns about doing wiki edits would feel like things would be easier if we had more templates abstracting things (like pros and cons).
[miklb]one thing I did see kinda work with a mediawiki instance was tagging (?) a page “incoming” if you weren’t sure where it went and if was formatted correctly and that was added to a special page for wiki gardeners
ZegnatI was addressing not the issue at all of creating new pages (where other people who do know about templates will probably do gardening anyway) but the usecase we constantly run into: we ask someone to add a vote or statement they made in chat to the wiki, and they don’t because they do not instantly recognise how to make it fit in.
tantekalso, if a 1 dimensional list is hard, making it 2 dimensional (a table) where one of the dimensions is purely presentational, is unlikely to help
ZegnatCombination. I got rid of both bulletpoints followed by a - or + (which was there originally) to hopefully help reading, and the output is generated by a template to hopefully encourage edits
LoqiPOSSE is an abbreviation for Publish (on your) Own Site, Syndicate Elsewhere, a content publishing model that starts with posting content on your own domain first, then syndicating out copies to 3rd party services with permashortlinks back to the original on your site https://indieweb.org/POSSE
tantek.comedited /wiki-page (+153) "/* IndieWeb Examples */ update urls for caseorganic, note dates that it was at a subpath /wiki with archive org link and used to support IndieAuth login" (view diff)
aaronpkI don't really have a strong opinion on which is better, the only reason I would see to use anything other than MW is because github popularized their markdown so more people are familiar with it
tantekaaronpk, my goal is provide something so much simpler / more readable than md that it will actually work just as plain text, and be even more popular
LoqiGenerations in the context of the indieweb refer to clusters of potential IndieWeb adopters in a series of waves that are expected to naturally adopt the indieweb for themselves and then help inform the next generation https://indieweb.org/generations
ben_thatmustbemei have my entire site to finish getting working, i have an mf2 - > jf2 feed converter i want to write, a websub implementation i want to write
ben_thatmustbemewas thinking about this last night, create a service that will convert h-feed to jf2 feed, and also support websub with it... but not only as a publisher, but as a consumer as well, so if the original supports websub, it will push updates to the JF2 Feed version as well
ben_thatmustbemelooking to make it as simple as possible, so long as the page can generate the hash and say "enter this into your config file" it should be fine
gRegorLoveRe: reading the wiki, I don't think lists in themselves are a problem, but some of the typography and whitespace in the (quite old) MediaWiki version we're running. Newer MW and Vector skins will help. I've made some tweaks in my user CSS that I think make it better (interim solution): https://gregorlove.com/2016/06/i-am-tinkering-with-the/
Loqi[gRegor Morrill] I am tinkering with the user-customized CSS for the indiewebcamp.com wiki and thought I would share.
My custom CSS is here. You can edit yours by going to “My Preferences”, clicking “Appearance”, then clicking “Custom CSS” beside the Ve...
sebselsknebel Yeah, but that would require an edit in an extra file. The <?php die() ?> thing could be managed from the single file. You still need read/write rights tho.
ZegnatHmm, can you write to a file within a PHAR? I wonder if that would be a solution, just have a single PHAR that people can include that handles everything internally
Loqiaaronpk: ben_thatmustbeme left you a message 2 hours, 23 minutes ago: https://indieauth.com/faq seems to indicate you must own your own domain name, doesn't it allow subdirs?
aaronpkthe main limitation with signed tokens is being able to revoke them but that's not an issue with auth codes because they are supposed to have a very short lifespan anyway
aaronpkI would definitely recommend that over trying to find a place to store the data. The only trick is you'll need to create a secret for it in the config file
vanderven.se martijnedited /2017 (+169) "/* Participating */ Link to Mozilla Community Participation Guidelines, tantek brought it up in chat" (view diff)
tantek.comedited /2017/Schedule (+198) "explicit introduction and housekeeping before keynotes, do intros and demos before lunch so people meet each other" (view diff)