skysight-inc/HackerNews huggingface dataset:
Well breaking the rules in a usually oppressive society is to be expected.

- Vedic to pre-Islamic era - get oppressed by rajas and brahmins based on caste.

- Sultanate and Mughal era - get oppressed by Mughals, Afghans, Turkomans, Persians, etc.

- Colonial era - get oppressed by the British and their English-educated/paid lackeys

- Modern era - get oppressed by police and Sarkari government babus

Oppressing other peoples seems to be a part of Indian society, so any reversal of the roles should always be celebrated imo.
No, I did not. I threw quite a lot of compute power at it using bkcrack (CPU) and hashcat (GPU) but never found out what it was. It was definitely not TIMBOBIMBO, sadly!

I also ended up sponsoring the bkcrack project because the maintainer added a new option for me: https://github.com/kimci86/bkcrack/pull/126
> ...I approached musée Rodin with a strategy to illicit a full airing...

Minor typo: if the author or anyone who knows him is reading this, the word wanted there probably is elicit.
Adobe Firefly use of 3D Gaussian Splatting
Adobe Firefly uses 3D Gaussian Splatting for 3D representation. This is one of the probably unrecognized use cases where this still quite new tech blends into a product, without being the product itself.

This is one of my first posts here, please remove it if i does violate a rule.
sure but you cannot just remove 'sql like syntax' and claim you can do linq in any language.
Meanwhile StarLabs regularly cranks out coreboot firmware for their different products with like three in-house developers. Guess you just need to put your mind to it.

https://github.com/StarLabsLtd/firmware
Note that the exact version of this technique is used in chess for the endgame, referred to as a tablebase. Chess is solved once there are 7 pieces on the board, in an 18.4TB database, described here: https://lichess.org/@/lichess/blog/7-piece-syzygy-tablebases...
I liked the previous password generation in Keychain when you chose memorable password. It would be two words with a couple of numbers and/or symbols in between.

That option isn't available anymore though.

I use 1Password to store it though and have since 1Password 7, maybe sooner.
If it were trivial you'd see LINQ-like providers implemented in "practically every high level language".

Source code of the function means you have to implement the parser/lexer to convert it into a usable AST which is bad for both runtime performance and library size.

Very much doubt this is available in Java, which Java ORM lets you use native Java language expression syntax to query a database?
Freeman Dyson: A Rebel Without a PhD [video] (2015)
Per https://stackoverflow.com/questions/57528450/adb-connection-... newer Samsungs (after 2015 per https://news.samsung.com/us/six-advantages-of-tizen-os-on-sa...) run Tizen https://www.tizen.org/
Same exact boat. Logical replication is nicer than our 'in place' upgrades we did before, but still leaves lots of other issues.

We are constantly making changes to our schemas (adding tables, columns, etc). Its never an issue on physical standby's, it just gets created, but logical replication, we have to manually run the changes on the subscriber.

We have lots of instances where we create a new table for a feature coming, and alter another to add a column.

If those get missed on the logical subscriber, you don't even know until someone tries to write data to that new table or new column.

I know logical is supposed to be flexible, but I wish there was a setting to have a replica via logical, so I can handle upgrades easier.
>fluent interface

Various names, same concept.

"fluent interface is an object-oriented API whose design relies extensively on method chaining."

>What does this have to do with LINQ or C#.

Check the name of the namespace where all those APIs like Where, GroupBy, etc. are implemented, it is "System.Linq"

So thats why majority of ppl think about them when talking about LINQ.

Query syntax has like less than 1% of the "market share" versus method chaining style
> ...surely drones, night vision, and guns could help solve this problem?

It takes an average of ten hours of searching per snake during which time they mostly drive around so I don’t think drones are a realistic option here due to flight time. There’s little benefit to searching far beyond the roads/levees because the swamp is a very tough terrain to navigate and it gets dangerous thanks to the gators.

Can’t use (real) night vision googles because any stray light from the car could blind the wearer and it would kill the driver’s peripheral vision making it impractical to drive.
Google Executive Overseeing Search and Advertising Leaves Role
I cannot wait for them to feed this content back into the machine.
Ogre-Next 3.0.0 Released
For anyone that hasn't read the previous papers before the "1.58-bit" part comes from using 3 values (-1, 0, 1) and log2[3]=1.58...
You had me until vi.
I think it was the fishing trip with Mandela and then-Prime Minister F.W. de Klerk in 1990 that ended apartheid. Specifically when one of de Klerk's people got a hook in his hand, and a Mandela person cleaned and bandaged it. After that trip Apartheid was finally broken.
I found the added complexity of this normalization funny/ironic when I wanted to process some OSM data. As IMO, the benefits don't nearly outweigh the added complexity and costs caused by it.

A different way of creating new topological connections wouldn't be that difficult. For example, some topological connections are already being created via relation type.

I'm not involved with OSM project, but I think that some changes to OSM data model would benefit it greatly. Resolved geometries would enable stream processing and decrease complexity for majority of task. It would make OSM data much more accessible.
Could you please help us better understand the work or at least let us know what is missing in nuance from the above poster’s usage?

The usage you are criticizing is the common understanding of the term “Faustian bargaining” but it seems that you have a better understanding and it would be nice to be better informed.
A 10 character password with all lowercase is 47 bits, if you do half upper/half lower it goes to 57 (using Shannon entropy).
It just opens/closes the file/edit/view menu.
You multiply the entropy of the previous word by the added entropy of the new symbol. This grows exponentially!

Extra character classes can help if you're stuck needing to make a really short password for some reason, but if you're randomly generating each symbol anyway, just tossing a few more on the end is *far* more effective. You massively increase the brute force search space with each additional symbol.
A single shot is unlikely to kill, and in these areas a snake can very quickly disappear into water or foliage. I doubt drones or night vision would help much for similar reasons - the issue lies as much in being able to reach the snakes as it does in being able to locate them. The Everglades are incredibly thick, a snake will easily outpace and hide from a human outside of roads. It does seem like there should be a better way than wrestling them but it's hard to say what that might be.
This all reads like bad business communication. Were any contracts actually signed? It's all just "he said, she said".
How often do people actually end up typing these random passwords though? Personally, I almost always can copy/paste or autofill. For devices like TVs, it seems like many of them let you pair via a QR code or other mechanism. And sure, there are times where you need to manually type a password, and for those specific cases you can use a different scheme (like avoiding special characters or using something like Diceware https://diceware.dmuth.org/) but I wouldn't go so far as to never include special characters. IMO if you expect to always be able to autofill, use as many character classes as possible.
Maybe it's the 80-20 Rule in action. Do 20% to learn the 80%.
I'm using Zen browser
If I'd answered this question a decade ago, I would have said the internet, but (especially the web) has been getting increasingly problematic for me, and I have something akin to "buyer's remorse". The cost/benefit ratio has turned unfavorable. At this point, I don't really think of it as a positive game-changer on the whole. Instead, I put energy into decreasing my dependence on it and increasing the separation between it and my real life needs.
Normal brain : The joy of considering future reward is greater than the joy of actual reward.

Dysfunctional brain : The reverse.

(Which makes me go hmm)
I thought Zuckerberg is a blowhard for renaming Facebook to Meta but calling a company "World" really takes the cake. Will Altman go after people using the word "World" without paying a license fee?
Hopefully the Factorio expansion doesn’t feel like the constant new buttons added to CK and EU. Those ultimately add nothing to the experience. Why do we need a fourth way to spend political points to improve your regions?
Not to mention:

- If you're scared to perform upgrades, this is a good indicator that you lack confidence in your backup/recovery/reversion policies and procedures, probably for good reason, so maybe fix that.
Glad your wife's treatment seemed to work out well.

I'm sure it was hard to watch your wife wait out the next Dr appointment. I have a friend and they decided to "pray the cancer away", and didn't seek medical treatment until there were skin lesions visible. The nurse at that appointment had to leave the room to vomit it was so bad. They went through surgery+chemo+rad and she's been in remission for a number of years now. So, even in fairly bad cases of waiting it out, there can still be good outcomes.

Definitely don't wait though. In my wife's case, they were confident that surgery would resolve it. But when they got in there, it was "acting weird"; it had grown much, much faster than it should have over that time. Initial diagnosis was stage 1, after surgery they called it stage 3+.

I had to do battle with the insurance company, because our company was changing insurance, with the new insurance becoming active 4 days before her scheduled surgery. We have a "benefits advisor" that always says "if you have any questions, ask us and we'll take care of you", but they've been fairly useless. In this case, they were telling us that we needed to wait until we had the new insurance cards, which would happen sometime within a few weeks after the new policy became active, then we'd have to submit for pre-approval, which could take another few weeks. And the specialized surgeon was scheduling like 6 weeks out...

We eventually found that we could personally guarantee payment, and the doctor was confident that insurance basically never denies coverage in situations like ours, so we went ahead with this course and got everything paid for. Which was good, because as I said, the cancer was "acting weird" and in the 2 weeks between initial location of the growth and the surgery that we were lucky enough to be able to get in due to someone else needing to reschedule, the growth doubled in size. Another 4-8 weeks very likely could have resulted in spread to the lymph nodes and much worse outcome.

Another moral of the story: Don't let the insurance company push you around. With cancer, time is always of the essence.
Enough that it's worth thinking about. It's not frequent but it happens.
Blazor for better and worse can't have the same ending as Silverlight did. In Server Mode it is just Razor + SignalR for HTMX-style frontends that sort of live update/"magic RPC". In Client Mode it is just Razor as a virtual DOM-ish framework running directly in Web Assembly (wasm) in the Browser. At the end of the day Client Blazor is much more like writing front end websites with Elm than writing websites for the Silverlight plugin.

(Hybrid Blazor where you use both server and client possibly in the exact same assembly/project is where most of the worst Blazor mistakes lie, but those aren't the mistakes of Silverlight, those are the mistakes of ASP Classic before .NET where you can be easily confused by new versions of the which bit of this is `runat="server"` and which bit is `runat="client"` and easily and accidentally create wild RPC ravioli/spaghetti code.)
I'm working on Boxy SVG which combines vector drawing and animation tools: https://boxy-svg.com
AWS Has a Moral Responsibility to Fix the Free Tier (2022)
Isn't Olmstead mentioned heavily in that novel about the serial killer in Chicago?
I was summarizing this from a Google search. https://isocpp.org/wiki/faq/intrinsic-types#:~:text=One%20wa....

As I read it, this link may be describing a hypothetical rather than real compiler. But I did not parse that on initial scan of the Google result.
https://x.com/alex_wohlrab/status/1512750950330642432
Do they offer an explanation as to why it’s set up that way?

It seems too comically slow and inconvenient.
In the context of web authentication, does entropy even matter (beyond an extremely low threshold)? Are there any attacks that actually occur that are defeated by increasing entropy? AFAIK basically all the auth attacks we see today are from password re-use, and out-of-band authentication, neither of which password entropy has an effect on.

"Summer2024!" is perfectly fine, if you use it for exactly one service. Frankly, "1235" is probably fine. No one is out there brute-forcing passwords.
That and capitalism doesn’t reward slow and steady, keeping things stable and well oiled. It rewards delivering shoddy features at break neck speed even if they need to be recalled after two weeks. That’s what Wall Street and the shareholders want. Hence why senior management rarely cares about addressing tech debt.

“Show me the incentive, I’ll show you the outcome”
Switching one uppercase letter in an otherwise lowercase password adds exactly 1 bit of entropy (per switched letter).

On the other hand, any extra lowercase letter will increase the entropy by 4.7 bits (assuming a password on [a-z]).

Given that most passwords have at best 2 uppercase letters, I would argue it is safer to force longer passwords than passwords with at least one uppercase letter.
Nobody will probably like it but I just use pwgen to generate passwords now and store it in 1Password since Keychain removed the memorable password option.

pwgen: aliased to pwgen --ambiguous --capitalize --numerals --symbols --secure
>folders require you to use hierarchical organisation, and everything has to be stored in exactly one place.

You can make aliases/shortcuts to files on MacOS, can't you?
> "preserve nature exactly as we found it forever"

It's not even "as we found it", it's "as it was at a certain arbitrary point in time". I've seen zero proposals to eliminate earthworms, honeybees, or dandelions from the Americas.
> none of them could articulate what part of its feature set they actually needed to use.

Transactional DDL: migration errors never leave the database in an intermediate/inconsistent state.

Range types + exclusion constraint: just no way to do this in MySQL without introducing a race condition.

Writeable CTEs: creating insert/update/delete pipelines over multiple tables deterministically. Seriously though, the RETURNING clause is something I use all the time both in and out of CTEs.

Filtered aggregates and grouping sets: cleanly get multiple data points for a dashboard in one shot.

Unnest: converting arrays into a set of rows. Inverse of array_agg(...).

Types: arrays, booleans, IP/subnets, UUIDs (without binary(16) hacks), etc.

Materialized views: seriously, how does MySQL not have this yet?

Statement-level triggers: another option from per-row.

Row-level security: setting data visibility based on configurable policies.

I can cite specific use cases I've deployed to production for each of these and more.
While I generally like Apple format, it still fails due to including ambiguous characters.

Such as: i, I, l, L, o, O, 0,
I especially like sites that disallow pasting into password fields.... Yes, that is apparently a thing, especially for banking or finance related sites (from my experience)
This has been solved by logical replication a few versions ago.

1. Leave your old database running

2. Start your new database with new version

3. Run logical replication and let it catch up

4. Decide you want to switch over.

5. Using a script: Stop your apps writing to the database (or switch to read only mode), let logical replication catch up one final time, stop logical replication, run a procedure to fix your sequences, and switch your apps over to the new database.

You are now done. Sure, it requires a one-time investment to work out the exact steps needed for your situation, but it's easy to do with minimal downtime.

Of course if you don't care about downtime just shut down your database server, make a backup(!), and then do pg_upgrade.
It’s really weird how much you comment about FSD being fake. My Tesla drives me 10+ miles daily and the only time I touch any controls is pulling in and out of my garage. Literally daily. I maybe disengage once every couple days just to be on the safe side in uncertain situations, it I’m sure it’d likely do fine there too.

FSD works. It drives itself fine 99.99% of the time. It is better than most human drivers. I don’t know how you keep claiming it doesn’t or doesn’t exist.
I generally follow if it’s not broken, fixes need to be carefully planned. I can’t tell you how many times I thought I’d quickly do an upgrade and things would go wrong, like all of my home automation stop working right before bed.
The kind of person who’s good at making games and is excited about ancient artifacts makes their own 3D assets that make the most sense for their game.
With mongodb in a HA setup you can perform a staggered upgrade of individual nodes in the cluster with no downtime. Very smooth in my experience.
> And being Apple, they wouldn't care about people needing to use anyone else's devices.

Did you RTFA?

>> To make these passwords easier to type on suboptimal keyboard layouts like my colleague’s game controller, where the mode switching might be difficult, these new passwords are actually dominated by lowercase characters. And to make it easier to short-term have in your head little chunks of it to bring over to the other device, the passwords are based on syllables. That’s consonant, vowel, consonant patterns. With these considerations put together, in our experience, these passwords are actually a lot easier to type on a foreign, weird keyboard, in the rare instances where that might be needed for some of our users.
OnlyFans Chatters Class Action Lawsuit
This reminds me of Lucky Framework for Crystal

https://luckyframework.org/guides/frontend/rendering-html
> My experience has been that they spin up either a hideously under or over-provisioned RDS or Aurora instance, and then never touch it until it breaks

That's a true shame considering how easy it is to make a read replica of any size and then fail over to it as the new primary. Definite skill issues.
This doesn’t seem likely, the major tourist destinations during the busy season are so crowded, or slot limited, that it’s a pretty unpleasant experience.

If anything it would reduce overcrowding .
Not GP, but if Prolog has been around for 52 years, has many implementations old (SICStus/Quintus, SWI, yap, ciao, xsb, eclipse, many more) and new (Scryer, Quantum, Strawberry, Tau, Trealla, ...) then it follows it's not doing so bad after all.

I have to say the "expert system" quote comes from lack of insight and perhaps outdated CompSci lecture notes when even at the height of "expert systems" around 1990 or before, Prolog's backward-chaining was seen as the opposite of an expert system's forward-chaining.

It may have been the case that what was understood as an "AI language" was anathema following the AI crash around 1988/89 (the original "AI winter").

What also may have contributed to the impression of Prolog becoming less used around 2000-2012 or so is the effect of W3C's/TBL's "Semantic Web" and description logics efforts capturing a portion of the academic and commercial attention in graph and logic databases, as well as in other applied logic domains such as formal verification (in a quite direct sense considering research grants for OWL, etc.)
It's been a while since I've shared anything I've written. And since it's published online I might as well share here.
Thanks, like most engineering things it's all about picking the set of tradeoffs that you can live with. :D
I’m sad to see this - I used to binge their videos a few years back. As someone who discovered and fell in love with classical music late in life (~26), and is now a hobbyist content creator [1] they were a terrific bridge into learning about orchestral instruments that I don’t play.

I agree with others that this seems like an attempt to pivot to “music as a higher art”, e.g. the rumored Two Set Academy, like a Tonebase competitor. Which is an absolute shame, because I think they did wonders to challenge that status quo and make classical music fun.

[1] Shameless, but if anyone is curious about an adult hobbyist learning classical guitar, I’m livestreaming almost daily: https://youtube.com/jcpractices
> Lastly, Wpengine never fully disabled post revisions, they just limited it to 2-3.

Not quite. https://wpengine.com/support/platform-settings/#Post_Revisio...

"Every WP Engine site has WordPress revisions disabled by default... Revisions can only be enabled by contacting Support... Support can help you enable 3 revisions for your posts to start. Revisions should not exceed 5."
And considering how many people use some sort of abstraction layer like an ORM, have databases installed as part of some deployed application, or just do basic CRUD stuff, it probably would have worked on a postgres install from the 90s.

I keep an eye out for vulnerabilities, and that's about it.
I really like the general notion. Yes we should start to improve glue! So much of what coders do today is glue code, and it's so rarely given form or distinction even though it's so omnipresent.

Think of something like Yahoo Pipes or If This Then That: almost purely glue code systems. And these programs composing systems so seem worthy of being their own things.

Marcel Weiher is lead author. https://news.ycombinator.com/user?id=mpweiher here, and lots of great posting on https://news.ycombinator.com/from?site=metaobject.com
As someone who really cares about a good trackpad and owns a Magic Trackpad 2, I never understood people who put Apple ones on pedestal. It's macOS that had good trackpad handling sooner than other OSes/DEs; their hardware was always comparable to other laptops from the same class. The only thing they actually differentiated in was haptic feedback, and it's mostly just a gimmick unless you happen to care about making tactile clicks as quiet as possible.

Sure, if you bought some shitty cheap laptop you got a shitty cheap trackpad on it, but that's hardly surprising.
"Leaves Role" is such a strange choice of words.
The tech side of this is really cool but I'd also like to read more about the non-tech stuff. I wonder if the sympathetic Dutch flight attendant is still alive or the guys who actually carried the Trojan horse books to Mandela.

What an amazing story!