skysight-inc/HackerNews huggingface dataset:
I was wrong about the era, apparently the height of the comic book scare was the late 1950s, but it continued to the end of the century as far as I remember.

It's all based on this book Seduction of the Innocent: https://www.amazon.com/Seduction-Innocent-Frederic-Wertham/d...

Here's an article about it: https://slate.com/culture/2008/04/the-campaign-against-comic...

The scare went all the way to Congress.

Here's a book about the history of the comic book scare: https://www.amazon.com/Ten-Cent-Plague-Comic-Book-Changed-Am...
Any new tech that has the potential of advancing the human species I am excited for. And this is one of these.

The challenge is how to adapt to create new opportunities.
Lots of other research says otherwise https://academic.oup.com/abm/article/45/3/338/4443220?login=...

N that doesn’t even get into how well documented it is to be alone as we age.
It's the same with a lot of open source contributions; those need to do so for legal and copyright reasons.

If you're afraid of doxxing and / or stalking though, at least you have the choice to not contribute. You can still post somewhere else and ask someone else to make the report for you if need be.
Zuo is interesting because (as far as I know) its primary user is the Racket project itself, for bootstrapping the compiler.
Also, DALL·E 3 "HD" is double the price at $0.08. I'm curious to play around with it once the API changes go live later today.

The docs say:

> By default, images are generated at standard quality, but when using DALL·E 3 you can set quality: "hd" for enhanced detail. Square, standard quality images are the fastest to generate.

https://platform.openai.com/docs/guides/images/usage
Wikipedia: "[The mantle] is predominantly solid but, on geologic time scales, it behaves as a viscous fluid, sometimes described as having the consistency of caramel."
I think you are wrong, this is not how TLS works. In order to man-in-the-middle you, your ISP would have you install a certificate that makes their fake certificates for services (ie google.com) trusted on your devices.
it can certainly be equally rigid if that's what you're after; they have very close to the same young's modulus. thermal stability and vibration absorption is more challenging

i think castings often come out closer to net shape than weldments and thus need less final machining, but i could have that backwards. they both shrink as they cool, but weldments don't need draft
Boycotts/strikes* only work if most or nearly all people participate, because you'll only participate if you're pretty sure nearly everyone else is too. While if this blogpost merely gets 0.1% of developers to strike... Apple couldn't care less.

I think this developer strike is a great idea, but launching it as a single person's call to action (Jeff Johnson's) is not generally going to be effective in changing behavior.

What an organizer needs to do is to first personally contact somewhere between 50-200 other major, known, respected developers and get them to co-sign a joint letter which then gets published, so everyone can see this is a serious strike by people who know what they're doing -- not just one person's wish. It needs to get covered in all the major tech publications, so both Apple and all developers see it as well.

And then the letter needes to not lay out a list of all of the complaints, but rather the specific, verifiable actions Apple needs to take in order to end the strike, so this isn't some open-ended thing. And they need to be realistic actions as well, not wishful thinking -- signs of progress with dates and milestones, not fix-all-the-things-immediately.

If you're going to do a strike, you need to actually organize it. Writing a blog post that merely "encourage[s] all Apple developers to join me" is not the same as organizing. And generally speaking, writing a blog post claiming that you're striking isn't going to get anybody else to magically organize it for you.

* As the author indicates lower in the article, it's more of a strike than a boycott since it's stopping providing free labor rather than stopping purchases, so I'll refer to it as a strike
The map of middle earth isn't in the middle of a philosophical treatise on understanding the nature of the physical world and the composition of the universe..... :/
That's fair and i support that but it does not address historical bug patterns that may be a design issue.
JSON mode is a great step in the right direction, but the holy grail is either JSON-schema support or (E)BNF grammar specification.
It's a good strategy. For me, avoiding the moat means either a big drop in quality and just ending up in somebody elses moat, or a big drop in quality and a lot more money spent. I've looked into it and maybe the most practical end-to-end system for owning my own LLM is to run a couple of 3090s on a consumer motherboard at substantial running cost to keep them up 24/7 and that's not powerful enough to cut it and rather expensive simultaniously. For a bit more expense, you can get more quality and lower running costs and much slower processing from buying a 128gb/192gb apple silicon setup and that's much much much slower than the "Turbo" services that OpenAI offers.

I think the biggest thing pushing me away from OpenAI was they were subsidizing the chat experience much more than the API and this seems to reconcile that quite a bit. Quite simply OpenAI is sweetening the pot here too much for me to really ignore, this is a massively subsdizised service. I honestly don't feel the switching costs in the future will outweigh the benefits I'm getting now.
It’s not a dumpy alternative. It’s the only alternative that currently allows AI generated content in games.
> EDIT: On top of that, there's usually a bit of 'related' work you need for a task, by example when you find an edge case related to your feature, and now you also needed to fix a bug, or you did a bit of refactoring on a related service, or needed to change the data on a badly formatted JSON file.

I agree that's related work, but I'd argue that work doesn't belong in that branch. If you find a bug in the process of implementing a feature, create a bugfix branch that is merged separately. If you need to refactor a service, that's also a separate branch/PR.

That's actually the most common pushback I get from people when I talk about squashing. They say "but then a bunch of unrelated changes will be lumped together in the same commit", to which I respond, "why are a bunch of unrelated changes in the same branch/PR?"
Purely a guess, but having tried to scale services to new customers, it can be a lot harder than it seems, especially if you have to customize anything. Early on, doing a generic one-size-fits-all can be really, really hard, and acquiring those early big customers is important to survival and often requires customizations.
Ok, we've s/micro/PET /'d the title above. Thanks!
Awesome, I've been waiting for something like this.

It looks like we are moving away from apps to web GPTs, this looks like chatbot interface is here to stay and 'AI' is now the default interface that is to be expected.

I also don't need to spend lots of money on a developer to test my ideas out, this is great for product validation, I look forward to playing with GPTs.

I can see writing, travel and other bots being more enhanced and more powerful, hopefully existing startups will adapt to this change.

Exciting and interesting times!
> fixing the same conflict repeatedly is annoying

This is usually caused by merging an upstream branch (e.g. develop) into your feature branch and then later trying rebase it.

Effectively the commits you've merged in from develop undo the changes you've made in your feature branch. You fix them but the foreign commits undo the changes again.

The solution is actually pretty easy. Use git rebase --interactive to remove any commits from the rebase that aren't directly part of the feature work.

You may still have an odd merge conflict to fix but you'll only have to do it the once and everything should go smoothly.

I would also recommend never using the same commit message twice. When you have a list of 10 commits all called "Wip" it's hard to tell which are obviously duplicates that can be deleted.
I wonder how much money I could make making "GPTs" full time. Barrier to entry is nonexistent so I imagine highest revenue ones if this becomes a serious thing people use will be advertised externally or have some proprietary info/access.
They will start rolling out at 1pm PST today.
It is my recollection that the official Arc uses incompatible features. I can't remember where I read this, so it's entirely possible I am incorrect.
Definitely a very funny example of their own product's shortcomings
MIT Media Lab Identity (2015)
Pentagram’s page - https://www.pentagram.com/work/mit-media-lab/story
Seems pretty...underwhelming as the first product of x.ai considering the initial announcement of its founding came with such a splash. This is more like someone trying to piggy-back off the popularity of LLMs with a trivial tool than driving the space forward in any way.
This is a good counterexample for when you should believe a story like this -- the author is a historian who made an effort to "tell the truth" as best as he could, it doesn't describe anything implausible, he was rightfully skeptical about his own sources, and information that he used to say that the story was probably false is now evidence that it might be true. Herodotus wasn't immune from spreading bullshit(to say the least: https://listverse.com/2015/04/08/10-historical-facts-that-he...), but he at least gives you a good idea of where he was getting the bullshit from and gives you all the information you need to figure out if it was bullshit.
Is this just for the API for now?

I just got premium the other day for ChatGPT 4 and have been blown away. I’m wondering if I’ll automatically get turbo when it’s released?
> HEAD^^^^^^^

Dude! Learn the tilde notation
I’m not sure what you mean.
Keeping a system updated does include updating to the latest major operating system release when an older one no longer receives security updates.

Ansible (and other provisioning solutions) could help in the case where updates break an existing workflow by attempting to put the system back into the desired state. Of course if something broke after and update there’s a chance that trying to fix it will fail, but at least it would fail loudly during the provisioning process and you’d be able to see why.
Not really, Windows and Mac only show warnings for unsigned applications, and the policies for signing don't include revenue sharing with Microsoft or Apple.

Android of course has an app signing system which could be used the same way to verify the authenticity of third party app downloads, but Google chooses not to protect users in that situation the way that Microsoft or Apple do.

They do have Google Play Protect which scans all apps regardless of installation source but as far as I'm aware they don't go out of their way to confirm to the user that they are installing the real Epic Games Store.
Very hard to always be grant driven. That is a massive burden.
Alas, modern embedded screens (ex: NewhavenDisplays) are either SPI (for small screens) or "8080-protocol" (8080 bus-like protocol) on the faster / larger screens and somewhat easily implemented using bitbanging. So VGA is somewhat out-of-date for a hobbyist, the market has moved on from VGA in practice.

> Another a bit more exotic and involved application is a Time to Digital Converter, which can take advantage of the low-level routing inside the FPGA to sample a digital signal with significantly higher precision than the clock (resolutions of 10s of picoseconds down to below 10ps depending on the FPGA).

That certainly sounds doable and not too difficult to think about actually. But as you mentioned, its exotic. I don't think many people need picosecond resolution timing, lol.

Still, the timing idea is overall correct as an FPGA-superpower. While picosecond resolution is stupidly exotic, I think even single-digit nanosecond-level timing is actually well within a hobbyist's possible day-to-day. (Ex: a 20MHz clock is just 50 nanoseconds, and bit-stuffing so that you pass 4-bits of info / 16-time slots per clock tick means needing to accurately measure the latency of 3.125ns level signals...). This is neither exotic nor complicated anymore, and is "just" a simple 80Mbit encoding scheme that probably has real applicability as a custom low-power protocol.

And its so simple that it'd only use a few dozen or so LUTs of a FPGA to accurately encode/decode.

Ex: 0000 is encoded with a 0ns phase delay off the master clock.

0001 is encoded as 3.125ns phase delay off the clock.

0010 is encoded as 6.25ns phase delay off the clock.

... (etc. etc.)

1111 is encoded as 46.875ns phase delay off the master clock.
Morally, because valve is aleaady too big an influencer on the pc space. Financially, because valve doesn't have the the time nor care to performance benchmark every game. Valve isn't much better than Google when it comes to seeking a human review as is.

And user reported benchmarks are the worst metric I can imagine. There is so much work on profiling and inaccuracies among frame counters, I don't want to trust that to some random person on the internet.

>If the average hardware specs can't run that game >=60fps >=90% of the time on any graphical setting then it's beyond fair to give it a "Hardware reports indicate that this game performs poorly" label.

Not really. Framerate isn't everything and I don't think it's a good thing to further enforce. The best selling games still choose to run 30fps and most games running max specs will "perform poorly" by design. That's why most games only give "recommended specs", not specs for every settings.
I'm not sure about that. I think it's more akin to vendoring libraries in a C application by unpacking someone else's tarball into your own source tree.

The overall philosophy is that of AppImage I suppose. Flatpak doesn't really count because you still have "runtimes" that other apps depend on.
Also known as "we want you to use our software, but we can't be arsed to spend a few dollars on a Debian maintainer".
My guess is an LLM-based Siri is right around the corner. Apple commonly waits for tech to be proved by others before adopting it, so this would be in-line with standard operating procedures.
Taiwan isn't a US state as far as I know. The US doesn't even recognize Taiwan as a sovereign state.
There are, broadly speaking, two ways for a tool to become popular. The first is to be really good, and unfortunately that way doesn't work. The second is to already be popular, and that's where MySQL and Git came from. If git weren't written by Linus Torvalds, I'm sure it wouldn't have become nearly as popular.

Git is, per the XKCD, a really neat graph system. There's not much that's special about that, though. Now it exists, we can write another just like it as a programming tutorial. The UI is better than it used to be, that's pretty much the best that can be said about it. But if you know the magic incantations you need to interact with it, and especially if you're using IDEs, it's really no worse than CVS.

The biggest difference between git and MySQL is that the former is solid underpinnings but poor UI and the latter is poor underpinnings but easy to deploy. In both cases, the foibles are well enough known that most folk don't need to worry about them, and and most projects I've worked on would derive no benefit from switching to a different system that's only going to confuse people.

I say this as someone who appreciates the graph, but has occasionally resorted to invoking plumbing directly because I can't work out which plumbing commands would do what I wanted.
> 2,131 years after the war ended.

Edit: But also, that does not answer my question of why Carthage surrendering did not officially end the war.
I’ve had a life long struggle with nose breathing. It manifests itself with very dry mouth at night, waking me up frequently.

At one point I went to a prolific ENT surgeon who wanted to align my septum and remove turbinoid tissue (I’m guessing to fund a recent yacht purchase). Most painful surgery I can imagine and did nothing at all except permanent numbness on the bridge of my nose.

I then discovered the breathe right nasal strips (and cheaper clones) which made a massive difference. In allergy season it wasn’t enough though, and nasal steroid spray does the job (fluticasone propionate or similar). I find decongestant tablets (pseudoephedrine) not very useful unless I’m suffering from a proper cold.

I’ve been wanting to stop using the nasal strips after many years because I noticed it was making my nose puffier looking (slowly stretching the skin out).

In the last year I started reading about mouth taping and tried that. It’s actually really great and way cheaper than the nasal strips. A small roll of medical tape lasts 6 months and I just tape my mouth close each night. I was finally able to give up the nasal strips, but still use the steroidal spray if I need it (but cognisant it can cause cataracts so not something I want to use every day forever).

Anyways that’s my story in summary. Not a single doctor helped me and one even injured me. And in the end a small roll of medical tape is all it took.
> especially when fixing things that were mistakes in the first commit, and would have been committed as part of the first commit with more planning and/or no innocuous accidents?

Follow-up fixes reveal important nuance and implicit assumptions that shouldn't be erased.

As for your other claims of "simply" and "easy", you need only peruse this thread that covers plenty of rebase stories losing entire commit histories and requiring redoes of weeks worth of work to see either it is neither easy or simple.

Edit:
See also this point by point breakdown:
https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md
I don't know about Phorge, but Phabricator is no longer maintained: https://admin.phacility.com/phame/post/view/11/phacility_is_...
But where is the option/link to create a GPT? I can't find it
Rant: An Uncertain World
We live in a messed up society but I believe it is a necessary curse so we know the difference between good and bad.The Goodness stems not from God but from us.We are the creators of morality and we pass that beacon to our future generations.Let us not forget that goal in maximising growth.I have read about horrors of colonialism,the World Wars,the cold war arms race and went through the new cycle of covid ,Ukraine crisis,Post 9/11 and recent the Gaza conflict
The common falalcy we have is we think all event that took place recently are in a vacuum but they are not.Nations dont become corrupted nor
barbaric in a day.
Media simplifies everything in their pursuit of getting more revenue.
Politicians simplify everything in their pursuit of power.
But we all must carry that beacon of light with courage without being influenced by wrong sources and when the times come, pass on to the next Generation in hope that they are better than us.

P.S:I wrote this because I am happy on the progress AI is taking and saddened
by the the injustice that takes place daily.I am not a good writer but hopefully this will convey some meaning to someone.
I tried "Scientists create protein that can degrade a common plastic in bottles" as well but I think it's ok to say "PET" even if few people know what it is. It's implicit that it's (a) not all plastics and (b) the article will say what it is.
I think I speak for a few of us AI Doomers here when I say that this makes me excited and terribly anxious at the same time. So... well done OpenAI :). Great news, and a great feature!

I have no doubt that this will immensely increase uptake among the less technically literate, since it will allow the techy people in their life (or on the app store) to introduce them with much less friction. It'll be like the little examples you can find on the "New Chat" screen of every chatbot, but 1000x more engaging
So i guess the next wave of startups has been killed. I'm not even sure what kind of startup still makes sense as a gpt thin wrapper?
I dunno, I've literally never used merge ever since realizing what it does to the commit history.
Every prompt you put in somebody else's LLM goes into the training set of the next iteration of said LLM, with the explicit purpose of replacing you as a cognitively, and therefore economically, relevant entity. The only dignified move is not to play, though it's a very difficult choice. It probably not a winning move, though at this point there are no obvious winning moves -- you and I and all our loved ones will be obsoleted and replaced by tech within the next few years. Concretely, to not play means to stop feeding the machine data, i.e. disconnecting from the digital world. Given how digitalized society is becoming, possibly also from the modern society altogether. Godspeed.
Good improvements for many languages, numbers here

https://github.com/openai/whisper/blob/main/language-breakdo...
I just finished reading Empire of the Sum which is a book telling the history of calculators, and has an entire chapter on Olivetti and the Programma 101. Highly recommend if you're interested in calculators.

https://www.goodreads.com/en/book/show/62585968
Kanzi is a modern, modular, expandable and efficient lossless data compressor
As a very very occasional and light-duty packaging contributor, IMO the best thing Homebrew can do at this point is start writing much better docs for packagers. The Ruby API doc is very difficult to navigate if you aren't already a Ruby programmer. And it's very hard to know what the "right way" is for doing anything, other than browsing other formulas and hoping you land on a useful example.

This is another area where Homebrew has an opportunity to do better than the alternatives.

Making it faster wouldn't hurt either, but that's another story ;)
It's a language model. You don't expect your car to fly.
When I was house hunting I saw a house built in the mid-90's that the range vent vented into the kitchen. They did a lot of deep frying and every surface besides the counter was coated in grease.

Like I can understand it not being required on existing houses from years earlier but how was a house built in the 90's with that...

Also seen ones that vented to the attic with pretty gross results in the attic too.
> Your access to custom GPTs isn’t ready yet. We’re rolling this feature out over the coming days. Check back soon.

> Go to ChatGPT

Sad. Have a real-world use case ready to go and a plus account.