I really don’t see the issue. If the work account uses Google or Microsoft I use their respective web apps and export an ICS link to see the blocked slots in my own personal calendar.
For my own personal calendar I use CalDAV, which is widely supported, and an app that can import ICS links. (Self-hosted Radicale server and the Calengoo app for mobile and desktop, for the curious.)
A good overview of the circumstances of the recent Chevron decision.
Please note the final paragraph. Koch’s goal is exactly this: bringing cases in front of the Supreme Court that, if won, would cause grave disturbances.
They’re a very common form of personal backup. A few discs and an USB writer and you get a very long lasting medium for passwords, personal files, family photos etc.
Can also archive multimedia of course, the smallest discs are 25 GB and can pack a few films, a season of a series, or a lot of music.
Oh, God, he’s trying to use pointers again. He can never get them right. And they say I’m supposed to chase my tail…
SO gives you very specific, small examples. GenAI will happily generate entire projects, test suites etc. It’s much easier to get caught into the fantasy that the latter creates.
LLMs don’t generate information, they generate information shaped sentences
That is besides the point. A random number generator is more or less random but it still has applications.
The problem is not them being random, it’s hiding that they are being random so they can be used for applications where randomness is not a feature.
I think it’s more accurately to call it RFID rather than NFC. It operates on the range of frequencies that NFC also uses but this particular application (access ticket) doesn’t require any NFC features. So I doubt they went and made the readers NFC and took the penalties (such as the greatly reduced reading distance) for no practical reason.
As a simple rule of thumb, if the ticket works from more than 5cm away it’s most likely not NFC.
If you can use your smartphone instead of a ticket then it’s NFC.
If the models are random then we shouldn’t be trusting them to do anything, let alone serious applications. If any other type of software told us that it’s based on partially random results we’d say “get that shit out of here, I want my software to work first time, every time”.
“Statistically good enough” works for some applications but not for others. If a LLM finds a formula that has an 80% chance to be the cure for cancer or a new magical fuel or some amazing new material that’s cool, we’re not going to look the gift horse in the mouth.
But using LLM to polute the web with advertising texts that are barely inteligible, and using it as a pretext to break copyright in the process, who does that help? So far the only readily available commercial application for LLMs has been to spit out semi-nonsense so that a bunch of bottom-crawling parasitic industries can be enabled to keep on pinching pennies and shitting up everything they touch.
Which, ironically, it will help them to hit bottom all the faster, so in a strange way it’s a positive return, but the problem is they’re going to take down a lot of useful things with them.
You got it backwards. According to OpenAI and Microsoft you have to respect their copyright but they can ignore yours.
Also no you can’t pirate but they can.
Any questions?
It’s true robots is not regulation but if it’s proven they ignore it on purpose it will be a major point in future lawsuits. And those are the next step.
I’ve yet to understand how the hell they get away with “I don’t know how it works”. Either figure out how it works or stop using it, shithead. It’s software not magic beans.
There’s lots of complicated fields out there, none of them get a pass for “I don’t know how my drugs work” or “I don’t know how my rockets work”. That’s absolutely ridiculous.
You can download past versions of OpenJDK going back to 7 from the link I gave above.
On Google I get the link to the download page as 3rd result, and on DuckDuckGo is the first result.
There might also be some confusion related to the fact openjdk.org only called its builds “openjdk” for version 8 and for versions 11+. Versions 7, 9 and 10 were just called “JDK” so technically there’s no such thing as “openjdk 10”.
Yeah this is pretty much non-news at this point. The last unencumbered versions of JDK and JRE from Oracle went out in 2019, that’s 5 years ago, and they’re still allowing a grace period of another 6 months.
I mean don’t get me wrong, Oracle sucks and the way they go about licensing is shit, but at this point come on. If a company hasn’t bothered to get rid of Oracle’s version of Java for the last 6 years maybe they want to get shafted? I don’t kink-shame.
What do you mean? It’s very easy to find the download page for OpenJDK, and Adoptium’s Temurin seems to be equally easy to find.
Speaking of car plates, the Wikipedia pages for “Vehicle license plates of [insert country here]” are a rabbit hole.
I was just reading the page for Romania the other day, speaking of uniqueness, and they had this issue apparently where the combinations overall were enough for the whole country but not enough for their capital city, so they had to hack an extra digit into the plates for the capital.
These days I follow a hard heuristic: Always use synthetic keys for database tables.
And the way to follow this rule is fairly simple, but it has a few twists.
For internal use, the best and most common key (in a relational database) is an auto-generated incremental sequence. But it it ok to use it externally? – across databases, across types of data storage, across APIs / services etc.
It’s tempting to refer to the sequence number in API calls, after all they are going to that particular database and are only going to be used with it, right? Well not necessarily; the database and the code powering the API are different systems, who says there won’t be other apps accessing the database for example.
The current OpSec school of thought is that sequence keys are an internal database mechanism and sequence numbers should only be used for internal consistency, never used as external references (even for the “local” API).
Sequence keys also don’t offer any way to deal with creating duplicate data entries. If you’ve been around for a while you’ve seen this, the client sends the same “create” request twice for whatever reason (UI lets user multiple-click a button, client assumes timeout when in fact it had gone through etc.) Some programmers attempt to run heuristics on the data and ignore successive create attempts that look “too similar” but it can backfire in many ways.
An UUID is pretty much universally supported nowadays, its designed to be unique across a vast amount of systems, doesn’t give anything away about your internal mechanisms, and if you ask the client to generate the UUID for create requests you can neatly solve the duplicate issue.
Do keep in mind that this doesn’t solve the problem of bijection across many years and many systems and many databases. An entity may still acquire multiple UUID’s, even if they’re each individually perfectly fine.
There can also be circumstances where you have to offer people a natural-looking key for general consumption. You can’t put UUID’s on car plates for example.
“Nobody ever got fired for choosing IBM” - or something like that. It’s still a great defense when things go bust and they probably knew they would.
I beg to differ. I’ve been backing things up to optical for 25 years now with minimal issues. CDs could be easily scratched but it hasn’t been the case for DVD and BR.
M-DISK uses in-organic substances that make the discs mostly immune to exposure but it’s a more recent invention. Proper storage and handling still goes a long way towards protecting discs even if they’re not in-organic.