While attending IndieWebCamp in Brighton a few weeks ago, a bunch of us were talking about blogging. What is post? What should it contain? What's optional? Someone (probably Jeremy Keith said: A blog post doesn't need a title. In a literal sense, he was wrong. The HTML specification makes it clear that the <title> element […]
While attending IndieWebCamp in Brighton a few weeks ago, a bunch of us were talking about blogging. What is post? What should it contain? What's optional?
In a literal sense, he was wrong. The HTML specification makes it clear that the <title> element is mandatory. All documents have title.
But, in a practical sense, he was right. This blog post has an empty <h1> element - the document might be semantically invalid, it might reduce accessibility, but the post is still available.
A blog post can be a plain text document uploaded to a server. It can be an image hosted on a social network. It can be a voice note shared with your friends.
Title, dates, comments, links, and text are all optional.
No one is policing this.
Go create something which doesn't fit properly with the rest of the world.
🆕 blog! “Caboom! Comment Anywhere, Bring Onto Own Media”
In the IndieWeb movement there's a concept of "POSSE" - Publish Once, Simultaneously Syndicate Elsewhere. You should publish your words, pictures, songs, reviews on your own site. And then you can choose to share them out to where your audience is. Perhaps that's posting the link on Facebook, or a copy of a ph…
What I created while remotely participating at #IndieWebCamp Brighton 2024: wiki-gardened day 1’s BarCamp sessions notes pages, and documented my @-mention @-@-mention autolinking coding improvements I built the Sunday before.
Day 2 of IndieWebCamps is Create Day, where everyone is encouraged to create, make, or build something for their personal website, or the IndieWeb community, or both.
At the start of day 2, everyone is encourage to pick things to make¹. What to make at an IndieWebCamp² can be anything from setting up your personal website, to writing a blog post, redesigning your styling, building new features, helping other participants, or contributing to shared IndieWeb community resources, whether code or content.
Everyone is encouraged to at least pick something they consider easy, that they can do in less than an hour, then a more bold goal, and then perhaps a stretch goal, something challenging that may require collaboration, asking for help, or breaking into smaller steps.
For my "easy" task, I built on what another remote participant, @gregorlove.com completed the night before. gRegor had archived all the IndieWebCamp Brighton Sessions Etherpads onto the wiki, linked from the Schedule page³. gRegor had noted that he didn’t have time to clean-up the pages, e.g. convert and fix Markdown links.
I went through the 13 Session Notes archives and did the following:
converted Markdown links to MediaWiki links
converted indieweb.org (and some services) links to local wiki page links
fixed (some) typos
With some help from @alexsirac.com (@alexture), I figured out how to create a MediaWiki Contributions summary link of my edits:
I point this out to provide an example of an IndieWeb Create Day project that is:
incremental on top of someone else’s work
community contribution rather a personal-focused project
editing and wiki-gardening as valid contributions, not just creating new content
I point this out to illustrate some of the IndieWeb community's recognitions & values in contrast to typical corporate cultures and incentive systems which often only reward:
new innovations (not incremental improvements)
solo (or maybe jointly in a small team) inventions, designs, specs, or implementations
something large, a new service or a big feature, not numerous small edits & fixes
In this regard, the IndieWeb community shares more in common with Wikipedia and similar collaborative communities (despite the #Indie in #IndieWeb), than any corporation.
For my "more bold" goal, I wrote a medium-sized post about the auto-linking improvements I made the Sunday before the IndieWebCamp to my personal website with examples and brief descriptions of the coding changes & improvements.
My stretch goal was to write up a more complete auto-linking specification, based on the research I have done into @-mention @-@-mention user practices (on #Mastodon, other #ActivityPub or #fediverse implementations, and even across #socialMedia silos), as well as how many implementations autolink plain text URLs, domains, and paths.
That stretch goal remains a goal, however I did collect a handful of prior posts on @-mentions which I plan to source for specifying auto-linking and @-mentioning:
I was one of a few remote participants in addition to ~18 in-person participants, the overwhelming majority of overall attendees, who demonstrated something at the end of IndieWebCamp Brighton 2024 day 2. See what everyone else made & demonstrated on Create Day:
For example, you now can follow my blog on Mastodon by searching for "@blog", and you should receive my posts directly in your home stream.
The implementation was fairly easy, I only had some initial issues with the webfinger-URL-redirect, but once that was sorted out, it worked.
But it took me the better part of the afternoon to figure out how the avatar image and header image are supposed to work when the whole site, not a specific author, is the "actor".
The plugin tries to use the "website icon" or "custom logo" for the avatar, and a "custom header" image for the header image. Both images are set with "theme options" via the customizer.
Since I use a homegrown theme here, I never needed the customizer and those options didn't exist, so the fediverse profile fell back to using a default "WordPress" icon for the avatar, and uses no header image.
In the meantime I added the options to my theme, and now have a custom logo and custom header image, but it seems that Mastodon has a very long lasting cache. Although updates to my posts are updated in the timeline immediatly, the profile infos are not.
So, for now I'll sit back and see if and when "my" avatar and desired header image will finally show up in the profile.
In fact, this post here is another try to get the info to sync. :-)
Inspiring mix of perspective expanding and personal talks at border:none (https://border-none.net/@border_none) the past two days. Thanks speakers, volunteers, and especially organizers @marcthiele.com (@marcthiele@marcthiele) and @jkphl.is (@jkphl@jkphl).
Looking forward to the next two days at #IndieWebCamp Nürnberg @tollwerk.de (@tollwerk@tollwerk) of personal site demos, brainstorming sessions, and making, creating, & hacking things from UX to protocols to improve & interconnect our websites, with each other ( #Webmention ), #fediverse ( #BridgyFed & #ActivityPub ), and others ( #POSSE#backfeed ).
Still a few spots if you’re in town or can hop on a train and join us Saturday & Sunday!
If you're attending @marcthiele's and my border:none conference on October 26-27 and are in town anyway, you might be interested to know that @tantek.com@tantek.com and I will also be hosting the first #IndieWebCamp in #Nuremberg since 2018 right after #bono23 (on Saturday and Sunday). Don't miss the chance to join us if you're up for some great conversations and tinkering with your personal site (existing or yet to be created). It's free and will be fun! 🌞
Die IndieWeb-Bewegung hat gerade in den letzten Jahren enorm an Popularität gewonnen. Kein Wunder: Posterous wurde von Twitter gekauft und eingestellt, Google Buzz durch Google Plus ersetzt und MySpace hat seine Blogging-Plattform geschlossen. Alleine mit Geocities wurden 2009 knapp 23 Millionen Seiten unwiderruflich vom Netz genommen. Riskieren Sie keinen weiteren Datenverlust, schließen Sie sich dem IndieWeb an und machen Sie sich unabhängig.
Es freut mich sehr, dass das SCREENGUIDE Magazin im Allgemeinen, und Nicolai im Speziellen, der IndieWeb Idee so viel Platz eingeräumt haben!
Neben meinem Artikel über das IndieWeb, gibt es noch einen kleinen Abschnitt über IndieTech, ein Interview mit Aaron Parecki (einem der vier Gründer des IndieWebCamps) und einen Artikel über Known, DER IndieWeb Platform von Ben Werdmuller (dem Gründer von Elgg).
Ich würde mich diesmal sehr über Feedback freuen… also kaufen! Sofort!