413 is amateur hour.

1000 charge cycles. If you charge twice a week, that’s 500 weeks or a little less than 10 years. There’s no mention of degradation over time.

But back-of-the-napkin, it means for this to be cost-effective, they may want to come up with some sort of replaceable or battery swap system. Not sure anyone will want to buy a vehicle that needs a massive battery retrofit every 8-10 years.

So… Hyundai Automotive signed a deal with Hyundai Electric to supply them with electricity.

🤔

This is pretty sad.

I have a number of elderly relatives. The one thing I keep telling them is if they ever get approached, to contact their kids, or check with another family member before responding. So far, there haven’t been any problems.

But I heard an in-law’s parents in a different state lost a big chunk of money to one of these scams and may now lose their home.

Not a WP dev. Just a (techie) user.

This whole thing seems so unnecessary. FOSS devs would love to get a fraction of the goodwill being squandered here.

All the deserved ribbing aside, if you had to design a removable, R/W, high-capacity, environmentally tolerant, secure, fault-tolerant, mission critical storage system that could last 25 years, starting NOW…

What would you pick?

That’s a tough one, even if you design future hardware upgrades into the system.

Apple and Google can fix the problem. Apps are required to ask for permission to access location information. Most of the time, it’s for tracking and analytics, not anything related to the app’s functionality. That’s the data that is leaking to these data brokers.

In those cases, if asked, user can say no, but apps keep haranguing you until you capitulate.

Instead, the OS could add a button that says: “Yes, but randomize.” After that, location data is returned as normal, but from totally random locations nearby. They could even spoof the data clustering algorithms and just pick some rando location and keep showing returns to them, or just trade the data from one random phone for another every N days.

You do this enough and the data will become polluted enough to become useless.

It was the window seal.

Read the book. Great story. Was curious why they decided to roll up the program at the end and blow their own cover. Book mentioned it was getting too popular, but that didn’t sound right.

Hopefully, the talk will explain it a little better. Bookmarked to watch.

Out in the cloud world, several companies changed their FOSS license to prevent large cloud providers from making money off their work (eg, Terraform, Redis, Mongo, and ElasticSearch).

Their reasoning was sound, on paper. They were spending a ton of time and money supporting a popular product and the only way to make money on it was by selling hosted services to enterprise. Then these other cloud providers would take their work for free, compete with them for the same customers, and often win.

In almost all these cases, the FOSS developers were pilloried for changing the terms of their original license, leading to immediate forks and fragmentation of the community.

The only outfit that I know of that survived the transition was Thingsboard. They still offer an open-source service, but they take a lot of their enterprise-only adapters and do not offer it as FOSS. Only way to get these is to sign up with their service.

Wordpress could have taken a survey of their highest paying customers, then created features they needed behind a private hosting service. Yes, people would have been unhappy, but the core service would remain FOSS and the company would still make a lot of money.

This whole thing has been done in the worse possible, public, mud-slinging manner. I don’t understand who benefits from the scorched-earth approach.

Wonder if they had to tie the knot three times to get it right?

Have been playing with this inside Illustrator all day. Still a little glitchy. A couple years from now, though, not sure anyone will need commodity stock icons or images.

However, those able to design and build a consistent look and feel across apps/web/video/physical will still be needed, and likely worth even more.

0 out of 5 stars. Came here to find how to get rid of sewer gases backing up into my bunker and all I got was something about “window managers.”

WHO PUTS WINDOWS IN BUNKERS?

S3 started as a place on the cloud to store and retrieve files. But it’s evolved a lot over the years:

• You can directly stream music and videos from it.
• Along with a separate Content Distribution Network (CloudFront), you can have copies geographically replicated to be closer to end-users.
• There’s a separate service (Transfer), you can have multiple locations securely upload files to it. Examples are schools, retail outlets, enterprise divisions, news media, etc.
• It has a built-in event system, so whenever a file is uploaded, it can trigger a function to process the content automatically. This makes it handy for applications where users upload content (like videos) that need to be automatically converted, then copied to another S3 ‘bucket’ for streaming or download.
• You can make a ‘bucket’ (think of it as a directory of files) become a webserver, accessible via HTTP. This makes it dead-easy to build web front-ends using React/Vue, etc. and deploy them there.
• Also handy to host static HTML content, for things like blogs, portfolios, or galleries. A lot of static content generators like Hugo and Jekyll have direct upload to S3 built in.
• If looking to archive or backup, you can designate files to be put into deep freeze on Glacier. This means they are stored, but you will likely not have to access them that often. Storage and access costs are lots cheaper.
• There’s a whole audit log/access control backend for regulated industries like finance, law, or healthcare.
• You can set alarms so you are notified when there is a problem, and rules to prevent things like massive file uploads or DDOS downloads.
• You can create what’s called a ‘pre-signed URL’ so someone using it can securely access a file for a limited amount of time. Those without can’t access it.
• There’s a command line tool, as well as programming toolkits in lots of languages that let your websites and apps directly integrate with it.
• Cost-wise, it’s pay-as-you-go with no monthly fee. So you can store a bunch of files up there and the bill at the end of the month is like, $0.23.
• However, there is a fee for ‘egress’ traffic to the cloud, so if you want to put some content somewhere public and a lot of people access it, it can get expensive.
• A bunch of third-party services have sprung up to offer basic S3-like access with zero egress fees, but they trade that fee for a basic monthly one (Backblaze B2, CloudFlare R2, Wasabi). Generally, they’ll cost less, but you lose some of the above features.
• There are tools that mount S3 buckets as local filesystems, so you can add/list/delete files as if they’re local.

There’s more, but that’s the crux of it.

Good thing they stopped emptying train toilets on the tracks.

If you use github pages, you can create, deploy, and host static websites for free. Only cost, if you want your own URL, is for a custom DNS name.

You can use their default Jekyll static rendering engine, and create the content using Markdown. And with github actions, all you need to update the content is create markdown, then push the change to the same repo. After a few minutes, the new content shows up.

https://pages.github.com/

Hugo can also be used, but it takes a few extra steps: https://gohugo.io/hosting-and-deployment/hosting-on-github/

You can also find ‘themes’ to customize the look and feel of the site, specific to the site generation tool.

If you want a lot of extra features, Docusaurus is pretty much as good as it gets, and you can set it up to push out to GH pages: https://docusaurus.io/docs/deployment

My favorite tell is when a write-up starts with a verbose explanation of given knowledge on a subject. Yes, we all know what ‘World Wide Web’ and ‘Internal Combustion Engines’ are.

Get to the f’ing point.

So many $$$$$$$$$$$$$, no doubt, for a single record in a database.