After a long time, I reinstalled IndieWeb’s WordPress plug-in – Simple Location. It turned out that it automatically added all the posts to the geographical location of my current location. This is obviously unreasonable, because these posts are written in different places. Before installing the plug-in, posts did not have geographically related metadata. […]

#IndieWeb #WordPress

https://sanguok.com/en/notes/bc22025a18/

时隔蛮久重新装回IndieWeb的WordPress插件——Simple […]

#IndieWeb #WordPress

https://sanguok.com/notes/bc22025a18/

impact on the indie web is measured in meaningful interactions with real people

impact on regular social media is measured in reach and engagement.

The indie-web is de facto the *social* media/web where the social aspect is part of the equation.

Regular google web / meta platforms: publish platform where the curating editor is an algorithm

#socialmedia #indieweb #facebook

Also - I spent most of yesterday sprucing up my #blog design! Went with the newer Norrsken #WordPress theme from Anders Noren, whose themes have to be some of my favorites.

Yes, it's a block theme, which probably takes away some of the small amount of #IndieWeb cred I have (LOL is there such a thing as IndieWeb cred?). After refreshing myself on how to fiddle with block themes, I was able to get it how I wanted it to look. Not too bad if I say so myself.

Own Your Web – Issue 11: Welcome to the IndieWeb • Buttondown https://buttondown.email/ownyourweb/archive/issue-11/ #smallweb #indieweb

看起来WebSu …

看起来WebSub和IndieBlock插件已经配合得很良好了。我在Monocle界面给post点赞后,就被传入、储存为了一条规范的IndieBlock like记录欸

#IndieWeb #WordPress

https://sanguok.com/notes/05d8a5b9e5/

On my blog: Trying on the Indie Web, Part 1 https://john.colagioia.net/blog/2024/03/13/indieweb-1.html - The start of an irregular series where I explore the Indie Web technologies. #blog #indieweb #programming #techtips

#Business #Anniversaries
Marking the web’s 35th birthday · A call for reforming the web to prioritize user rights https://ilo.im/15y8y8

_____
#Web #OpenLetter #Movement #WebCommunity #OpenWeb #IndieWeb #WebEcosystem #WebTechnology #Development #WebDev

#Business #Anniversaries
Marking the web’s 35th birthday · A call for reforming the web to prioritize user rights https://ilo.im/15y8y8

_____
#Web #OpenLetter #Movement #WebCommunity #OpenWeb #IndieWeb #WebEcosystem #WebTechnology #Development #WebDev

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@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:
* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25

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.
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases


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:
* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
* https://tantek.com/2023/014/t4/domain-first-federated-atmention
* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread
#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention


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:
* https://indieweb.org/2024/Brighton/Demos

And read what other participants have blogged about their IndieWebCamp Brighton experience:
* https://roobottom.com/articles/plugging-into-the-indieweb/
* https://adactio.com/journal/20968
* https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/



This is post 13 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
→ 🔮


Glossary:

Create Day
  https://indieweb.org/Create_Day
IndieWebCamp Brighton 2024
  https://indieweb.org/2024/Brighton

References:

¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two
² https://indieweb.org/what_to_make_at_IndieWebCamp
³ https://indieweb.org/2024/Brighton/Schedule#Saturday
#IndieWebCamp #Indie #IndieWeb #Mastodon #ActivityPub #fediverse #socialMedia #autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention #100PostsOfIndieWeb #100Posts
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@todo.eu), I figured out how to create a MediaWiki Contributions summary link of my edits:
* https://indieweb.org/wiki/index.php?title=Special:Contributions&target=Tantek.com&namespace=all&start=2024-03-10&end=2024-03-10&offset=20240310143900&limit=25

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.
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases


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:
* https://tantek.com/2023/011/t1/indieweb-evolving-at-mention
* https://tantek.com/2023/014/t4/domain-first-federated-atmention
* https://tantek.com/2023/018/t1/elevate-indieweb-above-silo
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
* https://tantek.com/2023/109/t2/years-ago-first-federated-indieweb-thread
#autoLink #atDomain #atPath #atMention #atMentions #atat #atAtMention


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:
* https://indieweb.org/2024/Brighton/Demos

And read what other participants have blogged about their IndieWebCamp Brighton experience:
* https://roobottom.com/articles/plugging-into-the-indieweb/
* https://adactio.com/journal/20968
* https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024/



This is post 13 of #100PostsOfIndieWeb. #100Posts

https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
→ 🔮


Glossary:

Create Day
  https://indieweb.org/Create_Day
IndieWebCamp Brighton 2024
  https://indieweb.org/2024/Brighton

References:

¹ https://indieweb.org/IndieWebCamps/Attending#Day_Two
² https://indieweb.org/what_to_make_at_IndieWebCamp
³ https://indieweb.org/2024/Brighton/Schedule#Saturday

Our first tool is live: a simple email newsletter template. The code is free to use and you can build and edit your emails using the @blocksedit visual editor (also for free). https://indieaisle.com/newsletter-template/ #SmallWeb #indieweb #email

Chyrp Lite is the coolest smol #CMS and tumblelogging engine. Has #Webmention support. SQLite and #PHP.

https://chyrplite.net

https://github.com/xenocrat/chyrp-lite/

#indieweb #webdevelopers #webdev #tumblr

I would like to rent a bare metal server and install a simple webserver reserved to static sites (no CGI, php or whatever)?
I could share it and open registration for 1 GB space with a subdomain à la geo/neocities and provide an FTP over TLS and SFTP access.

Are you be interested?

#smolweb #smallweb #indieweb

no, there are already many or better solutions
yes, if totally free
yes, and I'd give a small tip
no, I want be able to use my own domain

I had a fantastic time over the weekend at #IndieWebCamp in Brighton! Lots of great people, interesting discussions, and new ideas.

Whilst it was all fresh, I figured I'd write done some of my thoughts, both on the event as a whole and the topics that were discussed.

A huge thanks to the organisers and the wider #IndieWeb community for making it such a success!

✍️ https://theadhocracy.co.uk/wrote/indiewebcamp-brighton-2024

If you liked Introducing the BOOK my feed URL is https://robertkingett.com/feed/ #RSS #IndieWeb #SmallWeb

Google Drive is hardly #indieweb, but look beyond "corporate = bad" and consider the nature of the relationship. They provide a commodity service: you pay them, they store your files.

Those files are a medium of exchange. If (when?) Google screws around, you can easily move the files to a different storage provider. Switching costs for hosted platforms like Tumblr or Instagram are _far_ higher.