• 0 Posts
  • 1.1K Comments
Joined 2 years ago
cake
Cake day: June 21st, 2023

help-circle

  • There sure are, and if necessary they can be applied and are good practices in general. As long as these web sites still see user traffic, monetized or not, even with users using workarounds, they’ll keep thinking what they are doing is cool, and the only problem is that they just have to monetize harder, and then “obviously” all those workaround users will fall in line and monetize like everyone else once they’ve “fixed the glitch”.

    If they see a void of user traffic, that gets their attention. Of course, for the person viewing the content, the person has to make a conscious choice to go elsewhere/watch something else/do something else. Would be a good time for content creators to start shifting as well. Patreon even lists a bunch of video services that are not YouTube: https://support.patreon.com/hc/en-us/articles/360046704651-What-are-my-video-hosting-options








  • The problem comes in so many directions in real life though. Say your company has a very large database. Replicating it across regions means you’re paying for data ingress/egress and more than one region’s copy of that already sharded and/or duplicated database. It even applies when transferring data across AZs in a given region. Backing it up to S3 is expensive, backing it up to Glacier is cheaper, until you ever have to do a restore, and then you have to lay off half the staff to pay for it.

    Other issues can arise, possibly through the fault of yourself, sometimes at the fault of Amazon, if data traffic routing has a glitch and data is routing to the wrong place. The onus either way is on your company to show Amazon the receipts if you expect to get credits for the overage. At larger scale, this could be hundreds of thousands of dollars in overage. Easy to torpedo smaller companies with one mistake.

    They didn’t used to nickel and dime as hard as they do now, which doesn’t help, but outside of history, they set up AWS to be the biggest slippery slope of wallet-deletion, as almost every move you make costs money. Entire companies exist to manage your AWS costs (for more money, of course) and other companies’ products you may use that are hosted in your infra may accidentally delete your wallet if you don’t constantly monitor them.

    Using AWS cost-efficiently is only accomplished by ostensibly day-trading your cloud resources like a high frequency stock trader, capitalizing on unpopular/weird system types, and keeping your code as portable as possible.

    …but if one didn’t care about cost, one would probably get pretty good reliability out of them, sure.



  • I only decided to set up a personal AWS for some minor things after having worked on it at employers for many years, after watching employers accidentally spend $3000 a day or $1 million a month or $35,000 in error. Cloud is the devil, bring back servers. One flat piece of hardware you can do whatever with…but even that’s not sacred. If you use hosted servers, the hosts often still charge for ingress/egress and other things now, so you still fall into traps if not careful. Simpler though.

    So I guess, storing your own server in your office is the way to go, but then the ISP issues…

    Let us all just go back to paper, actually.






  • The muppets in the Federal government are trying their hardest to make this occur so they can try and find some loophole to go ahead with their martial law plans to arrest all the people they don’t like that week. What we’re likely seeing is mature restraint on behalf of firearm owners.

    Some years back, the quote was something like, “as soon as you discharge your weapon, you are looking at spending at least $10,000 from legal fees” (if you don’t have firearm insurance and/or if it would even be applicable) - that number is probably tenfold now. Not to mention the very likely personal harm others have mentioned.

    Legal fees or not, being dead is pretty hard to come back from.