skysight-inc/HackerNews huggingface dataset:
Long answer incoming, recurring events plagued me for more time than I'd care to admit. I'm perfectly happy to clarify anything I've expressed poorly.

a) I had full control of the back-end, so my solution was ultimately fully custom -- I don't have any APIs to point to, sorry.

b) Look at the iCalendar specification if you haven't already if for no other reason than to see what kinds of crazy corner cases they were expecting to support.

c) Generally speaking, making recurring series of events ('recurrence sets' or 'rsets') is "easy", but altering rsets will make you want to kick a small animal. I'm just going to throw out a couple of examples to indicate how annoying this can be.

Assuming each event is in a rset.
1) I move an event on a week calendar from Tuesday to Thursday. Is there an event in the rset in the preceding week that should now be visible on my calendar?
2) I move an event in a series recurring on T/R from T->R. Is the set now R/Sa or is it still T/Th?
3) Do I permit changes to a single event while still allowing it to be a member of its recurrence set (iCalendar allows this!)? More to the point, do subsequent changes of that rset affect the event that you've now changed?
4) I move event from a T/R rset to a Friday. Does it even exist anymore? It's not on a Thursday or Tuesday after all (not joking!).
And there are so many "gotchas" of this variety.

Granted, a lot of this complexity will be the job of the backend, for which you may or may not be responsible. But you still need to affirmatively decide if you're going to ask the user if they want to make a ("this"/"this and following"/"all") type of edit on certain actions and what an action maps to in terms of the API you're using. And if you ever want to implement your own backend, you're locked into that decision and you might hate yourself later.

As for my personal solution (again, I was writing the backend):
Most calendar implementations of recurring events (if the iCalendar specification is followed) comprise a "base" event and a recurrence rule from which the other events may be calculated. I personally settled on a much more rudimentary solution where each event was initially calculated via a recurrence rule but was stored a first-class entity in my database. I also prohibited changing the recurrence rule of for a set of events that was already created. This made it so that the recurrence rule actually had no semantic meaning besides at creation. The individual events were linked in a "group" and things like drag and drop operations were done just by computing the time delta and shifting each individual event by that amount. I NEVER regretted making my calendar "dumber" and almost always regretted making it more clever.

A last word of warning -- if you do not know precisely the "specification" you want to achieve in terms of what actions are permitted on rsets, you are 100% going to rewrite it multiple times (ask me how I know :p).
In this case, the hardware limit is CPU time. NES Tetris will give you more points for clearing lines the higher the level is. For example, on level 0 clearing one line gives you 40 points but on level 9 clearing one line gives you 400 points. This is implemented in the code by adding the base number of points to the score in a loop where the counter is the level number: https://github.com/CelestialAmber/TetrisNESDisasm/blob/2bd89... NES Tetris is written with the assumption that its main game code won't run for more than one frame. When the player reaches a high enough level the "add score for cleared lines" code will take too long, and the processor will get interrupted for the start of the next frame while it's still adding the score. This causes the game to crash.
You know at first I was thinking the same thing, but after having 2x 3090's raise the temperature of my bedroom to 86 degrees in the middle of the night last week fine-tuning an LLM, I could see the draw of 64GB (for 2) with 400 watts total less heat than the 4090's in my work space.
I would imagine this is coin payments only. Most people probably used transit passes. So coin payments would be a small fraction of the overall revenue.
Winston Churchill: From Prisoner to Prime Minister
"Line up and wait" is, historically, the ICAO phraseology, which the FAA adopted (and ditched the "taxi into position and talk for thirty more seconds and block comms" phrase). The phrase adoption went into effect Oct 2010 in the States.
The game is beaten IMO when you beat level 255 and rollover back to 0 avoiding any position that would result in a crash before then.
Absolutely right!

Point was that if the taxi clearance didn't include "hold (short of 34R)" it might be seen as contributing factor in line with ICAO[1] or FAA recommendations.

Also quite terrifying that, given all the equipment at Haneda and according to https://www.youtube.com/watch?v=6NbVdIoJsHY, around 2:45, with taxi lights fully visible at 2:53, the DH8 was lined up on the runway for more than a minute before being run over by the A350.

But as you say, preliminary report should already have a clear timeline of the tower tapes.

1: https://www.icao.int/safety/runwaysafety/documents%20and%20t...
Location: Los Angeles / Orange County / Remote

Remote: Remote or Onsite

Willing to relocate: No

Technologies: Ruby on Rails / Javascript / Full Stack and Frontend engineer

Résumé/CV: https://bit.ly/ankur-patel-resume

Email: ankur@encoredevlabs.com

LinkedIn: https://www.linkedin.com/in/ankurgpatel/

Hi I am Ankur and have been working as an independent contractor specializing in full stack web and mobile development. I have built web and mobile apps for a wide variety of clients in diverse spaces, such as Bloomberg Law, IBM, Oracle, Goldman Sachs, Shutterstock, and MyTime. Feel free to reach out to me if you need someone hands on to help get a project started or to speed up deliverables of your project.
I don't like how the person who responded was very friendly and actually looked at the issue. It seemed like he was being taken advantage of.

More importantly, I don't want these kinds of reports to discourage friendly, investigative responses. Open source already has a problem, where many newcomers get discouraged by curt responses and their issues not really getting investigated or addressed. Sometimes the responders come off as rude, because they see so many low-effort PRs and issues and feature requests, and have very limited time. But a lot of "low-effort, low-quality" stuff is just submitted by people who are trying to join OSdev, so they deserve friendly responses and actual investigation like this responder did.

This stuff just makes maintainers' lives harder and increases the chance that newcomers get unreasonably-harsh responses, discouraging them from making future contributions (which may eventually become useful).

Ironically this is even a problem in HackerOne: I've read multiple blog posts where someone submit a CVE to a big company, and the company responded "this isn't a real problem" and just left it unaddressed (sometimes leading to the public disclosure in the blog post).
Additional context: for a flavor of what I have in mind, you can glance at the wiki page for vector spaces [0]. E.g. [1].

[0]: https://en.wikipedia.org/wiki/Vector_space

[1]: https://en.wikipedia.org/wiki/Vector_space#/media/File:Deter...
A similar phrasing I've internalized is "Make it boring (stable, predictable) or make it better"
"position and hold" was the old phraseology in the US. It changed to "line up and wait" on 2010/09/30 to match ICAO standards and because "hold (on the runway)" might be confused with "hold short (of a runway/taxiway), or "hold position (wherever you are now)".

https://www.faa.gov/airports/runway_safety/resources/luaw
Nobody artificially limits input rates because that would reduce responsiveness. You can analyze a series of inputs to detect humanly-impossible changes.
> But a system made up of individual humans (and computers) can catch errors, refuse to submit a DMCA notice unless there's ~100% certainty, etc.

What's your proof that such a system has been realized anywhere on the internet, with a '~100% certainty' rate?

Or is this entirely conjecture?
This is really cool!

Some ideas:

- Let me drag out guests to tables and then optimize around what I've done so far. It looks like optimize wipes the slate clean each time.

- You might consider letting people pick how many seats should be at each table with a +- tolerance.

- People really like seeing seat numbers, whether globally or local to a table.

- If you clean up the UI a bit this could also be something people print out for a reference chart at events.

Automatic seating has been one of the more common feature requests of my own seating chart app, seatpuzzle.com, but I haven't quite gotten around to modeling the right parameters and prioritized a different set of things instead.
Platforms don't change much. It's the velocity that matters, not height.

In other words - launching rockets from 100km above the ground wouldn't change much in terms of how much fuel you need.
Images altered to trick machine vision can influence humans too
I merged two codebases (several thousand commits each) into a monorepo using a similar strategy. Instead of top level files in an api repo, and top level files in a web repo, we have packages/api and packages/web. It feels magical that I can open up a blame for a file in either package when most commits occurred in separate repos spanning back 5 years
> I'm trying to put my finger on why this pisses me off so much

What I find frustrating when reading LLM output is that the eye glides over it easily, as it all has the right "texture" of text. But after reading a paragraph, you realize there is no content! And you have to squint hard looking for it, and you can't find it. It's exhausting.

And here, the person at the sharp end is doing a valuable, unpaid public service, which is adding insult to injury...
Location: Royal Oak, Mi

Remote: Yes, open to hybrid

Willing to relocate: Yes, for the right location

Technologies: Python, C++, JavaScript

Résumé/CV: https://www.linkedin.com/in/nasir-sharaf/

Email: nsrsharaf7 {at} gmail [dot] com

Preferred contact: Email or message me on linkedin

So basically I have my bachelor's in Mechanical Engineering and started out as an energy engineer but pivoted to software development. I got my masters in computer science and I am now working as a contractor for a Big 3 Automotive company in their embedded software group. It's fun, but I am looking at other options since they're making us come back into the office this year. I would be open to working in an office, but it has to be the right location.

I would love a role where I can learn more, diversify my skills, and have some cool stories to tell.
The paranoia is no longer prevalent, but I don't think this has much bearing on the underlying risk that exists regardless of the degree of awareness by the general population.

One of the only reasons MAD has held up is because we've successfully restricted the reach of nuclear weapons, i.e. if every country that wanted them could get them, the average person would have a lot more reasons to be paranoid.
I used to have a poster on my wall at my office at Borland that said:

DO IT.
DO IT RIGHT.
DO IT RIGHT NOW.

I interpreted it as "start by writing a test or some code. make sure the code gives you correct results. only then, when the code generates correct results do you jump in and optimize," which is pretty close to the OP's message.
I really miss the Infinite Jukebox. The original had MP3 upload support though, and this one doesn't...
I’d assume people would compare what they think is the greatest civilisation of the world with civilisation of compatible systems, but yeah if you want to race with Iran, SA and China and just be better than them, go ahead, be better than Iran, it will be great for Americans, there is also Afghanistan if you want to go a level further
> That sounds terrifying. Do people just pay them off within quickly if interest rates rise?

Variable rate mortgages were a better bet 88% of the time between 1950 and 2000:

* https://wowa.ca/static/fixed-vs-variable-study.pdf

Post-2000 variable did fairly well as well.

It's the recency bias of the last 1-2 years that have people really freaking out about it.
I am open to the premise of not using incarceration for most nonviolent offenders. I don't support that in all cases (we're better off with Maddoff and Bankman-Fried in prison for life), but at least it's not an insane proposition.

The total elimination of prison cells is insane though. Such a proposal does not deserve to be humored.
extremely relevant disambiguation that I for sure had never heard about:

> in this essay I will use the term 'live coding' to refer to the digital arts practice, as opposed to live programming more generally.

and following the "live coding" hyperlink yields:

> Live coding is a new direction in electronic music and video, and is getting somewhere interesting. Live coders expose and rewire the innards of software while it generates improvised music and/or visuals

so, whew, all those folks who say "project name collision!" got their beer held :sob:
"Line up and wait" is indeed correct!

https://www.faa.gov/air_traffic/publications/atpubs/aim_html...
Discord's never had major performance problems for me, at least compared to anything else like Skype.
I tried a few songs that didn't quite feel right with the default settings, but Immigrant Song by Led Zeppelin completely slaps: https://jukebox.davi.gq/jukebox_go.html?id=78lgmZwycJ3nzsdgm...
So this still seems like it would allow copyright to be extended for thousands of years? A 2 hour movie can easily be edited, significantly, a few dozen times.
Clearly, the justices and I have a difference of opinion about what a direct threat looks like (in the case of Westboro).
Managing superstars can drive you crazy
Yeah, make "make it work, make it right, make it fast" is only applicable if you get to throw out most of the work from the first two steps, which is rarely the case.
Though not mentioned in the blog post, this seems like it would have some applications for true "subliminal" advertising.
None of those things are examples of students being censored. Disinvitation and protesting are themselves protected activities. This doesn’t say what you’re claiming it says.
As I found out when I first put something up for review on HackerOne, there is a whole cottage industry of people just running scanners and blindly reporting whatever comes out. They are doing this to get something on their resume and maybe receive a bounty, not to improve global software health. It’s basically spam, because all the effort is on the part of the receiver to figure out if these reports make any sense. (And of course you can pay H1 to do that for you.)
emailed you subject "Hacker News ping"
It is if you can pool the memory. It's easier than having to do the split of the models in software (though that's a somewhat solved problem) and from what I know allows higher GPU utilization on both cards when they don't have to wait for information to pass back and forth.
Cabin crew are also eyes for the flight crew. Relevant discussion about the Shatner’s seat: https://news.ycombinator.com/item?id=13824985
LIPS has documentation builtin into every function. You can see the docstring when you hover over the name of the symbol in the REPL. It also has auto-indent. Also if you press enter you can get back and modify previous lines of code. History doesn't repeat lines only full S-Expressions so it's easy to rerun a big chunk of code.

Even though Try Gambit is a REPL it's not very user-friendly.
It's the norm in most entry level content pipelines. Instagram for example has been autogenerated computer voiced spam audio over stock footage for a literally physically impossible product for years. You basically cannot buy a legitimate product from an instagram ad.

For a decade or more, a reliable grift has been selling "buy something on ali-express and sell it on another site for 10x markup" as some sort of business secret to low information people and other scam-vulnerable populations, and nearly all of them nowadays amount to "the next step is to buy $10k worth of ads on instagram" for the same white label product that everyone else is dropshipping. They're just get-rich-quick schemes. That's why they are so clearly low effort and fraudulent, because that's just how get-rich-quick schemes always are, because the target audience believes that if they just scam a little harder, they can be rich too.
Location: Buenos Aires, Argentina

Remote: Yes

Willing to relocate: Yes

Technologies: Next, Typescript, React, Postgres, Team Leading

Résumé/CV: https://www.gvizo.so/about

Email: contact@gvizo.so
You're thinking in the lens of a consumer, that's the issue. I'm sure to Nadella MSFT is making off like a bandit. The users looking for a job aren't the customers of LinkedIn.
Discovery of the Lyme Disease Agent (2019)
Well my problem is the conditions of an airline crash (the smoke, extreme heat, etc) are triggers for our disease. It’s not a simple as a peanut allergy where you just avoid eating a certain food.

I’m not convinced that medical personnel would be on hand that quickly for all emergency landings — sure if you are at a major airport. But they may not notice someone who collapsed after being triaged away from the more severely injured.
Ah cool, somehow I didn't notice that! I've made an anonymized version of my guest list to try it out. Another thing that I noticed is that I put notes with some of my guests, and also some couples are in two groups - does your app work with multiple groups, or does that not make sense with the optimization?
Perhaps because the poster seems to be historian and not a CS practioner.

From the question

"Why I am asking

I am writing a history of the Fast Inverse Square Root, information about which is collected at 0x5f37642f.com. Part of investigating this as a historian means asking questions like this from the community. I do not have the expertise to distill, by myself, much of this because I am not a mathematician or a computer scientist."
If you don't have the time and agency to do-it-right, you won't.

It's tempting to believe that just by dropping the "discover what you need to do step" and you'll get enough time for it and make the thing a single change you can plug on your Jira. It's also delusional. A blatant lie people have been repeating to themselves for half a century, while fully knowing it's wrong for the entire time.
It's presumably to reduce the number of places where you might need to call free, and then fail to do so?

(This might already be happening in line 580? Though in practice perhaps that case never occurs.)
Ooh cool!

FYI you can lock people to the tables and it optimizes around it already. Just click on the lock icon.

Interesting idea on the tolerances.

Right now I'm not putting in specific seat numbers yet. You just mean number them for UX purposes?

How's seatpuzzle.com doing? Looks like a cool app!
> You're comparing demand with supply, which are not the same

That's fair, I did get them mixed up. The _supply_ is constrained since they introduced more strict rules for adding new emoji, the demand is still much larger than that.

> the 2023 additions produce endless varieties of human "representation", and everyone wants to be represented in emoji

Most of the 2023 additions are about horizontally flipping actions that have directionality. Only the new family pairings could be considered representation-related, but IMO they're mostly about completing the set of possible combinations.

> the new sequences depend on the new codepoints, otherwise they would be preexisting emoji, not 2023 additions

It's complicated, because Unicode publishes both the codepoints and also a list of recommended interoperable ZWJ sequences. Newer additions have been to this list.

Anyway, ultimately this is a matter of opinion, but arguing that unicode growing to encompass a lot of emoji as time goes by is not something scalable seems weird to me. One of the explicit goals of unicode was the ability to handle CJK ideograms. There are ~90,000 of those, and only ~3000 emoji. Even if they added 100 new emoji per year, which is far more than what they're doing, it would take about 900 years for the emoji set to match the size of the CJK ideograms set. This seems very scalable to me.
There's option 4: offer the absolute best value for money in your niche and don't have a digital media budget, rely on word of mouth instead.

e.g. Costco, Tesla itself in the early 2010s, etc...
After spending enough years mentoring juniors, you pick up on it pretty fast whether someone is worth your time. Ask for a specific solution, and you'll get it from me once. Ask for understanding the generalized case, and I'll happily sit around explaining things to you all day long.

Even asking for a specific solution is fine if it's followed up by thoughtful probing questions on the general patterns. But there's just no room for hand holding in this industry.
LLMs being LLMs.

Reading this makes me a feel a little more secure in my job.

They have a long way to go.
> Do we honestly believe that type of protectionism is going to create a bunch of jobs domestically

It's somewhat ironic saying this in response to someone who because of the high price (he thought) he was going to have to pay he took his business to someone local.
Trust the programmer is kind of still with us. Compilers assume the programmer is somehow capable of keeping perfect track of all the many footguns and somehow doesn't trip over them. I don't think that's what it used to mean.

> there should be no invention, without exception

_Generic? The _Atomic mess?

I've been vaguely thinking I need an off ramp from C as it staggers towards a more dangerous and annoying C++ dialect. Currently I think the right play is to write a C99 compiler that doesn't use UB => ruin as an optimising trick that incidentally stomps all over what the programmer thought would happen.
Developer of lan-mouse here:
I initially started working on this project with only wlroots compositors in mind or more precisely
- any compositor that supports the layer-shell protocol could be used for capturing input
- any compositor that supports wlr-virtual-pointer and virtual-keyboard could be used for input emulation

The main motivation was really to learn more about wayland at that point.

Then later I started to expand the project to support additional backends for e.g. Windows and MacOS (which currently only support input emulation) and of course Libei to get Gnome working as well (and likely KDE in the future).

For input emulation there is also support for the xdg-remote-desktop-portal which seems to be the only option for emulating input on KDE wayland until libei is supported there.

Input Capture using Libei is WIP since the whole project and particularly also the Rust bindings are in a pretty early state right now (thank you so much ids1024 for providing the reis libei bindings, if you are reading this!)

I agree, it's a shame that Wayland is so fragmented among the different DEs. Especially wlr-layer-shell support would be very nice to see on the Gnome Side (it was much easier to work with than libei!...) but I'm pretty sure that's not going to happen.

On the other hand I must also say that supporting wayland through the mentioned interfaces was a more pleasant experience than supporting Xorg with hacks like Xtst (Except for the broken implementation of the remote desktop interface in xdg-desktop-portal-kde maybe, which left me with permanently stuck keys several times...) and I'm still figuring out input capture which is likely also going to rely on more hacks than the wayland side of things.

I have also played with the idea of writing some sort of wlroots -> libei bridge that implements an eis server using the mentioned wlroots specific protocols.
This would reduce the amount of backends required in lan-mouse but add an additional layer of indirection between the application and the compositor, so I'm not sure its such a great idea.
For the foreseeable future, I will definitely keep support for everything within lan-mouse itself.