Show newer

Just a reminder that tomorrow is April Fools'. Don't leave your computer unattended.

In completely unrelated news: I updated my VSCode extension "Whoopee cushion keyboard". It adds fart noises as you type, and with the new version, you can now enable it per language (command palette: "This is a smelly business").

Can't publish something like this without wrapping it in layers of caveats and reassurances 😅

- This won't affect runtime behaviour
- Existing TS code would continue to work
- Runtime behaviour is not affected
- Types would be optional
- Does not influence runtime behaviour

The Storybook team is doing very cool work. Really hoping we'll get plug-and-play Next.js integration soon.

does anyone who is visually impaired or otherwise rely on screen readers have any experience with trying to use linux ?

from what i can tell the linux experience seems pretty hostile to screen readers, and there's not very much resources dedicated to orca, which seems to be the main implementation .

please share your experiences with me if you can, i want to try to make things better .

please boost :boost_requested:

People are literally getting rickrolled by people younger than rickrolling itself. Imagine that.

I like Progressive Web Apps, but I'm not convinced about installing them yet. Where's my tracker blocker? My other extensions? Browser preferences? Synced passwords?

Given how most browser chrome disappears when you scroll anyway, I find I'm mostly sticking with bookmarks, possibly as an icon on my home screen.

Being trained in the scientific method means that you get to prefix your bad arguments with "anecdotal, but".

Mozilla's unique selling point is that it's a non-profit. However, its real strength is that it answers to its community of contributors. It's not a perfect organisation, and it makes mistakes, but it can and will be held accountable, and that's what makes it better.

Welp, just posted my first StackOverflow question as a result of my first fight with the borrow checker, as is tradition. Now to wait until it's closed as a duplicate.

But if anyone has any pointers (hehe), would appreciate:

Show thread

Doing in again this year (this is not a promise that I'll keep it up 😛), and today is the first day that I feel like I've written somewhat idiomatic Rust, by myself. Very satisfying.

Anyway, keep in mind that I'm not a lawyer, and that there are nuances to every licence. That said, I hope that this rough mental model can be helpful to some of you when working with (or hopefully contributing to!) open source in the future.

Show thread

This mental model also helps explain how a project can have multiple licences: since they just confer extra rights, they're strictly additive. Users can benefits from the rights granted to them in both licences.

Show thread

It's not just to enable closed source work though. It can also prevent having to reach out to all contributors if there's a good reason to change the licence in the future.

For example, this is what LLVM is having to do now:

Show thread

Of course, that gets messy when there are multiple copyright holders: a contributor can use their *own* code in a closed source product, but not others'.

That's why some projects require a "Contributor Licence Agreement", giving an org even more rights than the licence does.

Show thread

It's also important to note that open source licences only *give* rights to others; the only limitation it places on the copyright holder is that they cannot revoke those rights.

That's why even under the GPL, the copyright holder can still build a closed product on top of it.

Show thread

This means that a licence violation, in essence, is just a copyright violation.

In other words, if someone e.g. uses GPL'd code in a closed-source product, the offence is the same as if they'd have used non-open source code: a copyright violation.

They were never given permission to use that copyrighted code in a closed-source product in the first place!

Show thread

Some examples:

- The MIT licence says that people can use your code, provided they do not remove the licence from it.

- The GPL says that people can use your code, provided that, for anything they build on top of it, they give the same rights to anyone they give it to.

Show thread

You (or your employer) automatically have copyright over everything you write. That roughly means that you can do pretty much everything with it, and others nothing.

At their core, open source licences simply allow others to use what you wrote as well.

Show thread

Given how open source is everywhere, it's useful to know how open source licences work. Luckily, a rough mental model is not too difficult to form. I'll sketch one out in the replies to this post.

I cracked my phone's screen 😢

However, it's a @Fairphone, so I just replaced the screen with that of a friend's old Fairphone. Took me all of five minutes 😎

Show older

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.