Readit NewsI have been using Dark Reader for years and years. Sometimes I forget that some websites don't natively support dark mode until I accidentally turn it off for some reason.
I recommend setting it to disabled by default, and manually enable it for websites which need it using the "Invert listed only" button.
https://chromewebstore.google.com/detail/dark-reader/eimadpb...
lategloriousgnu commented on Building Node.js applications without dependencies bonaroo.nl/2023/12/12/bui... · Posted by u/puuush
I have a question for you all:
When you're building something and you notice one of your dependencies has a bug or is missing a key feature that you need, do you (a) PR the fix into the dependency and then try to "harrass" the maintainer into merging it for you, (b) publish your own fork of the dependency with the necessary fix, (c) inline the source code for the dependency into your project, effectively taking it on as if it's your own code, (d) completely rewrite the dependency either as a separate package you control or built directly into your own project, or (e) code around the problem / do a hack?
I find that often maintainers are so over-worked that it's practically impossible to get a merge in a timely manner, and this leads me to rely on a fork until the PR eventually gets merged. However, I think creating a new package under either your own ownership or the company you work for is often really bad as it can become a kind of hidden technical debt. Nowadays, I definitely consider inlining as a way to capture ownership of the technical debt in a way that is highly visible, but this can add 100s or 1000s of lines of code to a project and if eventually the upstream project moves on you don't get the benefits of their changes without removing the inlined code and untangling any changes that were made to it.
The only other approach I've seen is the 'hack' approach, in which you try to dodge the bug or semantic issue. Honestly, that might be the right thing to do in some situations, but it isn't very hygienic within a long-term project (unless you carefully maintain a TODO list of things that need 'correct' solutions).
We patch our dependencies.
This adds a diff to your repo, not an entire fork of the dependency.
A package manager like pnpm will install the package as usual, then apply your patch over the top.
In theory - and as has happened in history - governments can repatriate (nationalize) critical assets. So as long as a nationstate has meaningful independence, even the threat of that emergency lever can prevent the worst abuse.
If such meaningful independence doesn’t exist, it arguably doesn’t make much of a difference who’s name plate is on the ownership?
39% all goods exported from Australia in 2019-20 were to China. Of that 39%, over half of that was iron ore. Australian iron ore production is valued at $136 billion a year to the economy.
Unfortunately, Australia really doesn't have much leverage in this space, and forcibly re-nationalizing an asset like that, would cause major diplomatic problems, like the harsh trade sanctions imposed by China over the last few years due to Australia backing a COVID inquiry.
Fosshost provides (provided) resources to those projects, but does not have any IP ownership.
Redhat does not own (100%) of GNOME IP, there are many contributors. Also redhat is just a brand asset of IBM, so it cannot actually own anything.
Parent means IP as in Internet Protocol, not Intellectual property. The DNS for gnome.org resolves to 8.43.85.5, which lists Red Hat Inc. as the ISP. Indicating it's unlikely to be hosted by Fosshost.
lategloriousgnu commented on 9M Australians affected by Optus data breach optus.com.au/about/media-... · Posted by u/tonteldoos
Because of this I finally decided to complain to my (Australian) bank about their max 6 character (alphanumeric) no symbol password policy... And lack of MFA for personal accounts... And continuing to only offer OTP via SMS to authorise transactions.
Well, I tried to complain... for you see after going through multiple pages/steps in the UI, when it came time to review and submit, after you press submit you are told that they can't receive complaints online at this time.
So I wrote in the web feedback form instead. At least that went through. As will, I hope, my screenshots of the process to the ombudsman.
In nearly all these microservice components, the UI has an outdated copyright year in the footer. 2016 in the feedback app, 2017 in a preference update component. The year sits right underneath a lock symbol and some text telling you how secure they are.
This tells me a number of things. Either no one has smoke-tested that component for 6 years, or picked up that the year was off, or it has been picked up and left in backlog because of other priorities leaving me to ask what else could be in the aged backlog, but really telling me they don't have the resources to do or to take software or UX seriously.
ING only requires a customer number, and a four digit PIN for online banking access. The customer number is printed on the back of the cards and at the top of letters. There is no MFA. I wish I was joking.
lategloriousgnu commented on Ask HN: Does anybody still use bookmarking services? · Posted by u/joe8756438
Copying, and making available for money, someone else's webpage sounds a lot like copyright infringement?
If they were to make the copy available for everyone through their own syndicator then sure, but they don't. The "copy" is only available for the original reader, who had legitimate access to the original anyway.
Under copyright, you're allowed to make full copies of works which you have legitimate access to, as long as you don't distribute them to others.
https://copyright.unimelb.edu.au/shared/using-copyright-mate...
To me, what Pocket is offering is like a warehouse where you can take books which you already own, and they're charging you for the warehouse space.
Doesn't sound like anything to do with copyright to me.
> If you signup for Netflix using the feature, you can't cancel your account and then signup with a new Apple email, it will only allow you to login with your original one.
You absolutely can. You can generate as many as you want, whenever you want
Ah, on further reading it looks like there are a couple parts to it.
I have only used the "Sign in with Apple" feature directly in apps, which only ever lets you create one for that app.
However, apparently with an iCloud+ subscription, you can generate arbitrary email addresses from within iCloud itself, and then use those wherever you like.
Disposable email domains aren't the issue here. Creating a disposable @gmail account to avoid paying is possible too. Don't use emails to assert user identity. Most companies use credit cards for that. Or make it so that creating another account from scratch is more of a hassle than paying.
Better yet, offer free tiers.
You can only create a small number of gmail accounts, since ever account needs to be linked to a valid phone number. Google actively work to prevent using their platform in this way.
- Offers a dev "enough" control (some HTML/CSS/JS support but not total control)
- Stays largely out of the way (maybe something like a "powered by" header/footer only)
- Doesn't try to lock free posts behind paywalls
- Is independently owned and not a big tech product (so no Blogger)
- Is abstracted enough so that someone doesn't need to know domain, DNS, hosting, VPS, or sysadmin stuff in general to start a website
The closest things I've seen to this are Neocities and Glitch. The best one used to be Blogger, but again it's big tech so you can't use it without being assimilated into the Google collective consciousness.
https://bearblog.dev
You can see examples on the discover page.
https://bearblog.dev/discover
It has a small collection of simple pre-built themes, while also supporting custom CSS.
https://docs.bearblog.dev/styling