Skip to main content

Jeremy Cherfas"/>

A space for mostly short form stuff and responses to things I see elsewhere.

jeremycherfas.net

jeremycherfas

EatPodcast

eatthispodcast

pnut.io/@jeremycherfas

micro.blog/jeremycherfas

Jeremy Cherfas

One step closer to PESOS from Instagram

1 min read

I had been barking up the wrong tree, trying to address `photo/edit` in order to create a photo post in WithKnown. Going through my old notes, I figured out how to do it through `micropub/endpoint` instead, which makes a whole lot more sense. Probably I should have started there.

Anyway, I know have the bare bones of being able to post automatically to WithKnown from the RSS feed of my Instagram account. Now I "just" need to build out all the rest; read the RSS feed, extract the relevant bits of data, construct the API request and bung it off.

Which will probably take forever, but hey.

Jeremy Cherfas

PESOS from Instagram?

1 min read

At last night's online HWC we talked a bit about getting pictures in and out of Instagram, now that they have become so much stricter about the API. Getting images into Instagram except through approved apps seems to be getting harder and harder, and is probably impossible by now. Getting images out of Instagram is also not obviously easy. But ...

A new (to me) thing, called Bibliogram, can, under the right conditions, create an RSS or Atom feed from one's profile. I poked around, and the feed contains a link to the image, caption and  date and time. The link to the image works. So maybe ...

I could send the feed to IFTTT or Zapier or similar, and have that create a post via Micropub to my instance of WithKnown. Or even, if I ever get it working, to my main site, which uses Grav.

But I can't even try for a couple of days.

Jeremy Cherfas

An ad-hoc meeting of the WithKnown Open Collective

5 min read

The past 24 hours saw perhaps more activity in the IRC channel (yesterday and today) and than I have ever seen before. Near the end of it all, jgmac1106, having previously voluntold me to be the first rotating organiser, voluntold me to “call all of today a meeting of the Open Collective”. Obviously you can’t have a meeting without minutes,[1] so here they are.

It all started with jgmac1106’s heartfelt plea that he just wanted to publish his site, “not learn backend engineering” and contemplating starting afresh. LewisCowles raised the question of how to reward Open Source software developers and maintainers, and that started a discussion of what it would take to put Known on a commercial footing.

Jgmac1106 was of the opinion that easier install with auto-update was needed. Lewiscowles and jeremycherfas thought that better direction of the project was needed, with a model that offered installation, domain management and updates, for a fee.

“Make it Known would be such a great tagline if we could get Sir Patrick Stewart on board.” Lewiscowles

There followed further discussion of operational models, including micro.blog; pay for hosting, including updates, and some backfeed, with a free offering open to IndieWeb if you have a capable site elsewhere.

On funding, jeremycherfas related his early experience hosting through IndieHosters and jgmac1106 talked about applying for grants to fund specific pieces of Known development. We played around with numbers, concluding that nobody knew enough to build even an outline business plan. There did seem to be agreement that venture capital should be rejected from the outset, while collectives and cooperatives could provide a more desirable structure, and that any kind of structure needs direction.

After a gap, some other people joined the channel and mapkyca explained that right now, a bigger block than money was time as he is working flat out. He also said that the maths does not work out for SaaS.

Benatwork then rejoined the meeting and explained in some depth the history of Known, including funding decisions and his original vision.

The original intention was to build a community platform that could be hosted securely, with discussion not monitored by the likes of a Facebook. … [I]t was never built to be an indieweb platform or an individual blogging engine from the start. The core idea was: flexible, social feeds that one or more people could contribute to, with per-item access control and integrations both in and out. I still believe that it has most value as a multi-user platform.

Major problem: we gave our entire platform away as open source, and it turns out there was a strong correlation between people who wanted to use it and people who didn’t want to pay. Although they were happy to pay for an account on a shared host, which of course didn’t go to us. So it didn’t really work as a scalable business.

Benatwork then filled us in on recent developments and why his direct involvement has dwindled, all of which is very understandable, closing with his belief that SaaS is not the way forward.

Jgmac1106 then voluntold jeremycherfas to take the lead on setting up monthly meetings for the next three months, as the first rotating organiser.[2] He also shared his idea of having something like Known to offer local media as something they can sell to subscribers as a built in social platform.

In response to a question from Aaron_Klemm, Benatwork shared the Known roadmap on github. He also explained some of the past technical decisions and that maybe some of those should be revisited to improve the product as a whole.

People shared their different ideas of what Known could become for them, with the question of the current admin tax prominent. Cleverdevil said he would be happy to pay mapkyca to update his site, raising again the potential demand for SaaS.

Benatwork’s vision is Known not as a blog CMS exclusively, but rather:

What Known can do is create a stream of many different kinds of content, and present it differently based on context. Filtering is a similarly powerful idea. “Show me all posts that are sensor readings and photos tagged with bats, from January 1st.”

There was some discussion of other aspects of Known that need attention, including the templating engine, which mapkyca said he hopes to separate completely from the back end.

Chrisaldrich raised the possibility of working with Reclaim Hosting to devise a package similar to what Reclaim offers universities, i.e. Reclaim does the heavy lifting for turnkey Known installs while allowing a small group of others to support people who signed up. Aaron_Klemm supported this idea strongly.

There was a lot more discussion of various ways in which Known could contribute to community internet literacy and how it might be used alongside other web publishing tools.

This summary is an entirely personal capture of the discussion; corrections and comments welcome. (You know how to do that, right?) I’ll suggest some times for an online meeting through the channel.


  1. Though apparently you can have one without an agenda.  ↩

  2. Which I will do, bearing in mind that, with exceptions, I am really only available Monday to Friday from 08:00 to 19:00 CEST.  ↩

Jeremy Cherfas

2020-03-17

1 min read

There's no way I know of to find old spam that came into WithKnown while I was not getting notifications. I had thought that my scheme of jumping on spam as soon as possible after receiving (restarted) notifications had found them all. But no. Today surfaced a bookmark post that had accumulated 10 spams since August 2018.

Lotta continua!

Jeremy Cherfas

#Hashtags & HTML

1 min read

Once again, there is chatter about how @Withknown deals with hashtags and HTML I still believe that it often removes a hashtag from the content of an Instagram description, sent here by OwnYourGram. I'll test that in a moment. And there certainly were problems with certain characters in Titles and body. So this is a test of this <- and that.

Jeremy Cherfas

2018-04-11

1 min read

Digging into how withknown creates RSS feeds, I can see two things.

One is that for a status post, which has no title, `<title>` is a truncated version of the post content, although the level of truncation seems to vary. Not sure why.

The other is that even status posts, with a truncated `<title>`, have a full `<description>` that includes `p-name` and `e-content` and even `entry-content`.

But micro.blog does not seem to read `<description>` at least not when it is coming from my withknown RSS feed.

Puzzling.

Jeremy Cherfas

You can get good help

1 min read

I managed to fix a long-standing niggle with my practice this afternoon, thanks to some great help from cweiske and others. For the longest time Quill, a micropub client that I can use to publish here, wasn't showing me an option to syndicate directly to Twitter. That meant that I tended reply to tweets and stuff right there in the silo and not bring them back here. Fair enough, especially when a reply without context is like an egg without salt. But we figured it out, in part by that old standby of "switch it off and then switch it back on again". That got things working, and was enough of an impetus to upgrade WithKnown to the latest build. And so far, everything looks good.

Jeremy Cherfas

I really want to use micro.blog and WithKnown, but ...

3 min read

I have never yet been able to post from my micro.blog to this stream, although the feed from here is reliably picked up there, and brid.gy reliably pulls replies from there to here. @manton suggested we move my complaints to help@micro.blog, but I can see no way of actually engaging with that account. So this afternoon, I decided to attempt to go back to the beginning.

It was a miserable failure.

Here's how it went:

  1. Revoke all current authorisations for micro.blog
  2. There were four of them, two from yesterday when I last tried.
  3. Launch OS X app
  4. OK!
  5. “If you’re using WordPress or another server, first open the preferences window and enter your web site URL to set it up for posting within the app.”
  6. Roger that. But the old website was still there. Is that going to be a problem?
  7. Start a new post; the old website is there at the bottom. This is going to be a problem.
  8. Same old Same old; Error sending post.
  9. Post does not arrive at micro.blog
  10. Post does not arrive at WithKnown
  11. WithKnown Error log is empty.
  12. Access log shows no sign of anything from recent attempt to post from micro.blog
  13. Check to make sure I have up to date micro.blog app
  14. “Micro.blog can’t be updated when it’s running from a read-only volume like a disk image or an optical drive.” Move Micro.blog to Applications folder using Finder, relaunch it from there, and try again.
  15. Strange. Check path to micro.blog.
  16. Path is “/Applications/Micro.blog.app”.
  17. Check the App Store; disappointed but also content that there is not an update.
  18. Delete web site URL from preferences; quit micro.blog, mostly for superstitious reasons; launch micro.blog.
  19. Very strange; web site URL is still there. Or back? Maybe the app pulls it from micro.blog?
  20. Repeat; same outcome. Superstition justified. Go to my account at micro.blog.
  21. See I have three App tokens. The one for MarsEdit is definitely pointless, as I am not hosted at micro.blog. Remove it.
  22. Throw caution to the winds; remove the tokens for IOS and OS X
  23. OK, IOS now says “Internal Server Error” on attempting to connect. I think I ought to sign out now and then sign back in.
  24. Phew. All is good. And I have a new app token.
  25. On iOS, try to write a new post; insert my Known site; authorise micro.blog; write a test post. Post it.
  26. “Error sending post”. Tear hair out, as now I do not seem to be able to post to micro.blog from iOS app.
  27. Go back to 22; remove iOS app token and authorisation token at WithKnown.
  28. Log back in. Can no longer post without adding WithKnown, and posting gives an error, as at 26.
  29. Try again from OS X; same error as at 8.
  30. Post to WithKnown; feed is picked up.

Any and all suggestions gratefully received.

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

Why the indieweb

1 min read

Richard MacManus is indiewebifying his site, and [had this to say](https://richardmacmanus.com/2017/06/22/openness-rivers-indieweb/):

> I’ve found the IndieWeb tools to be tremendously helpful, and the community to be open and friendly. But I think my own goals are a little different. I’m less interested in the technologies themselves (like microformats and webmention) and more interested in how they’re being used in the wider Web community. Not dissimilar to my interests when I started ReadWriteWeb. But of course to do this, I need to stand on the shoulders of the developers who build the tools.

All of which sums up my own position exactly. I'd go slightly further. I'm not as interested in how the technologies are being used in the wider Web community as I am in putting them to use myself.

*p.s. A major drawback of Withknown's excellent engine is that it doesn't allow New Posts to be replies, and that means I can't use the MarkDown formatting.*

Jeremy Cherfas

The future of WithKnown

1 min read

The question "does @WithKnown have a future?" is cropping up increasingly frequently of late. And the "official" answer is that it most definitely does, look at all the activity on github, nothing has changed. And it's true, there has been a lot of activity and things are moving, if you go and look. But for someone just looking in and trying to decide whether to use the software, the lack of outward facing activity must be a bit off-putting.

Or maybe it isn't.

I have no idea.

All this was [kicked back and forth on the WithKnown IRC channel yesterday](https://github.com/mapkyca/KnownchatLogs/blob/master/2017-03-23.md), with -- alas -- no input (yet?) from the developers.

I'm going to continue trying to understand Known because right now it seems to me the best place to continue pursuing ideals.

Jeremy Cherfas

Another test of Quill editor

1 min read

Writing something nice again, but I have enabled the Markdown plugin on Known.


And maybe a headline too

Like this

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.

Jeremy Cherfas

Completely mystified by editing a bookmark in @withknown

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 Cherfas

Plugging away

1 min read

Bummed out by the fact that Quill wasn't enabling me to syndicate directly to Twitter, I followed up on some good advice from Daniel Gold: Back to basics, uninstall and reinstall plugins one by one. Shades of WordPress. So I did that, and here's what I found:

With IndieSyndicate configured (*via* silo.pub) I can posts to Twitter just fine, but Quill still does not see that as a Syndication target and Quill cannot post to my site.

In retrospect, that's obvious, because there is no endpoint at my site.

So I enabled IndiePub and now Quill posts fine, but it still does not see any Syndication target.

I probably just have to live with that. At least for now.

Finally, re-enabled Brid.gy and everything looks good once again.

Just for the record, here, I've decided that for now I do not need these plugins: Static pages, Firefox, Events, Custom JS, Custom CSS, Comics, Audio, API tester. That may change in time.