skysight-inc/HackerNews huggingface dataset:
Even without greenscreen, actors in film and TV have to split their attention in unnatural ways. To preserve eyeline continuity in close-ups, actors often have to address themselves to a tennis ball or something near the camera lens, while their partner in the scene stands behind the camera. In the worst case scenario, sometimes the other actor is not even there when the closeups are being shot.
alright, do

curl | tee saved.sh | sh

then
Show HN: Interactive text game from a printable boardgame (by Taproot Wizards)
I mean, I am European, I'll give you that.

So, if I have a constant video recording where the officer is clearly at a distance, wouldn't that be great for my defense? Much better than if that same video showed me walking right up to them, within touching distance, with the video not showing where my limbs are at all times.

If you're worried about unlawful arrest, stay away from the cop and record them -- and if you do that, great, this law wouldn't affect you.
I knew we were in trouble when we started having to sort the query criteria in order to support caching of requests.

If I use graphQL again it’ll only be for admin features. Anything where very few users will use it and very infrequently. Preferably in spots where caching works against the workflow. OLAP vs OLTP.

GraphQL is really about reducing friction between teams. High functioning distributed systems all have two qualities in common: work stealing and back pressure. Without back pressure there is nothing to stop the project from running off a cliff.
I don't have any experience building an open-source community, but I do have a lot of experience in marketing. With that context, here's some thoughts – hopefully they're helpful, if they're not, I guess you can just ignore them.

1. Link everything together. If I'm on your github it should be obvious how I can get to your discord/slack/website/forum and vice versa, don't make me work for it.

2. Build a regular rhythm to your comms/emails etc. If people opt-in to hearing from you, you need to hold up your end of the deal and commit to regular, quality updates. This will become the heartbeat of the community.

3. Pick 1 or 2 'brand' assets. Try to make them distinct, and then use them consistently everywhere. Your logo is probably a good one, but some kind of color combination/sound/flair should be distinctively you. Use these assets everywhere so that it becomes a visual shortcut in people's brains.

Ultimately, keep it simple, and just start. Don't overthink everything, you can always pivot and change as you move forward.
It would be interesting to see the distribution across different countries.

My guess is that Europe and US have a lot more PS5s and peripheral economies have a larger PS4 base.
If you want to experiment on your own, you can easily spin up a simple LEMP stack with MAMP or XAMPP in a few clicks, and then configure each service to your liking.

I don't think there is any business value in maintaining a site that way for a small biz (I think "you don't know what you don't know" applies here, and there are a lot of issues you'll have to solve along the way that you might not have considered upfront). There's certainly educational value. But can't you do that on your own and learn in a lower-risk environment with a side project, instead of making your company's production website reliant on it?

If you really don't want to do that, sure, you can still roll your own and either just deploy the whole thing as-is (uploading files and mirroring DBs, etc.) or containerizing it with Docker. For making a reproducible LEMP stack that can be easily transferred to another host, also consider the free tool Lando: https://lando.dev/ It is a CLI wrapper around Docker, specifically for making it easier to deploy containerized LEMP stacks reproducibly.
You can run Yubico Authenticator locally on a desktop??? Or pass-otp?
Maybe. Can that one army fix GraphQL for all the teams in the company? Cause I've seen things work that way, but I've also seen tools that are pitched as "maintained in one place for everyone" but are actually a complexity burden on every single team, especially if/when its usage changes.
I'd love examples where DRY can really hurt performance. Typically what matters most in terms of performance is the algorithm used, and that won't change.

More importantly, cleverer people than me said "premature optimization is the root of all evil"
MongoDB were the first major player to do that (that I know of, at least) back in 2018 - see https://www.mongodb.com/legal/licensing/server-side-public-l... or hit google for a plethora of people being angry about it.
Google monetizes that data by serving ads. If you block ads that data is pretty much worthless to Google.
> trace/debug,

for whom? when was the last successful experience you had of telling a product manager to open their devtools and find the row in a websocket handshake showing the actual payload that went over the wire for the timeframe in question?

I am open to the fact that maybe there are super advanced organizations which have replay debuggers or Sentry or whatever that remove the need to utter the dreaded phrase "can you open the devtools?" but I regrettably haven't worked in one
For "wifi to work" you will need updates. Though updating all devices at once is a really dumb policy.
When the military finds a flaw in their immutable firmware, what do they do with those munitions? Throw them away and build new ones? Routers are networked and critical vulnerabilities that should be addressed get patched on them over time. Is the proposal to just tell the user to buy a new router?
Symfony API Platform boils to ORM-generated SQL via Doctrine, which is verbose, but not overly clever. So the only link I could give you there would be to the Doctrine query builder docs (I won't subject you to API Platform's docs). I imagine a more sophisticated graphql dialect like what Prisma supports can generate some pretty gnarly sql, but that's ORMs for you. But exposing your data model directly through graphql is also not recommended, same with REST APIs (I can't claim the high ground, my biggest graphql project exposes models directly. The tradeoff was worth it in this case). So in the end you're writing custom controllers/resolvers anyway, and field resolvers are where graphql really starts to shine.
I think the URL needs to be different. If that's the case, don't link to your home page but some more specific path. E.g. "https://yoursite.com/blog/how-weve-implemented-all-suggestio..." instead of just "https://yoursite.com/blog".
There's still plenty that can go wrong in a hurry even if you are just streaming along in lane. All it takes is for something non-routine to happen such as a car ahead reacting to an animal, or swerving as the driver reaches for something or spills coffee on themself, or a wheel come off a car (I've seen it happen to a car in front of me), or a car crosses the center median in opposite direction (which left my ex-boss hospitalized for 6 months).

I'd personally never trust an autopilot unless it's either backed by human-level AI which has also had years of driving experience, or it's in some very highly constrained environment (maybe airport bus going from gate to plane). Out on a highway or public road system is the most unpredictable environment possible.
I'd love to attend one in the bay. Seems like a prime crowd to target for this.

Please let me know if you find any. Happy to help start one too.
I suppose from the point of view of someone with a black-market HU card, DirecTV was an example of an Advanced Persistent Threat. Never thought of it that way before.
>> When using traditional slides, you are given a rectangle of white space to express your thought. When this rectangle is full, you have no other choice than erasing everything, and start again with a new white rectangle.

But if you scroll to far you have the same result and if you scroll less you may just use a slide where just move the bottom content to the top and add new content at the bottom.

I myself often still remember the position of the content even if I can't remember the content itself.
So I can skip through the slides and only watch certain parts of it without the need to read everything.

That would be harder with that approach.
Same. From what I've seen, most code is written with abstractions and DRY as a high priority rather than writing code that is performant and doesn't take jumping between 5 different files to make sense of it.
Ad blocking is personal infosec. We've seen malware get delivered by ads, and people getting tracked by ads. This is a losing battle for YouTube.

I suggest that YouTube should work on proving to the users that advertisers are trustworthy. You know, that unlike LiveIntent, an advertiser will allow and acknowledge a complaint, has a contact address, is not arrogant as hell.
You can configure a Lenovo Z13 Gen 2 with 64GB for little extra money (and choose between Windows, Ubuntu, Fedora, or no OS preinstalled).
Why would you assume that "fired" likely means some form of gross misconduct? Typically people are fired for doing a bad job.
I think the only hard and fast rule is to DRY the code that will introduce a bug if you change it in one place and not the other. And if it will, at least do a fat comment in both places for posterity.

Whenever I have to have a "mental model" of the code, I know I screwed up.
>At least in North America, a hexagonal sign is always a stop sign.

the back of a stop sign is often a slow sign, or a do not enter sign. The same shape of sign, but different meaning from different directions. The slow variant is often held by construction workers, hence the GPs example.
How do you consolidate code?

Good way to go at it is to isolate the functionality that is used many times and to pull it aside in its own function (or similar). That's just good code practice and also makes it easy to refactor and modify as needed.
I was going to write a comment that said something like "here comes Elliott Management!", but alas..
> the only users who are actually at risk of a surprise change to the keepassxc package are those running testing or unstable releases

> when Debian Trixie is released, upgrades and new installs of the keepassxc package will receive a transitional package that prompts them to decide between "full" and "minimal" packages

If you are running testing or unstable and not reading NEWS files then I think it's your fault - or is that victim blaming :P
Software dev.

> The non-existence of someone/thing able to do my job isn't why I work at my job.

Me neither. The reason that I'd quit, though, is because if my job can be automated then there's no point in doing it. I don't want to go to work every day knowing that I'm just a meat robot who isn't actually necessary.

I'd rather spend my time doing something that I can bring actual value to.
There's a certain psychological attraction to messy and confused situations which people are just too comfortable with but it explains why things like GraphQL (didn't have a definition for how it worked for years because "Facebook is going to return whatever it wants to return") inevitably win out over SPARQL (which has a well-defined algebra).

One of my biggest gripes (related to the post) is the data structure

create table student (
...
applied_date datetime,
transcript_received datetime,
recommendation_letter1_received datetime,
recommendation_letter2_received datetime,
rejected_date datetime,
accepted_date datetime,
started_classes_date datetime,
suspended_date datetime,
leave_of_absence_start_date datetime,
leave_of_absence_end_date datetime,
...
graduated_date datetime,
...
gave_money_date datetime,
died_date datetime
)

which is of course an academic example but that I've seen in many kind of e-business application. Nobody ever seems to think of it until later but two obvious requirements are: (1) query to see what state a user was in at a given time, (2) show the history of a given user. The code to do that in the above is highly complex and will change every time a new state gets added. The customer also has experiences like "we had a student who took two leaves of absence" or "some students apply, get rejected, apply again, then get accepted" When you find data designs like this you also tend to find some of the records are corrupted and when you are recovering the history of users there will be some you'll never get right.

If you think before you code you might settle on this design

create table history (
student_id integer primary key,
status integer not null,
begin_date datetime not null,
end_date datetime
)

which solves the above problems and many others in most situations. (For one thing the obvious queries are trivial and event complex queries about times and events can be written with the better schema.) I can't decide if the thing I hate the most about being a programmer is having to clean up messes like the above or having to argue with other developers about why the first example is wrong.

If "No code" is to really be revolutionary it's going to have to have built-in ontologies so that programmers get correct data structures for situations like the above that show up everyday in everyday bizaps where there is a clear right answer but it is usually ignored.
Which was also clearly not the case here.
It's all MFC C++ where most of the UI controls are custom ones that I created to achieve the kind of interaction I was looking for. I used LodePng and gifanimcplusplus for processing png and gif files, the rest of the code is all in-house. I learned a lot in terms of processing RGBA as fast as possible.
HN is your best bet to gain visibility open sourcing it. Your product looks great, I would choose it over odoo and the other open source options that look like software from the 2000s.

But the most important thing is, by reading your current mood with the project, open sourcing it will give your integrators the possibility of continuing using it when you totally stop caring about it.
Fair enough. I meant it in the sense of: change will happen, if he is reelected. But that kind of change is unlikely to please anyone.

Actually, I don't think he will be a dictator. That would require loyal, competent underlings. He doesn't seem to have a lot of those. Anyway, the swamp will drag him down.
I would never call anybody a pedo. Also, he does this sort of stuff all the time.
Because exposing your Database to the outside world is asinine. GQL sits between letting the frontend query semi-customizable queries and not having any customizability to select related resources.
I think comparing us to Neanderthals didn't do it justice. Imo it's more like going from single cellular organelle-less life to a full blown human.

That said, today the "machine brains" we're building are closer to the single cell side of the scale than the human side.

I like this analogy better because cells never went away -- they just self organized into something greater than their whole, and I'd imagine the same will be (is?) True with 'thinking machines' as well
I think it really depends and it's a case where a lot of engineering judgment and taste comes to bear. For example right now I'm maintaining a Jenkins system that has two large and complicated pipelines that are about 90% overlapping but for wretched historical reasons were implemented separately and the implementations have diverged over the years in subtle ways that now make it challenging to re-unify them.

There is no question in my mind that this should always have been built as either a single pipeline with some parameters to cover the two use-cases, or perhaps as a toolbox of reusable components that are then used for the overlapping area. But I expect the mentality at the time the second one was being stood up was that it would be less disruptive to just build the new stuff as a parallel implementation and figure out later how to avoid the duplication.
> digital art, codes or something else

These are smartphones, not tablets. This is exceedingly unlikely.
Some people treat codebases as an art project rather than engineering project.

I think this explains about three quarters of all engineering problems I've seen in corporate context, give or take.
It makes me remember Pedro Pascal and how he memorized scripts: https://people.com/pedro-pascal-reveals-tedious-way-he-memor...

> "You use the first letter of each word in these sort of towers, these columns I guess," he said. "And then it's this very, very tedious way of making yourself learn the line."

Reading the comments here on HN, I think it's safe to say that you need a combination of mechanical repeating and learning by heart.
Show HN: Unifying Warehouse Metrics and Funnel Metrics in Hashboard
Today we're launching funnels and event analytics into public preview in Hashboard. BI tools have often struggled with event analytics, despite them being very important to the complete story of a business! We said NO LONGER and are developing first class in-warehouse event analytics, governed by the same semantic data models as the rest of your metrics.

It's also the first feature we're launching on top of https://hashquery.dev/, our new open source analytics engine. Frankly, I'm pretty stoked about how often a difficult-sounding extension on this event analytics work has slotted naturally into Hashquery's semantics. Makes me feel like we chose some good abstractions :)

Schedule an onboarding session if you'd like to try it out. Hashboard has a free trial, so feel free to create an account and reach out to us!
Sounds like a mild form of PTSD
> We are also thrilled to report that we have achieved profitability.

BOOM! That's great news to hear. I've been paying for Kagi since the early adopter days and it's become one of my most used tools. It'd be really painful to replace it at this point and I hope Kagi stays in it for the long haul.

Just look at that side by side comparison with Google. I haven't used it without a adblocker in so long it's a shock. It's gotten really bad.
Same type of person who blocks Windows updates, messes with their registry, removes system files and processes, and then complains when Windows gets flaky on them and breaks in strange and unpredictable ways.
If every torrent includes a webseed, then you're still left with the problem of needing to build a full HTTP CDN, and now have to also maintain the largest tracker infrastructure ever deployed for Bittorrent.

Under normal conditions with well behaved clients, raw bandwidth for the large packages is essentially never the issue. Misbehaving clients, cache thrashing, IOPS are the sort of issues that cause pain for mirrors.
I am for sure no graphql ninja but I believe what you are describing is achievable via the introspection call, which the sibling comment hints at when mentioning the schema but I'm saying that's a runtime call just like any other and thus no "reading" required. I do think that introspection stuff is opt-in because some shops consider it an information leak vector, but for dev/staging I think it's a perfectly fine tradeoff

https://graphql.org/learn/introspection/
There is a cost to open sourcing. You have to maintain the community. If your goal isn't aligned with that, then you will get upset and probably stop maintaining the community.

Unless you plan to shutter the business, it could harm you more than help to open source if you don't spend the time maintaining the community, which could be a net negative for you.

It's highly unlikely that your userbase will grow or that your product will grow faster if you open source it. So you'll be adding an extra burden and still be in the same place.
Absent owning a computer, yes.
Perses – Dashboards for Prometheus (Grafana Alternative)
Congratulations to Vlad and the whole team. They are showing how a patient building of product and customer base can succeed, where a VC backed approach for a similar business model and product did not sustain. RIP Neeva.

We are delighted to support you as a customer and see your growth. Alternative search options are needed more than ever and becoming increasingly appreciated. We too are doing our bit in search, with a different business model and shared values about empowering a "human-centric and sustainable web that benefits individuals, communities, and society as a whole".
If that's what they wanted to prove they should have shown a better example.
Funny thing about directv is that because they allowed for many manufacturers to build receivers, directv had little control over the receiver firmware, so these counter-counter measures weren’t necessary at the receiver level.

Other providers that rolled out their own receivers had high control over the receiver firmware and once users figured out how to protect their cards, the receivers became an effective attack vector for the lazy.

But that’s where a lot of the public knowledge about JTAGs really started coming to light. Awfully nice of them to put in a cutout at the bottom of the receiver.
I’m still going through the ps4 library. The ps5 is nice but its library is small and I can’t justify the price at the moment. I might pick one up used but it’s not like they’re coming out with great games.
Good. That’s kind of the point.
Are you okay with Amazon taking your code and setting up their own version of SaaS for it? Not saying it'd make financial sense for them, just that… once you open source it they can do what they want.

Also remember that open sourcing something isn't a marketing panacea; you can still struggle to get people interested in it afterwards. It's a useful step if it calms your customers since they don't have to worry as much if you go away, and your value isn't the actual software but support around it or something along those lines.
That's mostly for Windows users.

The SQLite driver uses cgo, so we use both Ubuntu and Windows Server in CI to avoid cross-compiling. However, we still can't confirm that it's 100% ok on Windows. If any weird bugs occur on Windows, we don't have much experience or energy to deal with them.

The Docker image is based on Debian, we are more familary with it.
>what do they do with those munitions?

They're sent back to the manufacturer and the boards are replaced.
right? I mean even the traditional marriage vows (which given the possibility of divorce aren't really to be taken literally) include the phrase "until death do us part", implying that you are free to find somebody else once your partner has died.
Aka never underestimate the power of additional complexity to drive bad use, absent familiarity.
I have been surprised at the acceptance of the phrase "deep state" (regardless of your opinion of the topic) because it simply sounds like a foreign phrase to the English-speaking ear.

In the US, and in English in general, the use of "State" to talk about government is largely confined to political scientists and the odd reader of Leviathan. In popular culture, terms like "bureaucrat" are more typical, oftne with "unelected" tacked on the front. And of course in the US and Australia, at least, "state" is generally used for major subnational government divisions ("state of Texas").

On the other hand, the popular use of "state" as an actor or participant in its own right comes from 19th century revolutionary theory, especially communism. So countries heavily influenced by those movements (russia and former Warsaw-pact bloc, China, even Turkey, et al) use this construct naturally.

So it's fascinating that this loan-word has become popular in English.
I’m in my late forties and have been battling a terrible back problem for the last 16 months. Sadly, it was caused by my own decision to stick to barebones instead of upgrading decades earlier. The 16 months have been extremely expensive, to a point that I would have had a 1200% ROI even if I had splurged.

I know that one person’s bad luck doesn’t cancel out good rules for financial management. And I agreed completely with you up until 16 months ago. But in retrospect, I would have made different choices.