My XTEINK X4 got me reading again. My new X4 Pro arrived last week. Great little device, and the addition of a front light and touch screen make it nearly perfect. Those pogo pins, tho…
{
"type": "entry",
"published": "2026-09-10T04:13:40.445965+00:00",
"url": "https://cleverdevil.io/2026/my-xteink-x4-got-me-reading-again-my-new",
"syndication": [
"https://cleverdevil.club/@jonathan/117244796634982706",
"https://bsky.app/profile/cleverdevil.io/post/3mv56sq6nkr2u"
],
"content": {
"text": "My XTEINK X4 got me reading again. My new X4 Pro arrived last week. Great little device, and the addition of a front light and touch screen make it nearly perfect. Those pogo pins, tho\u2026",
"html": "<p>My XTEINK X4 got me reading again. My new X4 Pro arrived last week. Great little device, and the addition of a front light and touch screen make it nearly perfect. Those pogo pins, tho\u2026</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49508669",
"_source": "10"
}
Finished my re-read of Mistborn era one earlier this week. I had forgotten just how satisfying the ending is. It’s equal parts emotional, beautiful, and surprising. Everything fits together neatly and you’re left with a deep mythology of gods, forces in opposition, and harmony. 🤘🔥
{
"type": "entry",
"published": "2026-09-10T04:10:56.783130+00:00",
"url": "https://cleverdevil.io/2026/finished-my-re-read-of-mistborn-era-one",
"syndication": [
"https://cleverdevil.club/@jonathan/117244785910144585",
"https://bsky.app/profile/cleverdevil.io/post/3mv56nu53xw2c"
],
"content": {
"text": "Finished my re-read of Mistborn era one earlier this week. I had forgotten just how satisfying the ending is. It\u2019s equal parts emotional, beautiful, and surprising. Everything fits together neatly and you\u2019re left with a deep mythology of gods, forces in opposition, and harmony. \ud83e\udd18\ud83d\udd25",
"html": "<p>Finished my re-read of Mistborn era one earlier this week. I had forgotten just how satisfying the ending is. It\u2019s equal parts emotional, beautiful, and surprising. Everything fits together neatly and you\u2019re left with a deep mythology of gods, forces in opposition, and harmony. \ud83e\udd18\ud83d\udd25</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49508670",
"_source": "10"
}
Today’s #WASSUP tip: a search shortcut for saving pages in the Internet Archive’s Wayback Machine.
Yes this is a lot like yesterday’s tip, except for archiving a page, rather than looking it up.
For example if you try looking up a page in the Internet Archive and it’s not there.
Or if you find an “interesting” page, and want to blog it later, you may want to save a copy of it in the Internet Archive as you are seeing it today, because when you look later it may have changed (or gone away).
I used to do this by typing "https://web.archive.org/save/" into the browser address bar and then pasting the link I want to save in the archive.
Again this is not really a “search engine”, however Firefox’s search engine shortcuts simplifies this greatly (less typing).
Here’s how to create a save shortcut for the Internet Archive Wayback Machine:
1. open Firefox Preferences ("Firefox" menu, "Preferences" item)
2. select "🔍 Search" from the left column
3. click the [ + Add search engine ] button
4. enter "Internet Archive Save" into the Search engine name field (without quotes)
5. enter "https://web.archive.org/save/%s" into the URL field (without quotes)
6. enter "ias" into the Keyword field (without quotes)
When viewing a page that I want to save in the Internet Archive:
1. copy its link
2. activate the browser address bar (cmd-L does this in Firefox and Safari)
3. type "ias " (without the quotes)
4. paste the link I had copied earlier, and press return
Wait a few seconds (could take up to a few minutes) and the Internet Archive should save the page and show you the saved version.
If it fails for any reason (happens sometimes), likes takes a while and then displays something like:
"Sorry / Job failed"
You can click the "Return to Save Page Now" link on the page, and try pasting the link one more time into the text input box and pressing return.
If it says something like
"The target server blocks access to [URL]. (HTTP status=403)"
(literally happened to me today)
or some other HTTP status error code (5xx or 4xx), then you can try emailing the IT staff of the site you were trying to archive by emailing "webmaster@" the domain of that URL and perhaps CC: help@ that domain.
E.g. if the URL was https://example.com/some-path then you would email "webmaster@example.com, help@example.com".
With something like:
----
Dear [Domain Name] Webmaster,
Could you check your server configuration and explicitly allow the Internet Archive’s Wayback Machine to make historical archive copies of your pages?
This is important for the history of the open web, and greatly helps journalists, bloggers, and historians.
Please allow their User Agent: "archive.org_bot" to crawl and archive your site. More info on their "archive.org_bot" here: https://archive.org/details/archive.org_bot
Thank you for your consideration!
[sign your name]
----
Replace the two [ bracket phrases ] the domain name of the link you were trying to archive and your name respectively.
Good luck and happy internet archiving!
Previously: https://tantek.com/2026/249/t1/internet-archive-wayback-machine-search-shortcut
This is my sixth #WASSUP #WASSUP2026 post, and fourth useful web tip for September.
#InternetArchive #WaybackMachine #save #searchShortcut #Firefox #FirefoxSearch #archive #archives #tip #webTip #browserTip #webBrowserTip #archiveTip
{
"type": "entry",
"published": "2026-09-07 13:18-0700",
"url": "https://tantek.com/2026/250/t1/saving-pages-internet-archive-wayback-machine",
"category": [
"WASSUP",
"WASSUP2026",
"InternetArchive",
"WaybackMachine",
"save",
"searchShortcut",
"Firefox",
"FirefoxSearch",
"archive",
"archives",
"tip",
"webTip",
"browserTip",
"webBrowserTip",
"archiveTip"
],
"content": {
"text": "Today\u2019s #WASSUP tip: a search shortcut for saving pages in the Internet Archive\u2019s Wayback Machine.\n\nYes this is a lot like yesterday\u2019s tip, except for archiving a page, rather than looking it up. \n\nFor example if you try looking up a page in the Internet Archive and it\u2019s not there.\n\nOr if you find an \u201cinteresting\u201d page, and want to blog it later, you may want to save a copy of it in the Internet Archive as you are seeing it today, because when you look later it may have changed (or gone away).\n\nI used to do this by typing \"https://web.archive.org/save/\" into the browser address bar and then pasting the link I want to save in the archive.\n\nAgain this is not really a \u201csearch engine\u201d, however Firefox\u2019s search engine shortcuts simplifies this greatly (less typing).\n\nHere\u2019s how to create a save shortcut for the Internet Archive Wayback Machine:\n\n1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)\n2. select \"\ud83d\udd0d Search\" from the left column\n3. click the [ + Add search engine ] button\n4. enter \"Internet Archive Save\" into the Search engine name field (without quotes)\n5. enter \"https://web.archive.org/save/%s\" into the URL field (without quotes)\n6. enter \"ias\" into the Keyword field (without quotes)\n\nWhen viewing a page that I want to save in the Internet Archive:\n\n1. copy its link\n2. activate the browser address bar (cmd-L does this in Firefox and Safari)\n3. type \"ias \" (without the quotes)\n4. paste the link I had copied earlier, and press return\n\nWait a few seconds (could take up to a few minutes) and the Internet Archive should save the page and show you the saved version.\n\nIf it fails for any reason (happens sometimes), likes takes a while and then displays something like:\n\n\"Sorry / Job failed\"\n\nYou can click the \"Return to Save Page Now\" link on the page, and try pasting the link one more time into the text input box and pressing return.\n\nIf it says something like\n\n\"The target server blocks access to [URL]. (HTTP status=403)\"\n\n(literally happened to me today)\n\nor some other HTTP status error code (5xx or 4xx), then you can try emailing the IT staff of the site you were trying to archive by emailing \"webmaster@\" the domain of that URL and perhaps CC: help@ that domain.\n\nE.g. if the URL was https://example.com/some-path then you would email \"webmaster@example.com, help@example.com\".\n\nWith something like:\n\n----\n\nDear [Domain Name] Webmaster, \n\nCould you check your server configuration and explicitly allow the Internet Archive\u2019s Wayback Machine to make historical archive copies of your pages?\n\nThis is important for the history of the open web, and greatly helps journalists, bloggers, and historians.\n\nPlease allow their User Agent: \"archive.org_bot\" to crawl and archive your site. More info on their \"archive.org_bot\" here: https://archive.org/details/archive.org_bot\n\nThank you for your consideration!\n\n[sign your name]\n\n----\n\nReplace the two [ bracket phrases ] the domain name of the link you were trying to archive and your name respectively.\n\nGood luck and happy internet archiving!\n\nPreviously: https://tantek.com/2026/249/t1/internet-archive-wayback-machine-search-shortcut\n\nThis is my sixth #WASSUP #WASSUP2026 post, and fourth useful web tip for September.\n\n#InternetArchive #WaybackMachine #save #searchShortcut #Firefox #FirefoxSearch #archive #archives #tip #webTip #browserTip #webBrowserTip #archiveTip",
"html": "Today\u2019s #<span class=\"p-category\">WASSUP</span> tip: a search shortcut for saving pages in the Internet Archive\u2019s Wayback Machine.<br /><br />Yes this is a lot like yesterday\u2019s tip, except for archiving a page, rather than looking it up. <br /><br />For example if you try looking up a page in the Internet Archive and it\u2019s not there.<br /><br />Or if you find an \u201cinteresting\u201d page, and want to blog it later, you may want to save a copy of it in the Internet Archive as you are seeing it today, because when you look later it may have changed (or gone away).<br /><br />I used to do this by typing \"https://web.archive.org/save/\" into the browser address bar and then pasting the link I want to save in the archive.<br /><br />Again this is not really a \u201csearch engine\u201d, however Firefox\u2019s search engine shortcuts simplifies this greatly (less typing).<br /><br />Here\u2019s how to create a save shortcut for the Internet Archive Wayback Machine:<br /><br />1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)<br />2. select \"\ud83d\udd0d Search\" from the left column<br />3. click the [ + Add search engine ] button<br />4. enter \"Internet Archive Save\" into the Search engine name field (without quotes)<br />5. enter \"https://web.archive.org/save/%s\" into the URL field (without quotes)<br />6. enter \"ias\" into the Keyword field (without quotes)<br /><br />When viewing a page that I want to save in the Internet Archive:<br /><br />1. copy its link<br />2. activate the browser address bar (cmd-L does this in Firefox and Safari)<br />3. type \"ias \" (without the quotes)<br />4. paste the link I had copied earlier, and press return<br /><br />Wait a few seconds (could take up to a few minutes) and the Internet Archive should save the page and show you the saved version.<br /><br />If it fails for any reason (happens sometimes), likes takes a while and then displays something like:<br /><br />\"Sorry / Job failed\"<br /><br />You can click the \"Return to Save Page Now\" link on the page, and try pasting the link one more time into the text input box and pressing return.<br /><br />If it says something like<br /><br />\"The target server blocks access to [URL]. (HTTP status=403)\"<br /><br />(literally happened to me today)<br /><br />or some other HTTP status error code (5xx or 4xx), then you can try emailing the IT staff of the site you were trying to archive by emailing \"webmaster@\" the domain of that URL and perhaps CC: help@ that domain.<br /><br />E.g. if the URL was <a href=\"https://example.com/some-path\">https://example.com/some-path</a> then you would email \"webmaster<a href=\"https://example.com\">@example.com</a>, help<a href=\"https://example.com\">@example.com</a>\".<br /><br />With something like:<br /><br />----<br /><br />Dear [Domain Name] Webmaster, <br /><br />Could you check your server configuration and explicitly allow the Internet Archive\u2019s Wayback Machine to make historical archive copies of your pages?<br /><br />This is important for the history of the open web, and greatly helps journalists, bloggers, and historians.<br /><br />Please allow their User Agent: \"archive.org_bot\" to crawl and archive your site. More info on their \"archive.org_bot\" here: <a href=\"https://archive.org/details/archive.org_bot\">https://archive.org/details/archive.org_bot</a><br /><br />Thank you for your consideration!<br /><br />[sign your name]<br /><br />----<br /><br />Replace the two [ bracket phrases ] the domain name of the link you were trying to archive and your name respectively.<br /><br />Good luck and happy internet archiving!<br /><br />Previously: <a href=\"https://tantek.com/2026/249/t1/internet-archive-wayback-machine-search-shortcut\">https://tantek.com/2026/249/t1/internet-archive-wayback-machine-search-shortcut</a><br /><br />This is my sixth #<span class=\"p-category\">WASSUP</span> #<span class=\"p-category\">WASSUP2026</span> post, and fourth useful web tip for September.<br /><br />#<span class=\"p-category\">InternetArchive</span> #<span class=\"p-category\">WaybackMachine</span> #<span class=\"p-category\">save</span> #<span class=\"p-category\">searchShortcut</span> #<span class=\"p-category\">Firefox</span> #<span class=\"p-category\">FirefoxSearch</span> #<span class=\"p-category\">archive</span> #<span class=\"p-category\">archives</span> #<span class=\"p-category\">tip</span> #<span class=\"p-category\">webTip</span> #<span class=\"p-category\">browserTip</span> #<span class=\"p-category\">webBrowserTip</span> #<span class=\"p-category\">archiveTip</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49483071",
"_source": "2460"
}
Hey San Diego, come out to a Mutual Aid Comedy Show on September 19th! All proceeds benefit We All We Got SD.
Lineup: Shannon Hardy, Geoff Grooms, Max Kerwien, Pedro Martinez, Lauren Gural.
Info/tickets and original Instagram post.
{
"type": "entry",
"published": "2026-09-06 20:22-0700",
"url": "https://gregorlove.com/2026/09/hey-san-diego/",
"category": [
"comedy",
"SanDiego",
"MutualAid"
],
"syndication": [
"https://bsky.app/profile/gregorlove.com/post/3muvktgnjhs2n"
],
"content": {
"text": "Hey San Diego, come out to a Mutual Aid Comedy Show on September 19th! All proceeds benefit We All We Got SD.\n\nLineup: Shannon Hardy, Geoff Grooms, Max Kerwien, Pedro Martinez, Lauren Gural.\n\nInfo/tickets and original Instagram post.",
"html": "<p>Hey San Diego, come out to a Mutual Aid Comedy Show on September 19th! All proceeds benefit <a class=\"h-card\" href=\"https://weallwegotsd.com/\">We All We Got SD</a>.</p>\n\n<p>Lineup: Shannon Hardy, Geoff Grooms, Max Kerwien, Pedro Martinez, Lauren Gural.</p>\n\n<p><a href=\"https://events.humanitix.com/haiders-mutual-aid-comedy-show-sd\">Info/tickets</a> and <a href=\"https://www.instagram.com/p/DcuDVvuS-jq/\">original Instagram post</a>.</p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "note",
"_id": "49474322",
"_source": "95"
}
Today’s #WASSUP tip: a search shortcut for looking up pages in the Internet Archive’s Wayback Machine.
Ever click on a link for an article or photo and it’s not found (404), or redirects to a home page, or otherwise is not what you expect?
The Internet Archive’s Wayback Machine archives webpages (that allow it) and quite often you can lookup broken links in the archive.
I often do this by typing "https://web.archive.org/web/" into the browser address bar and then pasting the link I want to lookup, because I know some of the Internet Archive’s URL patterns.
Though it’s not really a “search engine”, I realized I could use the search engine shortcuts feature of Firefox to simplify this greatly.
Here’s how to create a search shortcut for the Internet Archive Wayback Machine:
1. open Firefox Preferences ("Firefox" menu, "Preferences" item)
2. select "🔍 Search" from the left column
3. click the [ + Add search engine ] button
4. enter "Internet Archive" into the Search engine name field (without quotes)
5. enter "https://web.archive.org/web/%s" into the URL field (without quotes)
6. enter "ia" into the Keyword field (without quotes)
Now if a link I follow fails to load (404) or is otherwise broken, I can:
1. copy that link (I may have to go back to the previous page and right-click choose "Copy Link")
2. activate the browser address bar (cmd-L does this in Firefox and Safari)
3. type "ia " (without the quotes)
4. paste the link I had copied earlier, and press return
Presto, an Internet Archive result for that link.
If you’re a frequent user of the Wayback Machine, hopefully this will save you some time.
And if not, try it anyway for the next time you click on a link and it seems broken.
This is my fifth #WASSUP #WASSUP2026 post, and third useful web tip for September.
#InternArchive #WaybackMachine #search #searchShortcut #Firefox #FirefoxSearch #searchEngine #archive #archives #PageNotFound #404 #404Error #Error404 #tip #webTip #browserTip #webBrowserTip #searchTip
{
"type": "entry",
"published": "2026-09-06 15:11-0700",
"url": "https://tantek.com/2026/249/t1/internet-archive-wayback-machine-search-shortcut",
"category": [
"WASSUP",
"WASSUP2026",
"InternArchive",
"WaybackMachine",
"search",
"searchShortcut",
"Firefox",
"FirefoxSearch",
"searchEngine",
"archive",
"archives",
"PageNotFound",
"404",
"404Error",
"Error404",
"tip",
"webTip",
"browserTip",
"webBrowserTip",
"searchTip"
],
"content": {
"text": "Today\u2019s #WASSUP tip: a search shortcut for looking up pages in the Internet Archive\u2019s Wayback Machine.\n\nEver click on a link for an article or photo and it\u2019s not found (404), or redirects to a home page, or otherwise is not what you expect?\n\nThe Internet Archive\u2019s Wayback Machine archives webpages (that allow it) and quite often you can lookup broken links in the archive.\n\nI often do this by typing \"https://web.archive.org/web/\" into the browser address bar and then pasting the link I want to lookup, because I know some of the Internet Archive\u2019s URL patterns.\n\nThough it\u2019s not really a \u201csearch engine\u201d, I realized I could use the search engine shortcuts feature of Firefox to simplify this greatly.\n\nHere\u2019s how to create a search shortcut for the Internet Archive Wayback Machine:\n\n1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)\n2. select \"\ud83d\udd0d Search\" from the left column\n3. click the [ + Add search engine ] button\n4. enter \"Internet Archive\" into the Search engine name field (without quotes)\n5. enter \"https://web.archive.org/web/%s\" into the URL field (without quotes)\n6. enter \"ia\" into the Keyword field (without quotes)\n\nNow if a link I follow fails to load (404) or is otherwise broken, I can:\n\n1. copy that link (I may have to go back to the previous page and right-click choose \"Copy Link\")\n2. activate the browser address bar (cmd-L does this in Firefox and Safari)\n3. type \"ia \" (without the quotes)\n4. paste the link I had copied earlier, and press return\n\nPresto, an Internet Archive result for that link.\n\nIf you\u2019re a frequent user of the Wayback Machine, hopefully this will save you some time.\n\nAnd if not, try it anyway for the next time you click on a link and it seems broken.\n\nThis is my fifth #WASSUP #WASSUP2026 post, and third useful web tip for September.\n\n#InternArchive #WaybackMachine #search #searchShortcut #Firefox #FirefoxSearch #searchEngine #archive #archives #PageNotFound #404 #404Error #Error404 #tip #webTip #browserTip #webBrowserTip #searchTip",
"html": "Today\u2019s #<span class=\"p-category\">WASSUP</span> tip: a search shortcut for looking up pages in the Internet Archive\u2019s Wayback Machine.<br /><br />Ever click on a link for an article or photo and it\u2019s not found (404), or redirects to a home page, or otherwise is not what you expect?<br /><br />The Internet Archive\u2019s Wayback Machine archives webpages (that allow it) and quite often you can lookup broken links in the archive.<br /><br />I often do this by typing \"https://web.archive.org/web/\" into the browser address bar and then pasting the link I want to lookup, because I know some of the Internet Archive\u2019s URL patterns.<br /><br />Though it\u2019s not really a \u201csearch engine\u201d, I realized I could use the search engine shortcuts feature of Firefox to simplify this greatly.<br /><br />Here\u2019s how to create a search shortcut for the Internet Archive Wayback Machine:<br /><br />1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)<br />2. select \"\ud83d\udd0d Search\" from the left column<br />3. click the [ + Add search engine ] button<br />4. enter \"Internet Archive\" into the Search engine name field (without quotes)<br />5. enter \"https://web.archive.org/web/%s\" into the URL field (without quotes)<br />6. enter \"ia\" into the Keyword field (without quotes)<br /><br />Now if a link I follow fails to load (404) or is otherwise broken, I can:<br /><br />1. copy that link (I may have to go back to the previous page and right-click choose \"Copy Link\")<br />2. activate the browser address bar (cmd-L does this in Firefox and Safari)<br />3. type \"ia \" (without the quotes)<br />4. paste the link I had copied earlier, and press return<br /><br />Presto, an Internet Archive result for that link.<br /><br />If you\u2019re a frequent user of the Wayback Machine, hopefully this will save you some time.<br /><br />And if not, try it anyway for the next time you click on a link and it seems broken.<br /><br />This is my fifth #<span class=\"p-category\">WASSUP</span> #<span class=\"p-category\">WASSUP2026</span> post, and third useful web tip for September.<br /><br />#<span class=\"p-category\">InternArchive</span> #<span class=\"p-category\">WaybackMachine</span> #<span class=\"p-category\">search</span> #<span class=\"p-category\">searchShortcut</span> #<span class=\"p-category\">Firefox</span> #<span class=\"p-category\">FirefoxSearch</span> #<span class=\"p-category\">searchEngine</span> #<span class=\"p-category\">archive</span> #<span class=\"p-category\">archives</span> #<span class=\"p-category\">PageNotFound</span> #<span class=\"p-category\">404</span> #<span class=\"p-category\">404Error</span> #<span class=\"p-category\">Error404</span> #<span class=\"p-category\">tip</span> #<span class=\"p-category\">webTip</span> #<span class=\"p-category\">browserTip</span> #<span class=\"p-category\">webBrowserTip</span> #<span class=\"p-category\">searchTip</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49472904",
"_source": "2460"
}
Kimi Antonelli is absolutely incredible. One of the best drives I’ve ever seen. #F1
{
"type": "entry",
"published": "2026-09-06T22:36:10.379479+00:00",
"url": "https://cleverdevil.io/2026/kimi-antonelli-is-absolutely-incredible",
"syndication": [
"https://cleverdevil.club/@jonathan/117226482595461400",
"https://bsky.app/profile/cleverdevil.io/post/3muv2kht2ag2n"
],
"content": {
"text": "Kimi Antonelli is absolutely incredible. One of the best drives I\u2019ve ever seen. #F1",
"html": "<p>Kimi Antonelli is absolutely incredible. One of the best drives I\u2019ve ever seen. #F1</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49472681",
"_source": "10"
}
{
"type": "entry",
"published": "2026-09-05T17:10:12-07:00",
"url": "https://aaronparecki.com/2026/09/05/25/",
"syndication": [
"https://www.swarmapp.com/user/59164/checkin/6a9caf644f7f9f1ea250ef2d"
],
"content": {
"text": "Battery drop off"
},
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"checkin": {
"type": "card",
"name": "O'Reilly Auto Parts",
"latitude": "45.522406",
"longitude": "-122.660345",
"url": "https://foursquare.com/v/4d66c97d83865481bb0ffc53"
},
"post-type": "checkin",
"_id": "49464326",
"_source": "16"
}
{
"type": "entry",
"published": "2026-09-05T15:09:03-07:00",
"url": "https://aaronparecki.com/2026/09/05/18/",
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/a6812a3c71b33a12896367cd416de27fb25cafa3517b2d4d31b2676928b0390e.jpg"
],
"syndication": [
"https://www.swarmapp.com/user/59164/checkin/6a9c92ff0f742e5c8b64d4f0"
],
"name": "at Community Warehouse",
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"checkin": {
"type": "card",
"name": "Community Warehouse",
"latitude": "45.551788",
"longitude": "-122.662",
"url": "https://foursquare.com/v/4f304b95e4b0ccb915d053e9"
},
"post-type": "checkin",
"_id": "49463740",
"_source": "16"
}
{
"type": "entry",
"published": "2026-09-05T11:45:26-07:00",
"url": "https://aaronparecki.com/2026/09/05/8/",
"photo": [
"https://aperture-media.p3k.io/aaronparecki.com/a40e704e8131cefca88ee7d06aae06dbb9f88939448f10469e19a786828951fc.jpg"
],
"syndication": [
"https://www.swarmapp.com/user/59164/checkin/6a9c6346ce2b411fed39a7f4"
],
"name": "at Community Warehouse",
"author": {
"type": "card",
"name": "Aaron Parecki",
"url": "https://aaronparecki.com/",
"photo": "https://aperture-media.p3k.io/aaronparecki.com/41061f9de825966faa22e9c42830e1d4a614a321213b4575b9488aa93f89817a.jpg"
},
"checkin": {
"type": "card",
"name": "Community Warehouse",
"latitude": "45.551788",
"longitude": "-122.662",
"url": "https://foursquare.com/v/4f304b95e4b0ccb915d053e9"
},
"post-type": "checkin",
"_id": "49462604",
"_source": "16"
}
So I think Miami is going to be good at football this year.
{
"type": "entry",
"published": "2026-09-05T06:01:00-07:00",
"url": "https://cleverdevil.io/2026/so-i-think-miami-is-going-to-be-good-at",
"syndication": [
"https://cleverdevil.club/@jonathan/117216911038807121",
"https://bsky.app/profile/cleverdevil.io/post/3muqsjthqbj2j"
],
"content": {
"text": "So I think Miami is going to be good at football this year.",
"html": "<p>So I think Miami is going to be good at football this year.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49457525",
"_source": "10"
}
Miami better beat Stanford by six scores to redeem week one…
{
"type": "entry",
"published": "2026-09-04T06:40:35.910793+00:00",
"url": "https://cleverdevil.io/2026/miami-better-beat-stanford-by-six-scores",
"syndication": [
"https://cleverdevil.club/@jonathan/117211400501548098",
"https://bsky.app/profile/cleverdevil.io/post/3muoe7whxih2d"
],
"content": {
"text": "Miami better beat Stanford by six scores to redeem week one\u2026",
"html": "<p>Miami better beat Stanford by six scores to redeem week one\u2026</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49449000",
"_source": "10"
}
Bring back Paul Johnson, you cowards.
{
"type": "entry",
"published": "2026-09-04T06:39:22.232608+00:00",
"url": "https://cleverdevil.io/2026/bring-back-paul-johnson-you-cowards",
"syndication": [
"https://cleverdevil.club/@jonathan/117211395676563650",
"https://bsky.app/profile/cleverdevil.io/post/3muoe5qc64o2k"
],
"content": {
"text": "Bring back Paul Johnson, you cowards.",
"html": "<p>Bring back Paul Johnson, you cowards.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49449001",
"_source": "10"
}
The #Blaugust 2026 blogging challenge had a nice set of awards this year based on reaching a certain number of posts published:
* 1* — Newbie Blogger. *if it was your first time doing Blaugust
* 5+ — Bronze
* 15+ — Silver
* 25+ — Gold
* 31+ — Rainbow Diamond
From https://nerdgirlthoughts.game.blog/2026/07/15/blaugust-2026-is-coming/.
These levels, and the total for the duration (rather than one per day) made the challenge more inviting, accessible, and fun, removing (most of) the stress of a typical daily challenge for a month.
When I started the Web And Standards September Useful Posts (#WASSUP) blogging challenge, I said it was similar to Blaugust and noted “30 posts during the month of September”. While I adopted Blaugust’s total posts for the duration (rather than daily) aspect, I meant to include such levels too.
James (@jamesg.blog) reminded me of this in his first WASSUP post yesterday:
* https://jamesg.blog/2026/09/02/hide-on-desktop-mobile-css
and noted explicitly:
“I am not planning to write every day about web development per the challenge, but I will try my best to share a few HTML and CSS tips throughout the month!”
After a bit of brainstorming in the #indieweb cafe channel and some further thoughts, again, inspired by the Blaugust levels, here are the #WASSUP2026 levels to start with:
* 1 ⭐️ Starter. Congrats on starting the challenge!
* 5 ✨ Weekly Tipster. Post once per week, or at least 5 times for the duration.
* 8 🕸 Weekends Weaver. Post every weekend day, or at least that same number, 8 times.
(Thanks to James for this suggestion!)
* 22 ❇️ Weekdays Wizard. Post every weekday, or at least that same number, 22 times.
* 30 💠 Superbly Useful. Post at least 30 times during the month.
I’ve updated the original post to include these awards, and they’re all self-assessed.
https://tantek.com/2026/244/t1/september-blogging-challenge-wassup
Let’s see your useful posts about the web or open web standards!
{
"type": "entry",
"published": "2026-09-03 18:37-0700",
"url": "https://tantek.com/2026/246/t2/awards-levels-wassup-challenge",
"category": [
"Blaugust",
"indieweb",
"WASSUP2026"
],
"content": {
"text": "The #Blaugust 2026 blogging challenge had a nice set of awards this year based on reaching a certain number of posts published:\n* 1* \u2014 Newbie Blogger. *if it was your first time doing Blaugust \n* 5+ \u2014 Bronze\n* 15+ \u2014 Silver\n* 25+ \u2014 Gold\n* 31+ \u2014 Rainbow Diamond\nFrom https://nerdgirlthoughts.game.blog/2026/07/15/blaugust-2026-is-coming/.\n\nThese levels, and the total for the duration (rather than one per day) made the challenge more inviting, accessible, and fun, removing (most of) the stress of a typical daily challenge for a month.\n\nWhen I started the Web And Standards September Useful Posts (#WASSUP) blogging challenge, I said it was similar to Blaugust and noted \u201c30 posts during the month of September\u201d. While I adopted Blaugust\u2019s total posts for the duration (rather than daily) aspect, I meant to include such levels too.\n\nJames (@jamesg.blog) reminded me of this in his first WASSUP post yesterday:\n* https://jamesg.blog/2026/09/02/hide-on-desktop-mobile-css\nand noted explicitly:\n\n\u201cI am not planning to write every day about web development per the challenge, but I will try my best to share a few HTML and CSS tips throughout the month!\u201d\n\nAfter a bit of brainstorming in the #indieweb cafe channel and some further thoughts, again, inspired by the Blaugust levels, here are the #WASSUP2026 levels to start with:\n\n* 1 \u2b50\ufe0f Starter. Congrats on starting the challenge!\n* 5 \u2728 Weekly Tipster. Post once per week, or at least 5 times for the duration.\n* 8 \ud83d\udd78 Weekends Weaver. Post every weekend day, or at least that same number, 8 times.\n\u00a0 (Thanks to James for this suggestion!)\n* 22 \u2747\ufe0f Weekdays Wizard. Post every weekday, or at least that same number, 22 times.\n* 30 \ud83d\udca0 Superbly Useful. Post at least 30 times during the month.\n\nI\u2019ve updated the original post to include these awards, and they\u2019re all self-assessed.\n\nhttps://tantek.com/2026/244/t1/september-blogging-challenge-wassup\n\nLet\u2019s see your useful posts about the web or open web standards!",
"html": "The #<span class=\"p-category\">Blaugust</span> 2026 blogging challenge had a nice set of awards this year based on reaching a certain number of posts published:<br />* 1* \u2014 Newbie Blogger. *if it was your first time doing Blaugust <br />* 5+ \u2014 Bronze<br />* 15+ \u2014 Silver<br />* 25+ \u2014 Gold<br />* 31+ \u2014 Rainbow Diamond<br />From <a href=\"https://nerdgirlthoughts.game.blog/2026/07/15/blaugust-2026-is-coming/\">https://nerdgirlthoughts.game.blog/2026/07/15/blaugust-2026-is-coming/</a>.<br /><br />These levels, and the total for the duration (rather than one per day) made the challenge more inviting, accessible, and fun, removing (most of) the stress of a typical daily challenge for a month.<br /><br />When I started the Web And Standards September Useful Posts (#WASSUP) blogging challenge, I said it was similar to Blaugust and noted \u201c30 posts during the month of September\u201d. While I adopted Blaugust\u2019s total posts for the duration (rather than daily) aspect, I meant to include such levels too.<br /><br />James (<a href=\"https://jamesg.blog\">@jamesg.blog</a>) reminded me of this in his first WASSUP post yesterday:<br />* <a href=\"https://jamesg.blog/2026/09/02/hide-on-desktop-mobile-css\">https://jamesg.blog/2026/09/02/hide-on-desktop-mobile-css</a><br />and noted explicitly:<br /><br />\u201cI am not planning to write every day about web development per the challenge, but I will try my best to share a few HTML and CSS tips throughout the month!\u201d<br /><br />After a bit of brainstorming in the #<span class=\"p-category\">indieweb</span> cafe channel and some further thoughts, again, inspired by the Blaugust levels, here are the #<span class=\"p-category\">WASSUP2026</span> levels to start with:<br /><br />* 1 \u2b50\ufe0f Starter. Congrats on starting the challenge!<br />* 5 \u2728 Weekly Tipster. Post once per week, or at least 5 times for the duration.<br />* 8 \ud83d\udd78 Weekends Weaver. Post every weekend day, or at least that same number, 8 times.<br />\u00a0 (Thanks to James for this suggestion!)<br />* 22 \u2747\ufe0f Weekdays Wizard. Post every weekday, or at least that same number, 22 times.<br />* 30 \ud83d\udca0 Superbly Useful. Post at least 30 times during the month.<br /><br />I\u2019ve updated the original post to include these awards, and they\u2019re all self-assessed.<br /><br /><a href=\"https://tantek.com/2026/244/t1/september-blogging-challenge-wassup\">https://tantek.com/2026/244/t1/september-blogging-challenge-wassup</a><br /><br />Let\u2019s see your useful posts about the web or open web standards!"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49448308",
"_source": "2460"
}
How to add MapQuest with a search shortcut to your Firefox:
1. open Firefox Preferences ("Firefox" menu, "Preferences" item)
2. select "🔍 Search" from the left column
3. click the [ + Add search engine ] button
4. enter "MapQuest" into the Search engine name field (without quotes)
5. enter "https://www.mapquest.com/search/%s" into the URL field (without quotes)
6. enter "m" into the Keyword field (without quotes)
If you already had an "m" search shortcut for another search engine, you may need to first edit that search engine (click the pencil ✏️ icon next to it) in the list of "Additional search engines", and remove/replace the existing "m" with something else.
This is my third #WASSUP #WASSUP2026 post, and second useful web tip for September.
#MapQuest #search #searchShortcut #Firefox #FirefoxSearch #searchEngine #map #maps #GoogleMaps #AppleMaps #LakeOntario #tip #webTip #browserTip #webBrowserTip #searchTip
{
"type": "entry",
"published": "2026-09-03 16:13-0700",
"url": "https://tantek.com/2026/246/t1/add-mapquest-search-shortcut-firefox",
"category": [
"WASSUP",
"WASSUP2026",
"MapQuest",
"search",
"searchShortcut",
"Firefox",
"FirefoxSearch",
"searchEngine",
"map",
"maps",
"GoogleMaps",
"AppleMaps",
"LakeOntario",
"tip",
"webTip",
"browserTip",
"webBrowserTip",
"searchTip"
],
"content": {
"text": "How to add MapQuest with a search shortcut to your Firefox:\n\n1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)\n2. select \"\ud83d\udd0d Search\" from the left column\n3. click the [ + Add search engine ] button\n4. enter \"MapQuest\" into the Search engine name field (without quotes)\n5. enter \"https://www.mapquest.com/search/%s\" into the URL field (without quotes)\n6. enter \"m\" into the Keyword field (without quotes)\n\nIf you already had an \"m\" search shortcut for another search engine, you may need to first edit that search engine (click the pencil \u270f\ufe0f icon next to it) in the list of \"Additional search engines\", and remove/replace the existing \"m\" with something else.\n\nThis is my third #WASSUP #WASSUP2026 post, and second useful web tip for September.\n\n#MapQuest #search #searchShortcut #Firefox #FirefoxSearch #searchEngine #map #maps #GoogleMaps #AppleMaps #LakeOntario #tip #webTip #browserTip #webBrowserTip #searchTip",
"html": "How to add MapQuest with a search shortcut to your Firefox:<br /><br />1. open Firefox Preferences (\"Firefox\" menu, \"Preferences\" item)<br />2. select \"\ud83d\udd0d Search\" from the left column<br />3. click the [ + Add search engine ] button<br />4. enter \"MapQuest\" into the Search engine name field (without quotes)<br />5. enter \"https://www.mapquest.com/search/%s\" into the URL field (without quotes)<br />6. enter \"m\" into the Keyword field (without quotes)<br /><br />If you already had an \"m\" search shortcut for another search engine, you may need to first edit that search engine (click the pencil \u270f\ufe0f icon next to it) in the list of \"Additional search engines\", and remove/replace the existing \"m\" with something else.<br /><br />This is my third #<span class=\"p-category\">WASSUP</span> #<span class=\"p-category\">WASSUP2026</span> post, and second useful web tip for September.<br /><br />#<span class=\"p-category\">MapQuest</span> #<span class=\"p-category\">search</span> #<span class=\"p-category\">searchShortcut</span> #<span class=\"p-category\">Firefox</span> #<span class=\"p-category\">FirefoxSearch</span> #<span class=\"p-category\">searchEngine</span> #<span class=\"p-category\">map</span> #<span class=\"p-category\">maps</span> #<span class=\"p-category\">GoogleMaps</span> #<span class=\"p-category\">AppleMaps</span> #<span class=\"p-category\">LakeOntario</span> #<span class=\"p-category\">tip</span> #<span class=\"p-category\">webTip</span> #<span class=\"p-category\">browserTip</span> #<span class=\"p-category\">webBrowserTip</span> #<span class=\"p-category\">searchTip</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49445642",
"_source": "2460"
}
If you find a wiki page seemingly from a MediaWiki, but without a "View History" link, here’s a tip for how to find it.
Example: the old HTML Working Group (WG) wiki at W3C
* https://www.w3.org/html/wg/wiki/Main_Page
Note the warning at the top: “This wiki has been archived and is now read-only.”
Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group’s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.
Note also the lack of a "View History" link as a tab top right adjacent to the content area (or anywhere else on the page).
This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.
Here is how to find such a page’s history:
1. Find the “last modified” date in the footer and note the year, month, day.
2. Check for the page in the Internet Archive, e.g. prepend its URL with "https://web.archive.org/web/"
3. If there’s (presumably) still no "View History" link, look at the year month day numbers in the URL — the first 8 digits after "/web/" E.g. "20260512" for this page as of today.
4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. "20150623" for this page. Press return to load that.
5. You may have to "close toolbar" the (x) in the top right of the page content.
6. Note the "View History" link, click it.
Presto, view history on a former MediaWiki page that’s been archived to static HTML.
This is my second #WASSUP #WASSUP2026 post, and first useful web tip.
#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified
{
"type": "entry",
"published": "2026-09-02 21:30-0700",
"url": "https://tantek.com/2026/245/t1/page-mediawiki-view-history-tip",
"category": [
"WASSUP",
"WASSUP2026",
"wiki",
"wikiPage",
"MediaWiki",
"ViewHistory",
"W3C",
"HTMLWG",
"wikiArchived",
"readOnly",
"staticHTML",
"InternetArchive",
"WaybackMachine",
"LastModified"
],
"content": {
"text": "If you find a wiki page seemingly from a MediaWiki, but without a \"View History\" link, here\u2019s a tip for how to find it.\n\nExample: the old HTML Working Group (WG) wiki at W3C\n* https://www.w3.org/html/wg/wiki/Main_Page\n\nNote the warning at the top: \u201cThis wiki has been archived and is now read-only.\u201d\n\nAside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group\u2019s wiki, and the top level general W3C wiki (http://www.w3.org/wiki). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.\n\nNote also the lack of a \"View History\" link as a tab top right adjacent to the content area (or anywhere else on the page).\n\nThis is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.\n\nHere is how to find such a page\u2019s history:\n1. Find the \u201clast modified\u201d date in the footer and note the year, month, day.\n2. Check for the page in the Internet Archive, e.g. prepend its URL with \"https://web.archive.org/web/\"\n3. If there\u2019s (presumably) still no \"View History\" link, look at the year month day numbers in the URL \u2014 the first 8 digits after \"/web/\" E.g. \"20260512\" for this page as of today.\n4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. \"20150623\" for this page. Press return to load that.\n5. You may have to \"close toolbar\" the (x) in the top right of the page content.\n6. Note the \"View History\" link, click it.\n\nPresto, view history on a former MediaWiki page that\u2019s been archived to static HTML.\n\nThis is my second #WASSUP #WASSUP2026 post, and first useful web tip.\n\n#wiki #wikiPage #MediaWiki #ViewHistory #W3C #HTMLWG #wikiArchived #readOnly #staticHTML #InternetArchive #WaybackMachine #LastModified",
"html": "If you find a wiki page seemingly from a MediaWiki, but without a \"View History\" link, here\u2019s a tip for how to find it.<br /><br />Example: the old HTML Working Group (WG) wiki at W3C<br />* <a href=\"https://www.w3.org/html/wg/wiki/Main_Page\">https://www.w3.org/html/wg/wiki/Main_Page</a><br /><br />Note the warning at the top: \u201cThis wiki has been archived and is now read-only.\u201d<br /><br />Aside: many years ago, each group at W3C had their own MediaWiki install, in a different path and disconnected from both every other group\u2019s wiki, and the top level general W3C wiki (<a href=\"http://www.w3.org/wiki\">http://www.w3.org/wiki</a>). I pointed out this made no sense, since groups more often than not had overlaps in documentation, technology, practices and would of course benefit from wiki-syntax interlinking. This was never really fixed at an infrastructure level, it had to be fixed at a cultural level, convincing working groups one by one to use the general W3C wiki, and ignore any WG-specific wiki. The other apparent hazard of having a WG-specific wiki is they can be (and have been) shutdown or frozen (like the example given), breaking any chance of fixing typos, other minor errors, or creating redirects to where the work has been restarted subsequently.<br /><br />Note also the lack of a \"View History\" link as a tab top right adjacent to the content area (or anywhere else on the page).<br /><br />This is likely because the page has been archived as static HTML, preserving the markup and styling, but removing any editing or history browsing or diffing or any other form submission based features that would require a dynamic backend like MediaWiki.<br /><br />Here is how to find such a page\u2019s history:<br />1. Find the \u201clast modified\u201d date in the footer and note the year, month, day.<br />2. Check for the page in the Internet Archive, e.g. prepend its URL with \"https://web.archive.org/web/\"<br />3. If there\u2019s (presumably) still no \"View History\" link, look at the year month day numbers in the URL \u2014 the first 8 digits after \"/web/\" E.g. \"20260512\" for this page as of today.<br />4. Replace those 8 digits with the year, month, day noted in step 1, with 4, 2, 2 digit numbers respectively. E.g. \"20150623\" for this page. Press return to load that.<br />5. You may have to \"close toolbar\" the (x) in the top right of the page content.<br />6. Note the \"View History\" link, click it.<br /><br />Presto, view history on a former MediaWiki page that\u2019s been archived to static HTML.<br /><br />This is my second #<span class=\"p-category\">WASSUP</span> #<span class=\"p-category\">WASSUP2026</span> post, and first useful web tip.<br /><br />#<span class=\"p-category\">wiki</span> #<span class=\"p-category\">wikiPage</span> #<span class=\"p-category\">MediaWiki</span> #<span class=\"p-category\">ViewHistory</span> #<span class=\"p-category\">W3C</span> #<span class=\"p-category\">HTMLWG</span> #<span class=\"p-category\">wikiArchived</span> #<span class=\"p-category\">readOnly</span> #<span class=\"p-category\">staticHTML</span> #<span class=\"p-category\">InternetArchive</span> #<span class=\"p-category\">WaybackMachine</span> #<span class=\"p-category\">LastModified</span>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49436967",
"_source": "2460"
}
{
"type": "entry",
"published": "2026-09-01 16:53-0700",
"url": "https://gregorlove.com/2026/09/new-mf2-to-icalendar-release/",
"category": [
"indieweb",
"microformats"
],
"syndication": [
"https://news.indieweb.org/en",
"https://bsky.app/profile/gregorlove.com/post/3muisuskpi22r"
],
"name": "New mf2 to iCalendar release",
"content": {
"text": "I\u2019ve released version 0.0.5 of mf2 to iCalendar, a library to convert h-event microformats into iCalendar.\n\nThere is now an option to directly provide the HTML to convert instead of fetching it from a URL. There is also support for the experimental event-status property. As noted in the readme, this isn\u2019t known to be published and could change when there is more consensus.\n\nPreviously",
"html": "<p>I\u2019ve released version 0.0.5 of <a href=\"https://github.com/gRegorLove/mf2-to-iCalendar\">mf2 to iCalendar</a>, a library to convert <a href=\"https://microformats.org/wiki/h-event\">h-event microformats</a> into iCalendar.</p>\n\n<p>There is now an option to directly provide the HTML to convert instead of fetching it from a URL. There is also support for the <em>experimental</em> <code>event-status</code> property. As noted in the <a href=\"https://github.com/gRegorLove/mf2-to-iCalendar#experimental\">readme</a>, this isn\u2019t known to be published and could change when there is more consensus.</p>\n\n<p><a href=\"https://gregorlove.com/2020/12/ive-released-version/\">Previously</a></p>"
},
"author": {
"type": "card",
"name": "gRegor Morrill",
"url": "https://gregorlove.com/",
"photo": "https://gregorlove.com/site/assets/files/6268/profile-2021-square.300x0.jpg"
},
"post-type": "article",
"_id": "49424562",
"_source": "95"
}
Welcome to September! Time for a new blogging challenge for the month. After some ideation, here’s my proposed September blogging challenge, on topics I find myself reading and posting about, with an emphasis on pragmatism:
The Web And Standards September Useful Posts blogging challenge
Or the #WASSUP challenge for short.
I really enjoyed the #Blaugust blogging challenge last month (31 posts ✅ — summary in another post), and not feeling a resonance with the two prior September challenges noted on the IndieWeb wiki, decided to come up with my own. Iterated on some ideas yesterday until arriving at WASSUP (yes, as a backronym, inspired somewhat by WHATWG which also has WHATNOT and WHATUP meetings).
Similar to Blaugust:
* 30 posts during the month of September (1 per day if you wish, or double/triple-up to get ahead or catch-up)
Topic:
* Anything *useful* (features, tips) about open web standards, the open web as a whole, web browsers, or web services like search engines.
Hashtags:
* #WASSUP #WASSUP2026
And that’s it.
If those are topics you already blog about, great, join in using the hashtags and share what you find useful about them!
Otherwise, take a look at how you frequently use the Web, and post what you have found useful, especially the most useful for you.
Blog clever tips about how you have made better use of the Web, web browsers, search engines etc.
If you’re a web developer or designer, share what you find most useful about web standards, your choice, either in their entirety or of individual features, like HTML elements, attributes, CSS properties, Selectors, DOM features, WebAPIs, standard media formats on the web, etc.
Let’s see what positive pragmatic things we can share with each other about the web and how it works in practice.
Glossary:
Blaugust:
* https://indieweb.org/Blaugust
blogging challenge:
* https://indieweb.org/blogging_challenge
September blogging challenges:
* https://indieweb.org/September#Challenges
standards
* https://indieweb.org/standards
#blog #blogging #bloggingChallenge #September #web #openWeb #webStandards #openWebStandards #webDev #webDevs #webDeveloper #webDevelopers #webDesign #webDesigns #webDesigner #webDesigners #useful #pragmatic
This is post 20 of #100PostsOfIndieWeb. #100Posts #indieweb
← https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain
→ 🔮
{
"type": "entry",
"published": "2026-09-01 13:31-0700",
"url": "https://tantek.com/2026/244/t1/september-blogging-challenge-wassup",
"category": [
"WASSUP",
"Blaugust",
"WASSUP2026",
"blog",
"blogging",
"bloggingChallenge",
"September",
"web",
"openWeb",
"webStandards",
"openWebStandards",
"webDev",
"webDevs",
"webDeveloper",
"webDevelopers",
"webDesign",
"webDesigns",
"webDesigner",
"webDesigners",
"useful",
"pragmatic",
"100PostsOfIndieWeb",
"100Posts",
"indieweb"
],
"content": {
"text": "Welcome to September! Time for a new blogging challenge for the month. After some ideation, here\u2019s my proposed September blogging challenge, on topics I find myself reading and posting about, with an emphasis on pragmatism:\n\nThe Web And Standards September Useful Posts blogging challenge\n\nOr the #WASSUP challenge for short.\n\nI really enjoyed the #Blaugust blogging challenge last month (31 posts \u2705 \u2014 summary in another post), and not feeling a resonance with the two prior September challenges noted on the IndieWeb wiki, decided to come up with my own. Iterated on some ideas yesterday until arriving at WASSUP (yes, as a backronym, inspired somewhat by WHATWG which also has WHATNOT and WHATUP meetings).\n\nSimilar to Blaugust:\n* 30 posts during the month of September (1 per day if you wish, or double/triple-up to get ahead or catch-up)\n\nTopic:\n* Anything *useful* (features, tips) about open web standards, the open web as a whole, web browsers, or web services like search engines.\n\nHashtags:\n* #WASSUP #WASSUP2026\n\nAnd that\u2019s it.\n\nIf those are topics you already blog about, great, join in using the hashtags and share what you find useful about them!\n\nOtherwise, take a look at how you frequently use the Web, and post what you have found useful, especially the most useful for you.\n\nBlog clever tips about how you have made better use of the Web, web browsers, search engines etc.\n\nIf you\u2019re a web developer or designer, share what you find most useful about web standards, your choice, either in their entirety or of individual features, like HTML elements, attributes, CSS properties, Selectors, DOM features, WebAPIs, standard media formats on the web, etc.\n\nLet\u2019s see what positive pragmatic things we can share with each other about the web and how it works in practice.\n\nGlossary:\n\nBlaugust:\n* https://indieweb.org/Blaugust\nblogging challenge:\n* https://indieweb.org/blogging_challenge\nSeptember blogging challenges:\n* https://indieweb.org/September#Challenges\nstandards\n* https://indieweb.org/standards\n\n#blog #blogging #bloggingChallenge #September #web #openWeb #webStandards #openWebStandards #webDev #webDevs #webDeveloper #webDevelopers #webDesign #webDesigns #webDesigner #webDesigners #useful #pragmatic\n\nThis is post 20 of #100PostsOfIndieWeb. #100Posts #indieweb\n\n\u2190 https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain\n\u2192 \ud83d\udd2e",
"html": "Welcome to September! Time for a new blogging challenge for the month. After some ideation, here\u2019s my proposed September blogging challenge, on topics I find myself reading and posting about, with an emphasis on pragmatism:<br /><br />The Web And Standards September Useful Posts blogging challenge<br /><br />Or the #<span class=\"p-category\">WASSUP</span> challenge for short.<br /><br />I really enjoyed the #<span class=\"p-category\">Blaugust</span> blogging challenge last month (31 posts \u2705 \u2014 summary in another post), and not feeling a resonance with the two prior September challenges noted on the IndieWeb wiki, decided to come up with my own. Iterated on some ideas yesterday until arriving at WASSUP (yes, as a backronym, inspired somewhat by WHATWG which also has WHATNOT and WHATUP meetings).<br /><br />Similar to Blaugust:<br />* 30 posts during the month of September (1 per day if you wish, or double/triple-up to get ahead or catch-up)<br /><br />Topic:<br />* Anything *useful* (features, tips) about open web standards, the open web as a whole, web browsers, or web services like search engines.<br /><br />Hashtags:<br />* #<span class=\"p-category\">WASSUP</span> #<span class=\"p-category\">WASSUP2026</span><br /><br />And that\u2019s it.<br /><br />If those are topics you already blog about, great, join in using the hashtags and share what you find useful about them!<br /><br />Otherwise, take a look at how you frequently use the Web, and post what you have found useful, especially the most useful for you.<br /><br />Blog clever tips about how you have made better use of the Web, web browsers, search engines etc.<br /><br />If you\u2019re a web developer or designer, share what you find most useful about web standards, your choice, either in their entirety or of individual features, like HTML elements, attributes, CSS properties, Selectors, DOM features, WebAPIs, standard media formats on the web, etc.<br /><br />Let\u2019s see what positive pragmatic things we can share with each other about the web and how it works in practice.<br /><br />Glossary:<br /><br />Blaugust:<br />* <a href=\"https://indieweb.org/Blaugust\">https://indieweb.org/Blaugust</a><br />blogging challenge:<br />* <a href=\"https://indieweb.org/blogging_challenge\">https://indieweb.org/blogging_challenge</a><br />September blogging challenges:<br />* <a href=\"https://indieweb.org/September#Challenges\">https://indieweb.org/September#Challenges</a><br />standards<br />* <a href=\"https://indieweb.org/standards\">https://indieweb.org/standards</a><br /><br />#<span class=\"p-category\">blog</span> #<span class=\"p-category\">blogging</span> #<span class=\"p-category\">bloggingChallenge</span> #<span class=\"p-category\">September</span> #<span class=\"p-category\">web</span> #<span class=\"p-category\">openWeb</span> #<span class=\"p-category\">webStandards</span> #<span class=\"p-category\">openWebStandards</span> #<span class=\"p-category\">webDev</span> #<span class=\"p-category\">webDevs</span> #<span class=\"p-category\">webDeveloper</span> #<span class=\"p-category\">webDevelopers</span> #<span class=\"p-category\">webDesign</span> #<span class=\"p-category\">webDesigns</span> #<span class=\"p-category\">webDesigner</span> #<span class=\"p-category\">webDesigners</span> #<span class=\"p-category\">useful</span> #<span class=\"p-category\">pragmatic</span><br /><br />This is post 20 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">indieweb</span><br /><br />\u2190 <a href=\"https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain\">https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49421697",
"_source": "2460"
}
There are many paths onto the #indieweb. Two of the most common:
1. an idea for a name and a website
2. a desire to create and express yourself, independently of social media
If you start with (1), have an idea for a domain name, find one, and buy it, then you need a place to direct it to.
The simplest next step is setting up a content hosting service, and configuring it with your new domain name.
If you start with (2), a desire to create and publish, then similarly, the simplest first step is to set up a content hosting service.
Either way, you should choose a service that supports custom domain names.
Had a great chat with Joe Crawford (@artlung.com) this morning about the many ways people find their way to the indieweb, and set up their own indieweb site.
We talked about the challenges of attaching a domain name to a service, and how that could be better documented and explained.
Subsequently Joe took the initiative to create a new "custom domain name" page on the IndieWeb wiki to help consider and choose a content hosting service that supports custom domains:
* https://indieweb.org/custom_domain_name
There are both free options and paid options depending on what kind of features, user experience, and support you want.
Most paid options cost less than a latte a month, certainly less than monthly mobile phone or video streaming fees.
Know other content hosting services that support custom domain names?
Add them to the wiki page!
And if you prefer to install and run your own content management software or create your one yourself, you can do that too:
* https://indieweb.org/CMS
If you do create one, watch out for spending more time coding than writing.
Or code away! It’s your site, code, write, mix it up as you wish.
Previously: https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website
This is post 19 of #100PostsOfIndieWeb. #100Posts
#independent #socialMedia #domain #domainName #contentHosting #customDomain #customDomains #customDomainName #customDomainNames #CMS
#Blaugust #Blaugust2026
← https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website
→ 🔮
{
"type": "entry",
"published": "2026-08-31 23:50-0700",
"url": "https://tantek.com/2026/243/t1/many-paths-indieweb-custom-domain",
"category": [
"indieweb",
"100PostsOfIndieWeb",
"100Posts",
"independent",
"socialMedia",
"domain",
"domainName",
"contentHosting",
"customDomain",
"customDomains",
"customDomainName",
"customDomainNames",
"CMS",
"Blaugust",
"Blaugust2026"
],
"content": {
"text": "There are many paths onto the #indieweb. Two of the most common:\n1. an idea for a name and a website\n2. a desire to create and express yourself, independently of social media\n\nIf you start with (1), have an idea for a domain name, find one, and buy it, then you need a place to direct it to.\n\nThe simplest next step is setting up a content hosting service, and configuring it with your new domain name.\n\nIf you start with (2), a desire to create and publish, then similarly, the simplest first step is to set up a content hosting service.\n\nEither way, you should choose a service that supports custom domain names.\n\nHad a great chat with Joe Crawford (@artlung.com) this morning about the many ways people find their way to the indieweb, and set up their own indieweb site.\n\nWe talked about the challenges of attaching a domain name to a service, and how that could be better documented and explained.\n\nSubsequently Joe took the initiative to create a new \"custom domain name\" page on the IndieWeb wiki to help consider and choose a content hosting service that supports custom domains:\n\n* https://indieweb.org/custom_domain_name\n\nThere are both free options and paid options depending on what kind of features, user experience, and support you want.\n\nMost paid options cost less than a latte a month, certainly less than monthly mobile phone or video streaming fees.\n\nKnow other content hosting services that support custom domain names?\n\nAdd them to the wiki page!\n\nAnd if you prefer to install and run your own content management software or create your one yourself, you can do that too:\n\n* https://indieweb.org/CMS\n\nIf you do create one, watch out for spending more time coding than writing.\n\nOr code away! It\u2019s your site, code, write, mix it up as you wish.\n\nPreviously: https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website\n\u00a0\nThis is post 19 of #100PostsOfIndieWeb. #100Posts\n\n#independent #socialMedia #domain #domainName #contentHosting #customDomain #customDomains #customDomainName #customDomainNames #CMS \n#Blaugust #Blaugust2026\n\n\u2190 https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website\n\u2192 \ud83d\udd2e",
"html": "There are many paths onto the #<span class=\"p-category\">indieweb</span>. Two of the most common:<br />1. an idea for a name and a website<br />2. a desire to create and express yourself, independently of social media<br /><br />If you start with (1), have an idea for a domain name, find one, and buy it, then you need a place to direct it to.<br /><br />The simplest next step is setting up a content hosting service, and configuring it with your new domain name.<br /><br />If you start with (2), a desire to create and publish, then similarly, the simplest first step is to set up a content hosting service.<br /><br />Either way, you should choose a service that supports custom domain names.<br /><br />Had a great chat with Joe Crawford (<a href=\"https://artlung.com\">@artlung.com</a>) this morning about the many ways people find their way to the indieweb, and set up their own indieweb site.<br /><br />We talked about the challenges of attaching a domain name to a service, and how that could be better documented and explained.<br /><br />Subsequently Joe took the initiative to create a new \"custom domain name\" page on the IndieWeb wiki to help consider and choose a content hosting service that supports custom domains:<br /><br />* <a href=\"https://indieweb.org/custom_domain_name\">https://indieweb.org/custom_domain_name</a><br /><br />There are both free options and paid options depending on what kind of features, user experience, and support you want.<br /><br />Most paid options cost less than a latte a month, certainly less than monthly mobile phone or video streaming fees.<br /><br />Know other content hosting services that support custom domain names?<br /><br />Add them to the wiki page!<br /><br />And if you prefer to install and run your own content management software or create your one yourself, you can do that too:<br /><br />* <a href=\"https://indieweb.org/CMS\">https://indieweb.org/CMS</a><br /><br />If you do create one, watch out for spending more time coding than writing.<br /><br />Or code away! It\u2019s your site, code, write, mix it up as you wish.<br /><br />Previously: <a href=\"https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website\">https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website</a><br />\u00a0<br />This is post 19 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />#<span class=\"p-category\">independent</span> #<span class=\"p-category\">socialMedia</span> #<span class=\"p-category\">domain</span> #<span class=\"p-category\">domainName</span> #<span class=\"p-category\">contentHosting</span> #<span class=\"p-category\">customDomain</span> #<span class=\"p-category\">customDomains</span> #<span class=\"p-category\">customDomainName</span> #<span class=\"p-category\">customDomainNames</span> #<span class=\"p-category\">CMS</span> <br />#<span class=\"p-category\">Blaugust</span> #<span class=\"p-category\">Blaugust2026</span><br /><br />\u2190 <a href=\"https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website\">https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49414851",
"_source": "2460"
}
Aaron Donald and Myles Garrett on the same DL is going to be wild. This has to be the best shot at a Super Bowl for the Rams since 2021.
{
"type": "entry",
"published": "2026-08-31T04:49:14.571406+00:00",
"url": "https://cleverdevil.io/2026/aaron-donald-and-myles-garrett-on-the-sa",
"syndication": [
"https://cleverdevil.club/@jonathan/117188313462690118",
"https://bsky.app/profile/cleverdevil.io/post/3mue455tcnn26"
],
"content": {
"text": "Aaron Donald and Myles Garrett on the same DL is going to be wild. This has to be the best shot at a Super Bowl for the Rams since 2021.",
"html": "<p>Aaron Donald and Myles Garrett on the same DL is going to be wild. This has to be the best shot at a Super Bowl for the Rams since 2021.</p>"
},
"author": {
"type": "card",
"name": "Jonathan LaCour",
"url": "https://cleverdevil.io",
"photo": "https://cleverdevil.io/profile/photo"
},
"post-type": "note",
"_id": "49404791",
"_source": "10"
}
What does it take to be on or be part of the #indieweb?
As several have shared before me:
* own your domain and publish some content on it
That’s the foundation. If you have a personal website on a domain you own and control, you’re on the indieweb or part of the indieweb or however you would like to express a sense of belonging.
Of course there are lots of things you can do to be more indieweb, and that’s very much a choose your own adventure journey.
Maybe you’ll decide to post your content first on your personal site rather than on silos, and only post copies (syndicate) to social media walled gardens.
* https://indieweb.org/POSSE
Maybe you like taking an explicitly principled approach, step-by-step.
* https://indieweb.org/principles
Maybe you’ll decide to entirely quit using specific silos, for any reason, whether you created a replacement with your own site, or switched to a community owned and run solution.
* https://indieweb.org/silo-quits
Maybe you’re a developer and decide to implement various open web standards (formats and protocols) so your indieweb site can interact more with other indieweb sites.
* https://indieweb.org/building-blocks
Maybe you want to join a community of like-minded folks creatively expressing themselves on their personal sites, treating each other respectfully, encouraging each other, and collaborating on building better solutions than sites that require agreeing to long and heavily imbalanced terms of service.
* https://indieweb.org/join
All of these are optional.
Make a personal website on a domain you own, put some content there.
Welcome.
This is post 18 of #100PostsOfIndieWeb. #100Posts
#domain #domainName #ownYourDomain #ownYourIdentity #identity #personalWeb #personalWebsite #smallWeb #ownYourData #ownYourContent #POSSE #indiewebPrinciples #principles #siloQuit #siloQuits #openWeb #openWebStandards #webStandards #community #IndieWebCommunity
#Blaugust #Blaugust2026
← https://tantek.com/2026/240/t1/indieweb-your-own-words-actions
→ 🔮
{
"type": "entry",
"published": "2026-08-30 10:13-0700",
"url": "https://tantek.com/2026/242/t1/indieweb-own-domain-content-personal-website",
"category": [
"indieweb",
"100PostsOfIndieWeb",
"100Posts",
"domain",
"domainName",
"ownYourDomain",
"ownYourIdentity",
"identity",
"personalWeb",
"personalWebsite",
"smallWeb",
"ownYourData",
"ownYourContent",
"POSSE",
"indiewebPrinciples",
"principles",
"siloQuit",
"siloQuits",
"openWeb",
"openWebStandards",
"webStandards",
"community",
"IndieWebCommunity",
"Blaugust",
"Blaugust2026"
],
"content": {
"text": "What does it take to be on or be part of the #indieweb?\n\nAs several have shared before me:\n* own your domain and publish some content on it\n\nThat\u2019s the foundation. If you have a personal website on a domain you own and control, you\u2019re on the indieweb or part of the indieweb or however you would like to express a sense of belonging.\n\nOf course there are lots of things you can do to be more indieweb, and that\u2019s very much a choose your own adventure journey.\n\nMaybe you\u2019ll decide to post your content first on your personal site rather than on silos, and only post copies (syndicate) to social media walled gardens.\n* https://indieweb.org/POSSE\n\nMaybe you like taking an explicitly principled approach, step-by-step.\n* https://indieweb.org/principles\n\nMaybe you\u2019ll decide to entirely quit using specific silos, for any reason, whether you created a replacement with your own site, or switched to a community owned and run solution.\n* https://indieweb.org/silo-quits\n\nMaybe you\u2019re a developer and decide to implement various open web standards (formats and protocols) so your indieweb site can interact more with other indieweb sites.\n* https://indieweb.org/building-blocks\n\nMaybe you want to join a community of like-minded folks creatively expressing themselves on their personal sites, treating each other respectfully, encouraging each other, and collaborating on building better solutions than sites that require agreeing to long and heavily imbalanced terms of service.\n* https://indieweb.org/join\n\nAll of these are optional. \n\nMake a personal website on a domain you own, put some content there. \n\nWelcome.\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n#domain #domainName #ownYourDomain #ownYourIdentity #identity #personalWeb #personalWebsite #smallWeb #ownYourData #ownYourContent #POSSE #indiewebPrinciples #principles #siloQuit #siloQuits #openWeb #openWebStandards #webStandards #community #IndieWebCommunity\n#Blaugust #Blaugust2026\n\n\u2190 https://tantek.com/2026/240/t1/indieweb-your-own-words-actions\n\u2192 \ud83d\udd2e",
"html": "What does it take to be on or be part of the #<span class=\"p-category\">indieweb</span>?<br /><br />As several have shared before me:<br />* own your domain and publish some content on it<br /><br />That\u2019s the foundation. If you have a personal website on a domain you own and control, you\u2019re on the indieweb or part of the indieweb or however you would like to express a sense of belonging.<br /><br />Of course there are lots of things you can do to be more indieweb, and that\u2019s very much a choose your own adventure journey.<br /><br />Maybe you\u2019ll decide to post your content first on your personal site rather than on silos, and only post copies (syndicate) to social media walled gardens.<br />* <a href=\"https://indieweb.org/POSSE\">https://indieweb.org/POSSE</a><br /><br />Maybe you like taking an explicitly principled approach, step-by-step.<br />* <a href=\"https://indieweb.org/principles\">https://indieweb.org/principles</a><br /><br />Maybe you\u2019ll decide to entirely quit using specific silos, for any reason, whether you created a replacement with your own site, or switched to a community owned and run solution.<br />* <a href=\"https://indieweb.org/silo-quits\">https://indieweb.org/silo-quits</a><br /><br />Maybe you\u2019re a developer and decide to implement various open web standards (formats and protocols) so your indieweb site can interact more with other indieweb sites.<br />* <a href=\"https://indieweb.org/building-blocks\">https://indieweb.org/building-blocks</a><br /><br />Maybe you want to join a community of like-minded folks creatively expressing themselves on their personal sites, treating each other respectfully, encouraging each other, and collaborating on building better solutions than sites that require agreeing to long and heavily imbalanced terms of service.<br />* <a href=\"https://indieweb.org/join\">https://indieweb.org/join</a><br /><br />All of these are optional. <br /><br />Make a personal website on a domain you own, put some content there. <br /><br />Welcome.<br /><br />This is post 18 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br />#<span class=\"p-category\">domain</span> #<span class=\"p-category\">domainName</span> #<span class=\"p-category\">ownYourDomain</span> #<span class=\"p-category\">ownYourIdentity</span> #<span class=\"p-category\">identity</span> #<span class=\"p-category\">personalWeb</span> #<span class=\"p-category\">personalWebsite</span> #<span class=\"p-category\">smallWeb</span> #<span class=\"p-category\">ownYourData</span> #<span class=\"p-category\">ownYourContent</span> #<span class=\"p-category\">POSSE</span> #<span class=\"p-category\">indiewebPrinciples</span> #<span class=\"p-category\">principles</span> #<span class=\"p-category\">siloQuit</span> #<span class=\"p-category\">siloQuits</span> #<span class=\"p-category\">openWeb</span> #<span class=\"p-category\">openWebStandards</span> #<span class=\"p-category\">webStandards</span> #<span class=\"p-category\">community</span> #<span class=\"p-category\">IndieWebCommunity</span><br />#<span class=\"p-category\">Blaugust</span> #<span class=\"p-category\">Blaugust2026</span><br /><br />\u2190 <a href=\"https://tantek.com/2026/240/t1/indieweb-your-own-words-actions\">https://tantek.com/2026/240/t1/indieweb-your-own-words-actions</a><br />\u2192 \ud83d\udd2e"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://tantek.com/photo.jpg"
},
"post-type": "note",
"_id": "49400616",
"_source": "2460"
}