-
-
Notifications
You must be signed in to change notification settings - Fork 22
Journal
Tiddlyspot "save to web" is back!
How is it possible?!
Tiddlyhost has taken over the tiddlyspot.com domain name and now serves all the old Tiddlyspot sites, with "save to web" support just like the old days. Try it and let me know if you have problems.
Tiddlyspot saving is user/password based and doesn't require a Tiddlyhost account or a login, but if you do have a Tiddlyhost account you can claim ownership of a Tiddlyspot site. This lets you see it in your sites list, and (in future) will let you do things like change the password, and maybe some other stuff I won't mention just yet.
But really, how?
What's new:
- TiddlyWiki Classic support.
- Support for uploading an existing TiddlyWiki.
- A guide on how to upload existing TiddlyWiki, especially if it's 5.1.23 or older.
- A fix for missing plugin library.
- Various other tweaks and improvements.
Current focus:
- How do I create a plugin? (A lot has changed since the old days. I have some learning to do.)
Hub related updates:
- Clickable tags. Example.
- Clickable usernames. Example. Note: This requires adding a username to your account, which you can do here.
- Gravatar profile pics Note: This is off by default, but you can enable it at here.
- Searching. Example
- Sorting, by name or view count. Example.
Site related updates:
- Renaming sites no longer breaks saving
- A download button
- View counts
Meta:
- Not sure if I'll continue to maintain this journal here. Perhaps it could move to a TiddlyWiki, along with the FAQ.
- I guess some of the above items aren't all that new since I mentioned them below already.
Stats:
- So far we have 74 active users (for some definition of active), and 88 sites.
- There are currently 41 open issues, and 12 closed.
According to this blog post, we've launched. The "hub" is somewhat experimental, but I think it has some potential.
Recent new features:
- Site view counters
- A download link
- Clickable tags
Let's Encrypt is awesome. We're live! See 31e9371 for more details.
I'm not sure if it's production ready yet, so let's proceed slowly until I have a better idea how stable things are on the current hosting solution.
(From original README.md)
Rough plan:
- Should be 100% containerized from the start
- Should use SSL from the start
- Will use Rails, for better or for worse
- Should have a serious deploy process (somehow)
- Should support subscription billing for users (somehow)
- Use S3 for saving Tiddlywiki files (probably)