Katherine Moss (Twitter)My debate just got even more interesting; Do i run WithKnown or Wordpress? I can’t decide considering both have awesome IndieWeb support.
— Katherine Moss (@Cambridgeport90) April 19, 2019https://t.co/4ZDIYIAux3 here were my thoughts on why I chose #Knownchat over #Indieweb WordPress (https://t.co/H1eVLuO7wp)
— https://jgregorymcverry.com (@jgmac1106) April 20, 2019That looks pretty cool. I think I'm going to have to learn HTML fairly decently though before I could consider it.
— Katherine Moss (@Cambridgeport90) April 20, 2019
https://indieweb.org/multi-site_indieweb
I’ve been running versions of both for many years and they each have their pros and cons. In terms of IndieWeb support they’re both very solid. Why not try them both for a bit and see which appeals to you more? Depending on your skill level and what you’re looking for in your site you may find one easier to run and maintain than another.
Personally I’ve used WithKnown (I’ve used it for multiple sites since it started) in a more “set it and forget it” mode where I just post content there and worry less about maintenance or tinkering around. On my WordPress site I tend to do a lot more tinkering and playing around, particularly because there is a much larger number of plugins available to utilize without writing any of my own code. Lately I am kind of itching to play around with Drupal again now that it has a pretty solid looking IndieWeb module (aka plugin).
You don’t need HTML once Known is up (or really to set it up) but it takes some specialized knowledge. In fact my minor complaints about HTML are a result of making it unnecessary to touch.
Img upload on mobile also needs some styling.
That’s pretty cool; will look at the wiki article in a second, but … thanks for the insight. BTW, how did you do the reply thing on your site?
Katherine, The reply thing from my own site to your tweet is my favorite part of what IndieWeb enables! For me it’s really the whole ball of wax. It shouldn’t matter what platform I’m on and which platform you’re on–we should be able to communicate across domain names and across different CMSes and platforms, right!!? This is what allows us to own all of our data.
The short of it is that I write my reply on my own website and syndicated it (via POSSE) to your tweet on Twitter. I then rely on Brid.gy to provide the backfeed of your comment back to my reply. Now I’m able to write another reply on my site and thread it into the conversation seamlessly. Except that I’m providing the backlinks to my site (for the characters over 280), there are ways I could do this and you wouldn’t even be aware of the duplication of the two separate threads.
If you’re interested in the slightly longer story, I’ve documented it before here: Threaded conversations between WordPress and Twitter.
As I’m thinking of it now, I sort of wonder if, for better UI and accessibility sake, I should be using my URL fragments to have the link for the continuation of the conversation (ie at [more…]) be pointing to the exact point at which the conversation actually continues on the resulting page? (Perhaps I’ll try some experiments to see how it might look/work…)
Syndicated copies:
Right, but which plugin are you using to allow that? I know there are lots of them.
For this functionality there aren’t a lot of options. I think the minimal set would be
The backfeed of reactions from Twitter will require a free Brid.gy account connected to your Twitter account.
More details can be found here: Threaded Replies and Comments with Webmentions in WordPress. One change that has occurred since I wrote that piece is that comments added to your posts should now send their own webmentions automatically instead of needing to do it manually or to add the
u-in-reply-toportion.While it should all work even with a theme that doesn’t have great microformats support, your results will obviously be better if your theme does microformats 2 well (examples include SemPress, Independent Publisher, etc.)
If you need help, feel free to touch base and we can set up some time to do a video conference call/screen share to troubleshoot any problems you may have.
Syndicated copies: