It's interesting to think of the concept of the "free and open web" as a generational thing. I can't imagine that that phrase means much to someone born in Generation Z, who grew up with "the internet" meaning an array of chiclet-sized apps built by companies in Silicon Valley.

@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:reddit.com/r/europe/comments/a

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 vincenttunru.com.

Firefox is now more important, isolated and vulnerable. Some suggested ways we can support it:
• Set it as your default browser. And if you're back home with family over Christmas, suggest/set as their default too.
• When you hear web devs say "can't everyone just use Chrome", please challenge it.
• Contribute to Mozilla-led projects, e.g. MDN Docs: smashingmagazine.com/2018/05/c
• Donate to Mozilla if you can: donate.mozilla.org

If you really want to help Firefox succeed, file a bug on webcompat.com/ when you find a broken website. Don't just switch back to Chrome; let Mozilla know there's a problem so they can try to fix it.

When browsers lose market share, they fall into the "compatibility death spiral." Sites don't bother to test, they break, and users flee to the browser that "just works." Mozilla is fighting this battle every day, and it just got harder.

@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.

mastodon.social/@brennen/10119

“Microsoft is building a Chromium-powered web browser that will replace Edge on Windows 10”

windowscentral.com/microsoft-b

I’ll be really disappointed if this is the case. EdgeHTML is a really nice rendering engine with its own trade offs. A browser monoculture could destroy the web.

Sounds like it's time to redouble support for Firefox and Mozilla. 😕

I'm actively recruiting volunteer devs for a native Signal / Signal-like client in Gtk, in the hopes that we can bring it to the @Purism Librem 5 phone. Please contact sean.obrien@puri.sm if interested.

PGP/GPG: FA9D 40F1 5FE1 D8AB 8312 4AAA 77E3 1447 CD1F C3F6

For those interested, the configuration I use can be found here: gitlab.com/Flockademic/get-doi

(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.

Create React App now supports TypeScript!

If you're using Will Monk's fork "create-react-app-typescript", you might want to migrate to the official Create React App. I ported a few of my projects, and found that it was not that much work.

How I did it: vincenttunru.com/migrate-creat

Well, that's great. The next version of Google's reCAPTCHA should be added to multiple pages. Conveniently, this is also expands its ability to track you, in a way that by definition cannot be blocked.

webmasters.googleblog.com/2018

IMPORTANT UPDATE: I'd misread the docs, and the naming convention is only there to support the linter. So conveniently, that does away with the main remaining concern, and makes me even less worried :)

Besides, as a TypeScript user, I expect tslint will even be able to warn be about incorrectly naming a hook :)

That said, if and when such syntax arises, it is probably possible for React to gradually transfer to that, and the React team has so far been good about making it manageable to do so painlessly.

Show more
Mastodon

Follow friends and discover new ones. Publish anything you want: links, pictures, text, video. This server is run by the main developers of the Mastodon project. Everyone is welcome as long as you follow our code of conduct!