Feel like the (totally impractical) fediverse end-game would be for each individual to have their own activitypub service, and federation happening on a person-by-person basis. So you retain some control over anything you publish, and your history is yours to keep.
As others have said, changing UPS batteries is required maintenance, and I agree 18-24 months is the typical service life for even high-end UPSs. However, you may want to look into LiFePO4 based UPSs, which can handle many more charge-discharge cycles and often have 5-year warranties. More expensive and potentially not as recyclable as lead acid batteries, but maybe appropriate for your use case.
This is a good, short read. For those who are unfamiliar with the AGPL license that the author proposes we all start using, the main difference (and I am not a lawyer) is that under the AGPL, the source code including any modifications must also be made available to all users interacting with the software over a network. This prevents companies from making proprietary versions of AGPL software that are only accessible as a web service, which is one of the big ways that corporations are able to profit from GPL source code contributions these days.
Mine’s more like an LLM - exposed to a vast quantity of technical terms that they don’t really understand, but can mash them together well enough to make coherent-sounding statements in JIRA
In UNIX-y systems ./ is your current local directory, so if I was in /usr/home/will and I extracted your file I would expect any file that was like ./foo.txt to be extracted to /usr/home/will/foo.txt, and if there were files like ./testar/bar.txt, they would be extracted to a new directory /usr/home/will/testar/bar.txt – or is that not what you’re talking about?
Who is your PM or senior assigning the tasks? You need to take this up with them – everyone always needs a couple of quick hits in their back pocket. When you stall out grinding on task after impossible task it kills your motivation and productivity, and that’s your boss’s job to fix.
Fair enough. ML ⊆ AI then. But these days when everyone talking breathlessly about AI taking away jobs they’re almost always taking about LLMs. This article is about ML in particular which is a different discipline with different applications.
ML =/= AI. There are legit uses for ML that don’t have anything to do with LLMs and the cloud. I worked on an ML project 3 or 4 years ago to listen for fan noise that might indicate that it was about to fail soon. We trained a tiny GAN on good and bad noises. It runs on a tiny CPU, locally. Highly specialized work, and I have to imagine there are and will continue to be lots of similar opportunities to bring efficiencies by getting computers to make good observations and decisions - even if only about “simple” things like “does this thing seem like it’s about to break?”
Is this old enough to be called a classic yet?
draw.io is a capable web-based flowcharting program. Source code is on github but I’ve never tried locally hosting.
Hook them up, run a SMART test and see what their powered-on hours and error-rates look like. If it’s not a significant fraction of the MTBF, chances are you’ll be fine – assuming you’re using them in a RAID or ZFS array where a drive loss is not necessarily catastrophic.
Having a hard time determining whether this is sarcasm or not. Then I see the phrase “JavaScript Engineer” and become doubly confused.
For 100TB it’s worth looking into a dedicated storage server – there are tons of them available for cheap. labgopher makes it easy to track sales on ebay by price/storage/ram/whatever.
I worked in a field that managed a lot of technology in retail stores. The big ones know everything about you, it’s just astonishing. At the time (around 15 years ago) there was very little oversight, but also most CIOs were inept and couldn’t really make the data sing and dance. Today that is very much no longer true, and it’s almost too easy to build a comprehensive profile of an “anonymous” guest and then attach it to their personally identifiable information, all without their consent or knowledge.
Of the changes made last week to the license, this one stands out:
That is a weird carve-out, so I’d guess the license revision (and technically the reason it’s no longer open source) somehow has to do with Atlassian or their plugin marketplace?