Polite.one – Polite is the first sovereign Content and Culture Operating System.
Polite is our plan B to save the Internet we love.
Polite is our plan B to save the Internet we love.
In an attempt to capture my content, I spent all day working on parsing Indieweb content in WordPress export files. How time flies when your figuring out regular expressions #mbnov
I only recently1 found out about TiddlyWiki, and immediately became enamored with it. After a couple months of playing with individual files, today I made a breakthrough today in hosting TiddlyWiki on my site.
I tried a few ways to initialize with cPanel on my current host, without any luck (I may return to this next, now that I’ve seen it in action. It turned out to be much easier to spin up a DigitalOcean droplet with Node, and follow the instructions in this guide from Josh Sullivan. The only modification I made was to use pm2
instead of forever
(as DigitalOcean already had it configured). I found another article on initializing pm2 with Tiddlywiki, and I used the following command in place of forever
:
pm2 start --name wikiprocessname /lib/node_modules/tiddlywiki/tiddlywiki.js -- nameofwikifolder --listen author=name username=name password=yourpassword "readers=(anon)"
Now, my experimentation with TiddlyWiki involved saving single html files and playing with each individually. I ended up with a few single-topic wikis – one for archiving my old notebooks, one for my video game collection, etc. I may combine at some point, but I thought it would be better for now to host individually. All that needed to happen, at least with the DigitalOcean reverse proxy setup, was to initialize nginx correctly.
sudo nano /etc/nginx/sites-available/DOMAIN2.COM
sudo nano /etc/nginx/sites-available/DOMAIN3.COM
Then in each file, make sure the port is unique and the URL matches. Symbol links for each:
sudo ln -s /etc/nginx/sites-available/DOMAIN2.COM /etc/nginx/sites-enabled/
sudo ln -s /etc/nginx/sites-available/DOMAIN3.COM /etc/nginx/sites-enabled/
Rerun certbot if needed for these URLs, then intialize each in pm2:
pm2 start --name wikiprocessname /lib/node_modules/tiddlywiki/tiddlywiki.js -- nameofwikifolder --listen port=#### author=name username=name password=yourpassword "readers=(anon)"
You can play with the various arguments for the TiddlyWiki webserver outlined here. I made a couple available to only myself for now by removing “readers=(anon)”. Don’t forget to run pm2 save
so your server stays up.
Going to keep playing, but right now my commonplace book is live with barely anything in it. Hope this helps someone get theirs off the ground as well.
There’s a common refrain on Twitter that can be heard echoing across the feed any time there’s a big news day or fresh political horror. It varies slightly in wording and context, but stays consistent in sentiment. The medium by which it’s delivered is also the subject of its ire: Twitter is a “hell
Every time I read about Friend Camp, I ponder whether it’s worth trying to spin one up on my own
Introduction What follows may tend toward the jargon-y end of programming, but I’ll endeavor to explain it all and go step-by-step to allow those with little or no programming experience to follow along and use the tools I’m describing in a very powerful way. I’ll do my best to link the jarg...
A pain point of the IndieWeb is that it's sometimes not as convenient to share content as it is on the common social media platforms. Let's improve that.
Last year after IndieWeb Summit in Portland, I sat down with IndieWeb co-founders Tantek Çelik and Aaron Parecki to talk about the history of IndieWebCamp for my upcoming book, Indie Microblogging. Only part of the interview will fit in the book, so I’m including a full transcript of our conversa...
Lurking Yesterday I was catching up on chat logs and ran across a stub for lurking on the IndieWeb wiki. I cleaned up the formatting a bit and added some additional material. Later Ton Zijlstra dropped