Tried to use this with large (650+mb) FDA drug label JSON [0] and it does not work, offers no error message etc. Bummer.
JSON Hero: Enhanced JSON structure visualization
141–150 of 203 posts
Re: JSON Hero: Enhanced JSON structure visualization
#142For those looking for the ability to (locally) open and query very large JSON files, Dadroit is great: https://dadroit.com.
It's been a while since I used it last, but it was a life saver for me when working with JSON lines files in S3 and Kafka log dumps.
A side tidbit, IIRC, it was written in Pascal.
Re: JSON Hero: Enhanced JSON structure visualization
#143My number one requirement for a tool like this is that the JSON content never leaves the machine it's on. I can only imagine the kind of personal information or proprietary internal data that has been unwittingly transmitted due to tools like this. If my objective was to gain the secrets of various worldwide entities, one of the first things I would do is set up seemingly innocent Pastebins, JSON checkers, online fil…
All those free online .PSD utilities make my spidey-sense tingle.
Re: JSON Hero: Enhanced JSON structure visualization
#144Earlier quoted context omitted.
That's only for the telemetry that happens during the install process (if I've read the link correctly). Seems quite reasonable as long as we accept them sending telemetry during install. ("A single telemetry entry is also sent by the .NET SDK installer when a successful installation happens") For telemetry during actual use, you can set that flag any time, and a message is shown on first use to inform you about it.…
> That's only for the telemetry that happens during the install process (if I've read the link correctly). Wrong. That's for the dotnet cli tool to phone home each and every time you run a command. https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... Microsoft even provides a page which showcases summaries of some of the metrics they collect from you if you don't disable this feature. These metrics even in…
> These metrics even include MAC addresses.
MAC address SHA256 hashes, to be precise.
Re: JSON Hero: Enhanced JSON structure visualization
#145It's almost 2023, are people still looking at unformatted JSON strings in their browser?
Firefox even ships with a JSON viewer enabled by default.
Re: JSON Hero: Enhanced JSON structure visualization
#146Earlier quoted context omitted.
Personal requirements aside (I have the same requirements); just using this would constitute misconduct at the very least at my place of work. Yes it's a cool looking tool, but there are certslain requirements that ignorance doesn't exempt us from. My pet gripe is all of the seemingly local (open source) tools that phone home with opt-out metrics, not mentioned in the "getting started" and take some obscure flag to d…
> My pet gripe is all of the seemingly local (open source) tools that phone home with opt-out metrics, not mentioned in the "getting started" and take some obscure flag to disable and it's just that little bit more complex to do when running the defacto (containerised) build. Exhibit A: DotNet! https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...
Well, dotnet DOES mention it in getting started (first run):
Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.
Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
HN crowd associate telemetry with privacy or cancer and the T word gives shrugs... but it is not always the case.
> Protecting your privacy is important to us. If you suspect the telemetry is collecting sensitive data or the data is being insecurely or inappropriately handled, file an issue in the dotnet/sdk repository or send an email to dotnet@microsoft.com for investigation.
Re: JSON Hero: Enhanced JSON structure visualization
#147Earlier quoted context omitted.
It's always strange to think that we went through formats like XML (and even earlier, XDR) before inventing something as seemingly simple and obvious as JSON.
> It's always strange to think that we went through formats like XML (and even earlier, XDR) before inventing something as seemingly simple and obvious as JSON. It's my understanding that JSON was not invented. It's just the necessary and sufficient parts of JavaScript to define data structures, and could be parsed/imported in a browser with a call to eval(). People who complain about JSON completely miss the whole p…
I don’t understand what you mean by JSON was not invented. It was invented by Douglas Crockford. Before he invented JSON, we used XML to pass data around the web. After he invented JSON, it took quite awhile to catch on. There were many years of transition where some web services would only send xml and others could send xml or json. Eventually all web services gave you the choice of which one it would send. And then, gradually, xml was transitioned out and everything was json.
Re: JSON Hero: Enhanced JSON structure visualization
#148How far from WSDLs and SOAP we’ve come. I applaud this effort. I hate that we’re back to where this feels necessary. I’m not sure if there’s anything better. JSON sure felt better than XML. But did we abstract too far, or did we just get so much better bandwidth and processors, that enriched data exploration is just insignificantly possible? I read the use-cases for this, but I feel like: if you’ve gone so far to whe…
> I read the use-cases for this, but I feel like: if you’ve gone so far to where this is helpful/useful, have you just gone too far? I don't understand this perspective. JSON isn't used only for RPC, even if that's what most frontend software is doing. For better or worse, it became a data serialization and interchange format - the need for such support tools arises naturally once you're generating or processing anyt…
Totally fair. I guess I was mostly considering the more typical client-server consumption, RPC-type uses and wasn’t really thinking just how much we use it for basic data interchange and serialization. Thanks.
Re: JSON Hero: Enhanced JSON structure visualization
#149Earlier quoted context omitted.
> My pet gripe is all of the seemingly local (open source) tools that phone home with opt-out metrics, not mentioned in the "getting started" and take some obscure flag to disable and it's just that little bit more complex to do when running the defacto (containerised) build. Exhibit A: DotNet! https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr...
Well, dotnet DOES mention it in getting started (first run): Telemetry --------- The .NET tools collect usage data in order to help us improve your experience. The data is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell. Read more about .NET CLI Tools telemetry: https://aka.ms/…
It sends telemetry as part of the installation, too. It is implementing a deliberately dark pattern as well. It should be an option presented right at the installer screen, _and_ should be default to opt-out.
Re: JSON Hero: Enhanced JSON structure visualization
#150Earlier quoted context omitted.
> That's only for the telemetry that happens during the install process (if I've read the link correctly). Wrong. That's for the dotnet cli tool to phone home each and every time you run a command. https://learn.microsoft.com/en-us/dotnet/core/tools/telemetr... Microsoft even provides a page which showcases summaries of some of the metrics they collect from you if you don't disable this feature. These metrics even in…
> These metrics even include MAC addresses. MAC address SHA256 hashes, to be precise.
MAC addresses are only 48-bit and sparsely allocated (i.e. the first half indentifies the vendor). I wouldn't be surprised if the hashes for all normal hardware (i.e. with known vendors) can be easily brute forced.