mlfreeman

Please provide links to the relevant regulations from an actual government website such as eCFR in the US (https://www.ecfr.gov/)

And the ToS probably has a clause that says "we can alter the deal any time we want and you should pray we don't alter it further".

Does anyone even compile these into a site?

In potentially-dangerous-animal country (e.g. grizzly bears, mountain lions, etc), it could be a safety mechanism...I was told repeatedly you need to make some kind of distinctive noise regularly so they won't get startled by you rounding a bend.

And Wingdings for classified material!

Only allow clients to execute stored procedures?

Are the satellites being turned off, or could people with SDRs pick this up directly from space and offer it up for free?

I think this is the root of the problem.

I think library/runtime makers aren't saying "let's make an official/blessed take on this thing that a large number of users are doing" as much as they should.

Popular libraries for a given runtime/language should be funded/bought/cloned by the runtime makers (e.g. MS for .NET, IBM/Oracle for Java) more than they are now.

I know someone will inevitably mention concerns about monopolies/anti-trust/"stifling innovation" but I don't really care. Sometimes you have to standardize some things to unlock new opportunities.

The use of "unlikely" just screams that Ofcom will eventually pull a Vader..."We are altering the deal, pray we don't alter it any further".

It appears to literally just be their main page. Menu options bring up content and I logged in and and can still see an in-progress complaint I opened on Jan 7th.

What do the regulators writing this intend for this to slow down/stop?

I can't seem to find any information about that anywhere.

When I back up machines I only pull a full backup 3-4 times a year and then I stack weekly deltas on top of those.

I'd start with that and see how it seemed to work when trying to look through backups and test-restore things.

> it does nothing to protect you in the event of a password manager compromise. This is not a hypothetical; LastPass has suffered multiple breaches, and the more popular a solution, the more likely there are to be attacks against that solution.

You can mitigate this risk by not depending on your password manager app to do cross-device sync..keep a file on Dropbox/OneDrive/iCloud Drive/SFTP/etc and use an app like KeePass/Strongbox/etc that just deals in managing credentials.

My KeePass file storage provider doesn't know what the hell I store there because it's encrypted (I hope there are no known issues with KeePass's crypto)

As a bonus, you can keep offline backups to mitigate other risks like house fire, lightning strike induced EMP frying things (happened to me), storage vendor goes out of business, and more.

-------------

I think in the end, there is no universal solution - you really have to try to be reasonable about estimating your own personal threats and risks (such as asking "am I more likely to suffer a password manager compromise or more likely to break a device?") to decide whether to keep 2FA next to passwords or not.

I moved from my own colocated 1U running Mailcow to Fastmail and don't regret it one bit. This was an interesting read, glad to see they think things through nice and carefully.

The only things I wish FM had are all software:

1. A takeout-style API to let me grab a complete snapshot once a week with one call

2. The ability to be an IdP for Tailscale.

Are there any tools that can run (even across network on another box) to analyze possible duplication at various block sizes?

I am NOT interested in finding duplicate files, but duplicate slices within all my files overall.

I can easily throw together code myself to find duplicate files.

EDIT: I guess I’m looking for a ZFS/BTRFS/other dedupe preview tool that would say “you might save this much if you used this dedupe process.”

I see people pointing out the "Caesar -> tsar" link (and I've heard that myself too), but I have to wonder if Akkadian "sar" somehow became "Caesar".

Google’s track record of killing stuff quickly has got to be demotivating for employees.

What would this potentially do to Z-Wave devices?

Even if we can't can we think of better names?

"kibibyte" sounds like a dog treat not a unit of measurement.

> Wouldn’t this just encourage law enforcement to cite everyone for every little infraction?

Hmm, potentially...if they thought that would secure a much larger slice for themselves by knocking people out of the running...so maybe they'd have to be ineligible. However, in most cases that would require citing a hell of a lot of people (Jacksonville, FL has ~3000 cops for ~1.2m people, so they'd have to each cite several locals a day all 365 days of the year to make a dent in who's getting any money)

Since some criminals would be non-locals, you could also hand out the fines equally to all locals regardless of whether they got busted for anything or not.

> Everyone breaks law the eventually. The article mentions the “Miami right” as an example.

Yes, there is a randomness to it all (breaking the law vs breaking and getting caught) but I'm not going to try to compensate for or control it.

> So the government can purposefully take on more debt and then find infractions to pay it off?

Yeah, I realized this oversight 5 minutes after I clicked submit. However, perhaps it could be pooled and redistributed equally to pay down equal amounts of debt for all the governments in a region.

The point is that fines/seizures should not be a line item in a government budget EVER because then somehow the government will become dependent on criminal activity to an extent and go looking for it just for the money. It should be a completely unexpected windfall and thus either returned to the people or used to pay down debt. That's my hope, the details could probably take months to hammer out.

Apparently you and I think somewhat alike!

I worry that as long as the money remains in government hands at all there would still be abuse.

I had two ideas in this regard.

-----------------------

All fines (and proceeds from auctioning off seized assets) collected by all levels of government should be broken down into two categories:

- Traffic

- Criminal

If you have a drivers license and make it a whole calendar year without getting a traffic citation, you should get an equal slice of the traffic citation money from the feds and the city/county/state that has jurisdiction over the address on your DL.

If you have government ID and make it a whole calendar year without getting cited/arrested (let alone convicted), you should get an equal slice of the criminal seizure/fine money from the feds and the city/county/state that has jurisdiction over the address on your ID.

The funding for the distribution infrastructure should NOT come from the fines/citations/seizures.

In short, redistribute the fine money from those who broke the law to those who didn't (or at least didn't get caught).

-----------------------

The other far simpler option is that all fines/penalties automatically get applied to paying down debt owed by the collecting government.

If somehow a government has no debt (shocked face here) it would kicked upward to pay down debt at a higher level (e.g. city has no debt, so it gets sent to the state...and if somehow the state has no debt, it goes to the US Treasury's donation office).

Many years ago I partially cloned the old iGoogle homepage because I liked it (and Google was killing it off). It's gone through a few experimental rewrites in various technologies for personal educational purposes.

Right now, it's ASP.NET/.NET 8 on the backend and still plain jQuery on the frontend.

I display RSS feeds, US National Weather Service data, and comics in it. I also have it send some things to friends and family as emails periodically.

Hangfire works on the backend to actually fetch new data at appropriate intervals.

I occasionally have to modify something and manually push a new build because something remote changes but it feels fairly stable right now (knock on wood).

I want to redo it to use ASP.NET AssemblyParts and work towards essentially giving each little box its own DLL as a sort-of-plugin-system so that I feel more comfortable adding more types of boxes (stocks, different weather data, etc) and maybe one day can open-source it. (I'd like to so I can point prospective employers at it and say "see, i can actually write reasonable real world code.")

Also it's greener over the septic tank.

change "professional software developers" to "real programmers" and this is like watching https://xkcd.com/378/ come to life.

Taking the device offline requires you to either have control of or destroy the current phone, while that SIM protection sounded like something a customer service rep could be tricked into working around.

I'll throw out an idea that seems simple to me...

An *opt-in* option to require that lines on your account can not be moved to a new SIM unless the current SIM is offline as far as the cell grid is concerned.

This could even be made into something that customer service could be blocked from overriding.

If someone steals your phone, they try to get it into airplane mode as fast as possible to avoid activation locks. If you drop your phone in the ocean or off the side of a cliff, it's probably not going to remain working for long. If you're concerned about losing it somewhere where it'd remain active but you'd never find it, then don't opt in to this.

> you will probably still not be able to boot windows from btrfs.

See his other repo, he appears to be working on that. https://github.com/maharmstone/quibble

> What is the difference between a stock buy back and a dividend?

A dividend payout is cash in your hand, a share buyback is theoretical gains that may be gone by the time you sell.

I remember putting my ear up to the little holes and faintly hearing the audio even without anything plugged in.