✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.
The consumer Infinite Scroll Web leaves us feeling empty.
Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.
A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.
Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.
We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.
13 years ago I wrote²:
“The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”
Now I want the Read Write Suggest-Edit Accept-Edit Update Web.
The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).
Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.
If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.
Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?
To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.
There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:
* https://indieweb.org/edit
Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.
For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:
✏️ Suggest Edit
and link it to an edit URL for the static file for the post.
I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:
https://tantek.com/github/cassis/edit/main/README.md
This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.
After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.
It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.
We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.
#readWriteWeb #editableWeb #suggestEdit #acceptEdit
References:
¹ https://indieweb.social/@kevinmarks/113025295600067213
² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11
³ https://indieweb.org/responses
⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/
⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.
This is post 20 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/242/t1/indiewebcamp-portland
→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
{
"type": "entry",
"published": "2024-09-01 14:51-0700",
"url": "http://tantek.com/2024/245/t1/read-write-suggest-edit-update-web",
"category": [
"IndieWebCamp",
"Mastodon",
"ActivityPub",
"IndieWeb",
"readWriteWeb",
"editableWeb",
"suggestEdit",
"acceptEdit",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe consumer Infinite Scroll Web leaves us feeling empty.\n\nToo few of us participate in the Read Write Web, whether with personal sites or Wikipedia.\n\nA week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos\u00b9, I noticed a few errors, typos or miscaptures, and pointed them out in-person.\n\nKevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon\u2019s post editing feature and its support of #ActivityPub Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.\n\nWe should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.\n\n13 years ago I wrote\u00b2:\n\n\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d\n\nNow I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).\n\nWhy not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.\n\nIf the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.\n\nInstead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?\n\nTo enable such UIs and interactions across servers and implementations, we may need a new type of response\u00b3, perhaps with a special property (or more) to convey the edits being suggested.\n\nThere is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:\n* https://indieweb.org/edit\n\nOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.\n\nFor now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:\n\n\u270f\ufe0f Suggest Edit\n\nand link it to an edit URL for the static file for the post.\n\nI don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:\n\nhttps://tantek.com/github/cassis/edit/main/README.md\n\nThis will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon\u2074 for a \u201csuggested edit\u201d.\n\nAfter completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.\n\nIt\u2019s an awkward interaction\u2075, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.\n\nWe can start with the shortest path to getting something working, then learn, iterate, improve, repeat.\n\n#readWriteWeb #editableWeb #suggestEdit #acceptEdit\n\nReferences:\n\n\u00b9 https://indieweb.social/@kevinmarks/113025295600067213\n\u00b2 https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\n\u00b3 https://indieweb.org/responses\n\u2074 The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\n\u2075 \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.\n\nThis is post 20 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/242/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed",
"html": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The consumer Infinite Scroll Web leaves us feeling empty.<br /><br />Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br /><br />A week ago when we wrapped up #<span class=\"p-category\">IndieWebCamp</span> Portland and I was reading Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a>) live-tooting of the demos<a href=\"http://tantek.com/#t5Yn1_note-1\">\u00b9</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br /><br />Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #<span class=\"p-category\">Mastodon</span>\u2019s post editing feature and its support of #<span class=\"p-category\">ActivityPub</span> Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.<br /><br />We should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.<br /><br />13 years ago I wrote<a href=\"http://tantek.com/#t5Yn1_note-2\">\u00b2</a>:<br /><br />\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d<br /><br />Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br /><br />Why not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.<br /><br />If the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.<br /><br />Instead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br /><br />To enable such UIs and interactions across servers and implementations, we may need a new type of response<a href=\"http://tantek.com/#t5Yn1_note-3\">\u00b3</a>, perhaps with a special property (or more) to convey the edits being suggested.<br /><br />There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #<span class=\"p-category\">IndieWeb</span> wiki:<br />* <a href=\"https://indieweb.org/edit\">https://indieweb.org/edit</a><br /><br />Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br /><br />For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br /><br />\u270f\ufe0f Suggest Edit<br /><br />and link it to an edit URL for the static file for the post.<br /><br />I don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:<br /><br /><a href=\"https://tantek.com/github/cassis/edit/main/README.md\">https://tantek.com/github/cassis/edit/main/README.md</a><br /><br />This will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon<a href=\"http://tantek.com/#t5Yn1_note-4\">\u2074</a> for a \u201csuggested edit\u201d.<br /><br />After completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.<br /><br />It\u2019s an awkward interaction<a href=\"http://tantek.com/#t5Yn1_note-5\">\u2075</a>, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br /><br />We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br /><br />#<span class=\"p-category\">readWriteWeb</span> #<span class=\"p-category\">editableWeb</span> #<span class=\"p-category\">suggestEdit</span> #<span class=\"p-category\">acceptEdit</span><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yn1_ref-1\">\u00b9</a> <a href=\"https://indieweb.social/@kevinmarks/113025295600067213\">https://indieweb.social/@kevinmarks/113025295600067213</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-4\">\u2074</a> The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to <a href=\"https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br /><a href=\"http://tantek.com/#t5Yn1_ref-5\">\u2075</a> \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.<br /><br />This is post 20 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42140618",
"_source": "1",
"_is_read": false
}
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.
Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.
* https://indieweb.org/2024/Portland/Intros
There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.
We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!
* https://indieweb.org/2024/Portland/Demos
Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:
* https://indieweb.org/2024/Portland
Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.
The experience definitely raised our hopes and confidence for returning to Portland in 2025.²
References:
¹ https://indieweb.org/Create_Day
² https://indieweb.org/Planning#Portland
This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238
← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
{
"type": "entry",
"published": "2024-08-29 21:09-0700",
"url": "http://tantek.com/2024/242/t1/indiewebcamp-portland-10",
"category": [
"IndieWebCamp",
"IndieWeb",
"100PostsOfIndieWeb",
"100Posts",
"2024_238"
],
"content": {
"text": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.\n\nNearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.\n* https://indieweb.org/2024/Portland/Intros\n\nThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.\n\nWe wrapped up with our usual Create Day\u00b9 Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!\n* https://indieweb.org/2024/Portland/Demos\n\nGroup photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:\n* https://indieweb.org/2024/Portland\n\nThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.\n\nThe experience definitely raised our hopes and confidence for returning to Portland in 2025.\u00b2\n\n\nReferences:\n\n\u00b9 https://indieweb.org/Create_Day\n\u00b2 https://indieweb.org/Planning#Portland\n\nThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238\n\n\u2190 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\n\u2192 https://tantek.com/2024/245/t1/read-write-suggest-edit-web",
"html": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!<br /><br /><a href=\"https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br /><br />Being a one day #<span class=\"p-category\">IndieWebCamp</span>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br /><br />Nearly everyone gave a brief personal site intro with a summary of how they use their #<span class=\"p-category\">IndieWeb</span> site and what they would like to add, remove, or improve.<br />* <a href=\"https://indieweb.org/2024/Portland/Intros\">https://indieweb.org/2024/Portland/Intros</a><br /><br />There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br /><br />We wrapped up with our usual Create Day<a href=\"http://tantek.com/#t5Yj1_note-1\">\u00b9</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br />* <a href=\"https://indieweb.org/2024/Portland/Demos\">https://indieweb.org/2024/Portland/Demos</a><br /><br />Group photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:<br />* <a href=\"https://indieweb.org/2024/Portland\">https://indieweb.org/2024/Portland</a><br /><br />Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a href=\"https://martymcgui.re\">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a href=\"https://snarfed.org\">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br /><br />The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a href=\"http://tantek.com/#t5Yj1_note-2\">\u00b2</a><br /><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yj1_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Create_Day\">https://indieweb.org/Create_Day</a><br /><a href=\"http://tantek.com/#t5Yj1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/Planning#Portland\">https://indieweb.org/Planning#Portland</a><br /><br />This is post 19 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span> #<span class=\"p-category\">2024_238</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br />\u2192 <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42140619",
"_source": "1",
"_is_read": false
}
Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.
I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).
Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.
It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.
I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.
* URLs, @-s, and @-@-s
* # hashtags
* ^ footnotes
#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes
Previously, previously, previously:
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
* https://tantek.com/2023/043/t1/footnotes-unicode-links
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
References:
¹ https://indieweb.org/autolink
² https://github.com/tantek/cassis/blob/main/cassis.js
This is post 18 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/238/t1/indiewebcamp-portland
→ https://tantek.com/2024/242/t1/indiewebcamp-portland
{
"type": "entry",
"published": "2024-08-25 16:00-0700",
"url": "http://tantek.com/2024/238/t3/indiewebcamp-auto-link",
"category": [
"IndieWebCamp",
"IndieWeb",
"autoLink",
"hashtag",
"hashtags",
"footnote",
"footnotes",
"100PostsOfIndieWeb",
"100Posts"
],
"content": {
"text": "Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking\u00b9.\n\nI\u2019ve implemented an auto_link function\u00b2 that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).\n\nMuch of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.\n\nIt may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.\n\nI have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.\n\n* URLs, @-s, and @-@-s\n* # hashtags\n* ^ footnotes\n\n#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes\n\nPreviously, previously, previously:\n\n* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\n* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\n* https://tantek.com/2023/043/t1/footnotes-unicode-links\n* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\n\n\nReferences:\n\n\u00b9 https://indieweb.org/autolink\n\u00b2 https://github.com/tantek/cassis/blob/main/cassis.js\n\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/238/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/242/t1/indiewebcamp-portland",
"html": "Nice #<span class=\"p-category\">IndieWebCamp</span> discussion session with Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) on the topic of auto-linking<a href=\"http://tantek.com/#t5Yf3_note-1\">\u00b9</a>.<br /><br />I\u2019ve implemented an auto_link function<a href=\"http://tantek.com/#t5Yf3_note-2\">\u00b2</a> that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).<br /><br />Much of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.<br /><br />It may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.<br /><br />I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.<br /><br />* URLs, @-s, and @-@-s<br />* # hashtags<br />* ^ footnotes<br /><br />#<span class=\"p-category\">IndieWeb</span> #<span class=\"p-category\">autoLink</span> #<span class=\"p-category\">hashtag</span> #<span class=\"p-category\">hashtags</span> #<span class=\"p-category\">footnote</span> #<span class=\"p-category\">footnotes</span><br /><br />Previously, previously, previously:<br /><br />* <a href=\"https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a><br />* <a href=\"https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\">https://tantek.com/2023/100/t1/auto-linked-hashtags-federated</a><br />* <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />* <a href=\"https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\">https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo</a><br /><br /><br />References:<br /><br /><a href=\"http://tantek.com/#t5Yf3_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/autolink\">https://indieweb.org/autolink</a><br /><a href=\"http://tantek.com/#t5Yf3_ref-2\">\u00b2</a> <a href=\"https://github.com/tantek/cassis/blob/main/cassis.js\">https://github.com/tantek/cassis/blob/main/cassis.js</a><br /><br /><br />This is post 18 of #<span class=\"p-category\">100PostsOfIndieWeb</span>. #<span class=\"p-category\">100Posts</span><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t1/indiewebcamp-portland\">https://tantek.com/2024/238/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a>"
},
"author": {
"type": "card",
"name": "Tantek \u00c7elik",
"url": "https://tantek.com/",
"photo": "https://aperture-media.p3k.io/tantek.com/acfddd7d8b2c8cf8aa163651432cc1ec7eb8ec2f881942dca963d305eeaaa6b8.jpg"
},
"post-type": "note",
"_id": "42140620",
"_source": "1",
"_is_read": false
}
{
"type": "entry",
"published": "2024-09-04T22:46:37.102817764+03:00",
"url": "https://fireburn.ru/posts/byypbyN",
"category": [
"Bowl",
"Kittybox",
"IndieWeb",
"Micropub",
"https://news.indieweb.org/en"
],
"name": "Bowl for Kittybox 1.0",
"content": {
"text": "This is a submission for IndieNews, the IndieWeb news aggregator.\nBowl for Kittybox, a new Micropub client, is now released!\nWhat is this?\nThis is meant to fill the niche of native desktop Micropub clients for those who prefer old-fashioned native applications instead of web apps or web apps packaged in a shrink-wrapped Google Chrome shell.\nIt's also a testing ground for my UX experiments. I believe Micropub provides a single well-oiled joint for blog posting, and that any user experience enhancements or additional features can simply live on top of it. The media endpoint standard is actually one of such enhancements \u2014 the Micropub endpoint does not strictly need to know about its existence, it can just understand links that the media endpoint gives to the client to insert into the post.\nOne of these experiments is Smart Summary \u2014 an optional summarization feature powered by a large language model. Hitting the Smart Summary button with a blog post in the editor pastes the post into an LLM and tells it to produce a one-sentence-summary. I rarely if ever filled the p-summary field, but now I guess I have no excuse.\nI also plan to make Kittybox collapse long posts in the feed that have summaries, and make an optional query parameter to provide un-collapsed posts (for MF2 feeds?), and helping produce summaries ties nicely into this feature.\nOf course, LLMs are not intelligent, cannot understand what they ingest and produce, and most importantly, have no conscience to feel guilty if they lie or mislead their user. So I recommend carefully proof-reading these summaries. Bowl will also under no circumstances support having LLMs write actual post content.\nI don't want this!\nThis can be disabled when building, pass -Dllm=false to Meson when configuring. When disabled, all LLM integration code is completely purged from the binary, leaving it completely unaware of this technology's existence. (The settings schema, however, is unaffected. I may fix that in the future.)\nWhat are the next steps?\nWhen I add media support, I will also try to make another LLM integration, Alt Text Vision, that could quickly draft an alt-text for an image you upload. (Of course, the user will be given the opportunity to review the output.)\nI also am thinking of creating a Microsub client that could summon Bowl to interact with posts. That may require Bowl to become D-Bus activatable and potentially support displaying several windows at once.\nI am also thinking about offline support, being able to draft posts while offline and send them once internet connection is available. Micropub also has some extensions for working with drafts, and I can use that to allow syncing the drafts to your own website.\nP.S.: When generating the summary for this post using Smart Summary, the LLM confused Bowl and Kittybox, and thought Kittybox is actually the Micropub client. This is a reminder to always double-check the text LLMs write for you.",
"html": "<p><i>This is a submission for <a href=\"https://news.indieweb.org/en\" class=\"u-category\">IndieNews</a>, the IndieWeb news aggregator.</i></p>\n<p><a href=\"https://kittybox.fireburn.ru/bowl/\">Bowl for Kittybox</a>, a new Micropub client, is now released!</p>\n<h2>What is this?</h2>\n<p>This is meant to fill the niche of native desktop Micropub clients for those who prefer old-fashioned native applications instead of web apps or web apps packaged in a shrink-wrapped Google Chrome shell.</p>\n<p>It's also a testing ground for my UX experiments. I believe Micropub provides a <em>single well-oiled joint</em> for blog posting, and that any user experience enhancements or additional features can simply live on top of it. The media endpoint standard is actually one of such enhancements \u2014 the Micropub endpoint does not strictly need to know about its existence, it can just understand links that the media endpoint gives to the client to insert into the post.</p>\n<p>One of these experiments is <strong>Smart Summary</strong> \u2014 an optional summarization feature powered by a large language model. Hitting the Smart Summary button with a blog post in the editor pastes the post into an LLM and tells it to produce a one-sentence-summary. I rarely if ever filled the <code>p-summary</code> field, but now I guess I have no excuse.</p>\n<p>I also plan to make Kittybox collapse long posts in the feed that have summaries, and make an optional query parameter to provide un-collapsed posts (for MF2 feeds?), and helping produce summaries ties nicely into this feature.</p>\n<p>Of course, LLMs are not intelligent, cannot understand what they ingest and produce, and <em>most importantly</em>, have no conscience to feel guilty if they lie or mislead their user. So I recommend carefully proof-reading these summaries. Bowl will also under no circumstances support having LLMs write actual post content.</p>\n<h2>I don't want this!</h2>\n<p>This can be disabled when building, pass <code>-Dllm=false</code> to Meson when configuring. When disabled, all LLM integration code is completely purged from the binary, leaving it completely unaware of this technology's existence. (The settings schema, however, is unaffected. I may fix that in the future.)</p>\n<h2>What are the next steps?</h2>\n<p>When I add media support, I will also try to make another LLM integration, <strong>Alt Text Vision</strong>, that could quickly draft an alt-text for an image you upload. (Of course, the user will be given the opportunity to review the output.)</p>\n<p>I also am thinking of creating a Microsub client that could summon Bowl to interact with posts. That may require Bowl to become D-Bus activatable and potentially support displaying several windows at once.</p>\n<p>I am also thinking about offline support, being able to draft posts while offline and send them once internet connection is available. Micropub also has some extensions for working with drafts, and I can use that to allow syncing the drafts to your own website.</p>\n<p><strong>P.S.</strong>: When generating the summary for this post using <strong>Smart Summary</strong>, the LLM confused Bowl and Kittybox, and thought Kittybox is actually the Micropub client. This is a reminder to always double-check the text LLMs write for you.</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/.kittybox/media/uploads/fe/ad/f8/76/e94e284444605135ad468b1563070dac3d2ad642c366b1e180f6eb65"
},
"post-type": "article",
"_id": "42140392",
"_source": "1371",
"_is_read": false
}
Had a great time at IndieWebCamp Portland 2024 this past Sunday — our 10th IndieWebCamp in Portland!
https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k
Being a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.
Nearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.
* https://indieweb.org/2024/Portland/Intros
There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.
We wrapped up with our usual Create Day¹ Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!
* https://indieweb.org/2024/Portland/Demos
Group photo and lots more about IndieWebCamp Portland 2024 at the event’s wiki page:
* https://indieweb.org/2024/Portland
Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.
The experience definitely raised our hopes and confidence for returning to Portland in 2025.²
References:
¹ https://indieweb.org/Create_Day
² https://indieweb.org/Planning#Portland
This is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238
← https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
→ https://tantek.com/2024/245/t1/read-write-suggest-edit-web
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/242/t1/indiewebcamp-portland-10",
"content": {
"html": "<p>Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!<br /><br /><a href=\"https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\">https://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k</a><br /><br />Being a one day <a href=\"https://indieweb.social/tags/IndieWebCamp\">#<span class=\"p-category\">IndieWebCamp</span></a>, we focused more on making, hacking, and creating, than on formal discussion sessions.<br /><br />Nearly everyone gave a brief personal site intro with a summary of how they use their <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> site and what they would like to add, remove, or improve.<br />* <a href=\"https://indieweb.org/2024/Portland/Intros\">https://indieweb.org/2024/Portland/Intros</a><br /><br />There were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.<br /><br />We wrapped up with our usual Create Day<a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_note-1\">\u00b9</a> Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!<br />* <a href=\"https://indieweb.org/2024/Portland/Demos\">https://indieweb.org/2024/Portland/Demos</a><br /><br />Group photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:<br />* <a href=\"https://indieweb.org/2024/Portland\">https://indieweb.org/2024/Portland</a><br /><br />Thanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (<a href=\"https://martymcgui.re\">@martymcgui.re</a>) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) for the IndieWebCamp live-tooting, and Ryan Barrett (<a href=\"https://snarfed.org\">@snarfed.org</a>) for amazing breakfast pastries from Dos Hermanos.<br /><br />The experience definitely raised our hopes and confidence for returning to Portland in 2025.<a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_note-2\">\u00b2</a><br /><br /><br />References:<br /><br /><a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/Create_Day\">https://indieweb.org/Create_Day</a><br /><a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland-10#t5Yj1_ref-2\">\u00b2</a> <a href=\"https://indieweb.org/Planning#Portland\">https://indieweb.org/Planning#Portland</a><br /><br />This is post 19 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a> <a href=\"https://indieweb.social/tags/2024_238\">#<span class=\"p-category\">2024_238</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\">https://tantek.com/2024/238/t3/indiewebcamp-auto-linking</a><br />\u2192 <a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-web\">https://tantek.com/2024/245/t1/read-write-suggest-edit-web</a></p>\n<a class=\"u-mention\" href=\"https://indieweb.social/@kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://martymcgui.re\"></a>\n<a class=\"u-mention\" href=\"https://snarfed.org\"></a>\n<a class=\"u-mention\" href=\"https://twitter.com/kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://xoxo.zone/@kevinmarks\"></a>",
"text": "Had a great time at IndieWebCamp Portland 2024 this past Sunday \u2014 our 10th IndieWebCamp in Portland!\n\nhttps://events.indieweb.org/2024/08/indiewebcamp-portland-2024-8bucXDlLqR0k\n\nBeing a one day #IndieWebCamp, we focused more on making, hacking, and creating, than on formal discussion sessions.\n\nNearly everyone gave a brief personal site intro with a summary of how they use their #IndieWeb site and what they would like to add, remove, or improve.\n* https://indieweb.org/2024/Portland/Intros\n\nThere were lots of informal discussions, some in the main room, on the walk to and from lunch, over lunch in the nearby outdoor patio, or at tables inside the lobby of the Hotel Grand Stark.\n\nWe wrapped up with our usual Create Day\u00b9 Demos session, live streamed for remote attendees to see as well. Lots of great demos of things people built, designed, removed, cleaned-up, documented, and blogged! Everyone still at the camp showed something on their personal site!\n* https://indieweb.org/2024/Portland/Demos\n\nGroup photo and lots more about IndieWebCamp Portland 2024 at the event\u2019s wiki page:\n* https://indieweb.org/2024/Portland\n\nThanks to everyone who pitched in to help organize IndieWebCamp Portland 2024! Thanks especially to Marty McGuire (@martymcgui.re) for taking live notes during both the personal site intros and create day demos, to Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) for the IndieWebCamp live-tooting, and Ryan Barrett (@snarfed.org) for amazing breakfast pastries from Dos Hermanos.\n\nThe experience definitely raised our hopes and confidence for returning to Portland in 2025.\u00b2\n\n\nReferences:\n\n\u00b9 https://indieweb.org/Create_Day\n\u00b2 https://indieweb.org/Planning#Portland\n\nThis is post 19 of #100PostsOfIndieWeb. #100Posts #2024_238\n\n\u2190 https://tantek.com/2024/238/t3/indiewebcamp-auto-linking\n\u2192 https://tantek.com/2024/245/t1/read-write-suggest-edit-web"
},
"published": "2024-08-30T04:09:00+00:00",
"post-type": "note",
"_id": "42140354",
"_source": "8007",
"_is_read": false
}
✏️ I want the Read Write Suggest-Edit Accept-Edit Update Web.
The consumer Infinite Scroll Web leaves us feeling empty.
Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.
A week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos¹, I noticed a few errors, typos or miscaptures, and pointed them out in-person.
Kevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon’s post editing feature and its support of #ActivityPub Updates. But this shouldn’t require being in the same room, whether IRL or chat.
We should be able to suggest edits to each other’s posts, as easily as we can reply and add a comment.
13 years ago I wrote²:
“The Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.”
Now I want the Read Write Suggest-Edit Accept-Edit Update Web.
The ↪ Reply button is fairly ubiquitous in modern post user interfaces (UIs).
Why not also a ✏️ Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid "performative" suggested edits.
If the author’s posts provide revision histories, when a suggested edit is accepted, a post’s history could show the contributor of the edit.
Instead of asking Kevin in-person, what if I could have posted special "Suggested Edit" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?
To enable such UIs and interactions across servers and implementations, we may need a new type of response³, perhaps with a special property (or more) to convey the edits being suggested.
There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:
* https://indieweb.org/edit
Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.
For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:
✏️ Suggest Edit
and link it to an edit URL for the static file for the post.
I don’t use GitHub static files myself for posts, but here’s an example of such an edit link for one of my projects:
https://tantek.com/github/cassis/edit/main/README.md
This will start the process of creating a “pull request”, GitHub’s jargon⁴ for a “suggested edit”.
After completing GitHub’s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said “pull request”, it’ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub’s jargon-filled ceremonies to “Merge” or “Squash & Merge”, “Delete fork”, etc. to accept the edit.
It’s an awkward interaction⁵, however useful for at least prototyping a ✏️ Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.
We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.
#readWriteWeb #editableWeb #suggestEdit #acceptEdit
References:
¹ https://indieweb.social/@kevinmarks/113025295600067213
² https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11
³ https://indieweb.org/responses
⁴ The phrase “pull request” was derived from the git command: “git request-pull” according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/
⁵ “edits” in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to “Edit” and “Save”. We should aspire to Wikipedia’s simplicity, not GitHub’s ceremonies.
This is post 20 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/242/t1/indiewebcamp-portland
→ https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web",
"content": {
"html": "<p>\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The consumer Infinite Scroll Web leaves us feeling empty.<br /><br />Too few of us participate in the Read Write Web, whether with personal sites or Wikipedia.<br /><br />A week ago when we wrapped up <a href=\"https://indieweb.social/tags/IndieWebCamp\">#<span class=\"p-category\">IndieWebCamp</span></a> Portland and I was reading Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a>) live-tooting of the demos<a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-1\">\u00b9</a>, I noticed a few errors, typos or miscaptures, and pointed them out in-person.<br /><br />Kevin was able to quickly edit his toots and update them for anyone reading, thanks to <a href=\"https://indieweb.social/tags/Mastodon\">#<span class=\"p-category\">Mastodon</span></a>\u2019s post editing feature and its support of <a href=\"https://indieweb.social/tags/ActivityPub\">#<span class=\"p-category\">ActivityPub</span></a> Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.<br /><br />We should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.<br /><br />13 years ago I wrote<a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-2\">\u00b2</a>:<br /><br />\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d<br /><br />Now I want the Read Write Suggest-Edit Accept-Edit Update Web.<br /><br />The \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).<br /><br />Why not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.<br /><br />If the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.<br /><br />Instead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?<br /><br />To enable such UIs and interactions across servers and implementations, we may need a new type of response<a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-3\">\u00b3</a>, perhaps with a special property (or more) to convey the edits being suggested.<br /><br />There is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the <a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> wiki:<br />* <a href=\"https://indieweb.org/edit\">https://indieweb.org/edit</a><br /><br />Our interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.<br /><br />For now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:<br /><br />\u270f\ufe0f Suggest Edit<br /><br />and link it to an edit URL for the static file for the post.<br /><br />I don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:<br /><br /><a href=\"https://tantek.com/github/cassis/edit/main/README.md\">https://tantek.com/github/cassis/edit/main/README.md</a><br /><br />This will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon<a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-4\">\u2074</a> for a \u201csuggested edit\u201d.<br /><br />After completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.<br /><br />It\u2019s an awkward interaction<a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_note-5\">\u2075</a>, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.<br /><br />We can start with the shortest path to getting something working, then learn, iterate, improve, repeat.<br /><br /><a href=\"https://indieweb.social/tags/readWriteWeb\">#<span class=\"p-category\">readWriteWeb</span></a> <a href=\"https://indieweb.social/tags/editableWeb\">#<span class=\"p-category\">editableWeb</span></a> <a href=\"https://indieweb.social/tags/suggestEdit\">#<span class=\"p-category\">suggestEdit</span></a> <a href=\"https://indieweb.social/tags/acceptEdit\">#<span class=\"p-category\">acceptEdit</span></a><br /><br />References:<br /><br /><a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-1\">\u00b9</a> <a href=\"https://indieweb.social/@kevinmarks/113025295600067213\">https://indieweb.social/@kevinmarks/113025295600067213</a><br /><a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-2\">\u00b2</a> <a href=\"https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\">https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11</a><br /><a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-3\">\u00b3</a> <a href=\"https://indieweb.org/responses\">https://indieweb.org/responses</a><br /><a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-4\">\u2074</a> The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to <a href=\"https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\">https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/</a><br /><a href=\"https://tantek.com/2024/245/t1/read-write-suggest-edit-update-web#t5Yn1_ref-5\">\u2075</a> \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.<br /><br />This is post 20 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed\">https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed</a></p>\n<a class=\"u-mention\" href=\"https://indieweb.social/@kevinmarks\"></a>",
"text": "\u270f\ufe0f I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe consumer Infinite Scroll Web leaves us feeling empty.\n\nToo few of us participate in the Read Write Web, whether with personal sites or Wikipedia.\n\nA week ago when we wrapped up #IndieWebCamp Portland and I was reading Kevin Marks (@kevinmarks@indieweb.social) live-tooting of the demos\u00b9, I noticed a few errors, typos or miscaptures, and pointed them out in-person.\n\nKevin was able to quickly edit his toots and update them for anyone reading, thanks to #Mastodon\u2019s post editing feature and its support of #ActivityPub Updates. But this shouldn\u2019t require being in the same room, whether IRL or chat.\n\nWe should be able to suggest edits to each other\u2019s posts, as easily as we can reply and add a comment.\n\n13 years ago I wrote\u00b2:\n\n\u00a0\u201cThe Read Write Web is no longer sufficient. I want the Read Fork Write Merge Web.\u201d\n\nNow I want the Read Write Suggest-Edit Accept-Edit Update Web.\n\nThe \u21aa Reply button is fairly ubiquitous in modern post user interfaces (UIs).\n\nWhy not also a \u270f\ufe0f Suggest Edit button, to craft a fix for a typo, grammar, or other minor error, and send the author for their review, and acceptance or rejection? Perhaps viewable only by the suggester and the author, to avoid \"performative\" suggested edits.\n\nIf the author\u2019s posts provide revision histories, when a suggested edit is accepted, a post\u2019s history could show the contributor of the edit.\n\nInstead of asking Kevin in-person, what if I could have posted special \"Suggested Edit\" responses in reply to his toots, for which he would receive special notifications, and could choose to one-click accept and update (or further edit) his toots?\n\nTo enable such UIs and interactions across servers and implementations, we may need a new type of response\u00b3, perhaps with a special property (or more) to convey the edits being suggested.\n\nThere is documentation of this and similar use-cases, prior art / UIs, as well as some brainstorming on the #IndieWeb wiki:\n* https://indieweb.org/edit\n\nOur interaction after IndieWebCamp has inspired me to take another look at how can we design and prototype solutions to this problem.\n\nFor now, if you host your blog and posts as static files on GitHub (or equivalent), you could add a button like this to your posts alongside Like, Reply, Repost buttons:\n\n\u270f\ufe0f Suggest Edit\n\nand link it to an edit URL for the static file for the post.\n\nI don\u2019t use GitHub static files myself for posts, but here\u2019s an example of such an edit link for one of my projects:\n\nhttps://tantek.com/github/cassis/edit/main/README.md\n\nThis will start the process of creating a \u201cpull request\u201d, GitHub\u2019s jargon\u2074 for a \u201csuggested edit\u201d.\n\nAfter completing GitHub\u2019s ceremony of entering multiple text fields (summary & description), and multiple clicks to create said \u201cpull request\u201d, it\u2019ll be sent to the author to review. Presuming the author likes the suggested edit, they can perform the other half of GitHub\u2019s jargon-filled ceremonies to \u201cMerge\u201d or \u201cSquash & Merge\u201d, \u201cDelete fork\u201d, etc. to accept the edit.\n\nIt\u2019s an awkward interaction\u2075, however useful for at least prototyping a \u270f\ufe0f Suggest Edit button on sites that store their posts as files in GitHub. Certainly worthy of experimenting with and gathering experience to design and build even better interactions.\n\nWe can start with the shortest path to getting something working, then learn, iterate, improve, repeat.\n\n#readWriteWeb #editableWeb #suggestEdit #acceptEdit\n\nReferences:\n\n\u00b9 https://indieweb.social/@kevinmarks/113025295600067213\n\u00b2 https://tantek.com/2011/174/t1/read-fork-write-merge-web-osb11\n\u00b3 https://indieweb.org/responses\n\u2074 The phrase \u201cpull request\u201d was derived from the git command: \u201cgit request-pull\u201d according to https://www.reddit.com/r/git/comments/nvahcp/comment/h12hzj7/\n\u2075 \u201cedits\u201d in GitHub require taking far more steps, and navigating far more jargon, then say, Wikipedia pages, which come down to \u201cEdit\u201d and \u201cSave\u201d. We should aspire to Wikipedia\u2019s simplicity, not GitHub\u2019s ceremonies.\n\nThis is post 20 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/242/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/246/t1/adventures-indieweb-activitypub-bridgy-fed"
},
"published": "2024-09-01T21:51:00+00:00",
"post-type": "note",
"_id": "42140316",
"_source": "8007",
"_is_read": false
}
Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking¹.
I’ve implemented an auto_link function² that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).
Much of it is based on what I’ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.
It may be time for me to write-up an auto-link specification based on the algorithms I’ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.
I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.
* URLs, @-s, and @-@-s
* # hashtags
* ^ footnotes
#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes
Previously, previously, previously:
* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases
* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated
* https://tantek.com/2023/043/t1/footnotes-unicode-links
* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo
References:
¹ https://indieweb.org/autolink
² https://github.com/tantek/cassis/blob/main/cassis.js
This is post 18 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/238/t1/indiewebcamp-portland
→ https://tantek.com/2024/242/t1/indiewebcamp-portland
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fed.brid.gy/r/https://tantek.com/2024/238/t3/indiewebcamp-auto-link",
"content": {
"html": "<p>Nice <a href=\"https://indieweb.social/tags/IndieWebCamp\">#<span class=\"p-category\">IndieWebCamp</span></a> discussion session with Kevin Marks (<a href=\"https://indieweb.social/@kevinmarks\">@kevinmarks@indieweb.social</a> <a href=\"https://xoxo.zone/@kevinmarks\">@kevinmarks@xoxo.zone</a> <a class=\"h-cassis-username\" href=\"https://twitter.com/kevinmarks\">@kevinmarks</a>) on the topic of auto-linking<a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-link#t5Yf3_note-1\">\u00b9</a>.<br /><br />I\u2019ve implemented an auto_link function<a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-link#t5Yf3_note-2\">\u00b2</a> that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).<br /><br />Much of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.<br /><br />It may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.<br /><br />I have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.<br /><br />* URLs, @-s, and @-@-s<br />* # hashtags<br />* ^ footnotes<br /><br /><a href=\"https://indieweb.social/tags/IndieWeb\">#<span class=\"p-category\">IndieWeb</span></a> <a href=\"https://indieweb.social/tags/autoLink\">#<span class=\"p-category\">autoLink</span></a> <a href=\"https://indieweb.social/tags/hashtag\">#<span class=\"p-category\">hashtag</span></a> <a href=\"https://indieweb.social/tags/hashtags\">#<span class=\"p-category\">hashtags</span></a> <a href=\"https://indieweb.social/tags/footnote\">#<span class=\"p-category\">footnote</span></a> <a href=\"https://indieweb.social/tags/footnotes\">#<span class=\"p-category\">footnotes</span></a><br /><br />Previously, previously, previously:<br /><br />* <a href=\"https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\">https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases</a><br />* <a href=\"https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\">https://tantek.com/2023/100/t1/auto-linked-hashtags-federated</a><br />* <a href=\"https://tantek.com/2023/043/t1/footnotes-unicode-links\">https://tantek.com/2023/043/t1/footnotes-unicode-links</a><br />* <a href=\"https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\">https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo</a><br /><br /><br />References:<br /><br /><a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-link#t5Yf3_ref-1\">\u00b9</a> <a href=\"https://indieweb.org/autolink\">https://indieweb.org/autolink</a><br /><a href=\"https://tantek.com/2024/238/t3/indiewebcamp-auto-link#t5Yf3_ref-2\">\u00b2</a> <a href=\"https://github.com/tantek/cassis/blob/main/cassis.js\">https://github.com/tantek/cassis/blob/main/cassis.js</a><br /><br /><br />This is post 18 of <a href=\"https://indieweb.social/tags/100PostsOfIndieWeb\">#<span class=\"p-category\">100PostsOfIndieWeb</span></a>. <a href=\"https://indieweb.social/tags/100Posts\">#<span class=\"p-category\">100Posts</span></a><br /><br />\u2190 <a href=\"https://tantek.com/2024/238/t1/indiewebcamp-portland\">https://tantek.com/2024/238/t1/indiewebcamp-portland</a><br />\u2192 <a href=\"https://tantek.com/2024/242/t1/indiewebcamp-portland\">https://tantek.com/2024/242/t1/indiewebcamp-portland</a></p>\n<a class=\"u-mention\" href=\"https://indieweb.social/@kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://twitter.com/kevinmarks\"></a>\n<a class=\"u-mention\" href=\"https://xoxo.zone/@kevinmarks\"></a>",
"text": "Nice #IndieWebCamp discussion session with Kevin Marks (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) on the topic of auto-linking\u00b9.\n\nI\u2019ve implemented an auto_link function\u00b2 that handles quite a few use-cases of URLs (with or without http: or https:), @-name @-domain @-domain/path @-@-handles, hashtags(#), and footnotes(^).\n\nMuch of it is based on what I\u2019ve seen work (or implemented) on sites and software, and some of it is based on logically extending how people are using text punctuation across various services.\n\nIt may be time for me to write-up an auto-link specification based on the algorithms I\u2019ve come up with, implemented, and am using live on my site. All the algorithms work fully offline (none of them require querying a site for more info, whether well-known or otherwise), so they can be used in offline-first authoring/writing clients.\n\nI have identified three logical chunks of auto-linking functionality, each of which has different constraints and potential needs for local to the linking context information (like hashtags need a default tagspace). Each would be a good section for a new specification. Each is used by this very post.\n\n* URLs, @-s, and @-@-s\n* # hashtags\n* ^ footnotes\n\n#IndieWeb #autoLink #hashtag #hashtags #footnote #footnotes\n\nPreviously, previously, previously:\n\n* https://tantek.com/2024/070/t1/updated-auto-linking-mention-use-cases\n* https://tantek.com/2023/100/t1/auto-linked-hashtags-federated\n* https://tantek.com/2023/043/t1/footnotes-unicode-links\n* https://tantek.com/2023/019/t5/reply-domain-above-address-and-silo\n\n\nReferences:\n\n\u00b9 https://indieweb.org/autolink\n\u00b2 https://github.com/tantek/cassis/blob/main/cassis.js\n\n\nThis is post 18 of #100PostsOfIndieWeb. #100Posts\n\n\u2190 https://tantek.com/2024/238/t1/indiewebcamp-portland\n\u2192 https://tantek.com/2024/242/t1/indiewebcamp-portland"
},
"published": "2024-08-25T23:00:00+00:00",
"post-type": "note",
"_id": "42140266",
"_source": "8007",
"_is_read": false
}
New blog post 📰
Maybe I’m just bored and need a break from social networks and touch grass before winter gets here. 🤷♂️
#blog #smallweb #indieweb
https://basic.bearblog.dev/the-thing-about-social-networks/
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://fosstodon.org/@jnv/113082114760865191",
"content": {
"html": "<p>New blog post \ud83d\udcf0 </p><p>Maybe I\u2019m just bored and need a break from social networks and touch grass before winter gets here. \ud83e\udd37\u200d\u2642\ufe0f </p><p><a href=\"https://fosstodon.org/tags/blog\">#<span>blog</span></a> <a href=\"https://fosstodon.org/tags/smallweb\">#<span>smallweb</span></a> <a href=\"https://fosstodon.org/tags/indieweb\">#<span>indieweb</span></a> </p><p><a href=\"https://basic.bearblog.dev/the-thing-about-social-networks/\"><span>https://</span><span>basic.bearblog.dev/the-thing-a</span><span>bout-social-networks/</span></a></p>",
"text": "New blog post \ud83d\udcf0 \n\nMaybe I\u2019m just bored and need a break from social networks and touch grass before winter gets here. \ud83e\udd37\u200d\u2642\ufe0f \n\n#blog #smallweb #indieweb \n\nhttps://basic.bearblog.dev/the-thing-about-social-networks/"
},
"published": "2024-09-05T00:28:55+00:00",
"post-type": "note",
"_id": "42140127",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@inautilo/113082021296739514",
"content": {
"html": "<p><a href=\"https://mastodon.social/tags/Business\">#<span>Business</span></a> <a href=\"https://mastodon.social/tags/Resources\">#<span>Resources</span></a><br />Awesome Indie \u00b7 Products made by independent makers and creators <a href=\"https://ilo.im/15zzrd\"><span>https://</span><span>ilo.im/15zzrd</span><span></span></a></p><p>_____<br /><a href=\"https://mastodon.social/tags/Creator\">#<span>Creator</span></a> <a href=\"https://mastodon.social/tags/Product\">#<span>Product</span></a> <a href=\"https://mastodon.social/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://mastodon.social/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://mastodon.social/tags/Design\">#<span>Design</span></a> <a href=\"https://mastodon.social/tags/ProductDesign\">#<span>ProductDesign</span></a> <a href=\"https://mastodon.social/tags/UiDesign\">#<span>UiDesign</span></a> <a href=\"https://mastodon.social/tags/WebDesign\">#<span>WebDesign</span></a> <a href=\"https://mastodon.social/tags/Development\">#<span>Development</span></a> <a href=\"https://mastodon.social/tags/WebDev\">#<span>WebDev</span></a></p>",
"text": "#Business #Resources\nAwesome Indie \u00b7 Products made by independent makers and creators https://ilo.im/15zzrd\n\n_____\n#Creator #Product #IndieWeb #SmallWeb #Design #ProductDesign #UiDesign #WebDesign #Development #WebDev"
},
"published": "2024-09-05T00:05:09+00:00",
"post-type": "note",
"_id": "42140034",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.social/@rodmoi/113081577136466924",
"content": {
"html": "<p>Verify whether two lists contain identical entries:</p><p><a href=\"https://rm-o.dev/til/list-diff/\"><span>https://</span><span>rm-o.dev/til/list-diff/</span><span></span></a></p><p><a href=\"https://mastodon.social/tags/bash\">#<span>bash</span></a> <a href=\"https://mastodon.social/tags/blog\">#<span>blog</span></a> <a href=\"https://mastodon.social/tags/diff\">#<span>diff</span></a> <a href=\"https://mastodon.social/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.social/tags/til\">#<span>til</span></a></p>",
"text": "Verify whether two lists contain identical entries:\n\nhttps://rm-o.dev/til/list-diff/\n\n#bash #blog #diff #indieweb #til"
},
"published": "2024-09-04T22:12:12+00:00",
"post-type": "note",
"_id": "42139316",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"url": "https://blog.mat.tl/2024/08/27/front-end-study-hall/",
"category": [
"blog",
"2024",
"frontend",
"indieweb"
],
"name": "Front end study hall",
"content": {
"text": "Attended my first Front End study hall today, hosted by Joe. I\u2019m still pretty tired from XOXO but it was good to see so many people turn up.\n\n\n\nI look forward to the next one. \n\n\n\nMy old battered MacBook Air",
"html": "<p>Attended my first <a href=\"https://events.indieweb.org/2024/08/front-end-study-hall-009-GOn9JPtiRiHR\">Front End study hall</a> today, hosted by <a href=\"http://artlung.com\">Joe</a>. I\u2019m still pretty tired from <a href=\"http://xoxofest.com\">XOXO</a> but it was good to see so many people turn up.</p>\n\n\n\n<p>I look forward to the next one. </p>\n\n\n\n<img width=\"768\" height=\"1024\" src=\"https://blog.mat.tl/wp-content/uploads/2024/08/img_5413-1-768x1024.jpg\" alt=\"MacBook Air and a lemonade on a table in Starbucks\" />My old battered MacBook Air\n\n\n<p></p>"
},
"author": {
"type": "card",
"name": "Matt Lee",
"url": "https://blog.mat.tl/author/mattl/",
"photo": null
},
"post-type": "article",
"_id": "42138846",
"_source": "8334",
"_is_read": true
}
{
"type": "entry",
"url": "https://blog.mat.tl/2018/10/16/firefox-on-ios-approximately-a-month-in/",
"category": [
"free-software",
"2018",
"browser",
"firefox",
"indieweb",
"ios",
"webkit"
],
"name": "Firefox on iOS approximately a month in (in which Matt casually returns to blogging)",
"content": {
"text": "I never thought I\u2019d have an iPhone.\n\n\n\nI never thought I\u2019d like using one.\n\n\n\nI have to say I do and I mostly do. So here we are, a little over a year after my Google Pixel went into a reboot loop just after charging it and promptly went into a drawer. Out came the iPhone SE I had got when I exchanged an Apple TV I\u2019d won at OSCON. I used that for several months before dropping it one too many times on the cold night of celebrating the 21st anniversary of the NeXT/Apple merger. Oops. I blame the Dr. Gil Amelio impressions.\n\n\n\nBriefly I used an iPhone 6 Plus before being given a new iPhone 8 as part of my job. Courageously I struggle every day with its proprietary headphone jack (I carry two sets of earbuds everywhere \u2014 one for my laptop and one for my phone \u2014 and as much as I begrudge the proprietary connector they are very nice and comfortable when you\u2019re on a lot of meeting calls) and long for the day where I can consider retrofitting one. But yes, even dyed in the wool free software folk use smartphones and I\u2019m not patient enough to do the Replicant route these days after many an attempt over the years from both versions of the OpenMoko, to various HTC Dream phones in various states of liberation. Heck, I even bought an iPad recently when I found out the occasional travel tablet I had from Google wasn\u2019t supported anymore but I will admit it doesn\u2019t get used very much at all but it is quite nice to use on a train. I am still very much committed to using free software on my actual laptop as the pile of assorted machines on the floor of my messy apartment will confirm with my day to day machine remaining the Dell XPS I spoke about last year.\n\n\n\nBack to the iPhone. When I first switched I figured I\u2019d hate it and so I didn\u2019t make much effort to integrate things. Instead I just downloaded the various Google apps to the iPhone and carried on my the same account I\u2019d used on my Pixel phone and the half dozen or so Android phones I\u2019d used prior to that. But recently I was at XOXOFEST in Portland and hanging out with various IndieWeb people including Tantek (who has an interesting no-phone setup that involves a Me-Fi device and a couple of iPod Touch devices, with Firefox as their browser) \u2014 it got me thinking about using Firefox as my main browser for the phone.\n\n\n\nState of the Union\n\n\n\nApple still doesn\u2019t let alternate browser engines to run on iOS for some reason, and as a result Safari, Chrome, Firefox, Firefox Focus and even Microsoft\u2019s Edge browser all use WebKit and all use the same version of WebKit as each other. If only we could have had Microsoft adopt WebKit for Edge for Windows, there would be one less engine to worry about although I\u2019ve never encountered Edge in the wild actually being used by anyone as I suspect everyone on Windows gets pushed to install Chrome pretty quickly these days but I\u2019m happy to be wrong on this point. Hopefully everyone installs Firefox instead after reading this.\n\n\n\n(To me, the whole iOS browser saga is a bit like making your own \u201cbrowser\u201d on Windows in Visual Basic by adding the Browser object to a form and slapping a couple of buttons on it, but I suspect Apple wouldn\u2019t approve such an app which dashes my hopes of becoming an instant browser vendor I suppose.)\n\n\n\nDespite the one and only engine rule, all of these browsers do things a little differently:\n\n\n\n\n\n\n\nSafari who likes to take over occasionally and frustrate me no end.\nFirefox Focus which is a great browser (often coupled with a VPN) for looking at sites with tons of ads and pop ups and other nasties. Clears itself on exit. Handy for looking up flight prices and searching things outside of your browsers fingerprint of your habits too.\nChrome on iOS neatly integrates with Google\u2019s various sites and offers its own take on private browsing via incognito mode but does not seem to offer anything by way of blocking ads, which is a little frustrating.\nAnd then there\u2019s Firefox, which seems to do a great job of blocking things even if the user interface is a little cluttered in places I am enjoying using it a lot more than I thought. In particular, it has a dedicated reading mode feature (Safari has this too and it was one of the few things I\u2019d occasionally use it for) and seems to have an actual proper download feature. It also lets me copy virtually any image to the clipboard which Chrome does not.\nSo for now I\u2019m going to keep using my iPhone. I have my eye on Purism and their phone project but I suspect it\u2019ll be a while before it\u2019ll be usable to the level where I don\u2019t feel like I have to sysadmin my phone. Until then I\u2019m probably going to keep using the iPhone.\n\n\n\nGil Amelio joke by Stevie DuBois",
"html": "<p>I never thought I\u2019d have an iPhone.</p>\n\n\n\n<p>I never thought I\u2019d like using one.</p>\n\n\n\n<p>I have to say I do and I mostly do. So here we are, a little over a year after my Google Pixel went into a reboot loop just after charging it and promptly went into a drawer. Out came the iPhone SE I had got when I exchanged an Apple TV I\u2019d won at OSCON. I used that for several months before dropping it one too many times on the cold night of celebrating the 21st anniversary of the NeXT/Apple merger. Oops. I blame the Dr. Gil Amelio impressions.</p>\n\n\n\n<img src=\"https://blog.mat.tl/wp-content/uploads/2018/10/giphy.gif\" alt=\"\" width=\"295\" height=\"167\" />\n\n\n\n<p>Briefly I used an iPhone 6 Plus before being given a new iPhone 8 as part of my job. <em>Courageously</em> I struggle every day with its proprietary headphone jack (I carry two sets of earbuds everywhere \u2014 one for my laptop and one for my phone \u2014 and as much as I begrudge the proprietary connector they are very nice and comfortable when you\u2019re on a lot of meeting calls) and long for the day where I can consider retrofitting one. But yes, even dyed in the wool free software folk use smartphones and I\u2019m not patient enough to do the <a href=\"http://replicant.us\">Replicant</a> route these days after many an attempt over the years from both versions of the OpenMoko, to various HTC Dream phones in various states of liberation. Heck, I even bought an iPad recently when I found out the occasional travel tablet I had from Google wasn\u2019t supported anymore but I will admit it doesn\u2019t get used very much at all but it is quite nice to use on a train. I am still very much committed to using free software on my actual laptop as the pile of assorted machines on the floor of my messy apartment will confirm with my day to day machine remaining the Dell XPS I spoke about last year.</p>\n\n\n\n<img src=\"https://blog.mat.tl/wp-content/uploads/2018/10/img_3702.png\" alt=\"\" width=\"173\" height=\"173\" />\n\n\n\n<p>Back to the iPhone. When I first switched I figured I\u2019d hate it and so I didn\u2019t make much effort to integrate things. Instead I just downloaded the various Google apps to the iPhone and carried on my the same account I\u2019d used on my Pixel phone and the half dozen or so Android phones I\u2019d used prior to that. But recently I was at <a href=\"http://2018.xoxofest.com\">XOXOFEST</a> in Portland and hanging out with various IndieWeb people including <a href=\"http://tantek.com\">Tantek (</a>who has an interesting no-phone setup that involves a Me-Fi device and a couple of iPod Touch devices, with Firefox as their browser) \u2014 it got me thinking about using Firefox as my main browser for the phone.</p>\n\n\n\n<h3>State of the Union</h3>\n\n\n\n<p>Apple <em>still</em> doesn\u2019t let alternate browser engines to run on iOS for <em>some</em> <em>reason</em>, and as a result Safari, Chrome, Firefox, Firefox Focus and even Microsoft\u2019s Edge browser all use WebKit and all use the same version of WebKit as each other. If only we could have had Microsoft adopt WebKit for Edge for Windows, there would be one less engine to worry about although I\u2019ve never encountered Edge in the wild actually being used by anyone as I suspect everyone on Windows gets pushed to install Chrome pretty quickly these days but I\u2019m happy to be wrong on this point. Hopefully everyone installs Firefox instead after reading this.</p>\n\n\n\n<p><em>(To me, the whole iOS browser saga is a bit like making your own \u201cbrowser\u201d on Windows in Visual Basic by adding the Browser object to a form and slapping a couple of buttons on it, but I suspect Apple wouldn\u2019t approve such an app which dashes my hopes of becoming an instant browser vendor I suppose.)</em></p>\n\n\n\n<p>Despite the one and only engine rule, all of these browsers do things a little differently:</p>\n\n\n\n<a href=\"https://defectivebydesign.org\"><img src=\"https://blog.mat.tl/wp-content/uploads/2018/10/old-dbd-magenta.jpg\" alt=\"\" width=\"270\" height=\"360\" /></a>\n\n\n\n<ul><li>Safari who likes to take over occasionally and frustrate me no end.</li>\n<li>Firefox Focus which is a great browser (often coupled with a VPN) for looking at sites with tons of ads and pop ups and other nasties. Clears itself on exit. Handy for looking up flight prices and searching things outside of your browsers fingerprint of your habits too.</li>\n<li>Chrome on iOS neatly integrates with Google\u2019s various sites and offers its own take on private browsing via incognito mode but does not seem to offer anything by way of blocking ads, which is a little frustrating.</li>\n<li>And then there\u2019s Firefox, which seems to do a great job of blocking things even if the user interface is a little cluttered in places I am enjoying using it a lot more than I thought. In particular, it has a dedicated reading mode feature (Safari has this too and it was one of the few things I\u2019d occasionally use it for) and seems to have an actual proper download feature. It also lets me copy virtually any image to the clipboard which Chrome does not.</li>\n</ul><p>So for now I\u2019m going to keep using my iPhone. I have my eye on Purism and their phone project but I suspect it\u2019ll be a while before it\u2019ll be usable to the level where I don\u2019t feel like I have to sysadmin my phone. Until then I\u2019m probably going to keep using the iPhone.</p>\n\n\n\n<blockquote><p>Gil Amelio joke by Stevie DuBois</p></blockquote>"
},
"author": {
"type": "card",
"name": "Matt Lee",
"url": "https://blog.mat.tl/author/mattl/",
"photo": null
},
"post-type": "article",
"_id": "42138850",
"_source": "8334",
"_is_read": true
}
I really like personal homepages and have quite a list of them bookmarked. I'll post one every week unless I fall behind this schedule. 😉 So here's Cool Personal Homepages #CPH Vol. 22: Patrick Jordan https://www.ariel.com.au/patrick/
#SmallWeb #indieweb #smolweb #PersonalSites #homepage
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.online/@jlsksr/113081061214548045",
"content": {
"html": "<p>I really like personal homepages and have quite a list of them bookmarked. I'll post one every week unless I fall behind this schedule. \ud83d\ude09 So here's Cool Personal Homepages <a href=\"https://mastodon.online/tags/CPH\">#<span>CPH</span></a> Vol. 22: Patrick Jordan <a href=\"https://www.ariel.com.au/patrick/\"><span>https://www.</span><span>ariel.com.au/patrick/</span><span></span></a></p><p><a href=\"https://mastodon.online/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://mastodon.online/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://mastodon.online/tags/smolweb\">#<span>smolweb</span></a> <a href=\"https://mastodon.online/tags/PersonalSites\">#<span>PersonalSites</span></a> <a href=\"https://mastodon.online/tags/homepage\">#<span>homepage</span></a></p>",
"text": "I really like personal homepages and have quite a list of them bookmarked. I'll post one every week unless I fall behind this schedule. \ud83d\ude09 So here's Cool Personal Homepages #CPH Vol. 22: Patrick Jordan https://www.ariel.com.au/patrick/\n\n#SmallWeb #indieweb #smolweb #PersonalSites #homepage"
},
"published": "2024-09-04T20:01:00+00:00",
"photo": [
"https://files.mastodon.social/cache/media_attachments/files/113/081/061/278/362/191/original/e59b8773aeeebb12.png"
],
"post-type": "photo",
"_id": "42138022",
"_source": "8007",
"_is_read": false
}
Took a week and a half to try to tie together the thoughtful threads of thinky thoughts that @darius @molly0xfff @kissane and @edyong209 wove through the last #xoxofest During that time, I discovered a parallel conversation about the #smallweb #indieweb #cozyweb what-do-we-call-it-now was happening across many good and new-to-me blogs. Zeitgeist! Did my best to capture it all here: https://www.mmmx.cloud/after-xoxo
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://xoxo.zone/@nim/113080846908174273",
"content": {
"html": "<p>Took a week and a half to try to tie together the thoughtful threads of thinky thoughts that <span class=\"h-card\"><a class=\"u-url\" href=\"https://friend.camp/@darius\">@<span>darius</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://hachyderm.io/@molly0xfff\">@<span>molly0xfff</span></a></span> <span class=\"h-card\"><a class=\"u-url\" href=\"https://mas.to/@kissane\">@<span>kissane</span></a></span> and <span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.xyz/@edyong209\">@<span>edyong209</span></a></span> wove through the last <a href=\"https://xoxo.zone/tags/xoxofest\">#<span>xoxofest</span></a> During that time, I discovered a parallel conversation about the <a href=\"https://xoxo.zone/tags/smallweb\">#<span>smallweb</span></a> <a href=\"https://xoxo.zone/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://xoxo.zone/tags/cozyweb\">#<span>cozyweb</span></a> what-do-we-call-it-now was happening across many good and new-to-me blogs. Zeitgeist! Did my best to capture it all here: <a href=\"https://www.mmmx.cloud/after-xoxo\"><span>https://www.</span><span>mmmx.cloud/after-xoxo</span><span></span></a></p>\n<a class=\"u-mention\" href=\"https://friend.camp/@darius\"></a>\n<a class=\"u-mention\" href=\"https://hachyderm.io/@molly0xfff\"></a>\n<a class=\"u-mention\" href=\"https://mas.to/@kissane\"></a>\n<a class=\"u-mention\" href=\"https://mastodon.xyz/@edyong209\"></a>",
"text": "Took a week and a half to try to tie together the thoughtful threads of thinky thoughts that @darius @molly0xfff @kissane and @edyong209 wove through the last #xoxofest During that time, I discovered a parallel conversation about the #smallweb #indieweb #cozyweb what-do-we-call-it-now was happening across many good and new-to-me blogs. Zeitgeist! Did my best to capture it all here: https://www.mmmx.cloud/after-xoxo"
},
"published": "2024-09-04T19:06:29+00:00",
"post-type": "note",
"_id": "42137414",
"_source": "8007",
"_is_read": false
}
By way of introduction: I'm Phil Nelson, I have been creating independent and corporate things on the internet for over 20 years including founding GameWikis (sold to Wikia), helping to launch $1M+ campaigns for Structure Sensor and OpenCV AI Kit, hosting the weekly OpenCV Live streaming show, running the indie vintage media site RetroStrange (home of RetroStrange TV!), and gaming blog SetSideB. My blog is https://extrafuture.com #indieweb #gaming #introduction #streaming
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://xoxo.zone/@philnelson/113080246008216029",
"content": {
"html": "<p>By way of introduction: I'm Phil Nelson, I have been creating independent and corporate things on the internet for over 20 years including founding GameWikis (sold to Wikia), helping to launch $1M+ campaigns for Structure Sensor and OpenCV AI Kit, hosting the weekly OpenCV Live streaming show, running the indie vintage media site RetroStrange (home of RetroStrange TV!), and gaming blog SetSideB. My blog is <a href=\"https://extrafuture.com\"><span>https://</span><span>extrafuture.com</span><span></span></a> <a href=\"https://xoxo.zone/tags/indieweb\">#<span>indieweb</span></a> <a href=\"https://xoxo.zone/tags/gaming\">#<span>gaming</span></a> <a href=\"https://xoxo.zone/tags/introduction\">#<span>introduction</span></a> <a href=\"https://xoxo.zone/tags/streaming\">#<span>streaming</span></a></p>",
"text": "By way of introduction: I'm Phil Nelson, I have been creating independent and corporate things on the internet for over 20 years including founding GameWikis (sold to Wikia), helping to launch $1M+ campaigns for Structure Sensor and OpenCV AI Kit, hosting the weekly OpenCV Live streaming show, running the indie vintage media site RetroStrange (home of RetroStrange TV!), and gaming blog SetSideB. My blog is https://extrafuture.com #indieweb #gaming #introduction #streaming"
},
"published": "2024-09-04T16:33:40+00:00",
"photo": [
"https://files.mastodon.social/cache/media_attachments/files/113/080/246/027/738/708/original/f0f58250e85db163.jpeg"
],
"post-type": "photo",
"_id": "42135727",
"_source": "8007",
"_is_read": false
}
A new post in which I talk about meeting Chris Farley's sister.
A Chance Encounter: https://krueger.ink/a-chance-encounter/
#IndieWeb #Blog
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://social.lol/@philomath/113080090197056503",
"content": {
"html": "<p>A new post in which I talk about meeting Chris Farley's sister.</p><p>A Chance Encounter: <a href=\"https://krueger.ink/a-chance-encounter/\"><span>https://</span><span>krueger.ink/a-chance-encounter</span><span>/</span></a></p><p><a href=\"https://social.lol/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://social.lol/tags/Blog\">#<span>Blog</span></a></p>",
"text": "A new post in which I talk about meeting Chris Farley's sister.\n\nA Chance Encounter: https://krueger.ink/a-chance-encounter/\n\n#IndieWeb #Blog"
},
"published": "2024-09-04T15:54:03+00:00",
"post-type": "note",
"_id": "42135311",
"_source": "8007",
"_is_read": false
}
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://bolha.us/@diegopds/113079955209445842",
"content": {
"html": "<p><a href=\"https://curadoria.bearblog.dev/o-mito-de-sisifo-albert-camus/\"><span>https://</span><span>curadoria.bearblog.dev/o-mito-</span><span>de-sisifo-albert-camus/</span></a></p><p><a href=\"https://bolha.us/tags/livros\">#<span>livros</span></a> <a href=\"https://bolha.us/tags/OMitoDeSisifo\">#<span>OMitoDeSisifo</span></a> <a href=\"https://bolha.us/tags/AlbertCamus\">#<span>AlbertCamus</span></a> <a href=\"https://bolha.us/tags/OMitoDeS%C3%ADsifo\">#<span>OMitoDeS\u00edsifo</span></a> <a href=\"https://bolha.us/tags/resenha\">#<span>resenha</span></a> <a href=\"https://bolha.us/tags/review\">#<span>review</span></a> <a href=\"https://bolha.us/tags/books\">#<span>books</span></a> <a href=\"https://bolha.us/tags/Absurdismo\">#<span>Absurdismo</span></a> <a href=\"https://bolha.us/tags/Absurdism\">#<span>Absurdism</span></a> <a href=\"https://bolha.us/tags/Absurdo\">#<span>Absurdo</span></a> <a href=\"https://bolha.us/tags/Absurd\">#<span>Absurd</span></a> <a href=\"https://bolha.us/tags/LeMytheDeSisyphe\">#<span>LeMytheDeSisyphe</span></a> <a href=\"https://bolha.us/tags/TheMythOfSisyphus\">#<span>TheMythOfSisyphus</span></a> <a href=\"https://bolha.us/tags/IndieWeb\">#<span>IndieWeb</span></a> <a href=\"https://bolha.us/tags/SmallWeb\">#<span>SmallWeb</span></a> <a href=\"https://bolha.us/tags/SurfandoWeb\">#<span>SurfandoWeb</span></a> <a href=\"https://bolha.us/tags/CuradoriaDaInternet\">#<span>CuradoriaDaInternet</span></a></p>",
"text": "https://curadoria.bearblog.dev/o-mito-de-sisifo-albert-camus/\n\n#livros #OMitoDeSisifo #AlbertCamus #OMitoDeS\u00edsifo #resenha #review #books #Absurdismo #Absurdism #Absurdo #Absurd #LeMytheDeSisyphe #TheMythOfSisyphus #IndieWeb #SmallWeb #SurfandoWeb #CuradoriaDaInternet"
},
"published": "2024-09-04T15:19:43+00:00",
"post-type": "note",
"_id": "42134973",
"_source": "8007",
"_is_read": false
}
@ananas Pierwszy raz słyszę to określenie #indieweb i bardzo mi się podoba
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mastodon.online/@pluszysta/113079874185135422",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mstdn.social/@ananas\">@<span>ananas</span></a></span> Pierwszy raz s\u0142ysz\u0119 to okre\u015blenie <a href=\"https://mastodon.online/tags/indieweb\">#<span>indieweb</span></a> i bardzo mi si\u0119 podoba</p>\n<a class=\"u-mention\" href=\"https://mstdn.social/@ananas\"></a>",
"text": "@ananas Pierwszy raz s\u0142ysz\u0119 to okre\u015blenie #indieweb i bardzo mi si\u0119 podoba"
},
"published": "2024-09-04T14:59:07+00:00",
"post-type": "note",
"_id": "42134813",
"_source": "8007",
"_is_read": false
}
So nice to see random websites support Webmentions!
{
"type": "entry",
"published": "2024-09-04T12:37:39.828462757+03:00",
"url": "https://fireburn.ru/posts/byw0Tio",
"category": [
"IndieWeb"
],
"content": {
"text": "So nice to see random websites support Webmentions!",
"html": "<p>So nice to see random websites support Webmentions!</p>"
},
"author": {
"type": "card",
"name": "Vika",
"url": "https://fireburn.ru/",
"photo": "https://fireburn.ru/.kittybox/media/uploads/fe/ad/f8/76/e94e284444605135ad468b1563070dac3d2ad642c366b1e180f6eb65"
},
"post-type": "note",
"_id": "42133744",
"_source": "1371",
"_is_read": false
}
@pluszysta Też mam od dłuższego czasu chęci dołożyć cegiełkę do budowy #indieweb ale pewnie nigdy się nie zdecyduję na konkretne oprogramowanie 
Czekam na pierwszy wpis! 
{
"type": "entry",
"author": {
"name": "#indieweb",
"url": "https://mastodon.social/tags/indieweb",
"photo": null
},
"url": "https://mstdn.social/@ananas/113079115079451536",
"content": {
"html": "<p><span class=\"h-card\"><a class=\"u-url\" href=\"https://mastodon.online/@pluszysta\">@<span>pluszysta</span></a></span> Te\u017c mam od d\u0142u\u017cszego czasu ch\u0119ci do\u0142o\u017cy\u0107 cegie\u0142k\u0119 do budowy <a href=\"https://mstdn.social/tags/indieweb\">#<span>indieweb</span></a> ale pewnie nigdy si\u0119 nie zdecyduj\u0119 na konkretne oprogramowanie <img alt=\":blobcatroll:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/392/433/original/9ac2514ac820251c.gif\" title=\":blobcatroll:\" width=\"16\" /></p><p>Czekam na pierwszy wpis! <img alt=\":ablobcatwobfast:\" height=\"16\" src=\"https://files.mastodon.social/cache/custom_emojis/images/000/811/894/original/b117e4d9ffad7a77.gif\" title=\":ablobcatwobfast:\" width=\"16\" /></p>\n<a class=\"u-mention\" href=\"https://mastodon.online/@pluszysta\"></a>",
"text": "@pluszysta Te\u017c mam od d\u0142u\u017cszego czasu ch\u0119ci do\u0142o\u017cy\u0107 cegie\u0142k\u0119 do budowy #indieweb ale pewnie nigdy si\u0119 nie zdecyduj\u0119 na konkretne oprogramowanie \n\nCzekam na pierwszy wpis!"
},
"published": "2024-09-04T11:46:04+00:00",
"post-type": "note",
"_id": "42133069",
"_source": "8007",
"_is_read": false
}