skysight-inc/HackerNews huggingface dataset:
From TFA:

> Many explanations have been given, among them explanations in terms of the Aristotelian doctrine of catharsis, according to which it is beneficial for humans to purge their negative emotions by experiencing art.

I'd change the last sentence to:

> [...] purge their negative emotions by experiencing them.

Negative emotions are easy to repress: we don't want to show weakness, in what's an everyday rats' race. How many times did you have to put up a happy mask when entering the office, coworker asking you, "how are you", like on auto-pilot you put up a smile and respond "good, and how are you?" while dying a little bit inside. You're wasting your life on a 9-5 job you hate, your best friend's old cat died, your ex posted a vacation picture with their new partner, you're in conflict again with a person you love, and you're a shoulder-to-cry-on short. You go home to the safety of your noise-cancelling headphones and you put on some Anathema to force the tears out.

(inb4 depressed rollcat, don't worry, I'm actually OK.)
I think I'm sympathetic to that idea, but the ethical consideration there isn't that it violates copyright. It's that it's disruptive to society/the economy.

Or maybe one could argue that because it's owned?
Obviously there is a big disconnect between what we think and what you do from your comment. It's fair to ask why and examine it so we can get common ground here. Like seriously, we can't be living in different realities so there must be more to it.
So you posit that the ejection seat adds some selfishness to the pilots? Because I’m not kidding there are a lot of incidents where we have inflight recordings of pilots without ejection seats steering away from populated areas in their last action, as well as the incident where an Israeli pilot with an ejection seat choose not to eject (and died) moving his plane off line.

Then, I’ll just tell you in my personal experience in the airplane, I’ve seen 2 pilots risk their lives moving away from a town and not die (luckily) but crash and destroy their airframe. The other pilots I flew with, I’d say 95 out of 100 would do the same.

Maybe Chuck was just a selfish asshole.
But if they release model weights to their algorithmic raster image generator and don't succeed in their lobbying efforts to ban their competitors, it will result in the AI apocalypse. Think of the children!
I’d certainly pay to have websites from pre-SEO era. In fact, I do: I buy books, recipes for example. But I hear soon books will be generated…
I wouldn't go that far. I think he's just reflecting typical blue collar culture which tends to be more conservative
> Log Levels are meaningless. Is a log line debug, info, warning, error, fatal, or some other shade in between?

I partly agree and disagree. In terms of severity, there are only three levels:

– info: not a problem

– warning: potential problem

– error: actual problem (operational failure)

Other levels like “debug” are not about severity, but about level of detail.

In addition, something that is an error in a subcomponent may only be a warning or even just an info on the level of the superordinate component. Thus the severity has to be interpreted relative to the source component.

The latter can be an issue if the severity is only interpreted globally. Either it will be wrong for the global level, or subcomponents have to know the global context they are running in to use the severity appropriate for that context. The latter causes undesirable dependencies on a global context. Meaning, the developer of a lower-level subcomponent would have to know the exact context in which that component is used, in order to chose the appropriate log level. And what if the component is used in different contexts entailing different severities?

So one might conclude that the severity indication is useless after all, but IMO one should rather conclude that severity needs to be interpreted relative to the component. This also means that a lower-level error may have to be logged again in the higher-level context if it’s still an error there, so that it doesn’t get ignored if e.g. monitoring only looks at errors on the higher-level context.

Differences between “fatal” and “error” are really nesting differences between components/contexts. An error is always fatal on the level where it originates.
Yeah, the whole 'open' part of this was them aligning themselves philosophically with open-source. But of course they throw that away when the money comes talking...
Ten tools to validate your next startup idea
Cute, especially because all their competitors have very competitive offerings these days and integrate very well into a vendor based solution like HomeKit or a open source solution such as HomeAssistant.

Case in point: LIFX (https://www.lifx.com/)
I think it’s more subjective than that. For me the Stable Diffusion experience is far ahead of Midjourney. Running it locally, hundreds of custom models online for any kind of image you want, controlnet, plus it’s free.

The open source community is pushing forward SD forward far faster than Midjourney is improving.
I meant the original version.
> meaning 20% accuracy is equal to 80% accuracy,

Only if your model is outputting a yes/no answer right? And that your definition of accuracy is "class with highest probability" (and not "N classes with highest prob")

If your dataset has more than 2 classes like MNIST, a super low accuracy only tells you to ignore the class the model guesses. It doesn't tell you which of the remaining classes is correct
> But look at a single 'real' neuron, it is just calcium ions, electrical potentials, there is no 'emotion'.

Indeed; this is why I am willing to entertain the possibility that emotions may be present as an emergent property of simulating us. I don't expect it, but I can't rule it out.
XML semantics, not syntax, are good for configuration too. See https://kdl.dev/
Do you have any background reading for high performance java or how it's used in the finance world? I had no idea it was used in this niche. As a crufty Java dev who types `new` everywhere and never gives thought to GC, squeaking out high performance sounds like an interesting side of the language.
Everything has gaps that need to be filled, the main point is that the object I send is the same shape and schema as the API, same for their responses and the data in the system.

TF under the hood is using these APIs through an abstraction.
I say "go to the APIs" as (1) bypassing abstractions (2) in CUE, we can import the existing TF resource schemas from the Go types, or from the OpenAPI schemas. There are 2 camps in CUE about how to approach the CUE/TF/Helm/k8s intersection (one for each way)

CUE actually offers a really great space to enrich the APIs with the needed information.
Well, that makes it worth listening even more.
Serialization in Boost
A surprising number of people, still, to this day, believe that to be true. Names really do mean something.

Edit: and don’t get me started on the Better Business “Bureau”
Hooky is also down. It may just be a bug in npm's reporting or a system down somewhere.
unless it's way worse
So pretty much, "shut up and accept it, peon"

Yeahno... that's not gonna suffice. Squeaky wheel gets the oil!
I loved YAML until I read the spec, and now I dislike most of YAML beyond the basics and avoid it unless "ease of humans to edit" is a primary goal.
Let me guess: the submissions of the ones not rising to the top will still become the property of LG, with 0 compensation regardless of future implementation, right? It's hard to find information about this on the website, the Terms & Conditions says only important things like you can't smoke and get high, nothing about such unimportant stuff.
Those people are the ones who founded OpenAI, so it's specifically the kind of thing they are pivoting away from.
I'm not sure I understand his example:

“I need to configure this server and the server needs to know if this value is true or false.”
No, that’s bad. Don’t do that. That’s not a good use for XML.

But on the other hand, if you need to mark something bold, then XML is a great choice.

I see both cases as being quite equivalent: whether the server needs to know that a value is true/false or that it needs to display something as bold feels quite the same thing, isn't it?

Or does he mean that you cannot easily retrieve the value of an arbitrary XML element? Whereas to display a document you just process it sequentially and do not need to 'retrieve' arbitrary data. Is this it?
Can you unpack this a bit?

My recollection is that the program was initiated in 2014, with substantial contributions from private organizations. It was further funded in 2015 with more private sector contributions.

I believe it was shut down when Trump was inaugurated.
I take quiet satisfaction imagining that I say really smart stuff I read elsewhere, get dismissed by morons, and then the morons 3 years later read the exact same idea from a reputable source and go "hold on a second, that's what that guy on those forums was saying" :-)
If you have root access on the host machine you might get away with the host tooling (depending on your issue).

I (as a devops engineer) did that because (rightfully) rhe developers i was working with at the time didn’t include some troubleshooting tools (like tcpdump) and the inages were running as non root anyway.

Look up the manpage for nsenter, it’s all you need really.

Btw, tcpdump in production, hunting the correct network interface on a kubernetes cluster node… fond memories:)
How do you deal with schema migrations, and software updates (SQLite or Postgres)?
Bah. While YAML is far from perfect, it's fine for random config files written by humans. TOML is mostly better, but from its own homepage (https://toml.io/en/):

[servers]

[servers.alpha]
ip = "10.0.0.1"
role = "frontend"

[servers.beta]
ip = "10.0.0.2"
role = "backend"

is ugly to my eyes. And I'd rather swallow my own tongue than have to hand-edit XML in the most common case where there's not a dedicated editor for that specific doctype.

In fact, I'd echo the linked article's argument back: I don't know of a case where XML is the best option. For human-edited files, pick almost literally anything else. For serialization, JSON handles the common cases and protobufs-and-friends are better when JSON isn't enough. There's not a situation I can imagine where I'd use XML for a greenfield project today.
We should just start calling them Closed AI from now on, just like we used to call Microsoft M$.
Hey, cool and yup, that's exactly the kind of setup we aim to support and we have drivers for both Expo and React Native.

Re: RLS, not quite, you'll need to port your rules to our DDLX syntax https://electric-sql.com/docs/api/ddlx -- which is not fully implemented yet (we're working on right now, will be available shortly).
There's enormously more focus within the left on the struggles of women and girls. Which makes a certain amount of sense, but boys and men certainly have their own serious problems.
German citizen kidnapped by the CIA. Germany does not care:

https://www.dw.com/en/kidnapped-by-the-cia-the-case-of-khale...
A lowercase "i" prefix would really tie it together.
Cleve’s Corner: Cleve Moler on Mathematics and Computing
Not everyone is writing React, thankyouverymuch.

Good points re: XML and its misuse as anything other than a markup language (its in its name, afterall). After using things like HAML and whatnot for a few years I went back to plain HTML. I like it much better.

YAML, meh, I choose to use it in Hugo because that's what I'm used to and I'd rather not learn a new config language until I'm forced to. I prefer config to just be in the language I'm working in, though many people disagree for various reasons but, you know, like, whatever, man.
The article is interesting but overall the conclusions don't pass muster to me. Women are also suffering and many of the things in the article are just facts about men such as method of suicide. For example, women are more likely to attempt suicide but fail when men choose more violent means so they often succeed more often. I'm sorry that men choose more violent suicide methods but that doesn't reflect anything on society or women other than men are more violent by nature. Which is a fact.

For the first time in history, men aren't the end-all-be-all of economic impact and I don't think this is a problem. Women have been getting the short end of the economic stick for awhile. The fact is the economy is changing and the traditional jobs that men have had in the past are no longer as high paid or necessary due to advancements in technology. Here's a perfect example:

"You have an infrastructure bill that will create jobs largely for men. Two-thirds of the jobs in the infrastructure bill will go to men: black men as much as white men, and Hispanic men a little bit more, because they’re so represented in the construction industry. Don’t hide from that fact, as the administration does when they’re challenged on it."

I think is just wrong. We shouldn't be making bills for men we should be making bills for _people_ that _need work done_. If "shovel jobs" aren't economically valuable and men want to pick up shovels and women want to pick up computer keyboards, does that mean we have some kind of crisis of the gender that happens to pick up shovels more often? I don't buy it. We have a crisis where _people_ are picking up the wrong tools if their goal is to make maximum economic output. Men should pick a lane. Either they are content with doing "shovel jobs" or they can go to school like everyone else and get a non-shovel job that pays well. We don't support the horse economy anymore other than niche areas because horses are, besides ranching or farming, useless for economic output. Why would we subsidize an entire class of jobs which don't make economic sense for the benefit of men only? That's against the market forces that run our economy and it's also against equality women have been fighting for for _generations_
> Since when has advertisement even implied endorsement of nearby content?

It's not an endorsement. People make associations all the time consciously or not. There are obviously positive and negative associations. And if it's within your power to reduce the negative associations which might impact the perception of your product then why won't you do it? Advertising is primarily an appeal towards emotion not logic. It's manipulative by nature.

I don't know what I'm saying that's so unreasonable.

Also, I can't control whether some homeless person pees next to my billboard, but if my competitors also have billboards in the area then I may still come out on top. But if I can move my weight to move those homeless people elsewhere, preferably to my competitors billboards then I'll do it. This isn't a moral argument.
> I think this interpretation is right: there is a clear "easy answer" here. But it is unsatisfying.

It seems like that actually mostly solves the problem though? Syntactically, there are four relationships a type parameter can have to a trait:

<T> // dunno
<T: Leak> // needs leak
<T: !Leak> // needs not leak
<T: ?Leak> // don't care about leak

But `<T>` isn't actually a semantic possibility; it effectively gets desugared to `<T: ?Leak>` ("don't care") unless Leak is a ?Trait.

> The problem is that as a consequence, any 2024-edition trait that doesn't have Leak bounds on the generics in its functions cannot be implemented in 2021-edition code

In "edition 2021" `<T>` desugars to `<T: Leak>`, which is not "don't care about leak". But 2021 code can still use `<T: ?Leak>` to explicitly not care about leak, just like it can use `<T: ?Sized>` to explicitly not care about size. (So 2021-edition code can implement 2024-edition traits that don't have Leak bounds, it just has to write the lack-of-Leak-bound explicitly.)

In "edition 2024" `<T>` desugars to `<T: ?Leak>`, (and `<T: ?Send>`, and `<T: ?RandomOtherTrait>`, etc, but that's not a change). (2024 code can still explicitly declare `<T: Leak>` if it wants, as noted.)

So in the desugaring interpretation, the only thing you've changed is the default trait bound; all the semantics are still there. 2021 keeps the conservative, backward-compatible convention, which can't actually use !Leak types very much due to running into traits like Iterator or Deref, but can (explicitly) support !Leak types in most generic interfaces. Meanwhile, 2024 uses the actually-useful convention, and can opt-in to `<T: ?Leak>` versions of Iterator et al piecemeal, with the `<T: Leak>` versions being automatically derivable.
I used to have wireless infrared headphones. Sometimes, the audio would go crazy, but only in a certain area of my office. As it turns out, the IR blaster on my TV was interfering with the signals. It was really interesting to hear the clicks of data being sent over IR, though.
Basically all of the liberal publications treat it as a major topic every so often.

A hugely shared article from 2 months ago in WaPo:

https://www.washingtonpost.com/opinions/2023/07/10/christine...

Also in the Atlantic last year:

https://www.theatlantic.com/newsletters/archive/2022/10/21-r...

This is just off the top of my head, but it's easy to do a Google search.
Dall-E also doesn't allow you to say "in the style of X" and similar. Which I guess appease some concerns from artists, but also makes it harder to guide it where you want it.

So it's not just about wanting to make explicit images, it's about not having a different entity control what you can and cannot do.
You seem to be asserting some categorical difference between Bezier curves and pixels, likely because most output devices work in terms of pixels. But they're actually both just drawing primitives, and neither one is capable of representing perfect circles.

> the Bézier inaccuracy has nothing to do with rasterization

Obviously, because rasterization refers to pixels and has nothing to do with Bezier curves. On the other hand, that inaccuracy has everything to do with Bezierization.

> there's a base level inaccuracy and then your rasterization brings a whole new, different inaccuracy into play.

Yes, stacking two inexact transformations will result in more inaccuracy than a single one.

Since you seem to be attached to your analogy - it's more like a person making the argument that humans can't fly unassisted, while showing a picture of a pig as an example of flying, and I'm pointing out that pigs can't fly either.
You don’t have to. It’s clear many of us feel this way, and you’re not the arbiter of which feelings are valid.
Apples are unusual insofar as they can be stored for 12+ months. Most produce isn’t so resilient.
My lightweight Docker deployment script for webhooks
Anyone who complains about the debt and doesn't propose ending the Trump tax cuts isn't serious. Or raising taxes to pay for retirement of Boomers which we've known would need to do for decades.

Also, there is a strong argument that we should be borrowing as much as possible while we can to forego the bigger future expenses of climate change. The US has 1TW of electric generation capacity; borrowing $2T to build wind and solar would be very good investment.
U.S. Phone-Tracking Firm Demo’d Surveillance Powers by Spying on CIA and NSA
Our design is parallelized, runs efficiently on multi-core cloud servers and
scales horizontally with the addition of app servers. Our DB is, for the most
part, used for caching and configuration, so it's generally not an issue.
Democratic People’s Republic of Korea. Democratic Republic of the Congo. Anyone who puts the word Democratic in their name is likely to be less democratic than others
as someone who has largely progressive values, I hesitate to call myself liberal anymore because of a lot of the downright embarrasing shit comming from the left these days.

> The left talks about this all of the time,

every time I've seen leftists talk about this. its always in the form of gaslighting men into blaming themselves for their failures. as if the k-12 educational system isn't currently stacked against them.
In the US the "winky" receptacles that go (-|) or (⊣|) - except the T faces the other way - are 20 amp outlets, 120 volts. every receptacle that differs from the "shocked face" means something. Our standard shocked face receptacles are 15A. In hospitals, you need a guarantee that your monitors or assistive devices aren't going to trip a breaker somewhere if someone plugs in a vacuum; making it impossible to use the receptacle for something else is something that only matters after it's too late, i'd think.
Dalle-3 is good at generating hands
Telcos used to monitor their copper outside plant for moisture. This was called Automatic Line Insulation Testing in the Bell System. The ALIT system ran in the hours before dawn. It would connect to each idle line, and apply, for tens of milliseconds, about 400 volts limited to very low current between the two wires, and between each wire and ground, measuring the leakage current. This would detect moisture in the cable. This was dealt with by hooking up a tank of dry nitrogen to the cable to dry it out.

Here's a 1960s vintage Automatic Electric line insulation test system at work in a step-by-step central ofice. [1] Here's the manual for automatic line insulation testing in a 5ESS switch.[2] 5ESS is still the major AT&T switch for copper analog phone lines. After that, it's all packet switching.

For fiber, of course, moisture doesn't affect the signal.

This led to an urban legend: "bell tap". While Western Electric phones were designed to not react to the ALIT test signal, many cheap phones would emit some sound from the "ringer" when the 400V pulses came through, some time before dawn.

[1] https://www.youtube.com/watch?v=Wt1GGdDa5jQ

[2] https://www.manualslib.com/manual/2755956/Lucent-Technologie...
Nice. When I looked at this last some months ago it only supported multi-tentant setups (where a whole db/table is synced) but seems like it now suports row based users, correct?
I was ready to give you my money, but you're Gmail only, sorry, I migrated out so will wait for IMAP support.
> it's bizarre to me when someone tries to divert a basic human concern into a political agenda

"The personal is political." It's a phrase originating in second-wave feminism and continuing onwards in current cultural issues.
Men have the rights to do all of those things.
>What happens if YouTube shuts down tomorrow? A, would society accept it and B, would they be bailed out?

I see no reason to "bail out" youtube if they close shop due to insolvency.

>I would not be against one of these massive services failing spectacularly to 'teach us a lesson' about trusting all our important things to private corps.

"important things"? You mean all the troll comments and misinformation being spread there? Or the very few videos that are actually interesting or useful? If the content creators don't still have those videos backed up somewhere other than youtube, then that's their failure. If they want those videos streamed on another platform, they are free to upload their content anywhere they want to, or even host it themselves.
but Sherlock Holmes access to production is sooooo fun…
So that's basically most of the lowest layers of the Xbox Live protocol as well. Simply game discovery happens over local broadcast instead of through the Live servers. There's some other specifics that change, such as logging into a host xbox doesn't diffie-hellman anymore but instead key sets are distributed by the server backends with the session information. Additionally the auth side is basically non existent on system link.

Great RE work!

Disclaimer: I created a proof of concept implementation of the Xbox Live server infrastructure here: https://github.com/xombieonline/xombie