fix: myriad typos and issues pt 2
This commit is contained in:
parent
be92f3bdf0
commit
b0aa0d6948
50 changed files with 120 additions and 69 deletions
|
@ -198,7 +198,7 @@ export default Webmentions
|
|||
|
||||
The final display looks like this:
|
||||
|
||||
<img src="https://files.coryd.dev/v/NG8lHj24OsJilx7QuxWO+" alt="Example webmentions" styles="width:100%;height:auto;margin:.5em 0" />
|
||||
<img src="https://files.coryd.dev/v/NG8lHj24OsJilx7QuxWO+" alt="Example webmentions" style="width:100%;height:auto;margin:.5em 0" />
|
||||
|
||||
[^1]: For my purposes, social media is GitHub, Mastodon and Medium. I've used the rest at various points and no longer have an interest in them for myriad reasons.
|
||||
[^2]: I've discussed this all a bit more in [this post](https://coryd.dev/blog/simple-api-fetch-hooks-with-swr).
|
||||
|
|
|
@ -9,7 +9,7 @@ I've been using Fastmail for years now and have explored a number of different a
|
|||
|
||||
For now, I've approached filtering my mail by applying regular expressions to reasonably broad categories of incoming mail[^2]. My thinking with this approach is that will scale better over the long term by applying heuristics to common phrases and patterns in incoming mail without the need to apply rules to senders on a per address or domain basis.
|
||||
|
||||
<img src="https://cdn.coryd.dev/blog/fastmail-workflow.jpg" alt="A diagram of my Fastmail workflow" styles="width:100%;height:auto;margin:.5em 0" />
|
||||
<img src="https://cdn.coryd.dev/blog/fastmail-workflow.jpg" alt="A diagram of my Fastmail workflow" style="width:100%;height:auto;margin:.5em 0" />
|
||||
|
||||
## Alias-specific rules
|
||||
|
||||
|
@ -92,7 +92,7 @@ In the event I've failed to tune a regular expression properly or an actual pers
|
|||
|
||||
## Mapping categories as folders
|
||||
|
||||
I've tailored these rules to align with folders on a per-topic basis. I have a broad `Financial` folder for things like receipts, bank statements and bills. That folder contains a few granular subfolders like `Deliveries`, `Media`, `Medical`, `Promotions` and so forth. All multistep rules are set to filter messages when `any` of the tabled criteria matches.
|
||||
I've tailored these rules to align with folders on a per-topic basis. I have a broad `Financial` folder for things like receipts, bank statements and bills. That folder contains a few granular sub-folders like `Deliveries`, `Media`, `Medical`, `Promotions` and so forth. All multistep rules are set to filter messages when `any` of the tabled criteria matches.
|
||||
|
||||
The top level `Financial` rule [looks like this](https://pastes.coryd.dev/mail-regexes-financial/markup).
|
||||
|
||||
|
@ -294,7 +294,7 @@ These I've left as a simple list wherein `any` included top level domain is file
|
|||
],
|
||||
```
|
||||
|
||||
That covers _most_ of what I use to manage my mail (outside of anything particularly personal). I fully expect the regular expressions I'm using could stand to be refined and I plan on continuing to do just that. But, with that said, things have worked better than I expected so far and false positives/miscategorizations have been infrequent.
|
||||
That covers _most_ of what I use to manage my mail (outside of anything particularly personal). I fully expect the regular expressions I'm using could stand to be refined and I plan on continuing to do just that. But, with that said, things have worked better than I expected so far and false positives/mis-categorizations have been infrequent.
|
||||
|
||||
If you have any questions or suggestions I'm all ears. Feel free to [email me](mailto:hi@coryd.dev) or ping me on [Mastodon](https://social.lol/@cory).
|
||||
|
||||
|
|
|
@ -9,7 +9,7 @@ I don't want your streaming music service, I just want the music I've collected
|
|||
|
||||
Apple Music *kind of* offers this, [with some serious sharp edges to watch out for](/posts/2021/apple-music-a-tale-of-woe/). Spotify doesn't offer this, neither does YouTube Music. Want to stream music? Sign up for a service, hope your favorite artists and albums don't rot out of their catalogue and run with the algorithmic recommendations sourced from that ever-shifting catalogue[^1].
|
||||
|
||||
I have the audio files for the music I care about and I've spent a long time collecting them. They're all tagged and named consistently using [Meta](https://www.nightbirdsevolve.com/meta/)[^2], shuffled off to an external hard drive, encrypted and mirrored up to B2 and GCP. *I just want to listen to them without using all of my local storage to do so.*
|
||||
I have the audio files for the music I care about, and I've spent a long time collecting them. They're all tagged and named consistently using [Meta](https://www.nightbirdsevolve.com/meta/)[^2], shuffled off to an external hard drive, encrypted and mirrored up to B2 and GCP. *I just want to listen to them without using all of my local storage to do so.*
|
||||
|
||||
I leaned on iTunes Match to do this for a while but, funnily enough, Apple will still dedupe your audio against their cloud catalog, overriding meta tags and audio availability as they see fit.[^3] You can sync music into Spotify via playlists, but that's not a scalable solution to, well, much of anything.
|
||||
|
||||
|
|
|
@ -7,7 +7,7 @@ tags: ['Eleventy', 'JavaScript', 'automation', 'GitHub', 'GitHub actions', 'cron
|
|||
|
||||
In an effort to get away from client-side Javascript and embrace Eleventy for what it is (a static site generator), I've dropped my [social-utils](https://github.com/cdransf/social-utils) instance offline and my now-playing track display on my home page that still relied on it.<!-- excerpt -->
|
||||
|
||||
To update my feeds ([feed.xml](https://coryd.dev/feed.xml) and [follow.xml](https://coryd.dev/follow.xml)) and [now page](/now) I've adopted [@11ty/eleventy-fetch](https://www.npmjs.com/package/@11ty/eleventy-fetch) and regular builds at [Vercel](https://vercel.com/) that are triggered by [Github Actions](https://docs.github.com/en/actions) that leverage cron for scheduling. [The workflow file](https://github.com/cdransf/coryd.dev/blob/e886857387661ceeba4f2b368989ec32f0c3f121/.github/workflows/scheduled-build.yaml) looks like this:
|
||||
To update my feeds ([feed.xml](https://coryd.dev/feed.xml) and [follow.xml](https://coryd.dev/follow.xml)) and [now page](/now) I've adopted [@11ty/eleventy-fetch](https://www.npmjs.com/package/@11ty/eleventy-fetch) and regular builds at [Vercel](https://vercel.com/) that are triggered by [GitHub Actions](https://docs.github.com/en/actions) that leverage cron for scheduling. [The workflow file](https://github.com/cdransf/coryd.dev/blob/e886857387661ceeba4f2b368989ec32f0c3f121/.github/workflows/scheduled-build.yaml) looks like this:
|
||||
|
||||
{% raw %}
|
||||
|
||||
|
@ -36,9 +36,9 @@ jobs:
|
|||
|
||||
{% endraw %}
|
||||
|
||||
This leverages three different Vercel secrets specific to your account that must be added to the [Github Actions Secrets](https://docs.github.com/en/rest/actions/secrets?apiVersion=2022-11-28) for your project (`Project repo -> Settings -> Secruity section -> Secrets and variables -> Actions`).
|
||||
This leverages three different Vercel secrets specific to your account that must be added to the [GitHub Actions Secrets](https://docs.github.com/en/rest/actions/secrets?apiVersion=2022-11-28) for your project (`Project repo -> Settings -> Secruity section -> Secrets and variables -> Actions`).
|
||||
|
||||
Your Vercel org ID and project ID will be at the bottom of your organization/personal acount's settings (in the General section), with your project ID located in the same section of your project settings.
|
||||
Your Vercel org ID and project ID will be at the bottom of your organization/personal account's settings (in the General section), with your project ID located in the same section of your project settings.
|
||||
|
||||
If you need to manually trigger a build, you can do so using a workflow with a {% raw %}`[workflow_dispatch]`{% endraw %} trigger like this:
|
||||
|
||||
|
|
|
@ -5,17 +5,17 @@ draft: false
|
|||
tags: ['social media', 'tech', 'culture']
|
||||
---
|
||||
|
||||
We've arrived at a point where we can say that our attempts to port relationships and social interactions to the internet has been an unambiguous failure.<!-- excerpt --> Cory[^1] Doctorow [captures how markets have driven this quite succintly](https://pluralistic.net/2023/01/21/potemkin-ai/#hey-guys):
|
||||
We've arrived at a point where we can say that our attempts to port relationships and social interactions to the internet has been an unambiguous failure.<!-- excerpt --> Cory[^1] Doctorow [captures how markets have driven this quite succinctly](https://pluralistic.net/2023/01/21/potemkin-ai/#hey-guys):
|
||||
|
||||
> This is enshittification: surpluses are first directed to users; then, once they're locked in, surpluses go to suppliers; then once _they're_ locked in, the surplus is handed to shareholders and the platform becomes a useless pile of shit. From mobile app stores to Steam, from Facebook to Twitter, this is the enshittification lifecycle.
|
||||
|
||||
It's a failure of imagination, a failure of requirements and a natural outcome of market incentives that have us sitting here and, frankly, it sucks. We've got networked devices, humans maintain a network of relationships and we tried to facilitate the latter using the former and, like so much what we do as a society, we tried to use the opportunity to turn a profit. Sounds cool right?
|
||||
It's a failure of imagination, a failure of requirements and a natural outcome of market incentives that have us sitting here and, frankly, it sucks. We've got networked devices, humans maintain a network of relationships, and we tried to facilitate the latter using the former and, like so much what we do as a society, we tried to use the opportunity to turn a profit. Sounds cool right?
|
||||
|
||||
I'd say it worked reasonably well while the technology was a nascent compliment to existing human relationships, where those relationships were rooted in a real connection. But those benefits didn't last all that long — the value diminished as these platforms worked to climb to the top of the enshittification curve, privatize profits and replace real relationships.[^2]
|
||||
|
||||
Is a friend on a social network a friend or someone you went to in high school ten years ago? Is that a relationship or a data point in a social graph that you don't own?
|
||||
|
||||
Your real social graph is a list of contacts — a list that may be tedious to main but, if a relationship is worth maintaining, you'll maintain its entry in that list. Modern social platforms make it easy to maintain relationships that aren't that. Log in, like some posts, log off. It's ritualized, it's addictive and it's devoid of value.
|
||||
Your real social graph is a list of contacts — a list that may be tedious to main but, if a relationship is worth maintaining, you'll maintain its entry in that list. Modern social platforms make it easy to maintain relationships that aren't that. Log in, like some posts, log off. It's ritualized, it's addictive, and it's devoid of value.
|
||||
|
||||
Pick up a phone and call someone, grab coffee, send them a text — if that's too much work then it sounds like you may have outgrown that relationship and moved on. We haven't scaled relationships or made them more convenient, we've created sticky platforms that don't benefit or empower their users.
|
||||
|
||||
|
|
|
@ -136,7 +136,7 @@ When the build runs, it renders any mentions of a given post via a [liquid.js](h
|
|||
|
||||
This conditionally displays different mention types based on the available data after being passed through the `webmentionsByUrl` filter which I shamelessly lifted from [Robb](https://github.com/rknightuk/rknight.me/blob/8e2a5c5f886cae6c04add7893b8bf8a2d6295ddf/config/filters.js#L48-L84).
|
||||
|
||||
I would like to also send outbound webmentions, but have yet to find a clear way to do so. One option I've seen mentioned is [Telegraph](https://telegraph.p3k.io/), but it's API interface requires a network call per link mentioned (which isn't untenable, but parsing posts for links and making a call for each _feels_ suboptimal)[^3].
|
||||
I would like to also send outbound webmentions, but have yet to find a clear way to do so. One option I've seen mentioned is [Telegraph](https://telegraph.p3k.io/), but its API interface requires a network call per link mentioned (which isn't untenable, but parsing posts for links and making a call for each _feels_ suboptimal)[^3].
|
||||
|
||||
[^1]: I've done so in [Next.js](https://coryd.dev/posts/2023/client-side-webmentions-in-nextjs/) and entirely in Javascript for [weblog.lol](https://coryd.dev/posts/2023/adding-client-side-rendered-webmentions-to-my-blog/).
|
||||
[^2]: Or, better yet, read [Robb's post on the subject](https://rknight.me/adding-webmentions-to-your-site/).
|
||||
|
|
Reference in a new issue