Hacker Newsnew | past | comments | ask | show | jobs | submit | Volundr's commentslogin

Fastmail is great, my one downside being that it charges per-account (to be clear, you can have unlimited aliases on that account), so if you want multiple accounts, e.x. for homelab stuff, your paying full price for each.

I also use purelymail for the above reason, and while it's barebones I've been quite happy with it.



73% of dentists own their own practice, so you are wrong.

Most states require that a dentist own the practice so PE essentially splits the business in 2 where a dentist (maybe the original owner, maybe a new dentist brought in by the PE) own hiring any dentists and the patient records, while an MSO owns the building, all other staff, contracts and cash flow rights. So sure on paper a dentist "owns" the practice, but in reality the PE firm owns everything that makes it a business and exerts a ton of control.

But sure, keep imagining PE is pumping money into the industry to buy nothing.


I referred to indirect ownership through owning stakes in the private investment fund(s) that owns their own practice.

I was responsible for administering a self hosted GitLab instance for a medium sized company and our backups never required downtime. The built in backup command doesn't require downtime but also isn't a consistent point in time snapshot (specifically because the instance keeps running while the backup is being taken). If they've decided they need one for some reason, stopping GitLab is certainly the easiest way, but not the only way of accomplishing that goal, but that'll be true of any self-hosted forge, including GitHub.

You could stop it, do a snapshot of the storage and backup that for <1 min of downtime probably.

But at the same time, if you're not a global company, doing it at 3am is probably fine.


Doing a snapshot of the storage while it's running wouldn't be bad either, it'd just be like having cut power at the point of the snapshot, right?

Yes. And the database used by GitLab is Postgres which handles that just fine.

It can be an issue if you are using gitlab as your container/package registry and production workloads need to pull from it, though.

They should be pulling from a pull through scanning repository cache anyway, so they can be scanned before going into production.

I seem to recall some apps refusing to run if developer mode is enabled. A workaround that means I can no longer use the apps I use every day isn't much of a workaround.

Correct, some of the banking apps I use don't work unless I turn off Developer Mode It's actually annoying to have to turn on and off every time

As of Android 17, "Developer Mode" consists of an extra options panel that is enabled through a sort of "Easter egg" process. It's not really even a mode. It's simply a bundle of options that are somewhat dangerous or confusing to twiddle. Users don't need to enter this mode for any practical reason, but entering this "mode" doesn't do anything except exposing more options behind one big toggle.

It doesn't affect the phone's security in any way, unless you specifically tweak a security-related option in that panel. It doesn't degrade the device encryption or Google Play Services. I don't see how any app could balk while it's enabled. There are no apps I have that even run differently. I use the same banking apps and all the other things as normal, whether or not this mode is enabled for me.


Is it Developer mode those apps trip on or USB debugging? I've seen several examples of the latter but haven't come across the former yet. I run Google-free Android (14, 15, 16) devices which run the Swedish and Dutch banking and e-ID apps I use on, some of these only work when USB debugging is disabled while others don't care. Some of them complain about Google Play Services not being available but they run nevertheless, that warning is produced by some part of the SDK which gets imported at build time but it does not (yet...) disable anything.

Although USB debugging (ADB) is arguably the main concern, a lot of apps just lazily check for developer mode - meaning they won't boot even if the menu is enabled. It allows stuff like location faking I suppose?

Inevitably we're going to need a separate device for banking apps. Which makes sense until every single app bans developer mode...

Or, we're going to have to start choosing banks without apps or with apps that don't have such ridiculous restrictions. Fortunately, at least in the USA there is an abundance of banks and credit unions, so if one of them treats you like this, just move your account over to a different one. I've changed my primary bank in a single day--It's not hard.

It's not just choosing a bank without an app, existing banks have been neglecting their web sites so that some things are only possible with the app even if an alternative exists. I've had that with my bank, and when I called them to report the problem with their web site their "fix" was that yeah, the web site is kinda broken, just use the app instead and it'll work.

It's not hard but it is annoying to update card numbers and payroll and stuff

those restrictions are actually about safety, which in case of banking apps is actually justified.

Either way, what Google plans to do is absolutely crazy.


It's not obvious to me how those restrictions improve safety

They don't.

I've considered this before, but the short software support timeframe given by device manufacturers makes this a costly endeavour. I still have a perfectly functional Galaxy Tab S2 9.7, but even the third party ROMs have dropped it. I have a pixel 4a, and although it works beautifully running a supported version of lineage it's very likely that the modem baseband has a significant vulnerability that Google isn't patching. I don't think running banking or crypto wallet software on those devices is any smarter than running it on my daily driver pixel 8.

The app my government pushes on everyone does not work with Developer Mode either.

You can likely disable developer mode after installing the app.

I’m not sure if you would have to re-enable it every time to sideload updates or new apps. You can also install via adb with no waiting period.


Adb also requires developer mode.

And my work doesn't permit it even with byod, it's so annoying. I've stopped running byod for that reason but now I'm stuck with two phones again.


Never byod. Besides MDM issues, it makes your personal device in scope for discovery if any lawsuit against the company.

Oh I don't live in America so this wouldn't happen, we don't have discovery here like that.

Besides, I would not comply anyway. I would just delete the device.


IANAL, however IIRC delete a device data is effectively destruction of evidence under most jurisdictions.

again IANAL but be careful.


If your device is under MDM it's already far more pwned than the topic of this article

Yes these days it is. It didn't use to be like that.

In the early days of BYOD, all they could do is delete the device if it would be lost. Which was not really a bother to me because I back it up to my own servers anyway, and in that case it would be lost anyway. And they would enforce a few basic things like setting a decent pincode and device encryption.

But lately the MDM and antimalware solutions have become more intrusive. Recently my work's MDM complained about an app I had on the personal side of my phone, something they should have no visibility of. Also they now want to route all the traffic through their VPN to inspect it which was obviously a non-starter.


Android 5 is where capabilities really took off, including the Device Owner profile which has pretty ultimate control over the device -- they've actually done some work to limit what admins could see across profiles in Android 11+

Android 7 is when always-on-vpn was could be enforced by an admin, in 2016.


> You can also install via adb with no waiting period

Is this confirmed? If so, that largely removes my issue with the 24 hour waiting period for enabling/disabling dev mode.


The 24 hour waiting period is only once per account, not on every activation, or even every device.

Yes, this has been widely reported everywhere except for the scaremongering OP.

https://android-developers.googleblog.com/2026/03/android-de...


Once enabled, it stays enabled even after developer mode is turned back off. It's also associated to the Google account (if any) so later device purchase don't have to wait the 24 hours period

Why do I need a remote cron job to install an app on my phone?

I have Pacman, mise, and nix on mine

If that's a problem or not is a matter of perspective.


I don't doubt it's got an electric system in it. I doubt it's got a battery sized for anything beyond that demo, a sufficiently rigid frame for road use, a reasonable steering and suspension system, etc.

My general assumption is that anything and everything that wasn't necessary for that demo was removed to trim enough weight to make the demo possible.


Do you know what a race car is? A race car is a car with, "anything and everything that wasn't necessary for that [Race] was removed to trim enough weight to make the [Race] possible."

Tesla's website literally says the Rocket version is "Not approved for public road use." And has "Seating for one." Any battery that can perform that demo can certainly power basic driving. You're accusing them of deception when every modification you describe is plainly stated on their website. (E.g. It's drive-by-wire, and the seats are modeled chassis elements. Yes, it's wildly minimal.)

The expectation that a vehicle that did a literal standing barrel roll (even if only a single time) be functionally equivalent to a Toyota Camry is madness to me. The much more interesting question is what type of localization system in 3D space were they running?


Stock car racers would literally dip the body panels into acid to make them thinner, shaving off weight.


Am I looking at the right thing?

https://github.com/emdash-cms/emdash

> EmDash depends on Dynamic Workers to run secure sandboxed plugins. Dynamic Workers are currently only available on paid accounts. Upgrade your account (starting at $5/mo) or comment out the worker_loaders block of your wrangler.jsonc configuration file to disable plugins.

Seems like a pretty poor replacement for WordPress, which will run on pretty much whatever random system happens to be within eyesight.


It can be deployed to a node.js server with sqlite https://docs.emdashcms.com/deployment/nodejs/

Not as simple as wp, but not tied to one hosting provider.


The sandboxing requires CF workers though, as it depends on V8 isolates. Seems fair enough, but it'd be nice to see easily deployable cross-platform support someday for isolates or something similar, and not just for emdash.


But how else am I supposed to collect their salary?


My mug only had to be transported to my house once. With disposable cups that's a recurring expense. Unless you have a dilithium powered replicator.


Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: