• by
    Just a small update today. I shipped the login screen I shared yesterday and planned out what I need to build to support IndieAuth. I think I can use DRF to help handle token generation and authentication using the token.
  • by
    With webmentions working, next up I want to tackle support for check-ins. Currently I'm using OwnYourSwarm to backfeed my checkins to my main site and I'd like to continue doing so with Tanzawa.

    Doing so requires that I add support for IndieAuth (so I can login using just my domain) and Micropub. I'm starting on the IndieAuth implementation, which means I need to actually start with a login page for users to authenticate (thus far I've been using the django admin).

    This is what it's looking like so far. Something feels off in the design of it, but I can't quite place my finger on what it is.

    The base login form

  • A short list of things cooler than Clubhouse

    by

    Inspired by Seth's Chasing the cool kids, I've made a short list of things that are cooler than Clubhouse.


    • Not caring what the "cool" kids are doing and doing your own thing.

    • Building and learning about the systems that make the world go around.

    • Not uploading your entire contact list to some random company so you can eavesdrop on the "cool" kids.

    • Fighting for an open web so that you and future generations can access the world without gatekeepers.

    • Owning your content.



    The urgent advice usually ends with “blogs are dead"

    If you always have to mention that "blogs are dead", perhaps they aren't actually dead. They never were dead. They're just not "cool" anymore. The people who made blogging cool and fun? They're mostly still blogging.


    Publish. Consistently. With patience. Own your assets. Don’t let a middleman be your landlord. Yell at Google for blocking your emails and hope it’ll work eventually. Continually push for RSS and an open web. With patience.

    Yes.

  • by
    Yesterday when I shipped sending webmentions I ran into an error that didn't occur in development. Posting the webmention would work, but my response would timeout when trying to save content.

    When updating a post you're supposed to send webmentions, update your content, then send webmentions again. As I'm trying to keep server requirements as simple as possible I'm doing all of the sending inline.

    Looking at my logs what appeared to be happening was everything would just lock, then once my timeout occurred, I'd see my initial post request to Tanzawa come through, the timeout, and then Wordpress making a request to Tanzawa to retrieve it's mention.

    This was happening because gunicorn only has 2 workers by default, which wasn't enough to handle processing a long request simultaneously with an incoming request. Increasing the workers from 2 to 4 solved the issue.
  • by
    Today marks 1 month since I got the first instance of Tanzawa live. 🎉

    Today I shipped support for sending webmentions. So now when I link to a post, Tanzawa will send webmentions. It's all done inline, so there's now a slow-down when saving. I should do it in the background, but I'm not sure I want to introduce redis/celery and all that complexity quite yet (or ever?).

    A webmention from Tanzawa


    I have a table you can view in the admin where you can see which posts sent which webmentions and if they were successful or not.

    I also shipped a small update to webmention receiving. When an existing webmention is updated, I now also update how the webmention is displayed. In the case of an update, the comment must be re-moderated.

    The final small "quality-of-life" update is when I save a post I now show a link in the success message to view the post.
    Small quality of life update
Previous 331 of 732 Next