JSON Hero: Enhanced JSON structure visualization • Hacker News Board

Re: JSON Hero: Enhanced JSON structure visualization

#111

Post by simplotek » Tue, Nov 29, 2022, 10:37 AM UTC

TeMPOraL wrote: post #109

simplotek wrote: post #106

Earlier quoted context omitted.

> Personal data is a red herring. It's not the only thing that matters. For starters, using this at work with anything not explicitly public is likely a violation of your contract. (...) "Personal data" means the reddest of data. If a system collects and tracks personal information then it will be expected to collect highly sensitive information that is not personal. It makes absolutely no sense at all to try to down…

I mean it the other way: I see the problems routinely downplayed with excuses like "it's not collecting personal data". See e.g. this, elsewhere in this thread: https://news.ycombinator.com/item?id=33784919 . What does the linked Microsoft page say? Quoting: > The telemetry feature doesn't collect personal data, such as usernames or email addresses. It doesn't scan your code and doesn't extract project-level data, su…

> I mean it the other way: I see the problems routinely downplayed with excuses like "it's not collecting personal data".

You claimed that personal data was a red herring. It is not. Shipping personal data is the worst possible scenario. It's unthinkable to try to make the case that a data leak is not serious because it's just personal data.

Re: JSON Hero: Enhanced JSON structure visualization

#112

Post by TeMPOraL » Tue, Nov 29, 2022, 10:42 AM UTC

simplotek wrote: post #111

TeMPOraL wrote: post #109

Earlier quoted context omitted.

I mean it the other way: I see the problems routinely downplayed with excuses like "it's not collecting personal data". See e.g. this, elsewhere in this thread: https://news.ycombinator.com/item?id=33784919 . What does the linked Microsoft page say? Quoting: > The telemetry feature doesn't collect personal data, such as usernames or email addresses. It doesn't scan your code and doesn't extract project-level data, su…

> I mean it the other way: I see the problems routinely downplayed with excuses like "it's not collecting personal data". You claimed that personal data was a red herring. It is not. Shipping personal data is the worst possible scenario. It's unthinkable to try to make the case that a data leak is not serious because it's just personal data.

> You claimed that personal data was a red herring. It is not. Shipping personal data is the worst possible scenario.

Which is exactly what makes it the red herring. Shipping personal data is one of the worst possible scenarios (I'd argue that, in corporate context, shipping data that's subject to export controls is worse, as it could easily get you fired, the company fined, and potentially land someone in jail) - which makes it a perfect distraction from all the other data that's being exfiltrated. "We're not collecting personal data" is the equivalent of putting a "doesn't contain asbestos" label on food packaging.

Re: JSON Hero: Enhanced JSON structure visualization

#113

Post by Timpy » Tue, Nov 29, 2022, 10:45 AM UTC

I get a lot of useful information from reading raw URLs, the exact thing they're advertising here is the thing I hate most about Jira. I even wrote a chrome extension that prevents Jira from loading smart links because I hate it so much. I can't imagine ever wanting a YouTube video preview while I'm skimming JSON data.

Re: JSON Hero: Enhanced JSON structure visualization

#114

Post by xigoi » Tue, Nov 29, 2022, 10:45 AM UTC

Could the examples on the main page stop switching every second so I can actually lookat them?

Re: JSON Hero: Enhanced JSON structure visualization

#115

Post by alpaca128 » Tue, Nov 29, 2022, 10:49 AM UTC

kaoD wrote: post #60

s3000 wrote: post #54

Earlier quoted context omitted.

Why does React use JSX when it could be all JavaScript and JSON? My guess is that XML is good for situations where text and data is mixed.

Named closing tags are good when manually writing stuff because it reduces the opportunity for errors.

What advantage does that have compared to simple bracket highlighting and indentation? Editors can easily highlight mismatched parentheses, they are however rarely smart enough to auto-close XML tag pairs. I just see it as unnecessary clutter.

Meanwhile the only issue I have with JSON is the lack of support for trailing commas.

Re: JSON Hero: Enhanced JSON structure visualization

#116

Post by simplotek » Tue, Nov 29, 2022, 10:50 AM UTC

TeMPOraL wrote: post #112

simplotek wrote: post #111

Earlier quoted context omitted.

> I mean it the other way: I see the problems routinely downplayed with excuses like "it's not collecting personal data". You claimed that personal data was a red herring. It is not. Shipping personal data is the worst possible scenario. It's unthinkable to try to make the case that a data leak is not serious because it's just personal data.

> You claimed that personal data was a red herring. It is not. Shipping personal data is the worst possible scenario. Which is exactly what makes it the red herring. Shipping personal data is one of the worst possible scenarios (I'd argue that, in corporate context, shipping data that's subject to export controls is worse, as it could easily get you fired, the company fined, and potentially land someone in jail) - wh…

Either you do not know what's the meaning of "red herring" or you're failing to understand the problem. Personal data is the reddest of data, even and specially in a corporate context.

You can also have more data that is red, but if your infosec policies fail to prevent or stop personal information being sent, which is the lowest of low-hanging fruits to spot, then you will assuredly be leaking more red data that is harder to spot.

It makes no sense to try to downplay the problem if leaking personal data. It's the most serious offense in any context, not only for the data but specially for what it says about the security policies in place.

Re: JSON Hero: Enhanced JSON structure visualization

#117

Post by Lariscus » Tue, Nov 29, 2022, 10:53 AM UTC

nemosaltat wrote: post #16

tfsh wrote: post #8

Earlier quoted context omitted.

Forking perfectly functional browser-based web app into Electron apps is an irritating trend with very limited benefits. Some apps exist as Electron apps because they require native OS access, this app does not, therefore there is no reason to do so. Porting to Electron would be trivial but in doing so you incur the following ramifications: - the user has yet another instance of Chromium running on their device. - th…

Interestingly enough, when I want the compartmentalization experience that comes from an “App” on macOS, I turn to… Microsoft Edge. Edge has a nifty little feature that lets you “Appify” a website. I mostly find this useful for company-required PWAs, and most-of-all, Microsoft Teams. The Edge-“Appified” MS Teams on macOS is leaps and bounds more performant than the “Native” (Electron) MS Teams apps on macOS (consumes…

Another benefit of this is that my ad-blocker still works with these apps and that you can always fall back to default browser behaviour like opening a link in a new tab.

Re: JSON Hero: Enhanced JSON structure visualization

#118

Post by orthoxerox » Tue, Nov 29, 2022, 11:01 AM UTC

KronisLV wrote: post #58

irrational wrote: post #43

The first thing I see when I go to the site: JSON SUCKS Uh... It does? I remember when XML was the main data interchange format of the web. That sucked. JSON is amazing, terrific, wonderful, etc. in comparison.

> I remember when XML was the main data interchange format of the web. That sucked. I wonder why - apart from the "Should this be an element or an attribute?" issues and oddities in various implementations, XML doesn't seem like the worst thing ever. Actually, in a web development context, I'd argue that WSDL that was used with SOAP was superior to how most people worked with REST (and how some do), since it's taken…

Namespaces. I know why they were introduced, but they still were an incredible pain to use, especially with SOAP. You want to pass a to the update method? No, it must be http://example.com/api/customers/v2"> that is wrapped in a http://www.w3.org/2003/05/soap-envelope">.

Oh, you're writing a service? You can't just XPath your way to that , because it's a namespaced , your XML parser will claim there's no in the message, you have to register your namespaces "http://example.com/api/customers/v2" and "http://www.w3.org/2003/05/soap-envelope" and look for /soap:Envelope/soap:Body/c:Customer instead.

JSON is annoyingly anal about its commas, but at least it has a single global namespace and I have never encountered a situation where I wished I could disambiguate between two different "customer" objects in my JSON payload.

Re: JSON Hero: Enhanced JSON structure visualization

#119

Post by janjones » Tue, Nov 29, 2022, 11:15 AM UTC

vincnetas wrote: post #57

rurban wrote: post #46

Earlier quoted context omitted.

jsoncrack cannot even open the simpliest of my json files (600K: too large), whilst this handled it easily.

what is the use case for having 600K (lines? bytes?) JSON? I'm a bit shocked and curious at the same time :)

machine learning datasets are often in JSON and can be arbitrarily huge

Re: JSON Hero: Enhanced JSON structure visualization

#120

Post by douglee650 » Tue, Nov 29, 2022, 11:23 AM UTC

JSON is actually a really good format, I disagree with their premise "JSON sucks". Like, sure it's got some use cases it doesn't handle well, but overall there's a reason it won.