skysight-inc/HackerNews huggingface dataset:
I can still cancel all my subscriptions on iOS services in one place, very easily, all the same way. I still only have to trust one big, reasonably competent & responsible entity with my money when making a purchase decision, rather than trying to evaluate things on a case-by-case basis with every little two-person indie development shop. I don't have to figure out a different checkout flow for every app or service I buy on iOS. There aren't even two of them! Just one. Consistent, fast, and I trust it (well enough).

Apple's overall ecosystem still does a lot to make people feel comfortable & safe saying "yes" to a purchase and installing some software from a developer they've never heard of, even if the curation and presentation could be a lot better (but would just invite more waves of "waaaaah Apple won't let my derivative, inferior, somewhat-scammy app in the store, it's so unfair!" posts on HN, to great acclaim)
Fine-tune GPT3 language model and gain a competitive advantage
Amazon is burning through workers like matchsticks. Close to no more matches.
> These are all features that primarily have value for repos that push the limits on size, like big monorepos (with a huge amount of files) or game development (with big asset files). But get it right, and you could massively cut down the time it takes to check out a branch and build it.

Would this be a good fit for large machine learning data sets?

Every time a new model comes out that touts having been trained on something like a quarter of a billion images, I ask myself "how the heck does someone manage and version a pile like that?"
Is it? I'm working for a small company and even at our scale, when the workflow is centralized, I find git a bit painful at times. I mean it's still an amazing tool, don't get me wrong, but when you have to deal with several sub-projects that you have to keep in sync and need to evolve together, I find that it gets messy real fast.

I think the core issue with git is that the submodule thing is obviously an afterthought that's cobbled together on top of the preexisting SCM instead of something that was taken into account from the start. It's better than nothing, but it's probably the one aspect of git that sometimes makes me long for SVN.

At the scale of something like Facebook you'd either have to pay a team to implement and support your split repo framework, or you'd have to pay a team to implement and support your monorepo framework. I don't have enough experience with such large codebases to claim expertise, but I would probably go for a monorepo as well based on my personal experience. Seems like the most straightforward, flexible and easier to scale approach.
Closed end bond funds - but their price hasn't been stable lately due to pricing in expected rate increases.
Why wouldn't it be great for other companies that run a monorepo? Would it be nuts to go from some other monorepo (like Subversion) to this?
I made a mac tool to do this for both web pages and files. Every time I mention it's name on HN, my account gets deleted. Sigh!
Reminds me of a teacher I know in a small town. Their school lost their sole librarian and the library was closed. The teacher volunteered to run the library so it could stay open. Union says it's not allowed, library stays closed.
Git usage for most developer is 3-4 commands or once in a blue moon when they fuck up badly save a copy of your changes and reset hard. There aren't enough user interface improvements possible to get people to switch.
(a) most people in the USA live in a region without adequate mass transit and thus needs cars to do useful things like keeping a job or shopping at the grocery store.

(B) did the Wall Street journal article also talk about the effects of the chip shortage and the subsequent new car shortage that hit last summer? If not, it is willfully misleading.

(C) another hint on where all that money went is the increase in fuel costs, rent costs, and food costs. The increased demand is exacerbated by the supply chain troubles including the decrease in US oil wells provoked by Biden's war on American-sourced fossil fuels.
You need good tooling to work with large monorepos, you need good tooling to work with large multirepos. Neither option is easy at that scale.
Disagree. We need to stop trying to cram meaning into phrases that are already defined. Open source means the source code is freely available. Adding anything else requires a different name.
As I wrote at the top of my comment. "I agree with you that react is definitely open source" (and no, I did not edit that in, it was there when you read it)

I'm aware react is licensed under the MIT license. I was just talking about how the parent comment chose to define "open source".
Scary for consumers
No idea how mullvad setup is done, but in theory I think you could use Tor -> mullvad wireguard configured VPN -> target site.

That way your traffic would be "legitimized" (no infernal Captcha loops), and if the sites you visit have certificate pinning mullvad network compromise wouldn't matter.

A bunch of ifs, but that's the state of things.

edit: written before thinking out all the details, probably can't tunnel udp connections over Tor.
> spent on useful things like food or invested

There are a lot of people for whom a used car is much more useful than bonds, shares of a company, etc.
That's certainly what I would do. I think its great that thttpd does not include a TLS dependency itself. Every once in awhile I find a project that forces their own TLS and its annoying to undo it.
What are the legal implications of having registered on this forum once with a personal email account but not having ever engaged in any transaction or downloading any leaked data, just lurking a few threads of nothing interesting at most.

Asking for a friend, of course...
No but you need a social security number and to be a US resident
Microsoft used their own fork of Perforce for a long time. Not sure what they use today.
There should be a comparison system based on genre, by the best ever, this year, and this decade.

Format would be something like:

Compared to the best 10/10 all-time movie of the Genre, Movie A, Movie X is a 7/10. Compared to the other movies of the genre in the last year, Movie X gets a 8.5/10. Compared to the other movies of the genre this decade, Movie X gets a 7.75/10. Final verdict, 7.75/10, if you like movies in this genre you will probably enjoy Movie X.
Gridware | Walnut Creek, CA | On-site | Full-time

Gridware (https://www.gridware.io) is a well-funded ($5.3M raised from major investors such as YC, True Ventures, 50Y) startup solving the wildfire and grid reliability crises in America. Our technology stretches from silicon to servers, and rides the cutting edge at every level of the stack. At Gridware, you'll own significant portions of the hardware, firmware, software, or data system, tackle very difficult but rewarding technical challenges, and make engineering decisions that directly impact the core product's design. If this sounds like your jam, drop me your resume at hallchen{at}gridware.io:

* Senior Backend Engineer: https://apply.workable.com/gridware/j/B646CE3278/

* Senior Embedded Software Engineer: https://apply.workable.com/gridware/j/263F3E415F/

* Embedded Hardware (Electrical) Engineer: https://apply.workable.com/gridware/j/196639314B/

* Data Scientist: https://apply.workable.com/gridware/j/0D54FE7D22/

Curious about our technology, but don't see an open position that matches your interests? Feel free to contact us directly, and let's talk!

Past Press Releases:

* https://techcrunch.com/2021/02/17/gridware-is-building-early...

* https://techcrunch.com/2021/05/24/gridware-seed/

* https://cleantechnica.com/2021/06/01/gridware-raises-5-3-mil...
So I'm pretty sure this is the technology revolution that we're all sleeping on.

Like, self-driving cars? VR? Meh.

Accessible programming? A safe environment for folks close to a business problem that lets them solve that business problem on their own?! That's cool.

Like for me, in my experience as a software engineer, there's basically four types of employees: The tech-naive domain expert, the tech-friendly domain expert, junior coders, and senior engineers.

The two ends of the spectrum should stay focused on they're good at: Doing business stuff, or coding on tough problems.

It's the two roles in the middle that interest me: Tech-friendly domain experts and junior coders.

Right now, in most companies, tech-friendly domain experts could totally figure out a tool like Zapier and do things that they'd normally need an engineer to do. But their company doesn't use something like Zapier, so they can't. They just have to talk to technical people and make them do it. But there lies long debugging loops and, just, slowness.

In some companies though, those that have embraced low-code platforms like Tray or Zapier or the product we made (https://docs.middle.app), they've enabled their tech-friendly domain experts to do tons of stuff they couldn't do before, without bothering people like myself, a more senior coder (I can work on platform things!).

ALSO, I've found that junior coders have a special role. We've hired non-programmers and taught them Python JUST so they could code new things in the developer side of our integration platform. It's a sandboxed environment with limited risk; they can go crazy coding whatever connectors or other things that those tech-friendly domain experts need. I don't have to be involved, outside of a code review every now and then. I know that they can't break anything other than the narrow thing they're working on.

It's neat. Neat stuff.
Python QT5 user here. I'm yet to find a better / faster way to build an interactive GUI for a simple desktop application for Python.

That said, I still hate trying to do basic stuff with Qt, for example using slots. Example: im calling an external script or process that could take 30 seconds to run. I'm doing this 50 times and using thread pooling to manage those workers. Try issuing an update to a widget to let the user know that its progressing. The slot setup barely makes sense, is a pain in the arse to understand, and I've not managed to do it successfully yet. The issue here is, its the main way of doing things and its a nebulous, poorly articulated concept in almost every bit of doc or guide, and very difficult to implement between the Designer and code of an existing application.
Great convo, thought I'd share some valuable zaps I've used over the last few years to save $$$ on headcount, dev time, and burn/debt on unproven ideas/experiments.

- Slack - pipe all kinds of events into special #channels to cross teams can check one spot for external happenings: new users, new sales, support chats, form/data submissions

- Forms > CRM/Sheets - shouldn't be understated. Using lead page or no-code CRM (webflow my fave) I've swapped out various signup flows to test ideas/friction/followups repeatedly before asking dev to build actual signup flows into the backend app. Can swap paperform, typeform, mailchimp, google forms in under an hour for multiple signup/landing pages w/o any devs.

- Calendar - I use Motion (similar to Calendly) across sales team to speed up meeting flows + use Zaps to pipe those bookings into sheets/Slack/CRM or EMS. Sales team calendars can be public on marketing site (webflow) and bookings generate all the alerts and data we need to just show up to the meetings.

- Leverage SMS channel - One-click surveys, recurring survey campaigns using SimpleTexting or YesInsights and piping results wherever I need 'em. Google Sheet with charted dashboards already set up to auto-update. Great for ecomm, great for call/response feature testing with zero dev required. Can add phone signups via form integration or email campaign.

- Manual issue / todo alerts: Use specific tag in Asana to pipe a ticket into Slack channel when team member wants to surface for manager/teammate - instead of asana firehose

- Light @mention feed - Pipe brand mentions/topics, including web (reddit etc - use F5bot) into sheet or #channel for marketing eyes to check daily

- Twitter bot - built @carryonbagsizes using just Zaps: anyone tweets airline name and gets carry-on bag size restrictions back from the bot (including variations on airline names ie United vs United Airlines)
Yup, honestly Twitter and Snap will be fine. What will totally go out of business is Meta. Instagram is the last stronghold for Meta and any teenager I speak to are more excited about Tiktok than Instagram.
You joke but I bet whatever software unions use to track member dues and involvement is in dire need of a 2022 upgrade. Everything from soliciting donations, text chains, to coordinating work stoppages. And charging SaaS-style per member makes perfect sense.
You're writing this just as "Everything Everywhere All at Once" is doing awesome in theatres.
And they'll promise not to peak, but with AWS-managed keys ;)
If you are taking a truncated SVD, the math says that it is the best representation of that data for a given truncation size, and will even give you a measure of how good that representation is. But picking how good you need often ends up being a kind of annoying and fuzzy heuristic thing. In addition, some data just gives you better singular values, and so fundamentally compresses better.

I guess the brain probably is dealing (in a hugely non-mathematical way -- it is just an analogy!) with a similar sort of thing. Somehow we pick some memories to keep in great detail -- either because they seem to be very valuable, or because they just seem to compress nicely.

It is a bit funny that one name for this sort of thing is a "singular experience."
That's fair! And I'm sure I'd stick with an Urushi, too, but my Decimo serves me well enough that I haven't felt the need for more pens of late. Maybe once I have a nice mid-century modern desk, and a big corner office, and while we're dreaming perhaps a pony... :D

I will say, speaking of flexes, I meant the word yesterday in the vernacular sense, but now I'm wondering if a quill might be a better option for a really flexible nib than any of the metal ones I've tried. "Cheap or good, pick one," and I'm always so terrified I'll wreck an expensive nib with what seems like flagrantly excessive pressure that I've never brought myself to the point of actually buying one. Goose feathers aren't too hard to come by, though, and I already know how to whittle and carve...
ok, so previously Google Drive used hard link equivalents and now they're using soft-link equivalents?

thanks!
I enjoy most projects that I work on. Recently I worked on some graph merging algorithm that was pretty fun. I am also working on a parser generator on my sparse time. Before that I worked on some database query planner.
Unlimited PTO is an expense savings measure so that HR doesn't have to pay out your unused sick time or vacation time when you leave the company.

It sounds good on paper, but it benefits the company, not you.
I had to get pretty stern with their recruiters to get it to stop. I was getting contacted at least once a month for a while, and it was getting close to once a week. I had to ask several different recruiters to get put on their "no contact" list, but what finally worked was mentioning the email alias of the previous recruiter who I had asked. My email ended with this:

> The recruiter who contacted me last week (John Doe, jdoe [not the actual name, obviously]) said he would do that, and that is clearly not the case. I'm finding these persistent emails rather obnoxious.

It's now been almost 3 months, and I'm very glad for the reduced spam.
According to TFA, about 1/3. With a minute's thought it occurs to me this may be the expected result for two reasons:

1. "Warehouse Work" as an industry represents a wide variety of dissimilar activities. Amazon warehouse work is obviously heavily skewed toward manually sorting, stocking, picking, packing and loading massive numbers of individual irregularly-sized small and medium parcels. This kind of activity would be more injury prone compared to warehousing consistently-sized units which lends itself to mechanization.

For example, I knew a guy who worked in the regional distribution warehouse for a furniture distributor. He basically drove a forklift every day unloading boxed sofas and recliners out of containers and onto palettes. They had safety zones marked on the floor where no one not in a forklift was permitted while forklifts were moving. Dude basically sat on an extra cushy memory foam seat surrounded by a full cage and roll bars. He and his mates were proud of their ability to coordinate and position their forklifts as precisely as synchronized ballerinas.

2. "Warehouse Workers" are not a homogeneous population. I've known some "professional" warehouse workers in the sense that they did it as a career. They tended to be "built for the job" both physically and in attitude. I've also met some Amazon warehouse workers and every one of them viewed it as a temporary gig on the way to something else and usually for a short-term (3 to 6 months). None of the ones I met seemed especially suited physically or temperamentally for repetitive warehouse work.

Without these obvious differences controlled for in the stats, the headline claim of TFA seems about what I'd expect. I'd be much more interested in a comparison with a population of non-Amazon warehouse workers who are equally short-term and who also do similar manual sorting, stocking, picking, packing and loading of individual irregularly-sized small/medium parcels.
Thanks!

> I guess a useful side effect of running this is that it will be super obvious when the docs contain broken code!

Yes! One of the things we've learned is that companies are building very complicated in-house systems to make sure their docs code snippets are runnable. With Devbook, you could just start a Devbook VM from you CI/CD pipeline and run all the code snippets in the same environment your users will get when they visit your docs.

> How are errors handled? Am I able to see errors that my customers raised while interacting with the docs?

That's what we are exploring right now. We are building a dashboard that would give you an overview of what is happening with your docs code snippets and give you better understanding if developers are struggling with your docs and API/SDK.
Sure, if all you need to know is "can this user login" and you don't have multiple servers that want to authorize the user, you probably don't need OAuth. You can use sessions and cookies. See my comment elsewhere in this post about this: https://news.ycombinator.com/item?id=31007003

Interestingly, your first scenario is the resource owner password credentials grant: https://datatracker.ietf.org/doc/html/rfc6749#section-4.3

The second scenario is, I believe, the JWT bearer grant: https://www.rfc-editor.org/rfc/rfc7523

Of course in the OAuth grants, the auth-server returns a token to be presented to other resources instead of a "yes" or "no" answer.
Your risk assessment may or may not be correct, but that's irrelevant to the point that rights should not depend on wealth. Either something should be legal for all to trade or none: not based on wealth.
One thing to keep in mind is that the I Bond rates will go way back down once inflation does. So it's great as an inflation hedge, but other assets will almost certainly out perform them in the long run.

Still worth getting the yearly $10k though.
Metro Bank has a great feature for transfer amounts. When you type an amount, commas are added automatically.

However, if you paste a number with commas in it, it will display correctly, but on the next screen you will discover it is transferring a different amount, as if it parsed the number up to the first comma.

(As an aside, this is one of the underrated things about best-practice React: that kind of bug can never ever happen. What is displayed is fixed by the rendering of the data model, never the other way around.)
1500 bytes isn't even enough to send a list of video titles and thumbnail images for a single page of videos.

If you imagine that the client already has a full database of all the available videos and metadata about them, then you could get by with tiny amounts of data, but that's not even close to the actual circumstances that Netflix operates under.
> it's a mixed bag like every other Megacorp

No, you can't simply dismiss the fundamental problems with Facebook/Meta with whataboutism. Google and Apple and Microsoft are standard mixed bags. Not Facebook.

Facebook is pure evil. It has queued up the complete obliteration of western democracy, which even Rupert Murdoch couldn't quite manage on his own. You can absolutely find non-directly-evil things to at Facebook/Meta, but it all supports the evil in the end.

https://www.theatlantic.com/magazine/archive/2022/05/social-...
I do it all the time and have been doing it as long as I can remember. I couldn't tell you why, but as others have pointed out it annoys the crap out of people when they're trying to read with me.
Your sentiments and questions are all perfectly valid. I believe the majority of developers implementing oauth2 on their servers or integrating another service they need oauth2 for have not fully understood what they are doing. I know that's the case for me and I successfully implemented solutions for OIDC, saml, three-legged oauth2 and two-legged oauth2 on both the server and client. It's all an overengineered mess.

A "complete guide" to this is still sorely lacking -maybe because it just is that complicated and can not be dumbed down?
My first impression of this sort of survey is → "define: crisis." I'm not even sure how I would answer this survey without some definitional clarity, and I'm probably one of the most cautious people around.
No. There is a reason you are limited to $10k a year. I bonds are not a financial product being sold for the benefit of the seller. They are a government service being provided for the benefit of the buyer.
This is good. I believe unions have less value in mature industries where the things the unions generally wanted are baked in, and they drive inefficiency in hiring and have fundamental control over some operational aspects. Auto industry is a bit of an example, likewise the public sector.

But where there are 'new games', with no historical labour power, they are often desperately needed.

Amazon, Walmart and the entire 'gig economy', fast food / service workers need unions.

In 20 years, when regulatory issues have caught up around the 'gig economy' they may be less needed.

A lot of the food / service economy issues could be resolved just with a good minimum wage and some basic regulations around scheduling, healthcare etc. but the US isn't there yet. So 'unions'.
I agree amazon warehouses are one of the best use cases for unionization, but I also believe there is almost nowhere unionization doesn't make sense. Collective bargaining makes sense wherever there is a collective that is being exploited AKA wherever employment is happening in which the means of production aren't entirely controlled by the workforce.
Too good to rent in East Palo Alto?
Or using it as your emergency fund. Just keeping in mind that you should probably ladder your emergency fund into them, since they're locked up for 1 year.
I switched from Dropbox to Nextcloud, and within a couple of months from Nextcloud to Google Drive. Really didn't like the software and it was so slow since I wasn't self-hosting it, but renting it from Hetzner.

Currently thinking of switching from Google Drive to Syncthing, since the new Google Drive clients suck and Google is going to be making my service worse with the new G Suite changes.