This Week in the IndieWeb is a weekly digest of activities of the IndieWeb community. It contains recent and upcoming events, posts from IndieNews, and a summary of wiki edits, sent out Fridays at 2pm Pacific time.
How to Subscribe
You can subscribe via email here:
The digest currently contains:
- This week's past events, with photo
- Upcoming events in the next two months
- Podcast episodes on Huffduffer tagged #indieweb added this week
- Posts on added this week IndieNews
- New user pages created
- A summary of all new and changed wiki articles
Archives of previous newsletters can be found below.
The newsletter gets the list of upcoming and past events from the events page. Make sure the event has a name, url, and start date, and that those are marked up with microformats2 classes. You can test the page in a parser to make sure the parser finds these fields. Starting with the timestamp from exactly 7d*24h ago, any event that either starts or ends after that date will be included.
For each upcoming and past event that will be included, it will fetch the event URL and look for photos on the page. If there is a microformats2 "photo" property, that will be used.
If there is a summary on the event permalink, it will also be included.
You can add any post to the newsletter by submitting it to IndieNews! You can submit your own posts by adding a u-syndication URL, or you can submit other people's posts by bookmarking them on your site. Full details are available here: https://news.indieweb.org/how-to-submit-a-post
You can add podcast episodes to the newsletter by posting them on Huffduffer and tagging them #indieweb. Any new podcasts added there this week will be included in the newsletter
This week's post is generated on Fridays at 13:30 Pacific Time, and announced in IRC for previewing. At 13:50, the final post is generated, and at 14:00, Mailchimp generates the email from the post on the server, and sends it to all email subscribers, and it is tweeted out from @indiewebcamp. The tweet includes the first photo in the newsletter.
Other things you'd like to see in the weekly summary:
- list pages that have received webmentions this week (in descending order of # of mentions)
- commits to relevant source code repositories (github.com/indieweb, or possibly from a list of source repositories on the wiki)
- new blog posts from community members with p-category=indieweb
- use Census to retrieve h-cards for domains to use their icon and name instead of domain name, e.g.: from/to:
- Suggest Loqi remind us once 12-24 hours earlier
- make some sort of trigger that people can do in IRC that will make Loqi regenerate it after adding to it, otherwise it's like adding things to a black box
Why sent on Friday
Q: Why is "This week in indieweb" sent out on Friday and not on the weekend?
A: Midday Friday is a good day and time to send out "This week in indieweb" for a number of reasons:
- Fridays tend to be slower (in terms of getting things done) so it makes sense to use that time to capture / reflect / broadcast what's been done the rest of the week.
- Lunchtime (Pacific Timezone) on Friday seems like a good time where (many) people in the community may be available to make last minute edits for the weekly summary.
- Friday seems a better day to send it out, especially since it also tweets a link to it, and Saturday evening seems like not the best time to have a tweet be seen.
- Sending it on Friday is also a good encouragement for folks (especially in Europe!) to take the (rest of the) evening off.
What photos are included in the tweet
Twitter allows either exactly 1 gif, or up to 4 photos to be included in a tweet.
If there are any gifs in the newsletter, the most recent one is included in the tweet.
If there are no gifs, then the most recent 4 photos are included.
Table of Contents