† https://indiewebify.me - linked in the article as "a quick start to becoming a citizen of the IndieWeb"
† https://indiewebify.me - linked in the article as "a quick start to becoming a citizen of the IndieWeb"
That meta chat room is something. Is that how you came to this thread? It's strange to see dismissive comments in there but no outreach to the sources of them. Feels very cliquey.
Is SSG a static site generator? I'm pretty sure Known is a SQL database backed dynamic kind of thing. I looked at it several years ago and I don't remember it being static.
> unless WordPress has grown a lot I doubt it's a complete solution (not theme dependant, etc)
I know very little about WordPress. I do know there are IndieWeb plugins for it. To what extent WordPress might be a solution for you, I wouldn't have any idea.
> That meta chat room is something. Is that how you came to this thread?
I wasn't in the chat room. IndieWeb is something that I've had some interest in and I generally look at posts here about IndieWeb related stuff when they show up from time to time.
You're right, I glanced over it too quickly. Installing it is still too much for anyone without basic web development or system administration skills.
> I know very little about WordPress. I do know there are IndieWeb plugins for it. To what extent WordPress might be usable for you, I wouldn't have any idea.
From the chat log it's my understanding that the theme handles markup as opposed to plugins. So it seems unlikely that you could rely on plugins alone to get full functionality.
What would you think of an onboarding experience like at https://demo.mro.name/shaarligo/o/p/ac2gthz
Hm. I consider that crucial for a user's control (agency) over it's digital property. To not depend on my tool for the existencial moments of creation and deletion of what is in between populated by my (other) tool.
> UNIX system administration skills
I refer to remote copying and ensuring proper permissions of a single file. And deleting in case. How more basic could it possibly be?
The permissions may be embarrassing and peculiar for Microsofters, but adding other tooling doesn't simplify.
Or as the saying goes, when swimming, you'll get wet.
Loads! There's a lot of work to do here, maybe it's not work you're interested in - that's ok - but there is definitely work to do. Are you familiar with things like Yunohost, Sandstorm, and the like? This is a nascent field, in app terms it's barely at untar-configure-make-install relative to an app-store one tap install.
> The permissions may be embarrassing and peculiar for Microsofters, but adding other tooling doesn't simplify.
I've had the experience of running a hosting control panel used by a couple of thousand users (organisations) and I can absolutely tell you that tooling does simplify things for users. It doesn't even have to be that good, every incremental step we made got more users using more things. Things they easily could have done themselves (they had SSH, Postgres, MySQL, Perl, PHP, etc).
I'm not worried about folks not learning UNIX system admin skills. I am worried that one of the proprietary service stacks (in which I include local ones like Synology's App Center) will become a defacto platform in the same way proprietary OSes have won on the desktop and mobile. Fortunately they're not much good at the minute, but it's a blue ocean for them if they get better first.
And to be clear, I'm not advocating that users should not have to learn anything. I don't know where the bar will end up, but I think it'll be far away from chmod, one way or another.
They add dependencies, complexity and TOS to the stack. That's not appealing, even less so when it just promises to hide cp+chmod.
> UNIX system admin skills
You talk about a single copy + chmod like being rocket surgery. I know that FUD. It helps selling administration tools and services and keeping people dependant. But I am all about enabling individual agency.
So in the end operating anything requires care or call it administration. This complexity can be hidden (comes with additional otherwise unnecessary dependencies and lock in) or reduced (my admitted radical approach).
So I both lower the bar and educate that cp+chmod don't hurt. The hardest part is prbly downloading and using a ftp client.
I do empathise with what you're saying, but there is nothing radical in your approach. It's a staid and common position in technical circles, and in my experience it lends itself to being blind sided.
Hopefully you will prove me wrong but I think I'll be proven right.
I'll do my best to offer a low-fat, no-sugar option to get stuff into the internet, that's absolutely layperson-friendly. And contribute to the fediverse if wanted. And even the silos.
Very few steps, no unexplained jargon, very few core concepts. Ideally no running code facing other users (alas, the search). Use existing tools, no NIH. Align with what the hosters explain and sell.
But absolutely zero dependencies that might need patches (except a webserver). No node, PHP etc. No DB. A minimal trusted computing base. You can simply copy the whole site to backup/mirror it.