@m2m @chris @grueproof What advice would you all give to individuals without deep IT skills who would like elegantly coded, resource-light, understandable websites for:
- booksite
- archiving text+image articles originally published as social media threads (ideally with comparable ease of use for image sizing & consistent layout)
- web version of talks, words+slides
- permanent personal sites for academics & independent scholars
Searching for 21 months, still stumped...
#IndieWeb ?

This is a product of this very-old-school LOTR fan site: https://www.lotrfanmb.com
(It’s got a banner!)

This site is mostly to host the fan forums but it also hosts an archive of fan works like the above. There are some other good “sung to the tune ofs” on there to check out

Gotta love the home grown, creator-owned fan works on display… this was before the “Web 2.0” social media companies centralized and devoured fandom interaction

Hoping the #indieWeb keeps on bringing that spirit back!

Indie social sign-in could go mainstream
https://blog.erlend.sh/indie-social-sign-in-could-go-mainstream
submitted by erlend_sh to fediverse3 points | 0 commentshttps://blog.erlend.sh/indie-social-sign-in-could-go-mainstreamBack in June I wrote about an exciting confluence of digital auth tech:
(1) The commodification of #OIDC infrastructure, (2) the emergence of #FedCM, (3) and the compatibility of both with #indieauth .
In short, it is now easier than ever to log into web applications using

Back in June I wrote about an exciting confluence of digital auth tech:

(1) The commodification of #OIDC infrastructure, (2) the emergence of #FedCM, (3) and the compatibility of both with #indieauth .

In short, it is now easier than ever to log into web applications using your own website as an identity provider. Or at least, it would be, if your favorite web apps supported these agency-enhancing technologies.

https://blog.erlend.sh/indie-social-sign-in-could-go-mainstream

#opensource #indieweb #identity

Thanking my RSS readers

Found a cool message on Kev’s blog about appreciating RSS readers, so I decided to add something similar to mine. This WordPress snippet displays a random welcome messages to all RSS readers.

https://jeremy.hu/thanking-my-rss-readers/

#EN #IndieWeb #plugin #RSS #Tutorial #WordPress

Taking a short break from Threads and Bluesky. Nothing against those services, but I started over-thinking the post length differences. I need to focus on work and blogging first. Because my blog natively uses ActivityPub, Mastodon folks will still see my posts.

static website with rss

WordPress is way too ambitious for a very simple website that lists cool blogs like blogroll.fr and I'd like to turn the current website into a static website, using ideally only HTML and CSS, or a tiny bit of something else if really needed.

The only thing that really worries me is that I would like to keep an RSS feed so that it's easy to follow when blogs are added (an

https://alexsirac.com/static-website-with-rss/

#en #HelpMe #indieWeb #WebDevelopment

Hosting your own content is the core of the #indieweb, says @shellsharks

"f you are reading this, or you have a personal site, you are already part of it. Full stop. You don’t need to be shy. You have things to say and people WANT to listen, they want to read, they want to connect. You don’t have to be an “influencer” or have a big following. Your writing doesn’t need to be AMAZING. You don’t need to write to an audience. Write for yourself. Then share it. "

https://shellsharks.com/notes/2024/05/14/one-of-us

Fediverse is a bust on tiny instances

If even long-time production-tested complex systems frequently fail, why do some people still maintain the illusion that a newly developed complex system, with each component created by a different developer, will function flawlessly when its parts assemble in production for the first time within the expected deadline?

https://rm-o.dev/notes/complex-systems/

#agile #complexity #development #indieweb #note #system

Thinking again on learning enough HTML to pass making a neocities site has been pretty rewarding so far, but I cannot stress enough that I have to be in "focus and problem solving" mode, which is sometimes not easy to be in, or stay in. (ADHD WOOOO)

https://www.w3schools.com/html
, and the neocities reddit have been great wells of knowledge for things that I know are simple, but still struggling with so far.

That being said. I fixed all the links from opening new tabs, THEN I set up a comment for myself in the future so I don't make the same mistake!

I'm liking this a lot so far, and even if I did have to rebuild my artist website, it suddenly doesn't feel so out of reach....

#HonestSelfHostingMeta #HTML #CodeNewbie #neocities #indieweb

Bei Heise-Online (und in der c’t) kann man diesen schönen Artikel über Kirby und das IndieWeb lesen (heise+). Jo Bager beschreibt in der Reihe, wie man Kirby Schritt für Schritt ans IndieWeb anschließt. Im aktuellen Teil geht's um die Installation von Kirby und meinem Komments Plugin. Später soll es dann mit dem IndieConnector weitergehen.
Freut mich sehr!

https://www.heise.de/select/ct/2024/19/2420713435195546878

#kirby #kirbycms #komments #indieconnector #indieweb

BPJ: Orchard Inn Blues Night

Brissle Proper Job series issue #5 Orchard Inn Blues Night, a venue on Spike Island at a 190 year old pub with great music on a Monday night. …

https://barrd.net/bpj-orchard-inn-blues-night/

#BrissleProperJob #IndieWeb

I'm talking about Aliens! But why aren't they talking back?

Read my blog summarizing a really cool hypothesis to the Fermi Paradox that was shared on the ArXiv last month.

https://caffeineandlasers.neocities.org/blogs/Aliens

#Astrodon #astronomy #scifi #alien #SmallWeb #IndieWeb #blog

If you liked Trunk Writing my feed URL is https://robertkingett.com/feed/ #RSS #IndieWeb #SmallWeb

I made a neat image annotation widget for my blog using OpenSeadragon and Annotorious: https://thzinc.com/2024/09/04/a-bike-tool-roll-made-from-a-canvas-bag.html

I tried to ensure this was still usable with a screen reader–I think I did okay?

#maker #indieweb #a11y

If I link to my own post that has webmentions wired up like https://ryanparsley.com/note/webmentions/, does that show up in my webmention list? I'm still trying to wrap my head around how this works. #IndieWeb

✏️ 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
#IndieWebCamp #Mastodon #ActivityPub #IndieWeb #readWriteWeb #editableWeb #suggestEdit #acceptEdit #100PostsOfIndieWeb #100Posts