I’ve been having some issues in self-hosting a TiddlyWiki the way I’d like to. If anyone has any clear cut documentation on how to host a TiddlyWiki on one’s own domain name, I’d appreciate it. The documentation doesn’t seem as clear as I would expect (or perhaps more likely my server is having issues propagating/connecting?). If anything it’s muddled by the fact that they can seemingly be hosted in dozens of places one might not otherwise expect. My primary reservation is that it looks to me like they’re designed as single user instances, so I’m not exactly sure how Kicks et al. are effectuating their hyperconversations. Part of my issue is my mental model of some of the wikis involved in addition to the busy-ness of the sites’ themes, not to mention some of the non-standard conversational style on some. (I’ll get there eventually.)
I’ve also been using the IndieWeb’s MediaWiki for several years, so I’ve become much better at how it works as well as the ins-and-outs of the markup and how to do some slightly more advanced things using it. I’d set one up nearly a year ago this month and used it sporadically at best.
One of the bigger problems with my MediaWiki install was that somehow I wasn’t able to log into the primary account to do some of the necessary administrative functions. Today I got fed up with being hampered a bit and went spelunking into my install to see where things went wrong, suspecting that it was a one button install issue.
After digging through some documentation, I dug into the mySQL database and found a daunting looking [Blob] in the user_email field. Why couldn’t it be an easy-to-edit field? I not knowing anything better to do, I downloaded it, opened it up in my text editor, and discovered that I’d managed to leave a letter out of my own name in the email address! No wonder it wouldn’t work and the system wouldn’t let me reset my email address or password. A quick text edit later, the email was fixed, I uploaded the (now less intimidating) [Blob], and did a reset of the password in the admin interface, and we’re back in business! I’m always glad not to have borked the entire database and site.
If nothing else, it’ll help me in my explorations. Onward.
Calling @sphygmus…
(This is a much better question for @sphygmus, who seems to have a dope Webmention setup for her TiddlyWiki.)
I’ve been keeping my TiddlyWiki on Dropbox. I know this isn’t very Indieweb anointed – but it can be! Just name the wiki
index.htmland then:Use <a href="https://twcloud.github.io/tw5-dropbox/?type=full#" rel="nofollow ugc">‘in the sky’</a> to edit on mobile or Chromebooks.
On a full PC, sync Dropbox locally and use TiddlyWiki directly from there.
On the server, you can sync just your TiddlyWiki folder.
Or you can make the folder public on Dropbox and – I don’t know – put a CDN in front of it or mirror it somehow. Hopefully someone can pitch in better ideas than mine – just thought this could get the ideas going.
Calling @sphygmus…
Calling @sphygmus…
Aha – since you’ve got Webmentions up, let’s do this!
Hey Jacob! I’m familiar with your website – I covered your linkroll in
Directory Uprising.
It’s really comforting to see you interested in projects like directories and
whostyles that aren’t necessarily protocols – which the Indieweb can get very
focused on. Whostyles are definitely a tough one to turn into a protocol – since
CSS evolves over time and it’s tough to know how to restrict the styling. (But
it’s also important bc perhaps you don’t want to load a bunch of whostyles that
blow up your site.)
Your introduction of
all: revertis exciting – didn’t know about that!So this is exactly what I do as well – just manually create the whostyles and
apply them once I get into a longer dialogue with someone. This gives me (and
hopefully you now) plenty of time to mess with whostyles in the field.
This is another thing I think about as well – and I guess I was going to take it
on a case-by-case basis. If h0p3 has a new style, I might make a new ‘h0p3_2’
style for him – or might just update the old stuff if it makes sense.
Ok – as far as your proposals, they look good! My original plan was pretty
shaky – so am glad to see improvements. Just feeling a lot of gratitude that you
took the time and have energy to put into it.
I guess, as a bit of additional response, I should also mention that I’ve
thought about doing this as a JSON format rather than as CSS.
Here’s a look at the JSON format we’ve been using for
Multiverse box styles.
{
"header": {
"color": "#6B1173FF",
"back": "#B6B5A8A5"
},
"main": {
"fill": {
"type": "Solid",
"color": "#FAE9FF00",
"back": "#FFFFFFF2",
"direction": "vertical"
},
"border": {
"color": "#000000",
"style": "none",
"radius": 0
},
"shadow": {
"type": "None",
"color": "#B6B5A8A5",
"style": "plain"
},
"highlight": {
"type": "None",
"style": "plain"
},
"text": {
"font": {
"family": "Roboto"
},
"fill": {
"type": "Solid",
"color": "#6B1173FF"
}
}
},
"title": {
"fill": {
"type": "Solid",
"color": "#FAFAFA00"
},
"border": {
"color": "#2DC0A6FF",
"style": "dotted_1px",
"radius": 0
},
"shadow": {
"type": "None",
"style": "plain"
},
"highlight": {
"type": "None",
"style": "plain"
},
"text": {
"font": {
"family": "Red Rose"
},
"fill": {
"type": "Solid",
"color": "#17C27FFF"
}
}
}
}
For fonts, we could keep an expanded list of font names that are supported – or
at least a kind of registry – just like browsers already understand Verdana, Arial,
Courier, etc.
So perhaps this paired with a font registry format would do the trick. I don’t
have a strong preference tho – and am just throwing this out there.
Syndicated copies: