**Growing up with Sci-Fi in the ’70s**
Science fiction played a large part in my youth, this is a story about some of the shows that influenced me during the 1970's.
Trunk Writing https://robertkingett.com/posts/6625/ #NoPayWall #IndieWeb #Blog #Blogs
Small Web September looks like a fun event!
https://smallweb.dreamwidth.org/2335.html
Via @LeGaosaure
#indieweb #SmallWeb #SmallWebSeptember #PersonalWebsite
Adventures in IndieWeb / ActivityPub (AP) bridging:
While in general my posts are being successfully federated by https://fed.brid.gy/ #BridgyFed, my most recent three posts, and two more earlier this year, were delivered successfully to multiple #Mastodon instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).
These most recent posts:
* https://tantek.com/2024/245/t1/read-write-suggest-edit-web
* https://tantek.com/2024/242/t1/indiewebcamp-portland
* https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
and these earlier this year:
* https://tantek.com/2024/173/t1/years-posse-microformats-adoption
* https://tantek.com/2024/044/t1/twenty-years-microformats
were all delivered to over 300 instances, which returned "202" codes, however none of them show up in profile views on those instances, e.g.
* https://indieweb.social/@tantek.com@tantek.com
* https://mastodon.social/@tantek.com@tantek.com
* https://social.coop/@tantek.com@tantek.com
* https://w3c.social/@tantek.com@tantek.com
(My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”)
Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?
GitHub tracking bug in case you can help narrow/track this down or have
* https://github.com/snarfed/bridgy-fed/issues/884
Let’s see if this post makes it to your Mastodon (or other #fediverse) reader/client.
#indieweb #ActivityPub
This is post 21 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/245/t1/read-write-suggest-edit-web
→ 🔮
"Use WordPress if you want. Use Blogger. Hell, use Frontpage 98 if you want. Or learn some HTML and CSS and type it all up in notepad.exe. Or just HTML, don't even bother with the CSS. Just make it yours."
IndieWeb vs. indie web https://fyr.io/post/indieweb_vs_indie_web
#blogging #PersonalWebsites #blogs #IndieWeb #WebDev #WebDesign #HTML #CSS #SmallWeb #SmolWeb #WordPress
#Business #Misconceptions
IndieWeb vs. indie web · “It’s unfortunate that the IndieWeb has that name.” https://ilo.im/15zz1z
_____
#Terminology #HumanWeb #IndieWeb #SmallWeb #SlowWeb #OpenStandards #Website #Blog #Development #WebDev
Search the git history for all commits that have added or removed a string or regex pattern across all branches:
https://rm-o.dev/til/find-all-commits-that-added-or-removed-a-string/
I'm not a big lover of horror films, although I have seen a couple. However, none have left me feeling more horrified than David Lynch's Mulholland Drive, notably the diner scene at Winkie's. For me, this is the most terrifying sequence in cinema history.
While in general my posts are being successfully federated by https://fed.brid.gy/ (#BridgyFed), my most recent three posts, and two more earlier this year, were delivered successfully to multiple #Mastodon instances AP inboxes (returned 202), however the posts do not show up if you look-up my profile on those instances (and thus followers never saw them).
These most recent posts:
* https://tantek.com/2024/245/t1/read-write-suggest-edit-web
* https://tantek.com/2024/242/t1/indiewebcamp-portland
* https://tantek.com/2024/238/t3/indiewebcamp-auto-linking
and these earlier this year:
* https://tantek.com/2024/173/t1/years-posse-microformats-adoption
* https://tantek.com/2024/044/t1/twenty-years-microformats
were all delivered to over 300 instances, which returned "202" codes, however none of them show up in profile views on those instances, e.g.
* https://indieweb.social/@tantek.com@tantek.com
* https://mastodon.social/@tantek.com@tantek.com
* https://social.coop/@tantek.com@tantek.com
* https://w3c.social/@tantek.com@tantek.com
(My most recent post on all of these is the same 2024-08-25 post starting with “All setup here at IndieWebCamp Portland!”)
Why would a Mastodon instance respond with a 202 to an AP inbox delivery and then not show that post on the local profile view?
GitHub tracking bug in case you can help narrow/track this down or have
* https://github.com/snarfed/bridgy-fed/issues/884
Let’s see if this post makes it to your Mastodon (or other #fediverse) reader/client.
#indieweb #ActivityPub
This is post 21 of #100PostsOfIndieWeb. #100Posts
← https://tantek.com/2024/245/t1/read-write-suggest-edit-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 @KevinMarks.com (@kevinmarks@indieweb.social @kevinmarks@xoxo.zone @kevinmarks) 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, 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
→ 🔮
Fun fact: I'm building a Micropub posting app, and one of it's features is letting the user automatically draft a summary for the post they're writing; I wonder what would happen if I fed it this post...
Added a Now page to my site! Such a simple yet powerful idea (and you gotta love a short URL😜) https://haglund.app/now #indieweb #blog #web
Para quien le apetezca curiosear blogs, o necesite inspiración, aquí hay para quedarse un buen rato:
(Descubierto a partir de un enlace al blog del autor compartido por @aperalesf. ¡Gracias!)
#blogs #indieweb #websencilla #SmallWeb