Skip to main content

Jeremy Cherfas

Quick gotcha: I moved this WithKnown site from shared hosting to a VPS yesterday, and today photos were not displaying and not uploading. Turned out that in the move the path to the Uploads directory had not changed. Fixed that, and all seems to be well again. I hope.

Jeremy Cherfas

Jeremy Cherfas

Jeremy Cherfas

Jeremy Cherfas

Reflections on Two Years of #Indieweb

Really good debriefing on two years of progress in the . I found this rather familiar:

While learning all of the requisite skills was challenging, the real struggle in joining the indieweb was piecing all the components together to hold a mental image in my head of what an indiewebsite should be. I spent a great deal of time trawling through the wiki and absorbing all of the ideas on disparate pages. At the time, there were many pages which would all have slightly different variations of the similar information.

There's still a ways to go, mind. When I did this reply to automatically, the title of the entry came though as "kongaloosh". I added the correct title by hand myself. The entry title is there, as `p-name` and I cannot tell whether the issue is at my end (WithKnown) or at Alex's end.

link

Jeremy Cherfas

The value of explaining yourself

2 min read

My father was devoted to cryptic crossword puzzles. He was good, too, but every now and then a clue would stump him. If I was around, he would read the clue aloud to me and, more often than not, before I'd even had time to think about it, he had solved it.

There's something about the act of saying it aloud that makes a different kind of thinking possible.

So it was last night, during the Homebrew Web Club virtual meeting in Europe. There was only me and Zegnat, much of the time, and first we explored further his comment, during the recent Indieweb Summit talk about Events, that "most of the things discussed are already available and possible with the current IndieWeb building blocks". So I fired up WithKnown and created an event for the virtual HWC and he replied and the reply was received and published. Just like that. Of course there are some things that could be improved, but it does Just Work.

Thinking more about improving things, I shamelessly took advantage by asking a lot of ill-informed questions about how to move further in the indiewebification of my presence on the web. Martijn was so helpful and patient with me, and I learned a lot. But the truth is also that just by asking the questions out loud, and having to think clearly about how to do so, I was able to see more clearly how things might work.

It's still pretty cryptic, but I'm getting there.

Jeremy Cherfas

The continuing saga of marking up status updates in @WithKnown

2 min read

I’ve been reminded by Chris Aldrich of something I think I knew before:

[M]ost major CMSes (including Known) strip out or severely limit (for security reasons) the html that is accepted in comment fields. … Many also will mark as spam comments that have one or more URLs in them. As a result doing fancy or even mildly complicated html or markdown in replies is something for which most platforms just don’t build.

That’s fair enough. As ever, spammers are spoiling things for everyone. I do have an objection, though. If I am legitimately signed into my own site which, in the , is where I will be if replying to some other site, then I’m unlikely to inject malicious code. And if I’m a spammer, and signed in under a false flag, then I’m not likely to need such subterfuges.

A really helpful CMS would, surely, allow me to do all the formatting I want on something I am generating myself, regardless of the specific type of entry.

Chris makes another point:

The other issue in status updates and replies is that they’re often syndicated to other platforms and it’s a more difficult issue to properly do this with each snowflake social media silo depending on how they individually handle html/markdown (or not).

Well, yes. But that’s not my problem on my site. Let them strip all they want, frankly, as long as the leave the link to my reply alone. As Chris acknowledges …

Either way, the end result on the other person’s site isn’t something I can ever control for, so I try not to sweat it too much. :)

For now, I think I’ll sweat this just a little, and add the u-in-reply-to by hand, and hope that does the needful.

Jeremy Cherfas

Flippin' useless, @withknown import.

I winnowed the stopping place down by searching for things, using that splitting by halves technique, and discovered that the Import had choked after 318 lines -- of 12058.

In reality, I ought to just give this up, but I'll have a quick look at the database and see if I can't screw that up.

Jeremy Cherfas

Not too helpful

Not too helpful

Dear @withknown

I am my system administrator.

Any clue as to how much you did manage to import? That would be nice.

If I do try again, what are the chances of duplicates being created?

Thanks

Jeremy

Jeremy Cherfas

For the sake of completeness, and as a necessary stage in my web plans, I am now going to attempt to extract my files from vaviblog.com and import them here.

We're both on the same version of , so it Should Just Work, right?