skysight-inc/HackerNews huggingface dataset:
You might not have noticed, but check for the button called "Extra Dim" in your Samsung top area quick controls. It's not enabled by default but allows toggling additional dimming. You can customise it in settings to control the level of dimming, adding a a screen or key shortcut, and control whether it activates on phone reboot or not.
Key shortcut (or deactivate on reboot) can be helpful if you set it way up, and have adaptive brightness off, and it is a sunny day.

(oh, and yeah, it does work nicely with B&W mode and blue light filter modes - all 3 are quite helpful for reading in bed without staying up too late)
1) - US lawmakers believe

2) - Mostly yes

3) - both

Which one of 3?
This web page tells me they really don't want you to read the license.

https://commission.europa.eu/content/european-union-public-l...

You have to go to a list of languages, and then once you find English on the list it gives you a PDF or text, no HTML version.

I read it, and I think the exception allowing for compatibility with the MPL would allow me to pretty much do what I want with a larger work, as long as I release changes to the code files, and shipped it with some MPL code. It says that where the license conflicts, the compatible license prevails. I'm also not convinced that the Distribution section behaves like the AGPL: https://opensource.stackexchange.com/a/12298
The US is not attempting to base nuclear weapons on Taiwan, so the comparison with Cuba does not stand up.

US moves can be both logical and rational in terms of power projection, and defend the innocent people of Taiwan. As a trading power, wanting to trade fairly and securely around the world with independent nations (ok so that is a bit of a stretch), it should be no surprise, and indeed quite gratifying that those two aims coincide.

US foriegn policy is not to create an empire, but to prevent others from doing so (USSR, and now China). Don't try to create empires, don't get the foot!
I do think it was important for duckdb to put out a new version of the results as the earlier version of that benchmark [1] went dormant with a very old version of duckdb with very bad performance, especially against polars.

[1] https://h2oai.github.io/db-benchmark/
Assistants API Overview
OpenAI launches GPT-4 Turbo and launches fine-tuning program for GPT-4
Every time Elm comes up people climb out of the woodwork to cast aspersions on it for no better reason than that Evan wants to run his project his way. Some people evidently just can't accept that and have sustained a grudge that drives them to comment on it whenever it comes up.

Look, I get it, I'm still sore about Google Feed Reader, 'member that?

But enough is enough. It's old news. Get over it. Etc.

It's like if every time someone mentioned Caddy server there was someone bringing up that time Matt Holt put that header in and pissed off a bunch of people. Life goes on. We forgive and let things go.

It's high time for folks to forgive Evan for his mistakes. I mean, he's very young still, eh? Cut the guy some slack already?
Fixing the option takes time and expertise, as well as an idea of what users actually are trying to do.

If you don't give feedback to developers, how do you expect them to know you wanted to use the option?

Better to remove a broken feature than let users burn hours futilely trying to make it work.
Yes. I think I’m in a rarely lucky situation where my employer lets me save my holiday and sandwich it around the Xmas shutdown so I end up with a month off at the end of every year
at the same time it's very hard to monetize GPT4 because the cost are so high
I don't like the idea proposed in this article of labelling artists. Art is too subjective to adhere to these labels. It also pushes a 'us/them' narrative, "The Rest of Us." For better or worse, artists are just regular people. Maybe applying this to pieces of art, like a song, painting, essay, play, video game, etc, could work.
In the bad old days, you literally had to write your code by hand in an IDE and not just imagine what you wanted and have it written, deployed and executed for you. People used to go to school to learn how to write algorithms and then they actually got paid to do this all day. How did people deal with that?

- People, circa 2095
I'm assuming you're familiar with Wayfair vs. South Dakota?
In Sweden it’s customary to get 25-40 days of vacation per year based on seniority, public vs private employers and other benefits.
It has its pros and cons, and it depends on your employer. Your employer generally has to approve PTO even on a PTO plan that tracks hours. If you don't trust your employer to honor a reasonable PTO policy - unlimited or otherwise - then you should get a new job because there's probably lots of other problems.

I've been able to take blocks as long a 3 weeks off at an employer with an unlimited PTO policy, because I worked hard when I was there and my manager and I were on the same page. I told them when I was going and how long for, and they said nice, have fun.

Etiquette was to give at least 2x as much notice as the duration of the PTO. If you're going to take 3 weeks off give at least 6 weeks notice.
Not in USA, but here I can by law take 4 weeks, not necessarily in one go, but it is more rare to split it up. And my bosses would not have any issues with that.
OpenAI API "JSON Mode"
My experience in the USA - yes, this unwritten rule exists. Or maybe I've only worked in places that are too small (or too disorganized) to provide coverage for longer intervals?

I've only taken greater-than-two-week intervals off /between/ jobs.
Agree strongly, it's nice in theory to view the intermediate commits but in practice have never needed to look at them
Your employer has the right to tell you how long you can take vacation for.

But she is lying when she says that it's convention to not take longer than 2 weeks off consecutively.
A clean history is one where there is a single commit, "big feature commit", that produces a worktree that is the same as the one produced by "fix 3" in the "unclean" history.
I'm not even sure the poster you're responding to is correct on a technical level.

My understanding (possibly flawed) is that github started by using the current git tooling but that they soon started running into issues because the CLI tools were never meant to scale and never as a web application.

So they wrote their own implementation of git (their own tool that understands git repositories) but did so in a way that's more compatible with the scale and the web-oriented work they do.

So it's not even clear to me how much of the actual code they have running is open source.
Normal ChatGPT. I asked it a question about the Soviet Union, and the response was lengthy
I think squash merges are a last resort heavy-handed tool for dealing with developers who refuse to clean up their commit history before merging. Most developers can do better by hand.

This is too much thought put into a VCS. I don’t want to have to think about my VCS at all beyond the commit message. For all of Git’s popularity, I’ve never seen benefits that justify the absurd amount of work and knowledge it takes to perform simple actions. It’s the VCS equivalent of Scheme or emacs.
I think these benchmarks are great, but also quite misleading and should be updated:

* the 1 billion row benchmarks are run on a single, uncompressed 50 GB CSV file. 50 GB should be stored in multiple files.

* the benchmarks only show the query runtime once the data has been persisted in memory. They should also show how long it takes to persist the data in memory. If query_engine_A takes 5 mins to persist in memory & 10 seconds to run the query and query_engine_B takes 2 mins to persist in memory & 20 seconds to run the query, then the amount of time to persist the data is highly relevant.

* benchmarks should also show results when the data isn't persisted in memory.

* Using a Parquet file with column pruning would make a lot more sense than a huge CSV file. The groupby dataset has 9 columns and some of the queries only require 3 columns. Needlessly persisting 6 columns in memory is really misleading for some engines.

* Seems like some of the engines have queries that are more optimized than others. Some have explicitly casted columns as int32 and presumably others are int64. The queries should be apples:apples across engines.

* Some engines are parallel and lazy. "Running" some of these queries is hard because lazy engines don't want to do work unless they have to. The authors have forced some of these queries to run by persisting in memory, which is another step, so that should be investigated.

* There are obvious missing query types like filtering and "compound queries" like filter, join, then aggregate.

I like these benchmarks a lot and use the h2o datasets locally all the time, but the methodology really needs to be modernized. At the bottom you can see "Benchmark run took around 105.3 hours." This is way to slow and there are some obvious fixes that'll make the results more useful for the data community.
It’s the sort of thing an engineering team builds when they have way too much time and no idea what to build. There is zero reason to use something like this over, say Jupyter notebooks and the advantages of notebook are obvious: actual researchers are already familiar with it, you can integrate everything into your data science workflow, visualise results etc
Just a thought, what about a dummy/honeypot path in robots.txt? If any request is made related to that path, block connections from that source?
I love the increased focus on benchmark testing recently, but I always find it a little weird to read for stuff like spark or dask.

Those are written to offer scale over large data so have very different overheads and limits compared to something like duckdb. Seems odd to have them on the same chart.

Also, side note but I'd love to see the performance impact of pandas/dask with pyarrow schemas.
Building tools or products is clearly an investment
If you think the mess (i.e. 50 mixed up mini commits as you work on a feature and iterate on it) is useful history (it usually isn't) then use a different DVCS because git was not designed around this mode of operation and a lot of its advanced features work poorly when applied to such a history.

Alternative DVCSes which support this workflow include: fossil
This is unbelievable nonsense.

Your employees accrue PTO. If you can't handle them using their PTO, maybe you shouldn't have employees.

If three consecutive weeks is a lot to ask, what would you do when that same employee gets hit by a bus and is dead for even longer?

Oh right, you'd just replace them and the business would move on.

OP, this is the real answer to your question. The business doesn't care about you or your well being.
The only "rule" around vacation is the longer the vacation the more notice you _should_ give. I've had colleagues take 5-6 weeks off, but they let the team know 4-5 months in advance so it wasn't a big deal and we could work around it.
Cloudflare issues Nov 4-6
Continuing issues from the recent outage; DNS updates are hours behind.
Atlassian Confluence data-wiping vulnerability being actively exploited
I believe that you are confusing "full history" and "true history".

Every single point in the commit history represents an actual state of a repository at a specific point of time, along with the information of which point or points were next before it. This is all part of the true history.

This is not a full history - you don't have every keystroke, abandoned commit, switch between branches and so on. But nothing that you're being told is wrong.

As soon as you do a rebase, you're rewriting history. You're claiming that there were specific points of time with specific states that never actually existed. You're losing information about points of time and specific states that actually existed, which someone once considered important enough to do a git commit over.

The difference becomes important if that someone, which at a previous job was me far more often than I would like, tries to go back to the historical commit. And finds that it is gone without a trace.
Is this based on any of Jean Giraud/Moebius's work?
I am not sure what you mean, but when I responded it was a single commet, no replies.
I pay for YouTube Premium already. And I would rather pay directly to Google for other services from them that I use. For E-Mail, search and browsers there are excellent alternatives to Google, so I don't know what else except YouTube that would be interesting from their offerings. Although it's easy to forget, considering the thousands of projects they have.
One of my favorite things about Debian's approach is that it provides immunity to the left-pad problem.
> Every card reader/lineprinter station had an operator to deal with the inevitable jams and other problems

on my campus in the late 90s there was an old lab with unix stations in it ( can't remember what they were) that nobody went to. I always ended up in that lab because it was quiet and the workstations worked just fine for me. They had these extremely high speed printers in there that were very large and under glass. I was playing around and did something.. i can't remember what maybe sent a binary to the printers or something... they took off and went crazy and caused lots of headaches.

I had the nickname "dammitchad" in some of the labs because "dammit chad, quit screwing stuff up" was a pretty common phrase. I was one of the "other problems" you mention haha.
It only needs to stop blowing for a week for your 8h battery to result in blackouts. And that happens almost every year.
I think if the definition of a “good history” is “clean and not messy”, then yes I agree that’s pointless. If the definition is “a clear ability to see what changes were made, by who, and most importantly why” I think that’s incredibly necessary and would even go so far as to say it’s naive at best to not support.

The amount of time that has been saved in my life by someone leaving an explanation in their commit (for some weird edge case or context I’d have no way of gleaning because they’ve since left the company) is SO much more than the extra time I’ve put in to make sure the history has this extra info in it.
I think there is an understanding that more than two consecutive weeks has a bigger impact on peers than less. As much as I dislike it, I have to say “yes” that the bar is higher at two weeks. It’s not a prohibition, but a checkpoint perhaps?
Seriously, I think my printer has an update every week or two.

What even is it doing? It printed before the update and keeps printing after the update
Be aware that you are privileged to be able to expose your identity; i.e. be non-anonymous. There are quite a lot of people for whom anonymity is crucial: <https://geekfeminism.fandom.com/wiki/Who_is_harmed_by_a_%22R...>
They are. Or at least can be. Typos I probably agree with, but I've seen plenty of logic bugs introduced in those "fix" commits and keeping them separate from the big one is useful when figuring out what was supposed to happen.
How is this comparison remotely similar? In the NBA you’re not allowed to break the rules. You’ll be promptly fired. Is the US govt going to shut down Tesla for turning down taxpayer money?

But I get what you’re ultimately saying, which is what I said — it would be a competitive disadvantage to Tesla if it turned down this money and its competitors did not. So it may accept it reluctantly while disagreeing with the overall handout. Again I have not heard that take from Musk. He just rails against the government.
How big is the startup? This conversation is going to be quite different at a company with 3 employees vs a company with 3000.
I absolutely don't think it's a laughing matter. I made a joke in the interview with the reporter as a kind of icebreaker (which clearly didn't seem to go well).

But as I also explained after doing that, "I’m pretty sure, went into what I thought was a more serious and thoughtful discussion, at least from my perspective."

I don't think making a joke about something is the same as someone then thinking an entire matter isn't serious. But I can appreciate you disagree.
My second co-op job was at a place that had mostly transitioned from punch cards but they still had a couple of hold outs. They wrote Fortran on special columned paper and then the keypunch operator would punch out the cards and the programmer would review the code. The keypunch operator would occasionally catch a typo and fix.

While I was there, the programmers started reviewing their code on the CRT and the keypunch operator was typing out the code instead.

By my second work term, one had retired along with the key punch operator and that was the end of that era.
Agreed. Maybe some are not as sensitive to this, but it is a major energy suck for me. A little post-processing on noise and compression would come a long way. This recording is as raw as the Ramsey meme.
Location: Latam

Remote: Yes

Willing to relocate: No

Technologies: React, Vue, Express/Node, Mongo, Mysql, AWS,
Laravel/PHP, Jest, Cypress

Email:me+hn @ segoviacristian dot com

Rate: 40 usd hour(willing to negotiate)

Have 5 years of experience working at US based startups and small companies. Looking for full stack roles with a bit of AWS(or more), though open to frontend or backend roles as well.
> You send a hoodlum to beat them up?

That, or some form of it, has traditionally been the method. Its only slightly different from the "legal" world, where you take them to court, and the court sends some one (the police) to enforce the courts decisions. Just in that case you have an (hopefully independent) third party to go through. Some more sophisticated criminal organizations actually have similar arbitration processes.
All of this talk about testing and labeling doesn't make sense to me or likely any layperson. I don't want to have to know what capabilities a cable needs and then compare it to a label and I really don't want to have to test a cable to see if it will work for my intended use case.

I want to be able to grab any USB cable and have it work regardless of my intended use. If that is impossible because the standard is so complex then we really should have different connectors. The entire point of it being universal is that regardless of circumstance it will work. Somehow that has morphed into the connector being universal while the actual utility of each cable is not; the latter of which is the only thing people really care about.
The benefit you get from code that is useful for along time is that it’s useful, for a long time.
Ye. Like trying to do a hard reboot on a MacBook Air, but at 70 mph and going faster ...

Or a hacker setting steeringWheelGain_S16 to 0 and turn full left.
Increased competiton is likely more the cause of cheaper GPT-4 than infrastructure improvements.
[Another try in case this is the type of answer you wanted.]

In Racket the batteries are included. Two examples of programs I had to write like two years ago for work:

* A bot to reply emails that uses IMAP, SMTP and web scrapping. (It's not 100% automatic. It replies only the easy cases and adds labels so I reply the tricky ones.)

* An program to cleanup Moodle backups that uses gzip and xml. I compiled it and send it to my coworkers. (The backups have too much info, so before restoring it in another site it's better to remove the unused parts.)

In both cases, and all the features were installed by default. There are many user defined libraries that can be downloaded as packages, but I didn't need to use them.
I personally was hoping for a 129k context window
I don't think you want your boss to replace you when you go on vacation.
Please, Expose Your RSS
GPT-4V API Docs
Reminds me of those "alternative" bittorrent clients that did neat things by, basically, behaving in selfish ways.

The main example behavior I remember was that these clients would sort of cheat by downloading the file chunks in sequential order (so they could start playing the media sooner) rather than in random order (which is a big part of what makes bittorrent a pretty effective protocol/algorithm)
I have 30 days of vacation in my contract and I am free to use them whenever I want. It is also backed with the legal right to 4 weeks of consecutive vacation during Jun-Aug, a right that the employer cannot deny.
Of course I live in Scandinavia. Sweden to be precise.
Kagi (www.kagi.com) is on an early stage, however I wouldn't say they are trying, since they have already beat Google with a large margin on search quality.
Sorry, just to clarify, arbitration isn't a new concept or one that would need implementation - it has always been an option for any legal dispute. In fact a lot of divorces go through a mediator instead of a judge since the difference in cost is so extreme.
Would you mind posting a screenshot of your phone screentime? Just curious
Reminder that the OP has a whole HN-style site for retro:

https://twostopbits.com/news
300 pages of context. Way ahead.
Yes that is all making software
what color is that bike shed ? /s
The OP doesn't indicate how much vacation time they've accrued. Perhaps they get "unlimited" PTO, which makes things murky.
how often is "understanding your project history" something that actually comes up for you? In all my years of working with projects in git, I will occasionally look at my history to help me find a change that may have led to a bug, but it really only comes up for me once or twice a year and even then, it is rarely an extensive deep dive and never very far back in time.
And the result of that preparation is that both sides are less entangled with one another and thus (theoretically) more ready to be at war with one another.

Anyway, the chain of who-started-it doesn't have a first link. There is no value-free way to assess it all..
Ask HN: How are you keeping up with your app secrets?
Tokens, passwords, API keys, and stuff like that.
I grew up around SF and was a free range teenager taking buses everywhere knowing the trunk lines across town would show up every 5 minutes, glad there were large shared spaces and affordable places to hang out and eat with friends.

Pieces from the New York Post would prolly make parents not want their kids to take MUNI regularly.
I think the proof for the closed-form version is accessible to people with a background in linear algebra. The matrix is diagonalizable (not all matrixes are diagonalizable, but this one is):

M = P Δ P^-1

Here, P is some invertible matrix and Δ is a diagonal matrix. The powers of M reveal how useful this is:

M^N = (P Δ P^-1) * … * (P Δ P^-1)

If you adjust the parentheses, you’ll see N-1 terms of (P^-1 P), which can be removed, giving:

M^N = P Δ^N P^-1

The powers of a diagonal matrix is done by taking powers of the entries on the diagonal.

You see the φ values (1±√5)/2 in the matrix Δ.

Diagonalization of a 2x2 matrix is simple to do on paper. The diagonal of Δ contains the eigenvalues of M, which can be found using the quadratic formula. Proving that this is a correct way to diagonalize any diagonalizable matrix is more of a chore, but for this specific 2x2 matrix, you can just show that that you’ve found the values for P and Δ.

This is very elegant mathematically, but I would not use the closed-form solution if I wanted the exact answer, because you’d need a lot of precision, and that’s inconvenient.
OpenAI announces GPT-4 Turbo
American PTO in my experience is nuts. It's full of unwritten rules and conventions.

Give me a fixed amount of leave, which everyone is forced to take, so I know where we're at and don't have to play your guessing games.
SEEKING WORK | REMOTE (Full Time/Part Time/Contract)
FULL STACK DEVELOPER
Time Zone: US time zones

Technologies: React, Vue, Express/Node, Mongo, Mysql, AWS, Laravel/PHP, Jest, Cypress

Email: me+hn @ segoviacristian dot com

Rate: 40 usd hour(willing to negotiate)

Based in: Latam

Have 5 years of experience working at US based startups and small companies. Looking for full stack roles with a bit of AWS(or more), though open to frontend or backend roles as well.