Woo hoo! it took a desire to slow down and make ‣ to resurrect this particular knowledge base previously archived:

select “Full screen” in the ... menu in the upper-right

select “Full screen” in the ... menu in the upper-right

A reoccurring theme that often introduces pain is putting your heart into a particular knowledge base platform only to have the platform shut down or no longer supported.

This is particularly an issue if the platform doesn’t provide a means to export your data or even worse, the owner of the platform doesn’t provide any notice and just goes MIA (bmfiddle.com)

If the export data doesn’t fully represent the interconnections of your data (Wikispaces), this become another hurdle to jump.

And in this case, I never had a plan as to if or where to host Tiddlyspace data and thankfully, the pandemic gave birth to running a server in the cloud (which technically I don’t own the hardware and would like a snapshot suitable for rebuilding the server locally)

[insert blog post in regards to designing an exit plan before you invest a lot of time into a new platform]

These reasons contribute to why developers prefer Open Source - it gives us/them control over our data.

I continue to be a fan of each having a Personal Data Locker, I time that has to come...