• Checkin to ホンダカーズζ¨ͺ桜 泉みγͺみ店

    by
    in Yokohama, Kanagawa, Japan
    1 year tune up for the car. Time flies.
  • by
    Seeing that Basecamp is shutting down their famous Signal vs Noise blog, I can’t help but wonder how much was the faff of dealing with Wordpress.

  • Checkin to Ootoya (ε€§ζˆΈε±‹)

    by
    in Yokohama, Kanagawa, Japan

  • First Days with Tanzawa

    by
    This was my first week using Tanzawa to power my actual blog and not just the dev blog. So far it's been great. I love how easy it is to post. I love that my site is IndieWeb native. I love that my site's stability has improved because I no longer require a database server. And I love that it's using fewer resources. It's great.

    This said, there's been a few rough edges that need polishing. Approving 50 some-odd webmentions after OwnYourSwarm started importing un-sent checkins required 50 some-odd page loads. Ouch.Β 

    I'd also like to improve site performance more in respect to images. Currently Tanzawa automatically requests the most efficient image format that your browser supports. Image format selection is all handled by the browser automatically (no Javascript). This alone usually cuts transfer size in half.

    While cutting the transfer size in half with a format change is a good start, I still don't need to be serving (at times) 4000px wide images. This is noticeable in streams where posts usually have images ( Checkins etc..) where the text loads instantly, but the progress bar lingers while images load.

    Rather, I'm going to change it to serve a resized (max 800px wide? ) image unless the original is specifically requested.

    Lastly, I want to start building a list of things that must (not should) be done before I can feel comfortable releasing Tanzawa for others to use and then start working on that list bit-by-bit.
  • by
    Fixed the rest of the site on mobile. Which really means content is now full-width and stacked, rather than in columns. It's amazing what you can do these days with just flex, flex columns and media queries (made super easy with Tailwind).
  • by
    I've fixed navigation on mobile, first time doing responsive design with tailwind. The hamburger menu is just a button with 3Β  8px by 1px brown divs inside.

    Fixed navigation on mobile.
  • by
    Added a small feature – clicking on the interaction count from the post list will open the detail page with the interactions open.
  • by
    Took my bike to the cafe to work a bit this afternoon. It’s so much fun. I can’t but feel like my parents and peers were sold a lie that driving brings freedom.Β 
  • by
    Migrated my graden (MediaWiki) from MySQL to SQLite like Tanzawa so I could shutdown and disable it on my server.Β  I'm also able to start importing checkins from swarm again – love how they look.

  • Response to https://twitter.com/simonw/status/1384383772255084546?s=20

    by
    I still think it's rude to return MBs of data if your client device might be an inexpensive mobile phone, but for things like server-to-server API responses I May have been being way too early 2000s in my thinking Turns out returning 10+ MB of JSON works fine these days!
    I used to think similarly until I started thinking about compute in terms of carbon emissions (all data transfer/parsing/sending/storage requires electricity and thus likely carbon emissions for now). Since then I try to minimize all compute wherever possible.
Previous 146 of 359 Next