Racial polarization in the US presidential election vote share has decreased since 2016.

Democrats have lost voter share among Black, Hispanic, and Asian voters between the 2016 and 2024 presidential elections, but gained voter share among White voters.

Conversely, Trump has gained voter share among Black, Hispanic, and Asian voters between the 2016 and 2024 presidential elections.

US election vote share by race for the 2016, 2020, and 2024 presidential elections

Based on data from the Pew Research Center:

Editor’s Note: Fixed some typos and the list numbering not working. See diff

I have recently changed how I use Todoist, but before doing so, I exported all (okay, I think it was more like most of) my data.

Since I exported all of my data once, I now want to export and back up my Todoist data regularly.

Here is how to get most of your data from Todoist using Nushell:

I’m going to assume you have Nushell installed. If not, install Nushell.

I would probably recommend doing so in Homebrew:

brew install nushell

But I’m not sure, because I installed Nushell before I realized I should be installing as much of my software through a package manager as possible.

1. Get your API key from Todoist.

   Be aware that this API key has, as far as I can tell, admin-level permissions for your Todoist account.

   Whatever you can do through the GUI, the API key allows you authorization to do. You can only have 1 API key at a time. You can’t restrict the API key in any way.

   You can revoke the API key by clicking the Issue a new API token button (on the same page). But that is going to log you out of all Todoist sessions, which is super annoying if you are logged into Todoist in Chrome, your phone and have a bunch of scripts and widgets using that API key.

2. Set the API key as the TODOIST_API_TOKEN environment variable

3. Copy this in as sync.nu:

    #! /usr/bin/env nu
   
    use std log
   
    const COMPLETED_TASKS_MAX_LIMIT = 200
    const ARCHIVED_SECTIONS_MAX_LIMIT = 100
   
    def get-sync-data [] {
        log info "Getting sync data"
        let result = http post --headers [ "Authorization" $"Bearer ($env.TODOIST_API_TOKEN)" ] --content-type "application/x-www-form-urlencoded" https://api.todoist.com/sync/v9/sync { sync_token: "*", resource_types: '["all"]' }
        $result
    }
   
    def get-completed-tasks-with-offset [offset: int] {
        log info $"Getting completed tasks with offset: ($offset)"
        const annotate_notes = true
        const annotate_items = true
        const limit = $COMPLETED_TASKS_MAX_LIMIT
        let url = $"https://api.todoist.com/sync/v9/completed/get_all?limit=($limit)&annotate_notes=($annotate_notes)&annotate_items=($annotate_items)&offset=($offset)"
   
        let result = http post --headers [ "Authorization" $"Bearer ($env.TODOIST_API_TOKEN)" ] --content-type "application/x-www-form-urlencoded" $url { sync_token: "*", resource_types: '["all"]' }
           
        $result
    }
   
    def get-completed-tasks [] {
        mut results = []
        mut offset = 0
   
        while true {
            let result = get-completed-tasks-with-offset $offset
            $results = $results | append $result
            $offset += $COMPLETED_TASKS_MAX_LIMIT
   
            if ($result | get items | is-empty) {
                break
            }
        }
   
        $results
    }
   
    def get-stats [] {
        log info "Getting stats"
        let result = http get --headers [ "Authorization" $"Bearer ($env.TODOIST_API_TOKEN)" ] https://api.todoist.com/sync/v9/completed/get_stats
        $result
    }
   

4. Copy this in as runner.nu:

    #! /usr/bin/env nu
   
    const RFC3339_FORMAT = "%Y-%m-%dT%H:%M:%S%z"
   
    source ./sync.nu
   
   
    let sync_data = get-sync-data
    let completed_tasks = get-completed-tasks
    let completed_tasks_stats = get-stats
   
   
    let endpoints = {
        "sync": $sync_data,
        "completed/get_all": $completed_tasks,
        "completed/get_stats": $completed_tasks_stats
    }
   
    let metadata = {
    "created_at": (date now | format date $RFC3339_FORMAT),
    }
   
    let result =  {endpoints: $endpoints, metadata: $metadata}
   
   
    $result | save -f todoist-export.json
   

5. Run nu runner.nu in your terminal.

   You should get a file called todoist-export.json in the same directory as the script.

actually lemme start with something simpler: tell me about your unfinished works? what do you have that you haven't gotten around to publishing/finishing? you don't need to post the thing just tell me *about* the thing https://t.co/1bsC6BUZaz

— Visakan Veerasamy (@visakanv) January 2, 2025

This tweet really resonated with me. I have a dozen-plus essays rattling around in my head that I want to write—some of which I’ll actually end up writing. An essay about how I manage my daily todo list in a plaintext file feels like the lowest-hanging fruit.

An essay on managing my daily todo list in a plain text file and how I want to extend that system going forwardhttps://t.co/3wkiyAFmeR

— Ram Vasuthevan (12/100) (@RamVasuthevan) January 7, 2025

I have been trying to find the name for this very common notation for analogies:

A:B::C:D to represent A is to B as C is to D

I have found it helpful to query LLMs (ChatGPT 4o in my case) with questions in the format A:B::C:??

I have tried to find the name for this notation by asking ChatGPT, using Google Search and Google Scholar, but I have not found anything authoritative.

I think the name Colon Analogy Notation is a good Schelling point. Someone familiar with the syntax would intuitively recognize the connection upon hearing the name. Likewise, if someone knows the syntax, this might be the name they would naturally search for.

I would love to know if there is a preexisting name for this notation and the history of its use. But it is hard to search for something when you don’t know its name.

So I have written the article I would like to have found for the next searcher.

This sub-blog is for posts written at a certain point in time. I don’t usually update them, but I’ll update this if I learn more.

If you know more, please email me (my email is in the footer) or reach out on Twitter.

I have always had the temperament of a satisficer. I find something that works for me, and I stick to it forever. It’s simple and easy, once I make a commitment to something, I don’t have to think about that category of thing again. I do this for bagels, pens and IDEs. But I am starting to wonder if I am missing out by not maximizing more.

When thinking about new solutions, whether it be software tools, hot sauces, or notetaking apps, I become a perfectionist. I start thinking of my elaborate theoretical use cases and then become overwhelmed and actually do nothing.

If it’s a cheap, reversible decision, the only real mistake is procrastinating on making a decision

TLDR: JUST DO IT!

Recently, I learned in a not-so-enjoyable fashion that Twitter caches summary card images.

While writing Verify Jekyll Minima Sites on Mastodon, I originally had a summary card image which was getting cropped poorly, so I kept the image that was being displayed at the top of the article but changed the summary card image with a wider version which got a better crop. And it showed up correctly in my preferred Twitter Card preview tool: BannerBear Twitter Card Preview Tool.

But when I posted it to Twitter, the old image would show up both when I actually posted it and in the preview when I was composing it.

After some frustrating troubleshooting, I found this support forum thread that said Twitter caches summary images for about a week, and the preview tool could be used to expire the cache.

And while the preview tool, no longer actually shows you a preview of a tweet, it does bust the cache.

Unfortunately, this type of amateurism is typical of Twitter.

I am not really happy with my investigation into this issue. I wonder if there is a way to accurately preview tweets with the cached images.

On Mastodon, one way that you can prove that you are who you say you are is by verifying that you own your personal site.

For example, on my Mastodon account, I have verified that I own ramvasuthevan.ca

You prove that you own a page by having a link from that page to your Mastodon account with a rel="me" attribute.

The two simplest ways to verify your site:

1. Adding an invisible <link> tag inside the <head> tag at the top page to the account that you’d like to be verified for:

    <link rel="me" href="https://mastodon.social/@RamVasuthevan"> 
   

2. By adding a hyperlink to your Mastodon profile somewhere on the page, like:

    <a rel="me" href="https://mastodon.social/@RamVasuthevan">Mastodon</a> 
   

Unfortunately, if you add your Mastodon profile to your config file like this:

mastodon:
  - username: RamVasuthevan
    instance: mastodon.social

Minima 2.5 does not automatically add the rel=me attribute to the link in the footer of your site. And there is no plans to add automatic verification until Minima 3.

But you can copy the _includes/social.html file and add it to your _includes file. And then add a rel="me" attribute to the a href tag for Mastodon.

Or you can just copy my version.

After adding the link to your page, go to https://mastodon.social/settings/profile and add the page you want to verify as one of the extra fields.

Your profile must be updated after adding the rel-me link to your web page. If you have added the link to your profile before, try removing the link from your profile, saving, re-adding the link, and then saving again. (See documentation).

In the spirit of early patio11, I’m going to write more about what I worked on, what I learned, and the problems I solved on any given day.

In that spirit, I have a bunch of repos with Dependabot enabled. It’s a pain in the ass to manually go to all of the repos and see if a Dependabot PR has been created.

Search query: is:pr author:app/dependabot is:open archived:false user:@me

GitHub Search for Dependabot PRs

Photo by Andrew Neel from Unsplash

I started writing this blog in the spirit of Visa’s do 100’s things. The best way to become a better writer is to write. Writing and writing energy is not scarce. It’s not like you have a finite number of things you can write in your life. The more you write, the more you can write. If you write an article about an idea, it doesn’t need to be perfect. You can always write more about it later.

I started writing on Ghost because it was easy to set up and maintain. At first, I didn’t mention my name anywhere. Eventually, I decided to merge it with my personal site after I became more confident with my writing and so that I could gain more control over how the site looked. As an engineer, I love being able to take advantage of Git for version control, setting up my writing environment using VS Code and knowing that I can easily maintain and migrate it from Jekyll if necessary.

Jekyll by default puts all blog posts into one feed, but sometimes, I want to write something small, a snippet, a note mostly for myself, that doesn’t really fit in Bits, Bips and Bricks.

By taking advantage of Jekyll categories and tags you can easily have multiple sub blogs each with their own Atom feed using only Liquid.

A category can be defined using the front matter keys category or categories (a space separated list of categories) or putting a directory above the post’s _post directory with the name of the category.

A tag can be defined using can be defined using the front matter keys tag or tags (a space separated list of tags)

This snippet is built to match the style of Minma, but similar logic can be used for other themes.

Copy the following code and paste it in _includes/blog.html:

<div class="blog">
    <h2 class="post-list-heading">{{ page.list_title | default: "Posts" }}</h2>
    <ul class="post-list">
      {%- for post in site.posts -%}
      {%- if post.categories contains include.category or post.tags contains include.tag -%}
      <li>
        {%- assign date_format = site.minima.date_format | default: "%b %-d, %Y" -%}
        <span class="post-meta">{{ post.date | date: date_format }}</span>
        <h3>
          <a class="post-link" href="{{ post.url | relative_url }}">
            {{ post.title | escape }}
          </a>
        </h3>
        {%- if site.show_excerpts -%}
          {{ post.excerpt }}
        {%- endif -%}
      </li>
      {%-endif -%}
      {%- endfor -%}

    </ul>

    {%- if include.category and site.feed.categories contains include.category -%}
      {% unless include.tag %}
      {% assign feed_location = site.feed.categories[include.category].path | default: '/feed/' | append: include.category | append: '.xml' | relative_url %}
        <p class="rss-subscribe">subscribe <a href="{{ '/feed/' | append: include.category | append: '.xml' | relative_url }}">via RSS</a></p>
        {% endunless %}
    {%- endif -%}

    {%- if include.tag and site.feed.tags contains include.tag -%}
    {% unless include.category %}
      <p class="rss-subscribe">subscribe <a href="{{ '/feed/' | append: include.tag | append: '.xml' | relative_url }}">via RSS</a></p>
    {% endunless %}
    {%- endif -%}

</div>

The above code is available under the MIT license and contains code from minima/_layouts/home.html

On the page that you want a sub blog with only posts from a certain category:

{% include blog.html category="category_name" %}

On the page that you want a sub blog with only posts with a certain tag:

{% include blog.html tag="tag_name" %}

If you don’t add a category or tag parameter, then all posts will be in the sub blog.

Minima assumes that if there are no posts, the feed will not be shown. I disagree, you can have a blog without blog posts.

Make sure to update your _config.yml according to the instructions for jekyll-feed to make sure that the feeds for your category or tag are generated.

On the 2023-2024 U of T Law School Course List, there seems to be 3 course related to real esate:

• From Blueprints to Buildings: Legal Issues in the Construction Industry (LAW306H1F)
  • Instructor Michael Valo is the co-author of a chapter in “Review of Construction Law: Recent Developments” about Building Information Modeling (Toronto: Carswell, 2012), and of the chapter “Sustainable Construction” in “Modern Legal Landscape of Design Professional Practice” (Toronto: Carswell, 2023).
• Real Estate Law (LAW275H1F)
  • Instructor David Carter is the Co-author of Real Estate Transaction 2nd Edition
• Community Planning: Problems in Urban Policy and Land Use Regulation (LAW224H1S)
  • Instructor Arnold Weinrib is the Editor-in-Chief of the Land Compensation Reports