A space for mostly short form stuff and responses to things I see elsewhere.
Now available for all: How much does a nutritious #diet cost. http://www.eatthispodcast.com/how-much-does-a-nutritious-diet-cost/
Done. The cost of eating a nutritious diet. Patreons can enjoy it now. Everyone else will have to wait http://patreon.com/etp
1 min read
Writing something nice again, but I have enabled the Markdown plugin on Known.
And maybe a headline too
Utterly bizarre; when I went to write a new post, the above was already there. In other words, the content of the post from Quill, without the block quote.
>This should be a markdown block quote.
I'm knackered. Will try some more tomorrow.
1 min read
Writing something nice again, but I have enabled the Markdown plugin on Known.
So need something in HTML, like this block quote
And maybe a headline too
This is the content of a regular note from quill
This is a test of silo via @aaronpk
1 min read
I cannot get my head around how @withknown is handling posts.
I bookmark a page, with a quote from the page:
I don't like the yellow behind the text. So I click on edit, expecting to be able to at least look around.
Where is the quote?
Beats me.
Jeremy Cherfaspublished this
Since I disabled the Markdown plugin, I see only the rich text editor (which is now Quill rather than TinyMCE, I believe. Can't find a setting to change that! May have to go back to Markdown, although that was dumb because it didn't translate markdown in status updates.
Just posted a response to your issue: github.com/idno/Known/iss…
, Feb 21 2017 on twitter.com
Also on: @EatPodcast
2 min read
Further to my note about a new #podcast about #indieweb things, I listened to Marty McGuire's rendering of This Week in the Indieweb. I really enjoyed it, even though I had read the text version. Production and audio were top notch, and it was very clear. My only quibbles concern the pace and the audience.
Even as a native English speaker, and despite Marty's very clear diction, it seemed a bit speedy to me. I wonder whether less fluent listeners manage to get it all.
A second, similar point, about the audience. In my estimate, as a newcomer to indieweb and a less than expert person, some of the stuff whizzed right by me. But if I were familiar with it all, I'd probably be keeping up with the IRC channels and the indieweb.org pages and so I'm not too sure why I'd need an audio version. But that's just a matter of choice.
The slightly bigger question is, would there be an audience for a more discursive podcast about the indieweb? Marty would be in favour. So would Chris Aldrich, who started this ball rolling for me. There's a fair bit of audio tagged indieweb at huff duffer, but nothing, apparently, dedicated to the topic.
We certainly have the technology to produce something that captures the history, what's happening now and how things might develop. There's no way I could do that on my own -- not least because I don't know enough to ask intelligent questions -- but with a co-host or two it would be a really interesting project.
Jeremy Cherfaspublished this
Jeremy raises some great points here that mirror some of my own worries about trying to summarize the discussions happening on the IndieWeb wiki and the many #indieweb chat channels. When I had the initial idea to do an “audio edition” of This Week in the IndieWeb, the question of “who is the audience” seemed to have an obvious answer: folks who would read the newsletter but preferred an audio edition. However, it quickly became clear that doing a “direct read” of the newsletter — where much of the content is names and links to changes on wiki pages — wouldn’t make a lot of sense when spoken aloud. So, my first crack at the format evolved into answering a slightly broader question: “how can I explain these updates to someone who might not already be familiar with the wiki?” My short (and unhelpful) answer is: this is hard. The discussions on the wiki tend to be very technical, jargon-heavy, and touch on an extremely wide set of topics. In the first episode, I attempted to give some structure with groupings like “IndieWeb Events”, “Software and Services”, “Silo Updates”, “Silo Issues”, etc., but I agree with Jeremy that it is still very fast and dense. While I want to keep the podcast short (less than 10 minutes), I think a next positive step would be to give topics more time to breathe with some explanatory commas that give context. It is my hope that projects like this podcast will help find new ways to phrase and frame the things that the IndieWeb community are doing and talking about, helping to reach new folks. I have a feeling it is going to be a lot of work. :}
, Feb 21 2017 on martymcgui.re
1 min read
Further to this morning's minirant about blocking Instapaper, I've now discovered that some sites -- I'm looking at you, HuffPo -- don't want me to be able to speed read, which I'm doing with a nifty little thing called Spritz. Or maybe they're just unaware there's a problem. The good news is that HuffPo does not appear to block Instapaper, so in the fullness of time, I will read the piece anyway. It looks really interesting.
Jeremy, this seems to be related to how the dBase holds the information. That doesn't answer your query, nor does it provide a solution; however the Editor element isn't pulling in the entirety of the information from the dBase to populate the Editing window.
Does this happen with the Plain Text editor also?
Daniel Goldsmith, Feb 21 2017 on headcrash.ascraeus.org