chiisana @ chiisana @lemmy.chiisana.net

Posts

4

Comments

500

Joined

2 yr. ago

This article is from May of this year and on a quick glance didn’t seem to add any value to the current iteration of the rumour mill discussion.

I’m not convinced one way or another until more reputable sources add more colours to the situation.

Sky is tabloid and often run hot takes without confirmation, so the original should be taken with a huge grain of salt. However, considering India’s position to benefit from cheap Russian exports right now, it is going to take a lot more in depth analysis than a couple of sentences of counter claim from Indian sources to definitively proof otherwise.

Future news headline: “The web server literally exploded under the DDOS attack.”

There’s also the option to turn on auto app update in Settings > App Store > Automatic Downloads > App Updates ; and it will be updated automatically in the background.

I scream test myself… kidding aside, I try to pin to major versions where possible — Postgres:16-alpine for example will generally not break between updates and things should just chip along. It’s when indie devs not tagging anything other than latest or adhere to semantic versioning best practices where I keep watchtower off and update once in a blue moon manually as a result.

Multiple compose file, each in their own directory for a stack of services. Running Lemmy? It goes to ~/compose_home/lemmy, with binds for image resized and database as folders inside that directory. Running website? It goes to ~/compose_home/example.com, with its static files, api, and database binds all as folders inside that. Etc etc. Use gateway reverse proxy (I prefer Traefik but each to their own) and have each stack join the network to expose only what you’d need.

Back up is easy, snapshot the volume bind (stop any service individually as needed); moving server for specific stack is easy, just move the directory over to a new system (update gateway info if required); upgrading is easy, just upgrade individual stack and off to the races.

Pulling all stacks into a single compose for the system as a whole is nuts. You lose all the flexibility and gain… nothing?

As with a lot of things in the crypto adjacent space, they’re offering a solution looking for problems. Some problems (such as storing and distributing files) are essentially solved (many cheap providers for both storage, distribution, and/or both to choose from), while others (such cryptographically secured immutable ledger for provenance tracking in specific use-cases) might benefit from the technology. Knowing which is which and where to adopt what tech is the challenging part.

How big is the volume/partition for that target? What filesystem are you using? I ran into an issue earlier this year/late last year where my volume exceeded 18TB which EXT4 doesn’t support on my setup.

If cost is a reason for concern, then the 5c/GB storage and 8c/GB egress on Pinata isn’t exactly cheaper than S3’s 2.7c/GB storage and 9c/GB egress. You can get much better mileage with something like Backblaze B2 0.6c/GB storage free egress, and couple with CloudFlare or other CDN for much lower egress (often free).

Civilian here. There are companies that mine, store, transport and broker uranium. These companies employe people with different skill sets from physical labor all the way up to management. An increase in price may lead to an increased level of employment by these companies, thereby increasing the number of jobs, and play a role in impacting the economy at large. It makes sense for this kind of news to be filed in the business section, even if it doesn’t directly affect most of our day to day.

“Too complicated” feels like a cop out… there’s no question as to whether or not clients can send both, from best practice point of view, the party instilling the change should bore the burden of supporting both for some time. I cannot and do not want to change the current release train, but I hope you can take this into consideration into the future, for future breaking changes.

I’m not asking about whether or not clients can do it, there’s no doubt a dual outbound header method is possible, but rather more about general development best practices. When instilling a change, isn’t it usually best to support both states to ensure least amount of users are immediately affected, and gradually bleed those stragglers out?

With the authentication header update, isn’t usual best practice to support both on the server side simultaneously, and set a deprecation window such that clients can update over time?

On similar note, it’s a shame to see perfectly functional older systems to be left behind due to expired root certificates or other similar issues. I don’t care about the bells and whistles of newer OS, but is there a way to update older systems to support slightly newer encryption standards so it can continue to hang on for a bit longer (as macOS system, I know of course I can install Ubuntu on it)? — looking at my unibody aluminum MacBook from 2011 or so, for example.

True. I’m looking for an extra headless system so it doesn’t directly affect me, but that could certainly be a concern if you’re in need for 4K.

At $80 a pop, might get more oomph from an older optiplex if electricity cost isn’t too big of a concern?

As much as most don’t like Facebook, I honestly don’t see why Facebook is at fault here. They’ve got a platform where advertisers come on, say “I want to sell ads to people Ages X-Y , Gender A, in Geography I, J and K”, and they serve ads accordingly. What are they supposed to do? Tell the advertisers “No no no, you need to also pay for ads on these other demographics that you explicitly excluded”? The plaintiff should be suing advertisers, not Facebook, for intentionally not targeting them.

Soon afterwards a row broke out between the Surrey district police and the Royal Canadian Mounted Police, who are something like India’s CBI or the US FBI.

Surrey district police => local police, think “NYPD”

Royal Canadian Mounted Police => RCMP, the federally operated police force, essentially have jurisdiction nation wide, generally the sole police force if there’s no locally established police force. Surrey Police was formed relatively recently as a former Mayor’s pet project and the current Mayor’s entire campaign is the reverse the change and get the RCMP back. 🤷

Apple is generally really good with privacy stuff. The health data stays on device unless you enable iCloud backup/sync. You can choose what app (if any) you’d like to share which part of your health data with (at which point you’re beholden by those app’s workflows and privacy policies). You can read directly from Apple here.

But the limiting factor is that you’d need to buy in to the rest of the ecosystem… or at least an iPhone. Not an issue for me, but YMMV depending on personal preferences.

If memory serves, one of the main selling point that was presented was that WebP was able to compress an image better while retaining more visually relevant information than JPEG.