Thanks for linking that. I’m a big proponent of using ISO 8601 but had either missed or completely forgotten about it specifying a format for intervals.
Note that ISO also permits a double hyphen as the interval separator which is hugely preferable to me personally and also works with file names (as mentioned in that Wikipedia article)
I heavily advocated for introducing GitLab at our company 5 years ago. We're now stuck with it, and GitLab is increasing the price continually. We started with the $4/month start edition because we needed 1 or 2 features, and now we are looking at $29/month for the same 1 or 2 features. We are seriously looking at ditching GitLab because of this. The price hike is insane. They're destroying their customer base in the long term for short term profits.
The only thing that I wish that camera-makers would finally agree on is a common mount. I'd love to try out camera bodies from different manufacturers, but that almost always means switching your entire lens collection as well. No, thanks.
I agree on built-in GPS (currently need to pair with a smartphone - which I'd rather love to leave at home), but everything else seems like a non-feature to me. I have zero interest for that on my Camera, because the experience would just be insanely annoying. Touchscreens are awful for camera operation - the feature is turned off permanently on my camera. Camera needs to be operatable blind, touchscreens are awful for this. Please give me more buttons and dials.
> but that almost always means switching your entire lens collection as well
Sadly, this is entirely by design. Like other industries, camera manufacturers want to ensure lock-in. At least we can usually keep lenses across body changes within the same brand.
There are some more or less standard mounts from early days of film: LTM, 42mm, even Pentax K has been shared by numerous manufacturers. There is the m4/3 mount for digital which is shared across several manufacturers.
The problem is that the mount is always a design constraint. The LTM mount means your lenses cannot have AF. The M4/3 mount means that your sensor size is maxed out at 1/4 the size of a full frame camera. Using the Pentax K mount means that you can't ever have a piece of glass closer than 45mm to the imaging surface.
The most interesting manuever might be Nikon's new Z mount which has the closest flange distance of any full frame mount as well as the widest diameter. This makes it so that it is compatible with the largest amount of lenses of any mount when using adapters. Bizarrely, I can use old Canon EF mount lenses with new Nikon cameras with more features than I can using old Nikon lenses from the same era!
Do you know of Scribus, or do you not consider it a good OSS equivalent for InDesign? Last time I've worked with InDesign was around 2011, and it was meh. Scribus is also really realy meh, but gets the job done. I've got an Affinity license and have been using Designer for a bunch of projects - to me it's a toss between that and Scribus for what I do. They are totally different, but I have more experience with Scribus and therefore am much quicker in using that.
Scribus is unfortunately pretty bad and also almost dead. Its maybe interesting if you want to layout embeded LaTeX but the ux will make you hate yourself.
My wife has been using it for years. Hates it. She upgraded a while back in the hope that the latest version was better, but it sucked. First, it did a one way upgrade in the file format, and every doc she printed from 1.6 looked like trash on her printer (no other settings changed). After messing with various settings for hours she downgraded to 1.5.x, restored her old configuration and and files from backups. Old version prints as expected. It also does totally weird and broken stuff, like the other day she was creating an A4 sheet with 6 cards on it. 5 were copy/pastes of the first one, with minor changes. When she printed it, only 3 of them actually printed even though they're visible onscreen. She printed to a PDF... Same thing. She created a new doc and copy/pasted all 6 into it and printed... they all printed fine. Like WTF is even going on there?
Long time ago ive tried to help the project but really its just too complex of a problem for the few people that maintain it.
At same time its dense C++ codebase that only experienced programmers will be able to contribite to. And those programmers often dont value UX/Design much so it becomes huge rift between bunch of designers unable to do anything themselves and few annoyed programmers.
When the API changes were introduced, I tried to overwrite and delete my comments with a similar browser addon.
I had to repeat the deletion for months afterwards every week, because Reddit restored some random comments of mine again and again, even though they supposedly can not be recovered after being deleted.
I'm fairly convinced that they keep the data even after you delete it. I tried to follow up with a GDPR request, which they answered dishonestly and incomplete, I escalated that to my local authorities and then it took a few months for that authority to get back to me, requesting more information. Sadly I'm not in the mood to throw more of my personal time on this, but hope that at some point Reddit faces some legal actions for their behaviour.
Of course. Does anybody really believe any online company "deletes" their content? Even if some company does make a good faith effort to delete. They have backups, and probably shoddy backup practices where your data remains, gets brought back, is even just laying around in some 'backup_old' directory.
Reddit said years ago that they keep the content of deleted comments, but editing overwrites the content in their database, that is why these extensions were written.
They must have changed it or been lying from the start. (Reddit was partly open source waaayyy back in the day, so one could go check)
Or they're conveniently considering the use of those extensions as an ongoing cyberattack (they probably go against ToS, at the least), and use this opportunity to test their ability to restore from backups.
Based on the information provided being contradictory with itself, and omitting things that were at that time plainly visible on the site. Also, there were comments restored against my will from years ago, which were not contained in the data dump, even though others were. Which means that Reddit holds data in other places (otherwise they would have been unable to restore that), but have not detailed them in the GDPR request, which means that they have answered dishonestly and incomplete.
Did I read this wrong, or is the article essentially "Microsoft screws up security over and over again. Let's throw humans in Russia that are exposing these vulnerabilities under the bus of a dictatorship and possibly get them killed in a war. Instead of forcing the gigantic cooperation to not screw up security over and over again and finally clean their house"?
I agree with your top level point, but I find your phrasing absurd.
The "humans who are exposing those vulnerabilities" are doing it to profit by committing extremely disruptive attacks on random businesses, hospitals, and important infrastructure.
I don't support literally getting them killed, but they're not innocent hackers driven by curiosity the way your comment makes it sound.
> Let's throw humans in Russia that are exposing these vulnerabilities under the bus of a dictatorship and possibly get them killed in a war.
Am I reading this right that you’re more concerned with Russian assets that hack US companies for both financial gain and political leverage, than the US citizens whose lives are put at risk? What exactly do you think happens when a ransomware gang locks down a hospital?
I'm concerned with suggesting that it's enough to fight one group of adversaries, which will then be replaced with another group, and another, instead of actually fixing the underlying issue. Suggesting threat of life to those people (which is a very real thing for russians now) is no better than what happens when a ransomware gang locks down a hospital. That would be fighting fire with fire.
Yes, brainiac, they're people too. Doesn't make them "good" people, sure, but they're people too. Everyone gets born into some fucked up system, brainwashed into believing whatever he needs to believe so he thinks he's the good guy doing the right things.
Once you start dehumanizing, you won't stop dehumanizing. Eventually only people you agree with will be considered "people", and boom, you're a fascist.
Most terrorists aren't born into some fucked up system. They cultivate those feelings slowly by letting themselves exposed to the wrong set of people, values, etc.
The Glasgow bombers were doctors who studied with my cousin in Saudi Arabia back in the day. My cousin didn't go around making bombs though.
The authors point was to treat cyberattacks just like physical attacks. If a country attacks you, you don't just tell your own military that they need to step up their game and close the holes. You seriously consider going and killing the bastards that attacked you, even if they exploited your own weakness, even if you made mistakes and could have prevented it.
Vector to me is more than just "high-performance" - It's a true swiss army knife for metrics and logging. We regularly use it to transform logs to metrics, metrics to different format, push them to different datastores, filter them, etc. It's wild how flexible this program is. It has become my first choice for anything regarding gathering/aggregating/filtering/preprocessing observability data.
Announced today. TL;DR: Run your loadbalancers in a single place, let other (workload-)clusters push their configs through KubeLB to the loadbalancer-cluster, which loadbalances onto the workload-clusters.
Low-latency (e.g. less than 20 lines) Videoswitchers/mixers. There's a huge amount of data (12Gbps for 4K/UHD) per input, with many inputs and outputs, all with extremely tight timing tolerances. If you loosen the latency restrictions you can do a small numbers of inputs on regular PCs (see OBS Studio), but at some point a PC architecture will not scale easily anymore and it is much more efficient to just use FPGAs that will do the required logic in hardware. It's such a small market that for most devices an ASIC is not a option.
Blackmagic's whole gear line is based on Xilinx FPGAs. Whatever product of them you see, if you tear it down, it will almost always be nothing more than SerDes chips, I/O controllers and FPGAs.
