Miners like Riot Blockchain are operating at a loss
I’m not a finance wizard, but I peeked at their last SEC filing, and first 3 quarters of 2024 they posted a 35m operating loss, but added almost 900m worth of assets to their balance sheet (mostly Bitcoin), which to me tells a very different story
The quote is actually from the article this one paraphrased and linked to, while leaving out all of the actual, you know, information
New data tells us that mining a single Bitcoin or one BTC costs the largest public mining companies over $82,000 USD, which is nearly double the figure it did the previous quarter. Estimates for smaller organisations say you need to spend about $137,000 to get that single BTC in return. BTC is currently only valued at $94,703 USD, which seems to be a problem in the math department.
Bitcoin mining will always be profitable for the people with the cheapest electricity and largest economies of scale. There is a difficulty adjustment algorithm in the protocol that ensures this. When the price tanks people turn off thier miners, difficulty adjusts downwards, and then it takes less electricity to find a block.
tl;dr title is wrong
OP said it was to notify you when an alarm went off, not when it ran out of batteries.
Especially because it’s to a newbie, who stands to benefit the most from using an OS with more user share and more available online resources.
Like once a month we have a fake site pop up using the name of our business with 1-2 characters changed. They use a web crawler to scrape all the content off our domain and they re-host all of our products on a woocommerce site where they steal our customers credit card information.
These all use cloudflare to conceal the hosting providers, who are entirely non-responsive without a police report or WIPO ruling. When all is said and done, the content is being hosted in China, Russia, or South Africa, meaning the only way to remove the content is from the registrar’s, because they are the only link in the chain that actually has to comply
You should look at how OPs example works first maybe
The python interpreter isn’t parsing comments, the add() function is just getting the current line number from the call stack context, and using a regex to spit out the numbers to the right of the “#” on the current executing line of the source code.
Do you stay away from C++ too? You can do this there too
https://en.cppreference.com/w/cpp/utility/source_location/line
This stuff is normally used for creating human readable error messages. E.g. printing the line of your code that actually set off the exception
The add function in the example above probably traverses the call stack to see what line of the script is currently being executed by the interpreter, then reads in that line in the original script, parses the comment, and subs in the values in the function call.
This functionality exists so when you get a traceback you can see what line of code triggered it in the error message
That assumes that an adversary has control of the browser
No it doesn’t, if they intercept an encrypted password over HTTPS they can resend the request from their own browser to get access to your account
The big reason you don’t want to send passwords over https is that some organizations have custom certs setup
What is the problem with that? The password is secure and only shared between you and the site you are intending to communicate with. Even if you sent an encrypted password, they wrote the client side code used to generate it, so they can revert it back to its plaintext state server side anyways
It is better to just not send the password at all.
How would you verify it then?
If not sending plaintext passwords was best practice then why do no sites follow this? You are literally posting to a site (Lemmy) that sends plaintext passwords in its request bodies to log-in
Client side verification is just security by obscurity, which gains you very little.
If someone is capable of MITM attacking a user and fetching a password mid-transit to the server over HTTPS, they are surely capable of popping open devtools and reverse engineering your cryptographic code to either a) uncover the original password, or b) just using the encrypted credentials directly to authenticate with your server without ever having known the password in the first place
You are acting like someone checked off a “log passwords” box, as if that’s a thing that even exists
Someone configured a logger to write HTTP bodies and headers, not realizing they needed to build a custom handler to iterate through every body and header anonymizing any fields that may plausibly contain sensitive information. It’s something that literally every dev has done at some point before they knew better.
This is only true for steam keys sold on other platforms afaik
More, but not way more - they would be licensing window IoT, not a full blown OS, and they wouldn’t be paying OTC retail rates for it.
lol. Did this in my old building - the dryer was on an improperly rated circuit and the breaker would trip half the time, eating my money and leaving wet clothes.
It was one of the old, “insert coin, push metal chute in” types. Turns out you could bend a coat hanger and fish it through a hole in the back to engage the lever that the push-mechanism was supposed to engage. Showed everyone in the building.
The landlord came by the building a month later and asked why there was no money in the machines, I told him “we all started going to the laundromat down the street because it was cheaper”
It’s unavoidable - once the cheese gets hot enough the steam will either force the liquid cheese out of existing holes, or it will make its own holes.
Make sure they are fresh out of the freezer when you put them in, as this lets the outside crisp up more before the inside becomes lava. Once you get close to the prescribed cooking time, you need to just sit in front of the oven door and watch them, and as soon as 2-3 break open, take the whole tray out
Maybe a riff on lutris? Not sure why though
The feature is explicit sync, which is a brand new graphics stack API that would fix some issues with nvidia rendering under Wayland.
It’s not a big deal, canonical basically said ‘this isn’t a bug fix or security patch, it’s not getting backported into our LTS release’ - so if you want it you have to install GNOME/mutter from source, switch operating systems, or just wait a few months for the next Ubuntu release
We have been at that point since GPU mining stopped being feasible in 2014, it’s just gotten worse. ASICs made it so the only people who could profit off mining were people who could place a wholesale sized order of hardware from bitmain, etc. Anyone else who claimed to be mining profitably was likely someone who was:
The algorithm already does this though. Every 2016 blocks if it took more than 10 minutes per block, the difficulty of mining bitcoin goes down, not up. This is why every halving event you see a radical drop in difficulty, because at a given kWh you are producing half as many bitcoin - meaning people turned off their miners because it’s less profitable. The flipside is the rate of issuance goes down, so there is a lower inflationary effect, and the price of Bitcoin usually also skyrockets (which means eventually these miners re-enter, and difficulty eventually goes back to where it was). It can never get to a point where Bitcoin mining is completely unprofitable unless the price goes to zero, because there will always be a guy with a solar panel and fully paid-off hardware who can mine it for free. Granted, it can get to a point where a lot of people have to take a huge loss on capital expenditures if the price nosedives and never recovers