Comment by mro_name
4 years ago
> your fediverse node on a static site, à la blog feeds powered by RSS/Atom.
I'm aiming for such called #Seppo! There's a proof of concept https://demo.mro.name/shaarligo and funding application paper in german for now https://mro.name/o/2022-03-08-201643-prototypefund12-037.pdf
Would you pay a doller per month for such?
Oh, I came across this long ago and forgot about it. Thanks for the reminder! Hope you will find funding via Prototype Fund too!
> Would you pay a doller per month for such?
For what? Hosting or development? I'd definitely pay $1 for development. :)
BTW, you say #Seppo, but the repo says ShaarliGo. Are you considering a name change?
> For what? Hosting or development?
development. Hosting will be strictly decentral under your responsibility.
> you say #Seppo,
indeed, the other is a proof of concept and will remain as is.
> indeed, the other is a proof of concept and will remain as is.
I've always said that a easy to deploy CMS is one of the missing pieces for the IndieWeb. Preferably it should work on any shared hosting. PHP/SQLite would be a good fit, but I understand if you have other preferences.
> 2. download https://mro.name/Linux-x86_64/shaarligo.cgi[...]
That doesn't sound like a static node to me, just another backend-heavy design.
Can I deploy this to GitHub Pages? NeoCities? Netlify (sans Functions)? If the answer is "no", then it really doesn't have anything to do with what I'm talking about.
If the target node can host static files it can serve as a mirror, if it can execute CGIs you can edit.
How do you tell 'backend-heavy'?
I don't understand your first sentence in your comment. (It doesn't parse).
> How do you tell 'backend-heavy'?
Is there something confusing about the litmus test I gave in the comment you're responding to? What are the steps for deploying this thing to NeoCities? How would I use this to operate a node at $WHATEVER.github.io (where $WHATEVER is the name of my account or organization)?
A host capable of executing CGI applications—making it an active participant (rather than a passive one)—is exactly what I mean by "backend-heavy".
2 replies →