skysight-inc/HackerNews huggingface dataset:
Re: and things are now moving towards the simplicity of how it used to be when creating desktop apps using web tech with the advantage that they're cross platform.

I suspect we'll need a new web standard that's GUI-friendly. For one, have the option of sending raw coordinates to the browser and have the (optional) layout/flow engine be on the server. That way you only have ONE layout engine instead of a different one for each browser version/brand, which is what we are really dealing with.

A. app -> server layout engine -> coordinates -> client -> screen

B. app -> markup/JS -> client -> DOM -> coordinates -> Screen

The problem with "B" is that each DOM is slightly different: different browser brands and versions. You have to test with about 50 variations to be sufficiently thorough. And as time goes on, they break more code. A more accurate diagram would fan out after "client" and have DOM1, DOM2, DOM3, DOM4, etc. Since the browser is dealing with raw coordinates in A, there fewer things to go wrong. Thin client = thin errors.

Another advantage of A is that you can choose different layout engines not bound to DOM standards and quirks. Or even have none and go WYSIWYG. (Web browsers don't really do WYSIWYG well in practice, partly because font-to-widget-size-ratios are not standardized.)

"A" is more stable. It's better factoring, period.
Yes, I am employed by PDFTron. I've been leading this project since early 2019.
This. The names of many tribes is simply "the people" in their language. You can easily read into it that those humans not that are not members of their tribe are not people.
http://www.native-languages.org/original.htm
This is a good start (and baskervald is even better) but is not of excellent quality. I am not talking about the character shapes themselves, that are OK, but about the relationship with greek characters, with LaTeX math, and the quality of accented characters. What the world needs is an available version of the "SMF Baskerville" described by Yannis Haralambous here: https://hal.archives-ouvertes.fr/hal-02101627
There is evidence that hunter gatherers would take care of extremely disabled people. What do you mean by "didn't fit into the role assigned by their tribe"? What are some references on the body of knowledge you are confidently referring to?
Also the idea that corporate legal departments are just doing nothing all the time unless they're suing people is the tech equivalent of only caring about IT when something's broken.
> I am aware there have been some revisions between gQUIC and QUIC as being prepared for standardization

I mean... are you though? Because this feels like if somebody told me they are aware there are "some changes" between "Nothing Lasts Forever" and "Die Hard". I mean, yeah, "some" -- like the "hero" cop is actually a hero because Bruce Willis didn't want to play a washed-up alcoholic nutjob whose paranoid fantasies come true... Wait that's a pretty different story isn't it?

Google was welcome to not use IETF protocols before (and sometimes they didn't) and it'll be welcome to not use IETF protocols afterwards (and likely sometimes they won't).

The IETF has no enforcement arm, it exists so that people can agree on things they all want to do. Or, they don't agree on what to do and then they do whatever they want. Lots of people want a better TCP with encryption, enhanced privacy, a way to avoid head-of-line blocking and a fold-away double bed and the QUIC working group has, starting with Google's experiment over two dozen drafts ago, been trying to build one. Some of its participant are from Google (which is great, they have some really smart guys) and of course most are not. You can and should contribute.
You are assuming a cell phone that calls in. But lots of people dial in manually from an actual telephone.
> This product is provided as a SECURE means of communication and it IS NOT.

Are you claiming that there are actual customers who believed that if they called up a Zoom conference via a phone number, their connection would be encrypted from their landline phone all the way to the other end, and were surprised to learn it was not?

> With a target in mind, you now have a goal: Find a way to convince zoom to send encrypted comms to any device within reach.

This attack has nothing to do with end-to-end encryption (i.e., it is equally possible against systems that are well-accepted as "end-to-end encryption," so if you're using this as a criterion, nothing is end-to-end encrypted.)

That doesn't mean I don't think it's a problem. That just means I think that words have meanings, and "end-to-end encrypted" is not a synonym for "secure under the threat model I care about," and never has been, for anyone.
Location: Seattle, Wa, USA
Remote: Yes
Willing To Relocate: No
Technologies: Chef, Jenkins, Kubernetes, Docker, Ruby, ELK Stack, Python
Resume/CV: https://likens.us/Scott%20Likens.pdf
Email: scott@likens.us
I have an AeroPress, a french press, and a Clever Dripper.

While I like the AeroPress, I don't find it makes enough coffee in one go. The Clever Dripper is basically a french press with a #4 filter, so you still get a filtered cup - no sludge (you do miss out on the oils though). It's a foolproof method to a great cup of coffee.
I assume there were plenty of survival challenges back then. Knowledge about farming, lack of food and clean water security, heat, natural predators, other tribes, medicine etc.
>It's like writing ultimate spaghetti code in a dynamic language.
The nature of biology is much like classes and data floating around and all seemingly randomly interacting with each other, because ultimately this is just chemistry with thousands of unique compounds, which makes things messy.

It should be noted that biological systems were one of the exlicit inspirations for extremely dynamic and object oriented languages like smalltalk.

Far from being a negative aspect the 'centerless' design and high degree of decentralization is messy, but also extremely robust.The internet as a whole is another example of a human technology that utilizes that sort of design.
So what? Including all animals in the title would make it long.

Also, this news is not that big a deal; it only goes to negate the CCP's propaganda about the source of the disease!
njnbgrwi
I would be interested in seeing it if open sourced. I used YouMail in the past and their UI really bugged me, so I was playing around with the idea of building something more modern and self hosted.
I guess what I think is absent is a recognition that Lynx is able to do what she does in part because she is a beneficiary of a history which specifically prevented others from living on the land. "Appropriation" of skills from traditional practices to me reads as a distinct harm from the very physical appropriation of actual territory.
A majority in the US will.

Edit:

maybe it's not in fashion to listen to the CDC in these times, but:

"Obesity is a serious concern because it is associated with poorer mental health outcomes, reduced quality of life, and the leading causes of death in the U.S. and worldwide, including diabetes, heart disease, stroke, and some types of cancer." [0]

Emphasis mine.

0: https://www.cdc.gov/obesity/adult/causes.html
So I watched the Cronkite stuff and it seems pretty similar to this.

https://youtu.be/VDv3_KfdBs4

So is your gripe generally applies to all contemporary journalism or specifically with CNN and Fox News? Isn't it just as likely that legacy news sources are still doing the news pretty much the way they always have but that the availability of alternative sources has allowed people to diverge their opinion from a mainstream one more than they could before? (Which I'm not saying is good or bad. I think it likely has benefits and drawbacks.)
From the website

> We’re announcing our public launch today, with a $3M seed round →

Seed rounds are now 3M, wow!

I wonder how they seemlessly authenticate with Okta, Google, Active Directory e.t.c ?
ngwibiuwrfb
The one guy i know that lives like this... his feet! oh god, do they smell. So much so, you don't notice the rest so much. You'd think being barefoot so much would air them out.
This could be read the other way too.
In my experience there is a spectrum from reckless to needlessly perfectionist, neither of which approaches are very helpful.
Being focused on delivery is not necessarily a bad thing. But then I've mostly worked in small startups, so perhaps it's different elsewhere.
If that’s what your thinking don’t say: There are really two options here.

Frankly, the US with effective leadership could have less than 1/10th your quoted 200,000 deaths, just look at South Korea. Any time someone says their are two options on a complex issue it’s a straw man argument which is what I objected to.
http://www.mawode.com/~waltman/talks/one_liners.yapc11.pdf
So, from a CS point of view, I guess instead of comparing DNA to procedurally executed machine code we should be comparing it to the source code of a set of classes, which once instantiated produces specific proteins that perform all sorts of biological tasks in our bodies.
Fair enough and technically, I think you're right that it's not a "defense" with legal precedence (and therefore not an actual defense). But, I don't think that reality stops many companies from trying to stop the use of their brand or product in other fields because they believe they're protecting the brand.

That said, this AM General case seems to be a licensing case -- they want money for the use of the of their design. To some degree, I don't blame them since Activision is profiting from their work.
Let me get this straight: Are you saying all the changes in arrow functions, the class syntax and generator functions were all a carefully planned initiative to get rid of the "function" keyword because it does too much?
Wait webrtc uses udp? Is this new? I thought there was no way to send udp packets through client side Javascript?
Not just minor sprains and hairline fractures. The fact that our body can heal from much worse injuries, shows, that it was useful back then and not necessarily a death sentence.
Instead of installing the Zoom software, join Zoom calls from within your web browser

With this trick you can join Zoom calls without ever installing the client on your computer.

Here's how to do it:

1) Uninstall the Zoom client if you have it installed (this is important).

2) When you get a Zoom link to join a meeting, click it to open it in your browser.

3) You'll be asked to download Zoom. Click the "download & run Zoom" link, but don't run the installer.

4) Wait for a few moments and a link to "join from your browser" will appear. Click this and join the call as normal. Most of the features work in this browser based version -- there is no need to ever risk your computer!

Here's a gif demoing what to click: https://assets.zoom.us/images/en-us/web/client/join-web-clie...
Yes, this is probably it. And it's scary how intelligent professionals can exist in a system of total dysfunction and in a way not recognize it. This is worth studying - how the perception reasonable authoritativeness (which is not actually authoritative) perpetuates itself in social systems, i.e. the blind leading the blind, unaware they are blind.

I worked in a Fortune 50 and recommended we 'find some smart young devs' to work on this project, they thought I was crazy, it hurt my credibility. A year later, one of our interns quit and did the same thing, almost alone, with much greater success. I shamefully admit I was looking for my 'I told you so' comeuppance, shockingly, it never happened. The system was too inept and lacking in self-awareness to see what had just happened, internalize and adapt. Nope. Just a mixture of unaware, don't care, ignored, avoid. Someone at lunch somewhere might have said 'Wow, look at what that intern did'. Of course, they almost went out of business but it's not the same for other conglomerates.
Navy fires captain who sought help for virus-stricken ship
"can" - easier said than done, especially tables.

I don't see it in the Demo. Did I miss it ?!
Experts estimated we'd be at 20k cases roughly by March 31st...we were at like 200-300k... so yeah experts don't know much either on how this will turn out. Some of the states not taking it seriously will drive numbers way up beyond experts best guesses.

Best way to guage the toll is take a glance at deaths in 2019 vs 2020 and the difference is covid-19 related. Even if it's a heart attack who couldn't get into the ER because it was full...etc..
Thank you for linking. Now I can confirm that the study is, frankly, bullshit. Ignoring the ridiculous sample size of 34, the "smells" are totally subjective. In fact one could argue in favor of each of them - this reminds me of open concept cargo culting:
Organizational Silo. Siloed
groups in the community that do
not communicate with each other,
except through one or two of their
respective members;

>1. Organizational Silo. Siloed
groups in the community that do
not communicate with each other,
except through one or two of their
respective members;

If I'm working on team A I don't need to know what literally every person on every other team is doing.

>2. Black Cloud. There is an
excessive information overload due
to the lack of structured
communication. This might lead to
a huge increase of data exchanges
across a community;

What? Lack of communication leads to excessive information? That doesn't even make sense.

>3. Lone Wolf. Unsanctioned or
defiant contributors who work in an
irrespective manner or regardless
of their team;

Where I'm from we call this initiative. I've been rewarded for showing it my entire life. This is not black and white.

>4. Radio Silence. One team member
interposes themselves into every
formal communication across two
or more sub-communities with little
or no flexibility to introduce other
parallel channels.

I don't even understand what this means.

None of the first three points are black and white, as they make them out to be. This is pure ideologically driven data mining playing off the stereotype of women being better communicators. Ironic.
Fed’s New Repo Measures Followed a $100B Treasury Exodus
Right,

- if it's an open-source client but it doesn't display fingerprints and you haven't modified it, you're stuck. (At least you know you're stuck, but you knew that already.)

- if it's an open-source client but you're trusting someone else's binary, they can attack you.

- if it's an open-source client but you're not trusting someone else's binary, you're not on the embargo list and so responsibly-disclosed bugs are effectively zero-days for you.

- if it's an open-source client but it's written in C, you have no practical way of auditing it against intentionally-malicious source code (i.e., for almost everyone, the cost of auditing it is higher than the cost of visiting your conversation partner in person).
Yup, it's been a while since I read the spec but I believe it leaves the transport up to what can be negotiated for maximum compatibility.

If you handle the SDP and SCTP handshake you can force it to only use UDP via SCTP. Chrome and FF both support it today.
I write a lot of documentation. I do it not because others ask, but because I genuinely believe it is going to be helpful to someone at some point, and anticipate this need. So when Bobby from marketing asks about a feature, or Kate the junior dev can’t wrap her head about some algorithm, hey, I got them covered!

So I think this mindset is the first thing you need in order to get going. It will inspire you to write more and better.

Secondly, my practical advice is the following:
divide your doc in sections. Plan them out beforehand by writing just titles and subtitles. See how they fit together, if their sequence makes sense. Rearrange them until they convey a clear story. Usually you might want to have three macro-sections: 1. Introduction - what is the document about, who is it indended for, and why it was developed. This helps set expectations right off the bat. You can also describe the big-picture goals of the system/feature. What is it used for. What are the main use cases.
2. System/Feature Overview: here you can describe the big-boxes architecture, the main components (apps, servers, middleware, db, whatever), what they do, and how they work together. Describe communication protocols and standards followed. Describe functionalities the system provides. You can follow up on the use cases you mentioned in part 1 and show how the system delivers them.
3. Technical Details/Implementation Choices: depending on the audience of your doc, you might want to document non-obvious design choices. This is also where might want to describe expected inputs and outputs. If it’s an API, describe the routes, accepted methods, paylods. Provide actual examples, as many as you can. Describe the data model.

Then as you follow this trace, you might find out you wrote a lot about a certain topic. Depending on the level of detail you want to achieve, break it down in smaller sub-sections, or move parts over to section 3.

As for the writing style, you might want a prose with short sentences and easy language. Make sure to explain stuff thoroughly and not take anything for granted. Everything that looks damn obvious today, won’t be 6 months from now.

Sorry if this looks like a stream-of-consciousness. It sort of is. I hope you can find some of it useful.
Interesting, I've never heard jeep used like that in the U.S. Actual jeeps are pretty common here though.
It’s perfectly acceptable to dismiss conspiracy theories that not only go against the actual narrative but against common sense.
Lifting it from one of my comments downthread:

Better to make the world's worst excuse than lie in a way that'll instantly be revealed in discovery for any case that comes of this.

The surprise is that he let himself be reached for comment at all. Between that and the "yeah, I sure goofed it, huh?" style of what he said when he was, I wouldn't be too astonished to see a golden handshake eventuate in the fullness of time.
I keep thinking of setting up something like this with Twilio as a backup... I don't trust GV to stay around forever... especially since it seems like they just stopped supporting voicemail transcription for a while (iirc over a month) and the settings and integrations seem to be left to die...

I haven't looked in a while, but running a Virtual PBX via Twilio or similar is really interesting to me... and something I'm surprised more aren't taking on, considering I've seen the amount of what providers for SIP support are charging.
Ehhh... depending on the severity, an X-Ray isn’t a bad idea to confirm that you haven’t messed something up in there.
You then have a DDOS problem
3D medical image segmentation with PyTorch
Well, capturing a 72 dpi screenshot and converting to JPEG (which more or less seems to be what you're doing) kind of makes the form filling pointless. Fillable PDF forms exist so they can be printed (or saved and then printed, which I don't think you have an option for either?)
I mean sure, that's probably exactly what all the bankers are going to say when the exact same thing happens with the economy vs a virus.
Nice talk. Somewhere in the middle I realized it was a room full of people and we don't do that anymore. How long will it be? Anyway, back to topic.

To hear him tell it, the situation is clear. And the path forward doesn't need discussion because analysis and recommendations are done. I shuddered at the insane 6 month change process story. Yet it's not that clear when you're in the middle of it. There are all these frustrations. People talk about rewriting. And a lot of things should have been completed yesterday. The tests are not written. Deployment relies on hacks you won't tell.

It helps a lot to have an outsider come in, look at the architecture, the processes, and just ask why. They say "look if you do this you'll have x, y, and z problems." And you realize that you indeed have x, y, and z. It's just always been that way. And often you understand you're stuck with it for the foreseeable future. Talking about architecture so that you know where you want to go, will allow taking incremental steps in the right direction.
Well, they seem to be better at communicating, so maybe they should be paid MORE.

But regardless, even if there’s a difference, we have to consider nature vs. nurture. I think men could be brought up to be more communicative, but that’s just me.

Furthermore, it’s absurd to say the pay gap somehow reflects different skillsets. We’re talking about unequal pay for the same work. Of course women should be paid the same as men doing the same work as they are.
It's so cool to see you in the mainstream and not hidden on teamliquid!

r1ch hwaiting!
Are there alternatives that have as simple and well documented an interface for development... considering how much some of the SIP providers I've seen charge for SMBs, I think it kind of evens out depending on usage.
This is getting dumb. Zoom is not malware.
Data decrypted when it reaches Zoom's servers, e.g., sending video directly over TLS to a webserver that then sends it to someone else over TLS.

This is what Slack, Skype, Google Hangouts, etc. do.
Has anyone taken the Stanford Compilers MOOC? Worth it?
Execute Program – Free for the Month of April
Emailing with Firebase: The Trigger Email Extension
Thanks for your feedback and your questions Adam! PDF.js Express has been in development since early 2019. We have a number of customers signed up and using it in production, and so far the feedback has been really positive. Your website looks great.
New to Cortex but when looking at a comparison of Prometheus and InfluxDB (like https://prometheus.io/docs/introduction/comparison/#promethe...) it appears that Cortex offers similar horizontal scalability features to the InfluxDB Enterprise offering. The linked comparison does note the difference between event logging and metrics recording but I am curious (choosy beggar that I am) whether others consider them separate tooling or whether it is possible to remain performant using one solution.
Having done the same kind of work - yeah, that. For every Edward Snowden, there's at least ten thousand Frank Underwoods and Michael Scotts.
Building Xbox Series X: Why Microsoft redefined the console form factor
You live on Reunion? What is that like?
You can't use the stuff you linked with TLS 1.3, and of course you can't use an older TLS version in QUIC. It's possible you knew those things, but I want to make sure.

My recent experience with the password manager that was linked on HN shows me that even an abuse-resistant API like Sodium cannot stop people being idiots. (The author believs some random passwords aren't "unique enough" so they have written a bunch of code on top of Sodium to avoid passwords like '4K2m_chmJ$gD' which they feel wouldn't be suitable because it has the letter 'm' more than once...)
Yeah, I assumed that a quality burr grinder is more important for fine grinds than coarse; I guess that's probably not true. I'll give it a shot, thanks.

I've only been using the french press more now because my home office is upstairs, and the Clever Dripper stays in the kitchen. With the press I can bring it up with me and save 4 whole minutes in my 'commute' :-)
Do you want to lose weight?
This is a commercially supported solution so the price is actually not bad ( given alternatives )
Wow. I've just done a couple of things that are very hard or next to impossible with Acrobat DC in Photopea without so much as hitch. Amazing Work!
Companies Avoid Advertising Next to Coronavirus News
Compiled list of all telemedicine companies