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.
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.
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.
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.
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.
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"?
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.
Nice to see this here. I've stumbled on this page while researching my stop and train change in Brussels on the way to Config Management Camp. This is the internet that I remember from the very early 2000s. Just plain information, a person happy to share their own interest and carve some space out in this sea of webpages.
This is what I want to see more of in the internet.
Does anyone have the link to the study? I'm tired of news articles referencing and summarizing their interpretation of a study, without giving me the option to validate the claims made.
From looking at it for a few minutes, the gist seems to be software-rendered wayland applications in a Container, streamed into a browser via Go? Or a Desktop client? Not certain yet.
Interesting question here would be the performance - is this efficient enough to get low latency and high framerates? if yes, this could be useful for a bunch of stuff, where you want to spin up a heavyweight GUI app on some kubernetes cluster quickly (think remote dev setup) and stream it to your laptop/tablet.
Edit: Looks like a Desktop client application, also written in Go. But the streaming is implemented with WebRTC and some custom signalling for keyboard/mouse/gamepad feedback, so this could theoretically also be adopted for a Webbrowser I guess?
One of the biggest reasons why digitization in Germany is so slow moving is that every municipality can (and does) decide on how to digitize individually.
There is no mandate for the upper levels of government to dictate which solutions are being used on a local level. Combine that with need for tendering on every single solution and you've got a big mess of small companies underbidding bigger companies that could unify the software landscape and instead build a cheaper, small solution that has zero interoperability with the neighboring municipality.
The need for fax et.al. is not because people don't know how to use computers, but because there's thousands of applications fulfilling the same exact job, but are incapable of talking to each other. Paper is currently the only compatibility layer that works everywhere.
There are ongoing efforts to provide a common data exchange format (technical working group) as well as redesigning how the software for government is being build (tendering processes, public money - public code movement, et. al.)
German government is currently incapable of doing its job in a way that is legally required, missing deadlines and not providing citizens with the services that they are entitled to because they are unable to manage the workload due to the paperbound processes. There is zero fear of humans being replaced by machines. It's rather that more and more humans are leaving government due to burnout.
That's exactly the one we picked. I've even commented it in our Sieve script. Funnily enough some spammers have picked up on this and send their spam even to those mailboxes.
Our company owns a one letter domain (e.g. "x.tld"), that follows a quite common sequence. A few months ago we've enabled receiving e-mails for all local parts on that domain.
We've received hundreds of notification mails, newsletter subscriptions, alerts (from internal systems disclosing details about infrastructure of giant corporations), etc.
It was quite fun, but became annoying quickly. We've then reduced reception to the common hostmaster@, ... mailboxes and for all other mailboxes we are now rejecting the mails with a nice reminder message in our Sieve filters.
Both times this page helped out a lot with technical details! Nice to see it on here. A treasure trove of hacking starting points to repurpose quite slow, but still useful hardware (and saving it from a landfill).