huh. Thanks for the recommendation. I'll look at SemPress and see if replacing Independent Publisher is something I want to do :)

— Nitin Khanna (@nitinthewiz) March 23, 2019

Take a look at Indieweb Publisher by @dshanske. It’s a fork of Independent Publisher.

Also on:

Register for Indie Web Camp Brighton 2019

#indieweb #brighton #indiewebcamp #events

Discrete replies

#replies #twitter #responses #indieweb #homepage

Reflecting On IndieWeb Summit: A Start

Reminder that there’s an IndieWeb Meetup (aka Homebrew Website Club) this Wednesday. I’ll bring some Micro.blog stickers. 6:30pm at the tables outside at Mozart’s. ☕

Space for the strange in digital urban planning

Homebrew Website Club Teesside

A meeting for people who are making websites or want to

A little automation ...

Quite apart from the fact that I have barely written a thing here for almost a month, I thought it would be worthwhile to pick a low-hanging fruit. So I followed the very simple instructions at Automate your outgoing webmentions and now my hope is that I have removed one more piece of grit from wh... More this way ...

Next Wednesday: IndieWeb Meetup at Mozart’s Coffee, 6:30pm. For writers, developers, photographers, designers, and anyone who feels we’ve lost something by letting big social networks dominate the web. We can do better. ☕

RSVPed Attending HWC London - 7th August 2019
Demos of personal websites and the opportunity to create, update or experiment on your personal website
Going. Might tinker around with Haunt and IndieWeb!
Reposted a post by Calum Ryan | calumryan.comCalum Ryan | calumryan.com
📢 Have a personal website to work on? / Want to start one? Then drop by at Homebrew Website Club London @ hub by Premier Inn London Covent Garden next week 📅 August 7th ⏰ from 19:00 https://indieweb.org/events/2019-08-07-homebrew-website-club#London / https://hwclondon.co.uk/meetups/20190807...
#indieweb #livecoding
#indieweb #livecoding
Following my last post about automatic updates in Dobrado I've already had to make a few changes to how it works. I realised that if there were any mistakes in a new build, then the problem would be dutifully rolled out to all subscribers without a chance to prevent it.

The fix was to create a second updates feed, this one is available at: https://dobrado.net/testing. Now when an update is built, a post is created in this feed. I still write the post to the original updates feed at https://dobrado.net/updates, but these posts are now saved as a draft with a scheduled publish time. At the moment that time is set to 24 hours later. Of course my publishing tools didn't have a concept of draft posts so I had to add that too... next I need to add UI support to make this feature available to users, at the moment it is only used by the Autoupdate module.

Lastly I added support for removing updates. This needs to happen so that the current version number can be re-used rather than leaving the current broken version in place. Sites that are subscribed to the testing feed will also need to re-apply the update at the current version number, and this is done by the build server removing the matching post in the feed. When the Autoupdate module sees that the post was removed from the feed, it will remove the matching version of the update. This means it will be able to install that version again when it is eventually re-published. The draft post also needs to be removed on the build server, but after that anyone subscribed to the updates feed will never know there was a problem.

So now I have a couple of servers subscribed to the testing feed, and the others that I really don't want to break when I build an update are subscribed to the normal updates feed.
Much easier than regulating to break up Facebook, just regulate to force them to make an API for us to get data in and out. We can break them up ourselves once we have that.

They used to have one, and IndieWeb was doing pretty well with that until FB decided to turn it off. Now *that’s* monopolistic behaviour and anti-trust.

Also on:

Mastodon

Ooo – a website built with Haunt (Guile Scheme static site generator) that is making use of some IndieWeb building blocks.

git.sr.ht/~jakob/blog/tree/master/haunt/jakob/builder/outbox.scm

Very relevant to my interests!

@jakob@mastodon.sdf.org

Homebrew Website Club SF!

Homebrew Website Club retro 1980s-style logo Topics for this week: Featuring: Dietrich Ayala — This one time, at DWebCamp… stories from the Internet Archive’s four-day retreat in Pescadero, California IndieWeb Summit Notes & Videos! Upcoming IndieWebCamps! IndieWebCamp Amsterdam IndieWebCamp Oxford IndieWebCamp Brighton Demos of personal website breakthroughs Create or update your personal web site! Join a community with like-minded interests. Bring friends that want a personal site, or are interested in a healthy, independent web! Any questions? Ask in #indieweb Slack or IRC More information: IndieWeb Wiki Event Page RSVP: post an indie RSVP on your own site!

Aaaaaaaaaaaaaand we live! https://twitch.tv/jackyalcine. Working on https://activitydesk.black.af for about an hour. #indieweb #livecoding #

#indieweb #livecoding #streaming

WPWeekly Episode 361 – Introduction to the IndieWeb With David Shanske

#indieweb #personal-website

A little automation ...

Quite apart from the fact that I have barely written a thing here for almost a month, I thought it would be worthwhile to pick a low-hanging fruit. So I followed the very simple instructions at Automate your outgoing webmentions and now my hope is that I have removed one more piece of grit from wh... More this way ...