Vincent Tunru @vinnl@mastodon.social

And the prize for "Best Project Name Ever" goes to a Scheme dialect to create Ethereum smart contracts: Pyramid Scheme.

https://github.com/MichaelBurge/pyramid-scheme

The good news is: it is! And the other good news is: there are enough accessibility experts on StackOverflow to actually provide you with answers, and who can actually link the relevant specs.

I've been doing some accessibility work recently, and I've been somewhat surprised by how some (I assume) pretty common things do not appear to have come up on StackOverflow before.

Or, well, surprised... Of course a11y is relatively often neglected. Still, I'd presume more people who aren't accessibility experts would have wanted to know whether button elements triggering click events on keypresses is standardised behaviour.

If not zero-config, then TypeScript support often is at most a matter of installing it and flipping a config option. In the spirit of which I should mention the plugin I wrote for React Static last week, that allows you to seamlessly use TypeScript in your React Static projects:

https://www.npmjs.com/package/react-static-plugin-typescript

Just found out about npm's tink (thanks @baldur), and the most interesting thing is not so much tink itself, but this:

> it does a lot of neat little things like load Typescript (...) out of the box

Many projects appear to move to zero-config TypeScript support out of the box. As a result, the barrier to entry is getting really low, and TypeScript usage is bound to grow even more.

@juliank Apparently that's not possible:> the intention to withdraw must, first, be submitted in writing to the European Council and, secondly, be unequivocal and unconditional.More extensive quotes and sources here:https://www.reddit.com/r/europe/comments/a4tsy2/bbc_news_uk_can_cancel_brexit_says_eu_court/ebhjvsf/

Of course, the major worry is that either of those two will be answered with "no" in the future...

After mulling over the Edge-Chromium announcement for a couple of days, there are two questions I have about the future:

1. Will web developers keep (?) testing in Firefox?
2. Will Mozilla be able to keep up with the presumably increased pace of Chromium?

If the answer to both of these questions is "yes", then I think the web might be better off, given that Microsoft might be a significant counterweight to Google in the Chromium project, and that Edge will be open source and cross-platform.

I finally gave in a wrote a bespoke blog generator. With excellent performance, thanks to some React-Static preloading magic.Check it out at https://vincenttunru.com.

@JohnONolan @nolan if you don't follow him yet :)

(Pretty much interested in the same things, btw, so thanks for asking - I'll be following the list.)

Perhaps one way to alleviate this would at least be to add a marker (e.g. an icon and a different colour) to mentions of usernames of people you follow?

I wonder if Mastodon will get large enough for identity theft to become a problem... What with instance names getting truncated from @mentions (at least in Pinafore), registering the same username+same avatar on a different instance is an easy way to impersonate someone. Not quite sure if there's a user-friendly longer-term solution.

https://mastodon.social/@brennen/101190875478427055

For those interested, the configuration I use can be found here: https://gitlab.com/Flockademic/get-dois/blob/master/.gitlab-ci.yml

(I use GitLab CI/CD, but it could work similarly on other build servers.)

Before publishing the package, all tests are run - unless the branch includes a commit whose message starts with `WIP:`, in which case they are skipped. The master branch is slightly different: tests are always run and the package is published as @next.

My workflow to publish npm packages is pretty sweet. Whenever new commits land on a branch, they are published to npm with the branch name as its tag. Thus, you can always npm install mypackage@test-branch. Whenever new tags are pushed, those are published as new versions.