Readit News logoReadit News
AntonyGarand commented on Apple violated antitrust ruling, judge finds   wsj.com/tech/apple-violat... · Posted by u/shayneo
jillyboel · 4 months ago
why do we want an apple link that just redirects to the original article? is this just "look at me i'm a mac user" levels of spam?
AntonyGarand · 4 months ago
I believe this is a way to use their own apple news subscription to access the article instead of using the archive version: It only redirects if you're not logged in to apple news.
AntonyGarand commented on Apache ECharts   echarts.apache.org/en/ind... · Posted by u/tomtomistaken
sergioisidoro · 5 months ago
A very large library of premade charts for web. Probably the largest I've seen. Less customizable than chart.js, and D3 is more of a rendering library than a charting library.
AntonyGarand · 5 months ago
I'm surprised by your claim of it being less customizable than chart.js, it has been very flexible from my experience.

It could rival d3 with a lot of customization and a worse DX from what I've seen: It's essentially a good amount of defaults, but you can override and replace essentially anything.

AntonyGarand commented on We asked camera companies why their RAW formats are all different and confusing   theverge.com/tech/640119/... · Posted by u/Tomte
gwbas1c · 5 months ago
> If a manufacturer comes up with additional data that isn’t included in the DNG standard, the format is extensible enough that a camera manufacturer can throw it in there, anyway.

It sounds like DNG has so much variation that applications would still need to support different features from different manufacturers. I'm not sure it (DNG) will really solve interoperability problems. This issue smells like someone is accidentally playing politics without realizing it.

Kind of reminds me of the interoperability fallacy with XML. Just because my application and your application use XML, it doesn't mean that our applications are interoperable.

I suspect that a better approach would be a "RAW lite" format that supports a very narrow set of very common features; but otherwise let camera manufacturers keep their RAW files as they see fit.

AntonyGarand · 5 months ago
Seems like DNG does behave like the RAW lite format you've just described: Everything common would be stored within the base DNG file, while everything "advanced" / more specific to a camera would be stored in additional metadata properties, which do not need to be parsed to still be able to process the base image. You can add support for these metadata on a case-by-case basis without breaking the original format, so you're not stuck re-implementing your whole raw parsing when a new camera is released as the base subset of DNG would still work.
AntonyGarand commented on We asked camera companies why their RAW formats are all different and confusing   theverge.com/tech/640119/... · Posted by u/Tomte
PaulHoule · 5 months ago
Don't know what's confusing about it... I mean, I shoot ARW with my Sony, these work fine with Lightroom and work fine with DxO PhotoLab [1] at least as long as my ARWs are not compressed (it's not that the compression is proprietary, it's that the compression is lossy and breaks denoising)

[1] Shoot ISO 12,800, process with DxO, people will think you shot at ISO 200; makes shooting sports indoor look easy, see https://bsky.app/profile/up-8.bsky.social/post/3lkc45d3xcs2x so I got zero nostalgia for film.

AntonyGarand · 5 months ago
Proprietary formats require 3rd party developers to adapt their tools: While most mainstream software will be updated to support most/all cameras, this makes it harder for smaller projects to do. If they used an open standard, the advanced features could still require additional work to be compatible (ex: If they store custom metadata), but you could normalize everything that's shared, ensuring the core capabilities will never break for a new camera with its updated proprietary RAW like it currently does.
AntonyGarand commented on Twitter.com – Is Twitter Down?   isitdownrightnow.com/twit... · Posted by u/antimora
tkubacki · 6 months ago
What are X/twitter alternatives ? I left twitter after recent Musk pro Russian statements.
AntonyGarand · 6 months ago
Mastodon and Bluesky are the main ones as far as I'm aware
AntonyGarand commented on Ask HN: Alternatives to Bitwarden?    · Posted by u/rossng
powersnail · 10 months ago
The problem with that statement is what exactly does "in a way that maintains GPL compatibility" means, especially since they plan on moving more functionalities into the proprietary code, so the two "separate" components will be increasingly coupled together.

I'm not a lawyer, but I'm quite skeptical of the outcome. Is it really going to produce a valid GPLv3 licensed client? To me, it seems like the whole thing is just going to be a combined proprietary + GPLv3 license, which will contradict itself.

But again, I'm not a lawyer, so my understanding of this might be way off.

AntonyGarand · 10 months ago
Seems like they relicensed their whole SDK to GPL so that's a move in the right direction!

https://news.ycombinator.com/item?id=41940580

AntonyGarand commented on Ask HN: Alternatives to Bitwarden?    · Posted by u/rossng
AntonyGarand · 10 months ago
Per their response to this issue, seems like this is a bug: While they do have some non-FOSS code in their `sdk` package, the client should still be buildable without the SDK:

> Hi @brjsp, > Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility. > > > the SDK and the client are two separate programs > code for each program is in separate repositories > the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3 > Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

AntonyGarand commented on Bypassing airport security via SQL injection   ian.sh/tsa... · Posted by u/iancarroll
jerf · a year ago
You know it's bad when it's so bad that as I write this no one has even bothered talking about how bad storing MD5'd passwords is. This even proves they aren't even so much as salting it, which is itself insufficient for MD5.

But that isn't even relevant when you can go traipsing through the SQL query itself just by asking; wouldn't matter how well the passwords were stored.

AntonyGarand · a year ago
The md5 part of the sqli is added by the pentester, likely because they needed a call that would end in a parenthesis within the injection parameter
AntonyGarand commented on The Time I Lied to the CTO and Saved the Day   GrumpyOldDev.com/post/the... · Posted by u/mundanerality
itronitron · a year ago
I heard rumor back in the late `90's of an e-commerce site that stored the prices for it's products in the browser cookie. Presumably a motivated buyer could go in and edit the cookie before checkout, although I don't know if that ever actually happened.
AntonyGarand · a year ago
This brings back memory: This was the case for a gold-buying website for the Runescape game in the 2000s. You could edit your cookies or other front-end facing information to change the price of items in your cart, so you could buy gold or items for much cheaper than the market rate. At some point, while the vulnerability remained, they started cancelling orders abusing this and manually checking the orders.

I think you could still find some old youtube videos or threads on obscure forums with enough digging about that topic, that's how I learned of it initially.

So this was a real thing!

u/AntonyGarand

KarmaCake day284July 5, 2017View Original