Base Thoughts 

• I don't think posting should be syndicated automatically on publish. There's a couple of reasons for this: 
  • Tanzawa doesn't support any kind of background tasks. Posts that have a bunch of links take a while to complete it tries to send webmentions. Adding more external requests could increase the response time to longer than the request timeout allows quite easily. This is especially true because webmentions require 2 requests per save (before content update and after content update). We could probably process webmentions concurrently to speed this up, but that feels like a bit much at this point? It may be easy with asyncio, but I'd need to research it.
  • When I was posting with Wordpress there was a syndication checkbox (via brid.gy) and found it you'd get errors if you saved twice as the post had already been syndicated. Because there also wasn't a preview, it was always a bit of a gamble for how it would post.
• Syndication is a separate concern from authoring posts themselves. And as such warrants dedicated screens to make it _right_.  Initially I had thought it might work well to handle syndication via a modal on the edit post page, but the more I think about it, it would box us in.
• Brid.gy is still super handy for backfeeding likes/replies as webmentions. I still think brid.gy is useful / "required" unless we were to build in some kind of polling mechanism, which is difficult without support for cron/background tasks. ( It could be done "easily" with a django management command, I'm hesitant to introduce undue complexity).
• "Syndication" feels a bit jargony to me. Is "Cross post" (or something similar)  a better term to use in the interface?
• Each syndication destination is going to require some kind of settings (API keys, mostly). These can / should be managed via the Django admin?

Workflow

• Creating a new syndication would happen from the edit post button. The button should be on the meta menu (on the right), below the publish  buttons and only display once the post is published (you can't syndicate a draft).
• Clicking this button would take you to dedicated syndication page.
• The top of the page would be a form. The form would display the syndication text and up to 4 photos (with the caption).
  
  The syndication text is free text and pre-filled with either the post title + link or the first 280 chars of the note. Above the text field itself would be a segmented control (tabs? radio button?) that when clicked would let you toggle between the different presets.
  
  You may not want to syndicate each photo, so perhaps a checkbox is warranted to let you select which photos will be sent.
• Finally at the bottom there's some checkboxes for which networks to syndicate to. As you can only syndicate a post once per network, posts that have already been syndicated to would be disabled with text explaining that you've already syndicated to that network for this post.
• Once syndicated they'd store the url of the syndication and create a TSyndication record.

from django.contrib.gis.geos import Point

# Keep our familiar lat/lon ordering without messing up the data point.
point = Point(y=35.31593281000502, x=139.4700015160363)

python3 -c "import secrets; print(secrets.token_urlsafe())" | xargs -I{} -n1 echo SECRET_KEY={} >> .env

Picking a Topic

Outlining

Writing

Editing

Conclusion

• As wrong as it feels, your entry point for processing your CSS should be a Javascript file.
• Webpack by default does not output a separate stylesheet file. In order to output a plain CSS file, you must use the MiniCssExtractPlugin.
• Despite wanting to output only CSS, and specifying the filename in the options (style.css), Webpack will create an empty Javascript file regardless. There isn't a way to prevent this unless you add another plugin. I'm adding it to .gitignore.
• The "use" plugins have the following roles
  • MiniCssExtractPlugin: Exact built css to a dedicated css file.
  • css-loader: Allow you to import css from your entrypoint Javascript file
  • postcss-loader: Run postcss with your 

// webpack.config.js
const path = require('path');
const MiniCssExtractPlugin = require('mini-css-extract-plugin');

const tailwindConfig = {
  entry: "./css/index.js",
  output: {
    path: path.resolve(__dirname, "../static/tailwind/"),
  },
  plugins: [
    new MiniCssExtractPlugin({ 
        filename: "style.css"
    }),
  ],
  module: {
   rules: [
    {
      test: /\.css$/,
        use: [
          MiniCssExtractPlugin.loader,
          { loader: "css-loader", options: { importLoaders: 1 } },
          "postcss-loader",
        ],
    },
   ],
  },
}
module.exports = [tailwindConfig]

// postcss.config.js
module.exports = {
  plugins: [
    require("tailwindcss")("./tailwind.config.js"),
    require("autoprefixer"),
  ]
}

// package.json
{
  ...
  "scripts": {
    "build": "NODE_ENV=production webpack --mode=production"
  }
  ...
}

• not have any bugs
• be easy to use
• have proper documentation for getting started

and so on and so forth. I keep on finding new things to add or fix that are "must haves" and so I keep on finding reasons to delay the release. And it's slowly been adding a bit of self-induced stress.

No more.

Tanzawa is now open source. It lives on GitHub at jamesvandyne/tanzawa. It has bugs. It has a bunch of edges rough enough to cut you. It has zero documentation for how to install and use it.

But I'll address them overtime. And eventually, someday,  it will reach my vision of being a simple and sustainable  home on the web.

If you need help or have questions or want to lend a hand: reply here, ping me on twitter @jamesvandyne, or open an issue.

Modern society has come to rely so heavily on mobile apps that any phone manufacturer must ensure that such a healthy ecosystem exists as table stakes for anyone to buy their phones.

And by privacy I don’t mean cookies or my Social Security number or whatever—I mean the fragile sphere of imagination in which I exist when I’m not diddling about online. I mean what’s left of my nondigital self. When I clack your two halves shut, you glorious techno-mollusk, that’s it. Sauron cannot see me.