-
The Week #34
by- I forget what I was searching for but I found this fantastic blog (in English) about trains in Japan called Tokyo Railway Labrinth. It has history of different trains and so much more. I love when I find a site where someone is just geeking out about their passion online.
- During the week some co-workers and I were discussing burgers. This gave me a craving for an avocado cheese burger from Kua`Aina. I recounted the story of how, even though in Japan you're supposed to have a nice light Japanese meal the day before the birth of your child, my wife was craving a burger and calories, so we went to the Enoshima Kuga`Aina before Leo was born. It was delicious as always. And since we got there right after they opened, not busy.
- I also visited the Fujiko Museum in Kawasaki over the weekend a.k.a. the Doraemon museum. I've never read the manga, but I have watched a couple of the movies (Leo's going through a mini-boom at the moment). It was pretty great, though I spent most of the time holding Leo watching this giant Rube Goldberg machine move a bunch of different balls across the room.
- I started working on replies in Tanzawa. Introducing Turbo to add some dynamism to admin interface. It's turned into a bigger rabbit hole than expected. I imagine most rails devs are familiar with the basics of Turbo (Links) but as a Django dev, things like Turbo aren't included, so there's a bit of a learning curve for me to implement it properly. That said - it's coming along.
-
byBreaking the admin into TurboFrames and it feels like I'm rewriting the entire app. It's a good opportunity to refactor templates and views, but man do I feel like a hamster running on a wheel while I figure out the implementation patterns.
-
Checkin to Fujiko F. Fujio Museum (θ€εγ»Fγ»δΈδΊιγγ₯γΌγΈγ’γ )
Doraemon! -
byReworked my template a bit and it seems that comments are now coming through!
Reply from Tanzawa in moderation -
byI can now extract the reply data for microformat and schema.org schemas when I reply. Editing and RSS is also working nicely as well. I'm sending webmentions, but I think my template needs some tweaking as the comment is coming through.
Mixing Turbo (for replies) and regular page loads (for status/articles) is starting to show it's limits. I think after I get replies shipped, I need to step back and refactor my admin template to go full-in with Turbo. -
Checkin to Enoshima Station (EN06) (ζ±γε³Άι§ )
-
Checkin to KUA`AINA
-
byWorking on the display of replies. It's still a big work in progress - but progress none the less. The publish date / by-line work well for articles, but adding in the reply to URL makes it feel like there's too much information.
My initial design matching the admin interface.
Perhaps it would be better to make the response title itself a link and hide the url?A bit cleaner look? -
by
I wrote a small post on the Tanzawa blog about My Goals for Tanzawa.
-
My Goal for Tanzawa
byI realized while I've been blogging about the development of Tanzawa, I haven't talked much about my overall goals for the system. This post will dive a bit into what my goals are for the system and how I envision it working.IndieWeb
My main goal for Tanzawa is to make a system that makes it enjoyable and easy to blog (be it micro, photo, articles, whatever) while maintaining ownership of your content. Yes, you can achieve this Wordpress, to a degree, but it's not made for it.
David Shanske and the other devs who've made the IndieWeb plugins for Wordpress have done fantastic work. It got me back into blogging and fighting for the open web. Tanzawa is my attempt to build upon the ideas in their work and push it forward.Sustainability & Privacy
My other main goal for Tanzawa is to bring awareness and advocate for a sustainable web. Modern computer systems waste so many resources with poor design, unoptimized media, legacy formats - you name it. Tanzawa will always strive to have the lightest impact on your server, your network, and when rendered on your computer/phone.
To those ends Tanzawa uses minimal css styled with Tailwind - no large component frameworks. Image tags are written so browsers always choose the latest file format with the best compression so less data is transferred. What's more, we don't change file formats until it's first requested, saving your server from making and your disk from storing images that will never be served. We proudly use system fonts, avoiding megabytes of downloads.
A smaller, but still important goal for Tanzawa is to build a system that respects your privacy and the privacy of your visitors. We don't include any third-party libraries or scripts that track anything about you. We also strip all location and other exif from uploaded photos.Own Your Data
One of the promises of the of POSSE and backfeeding is that you are in control. The current tooling works, but it feels too geeky. I either need to have a custom setup with a static site (which means writing Markdown and using a command line) or use Wordpress, and then you're stuck within the confines of Wordpress.
I want to make it simple to "tweet" from your blog. To backfeed from the silos into your blog. And I want to be able to remix this data together, to make new posts and pages, rather than having it locked in posts or behind an opaque API.
The recent resurgence of interest in blogging and RSS makes me hopeful that when Tanzawa is ready to general usage there's a chance it'll make a difference.