skysight-inc/HackerNews huggingface dataset:
The Half Lemons app is available for iOS, and it's the first thing I've built! I'm a product manager by trade, and I learnt to code (Swift) to build HL. Very excited to hear any feedback from the community.
geez, when was this made, recently/now? It's like come on, "dead longer than it was alive"..... there were so many contributing factors to the environment and shifts of the day when it happened -- this endlessly bringing it up shows like so much unawareness of surroundings/history

and also, what other options took its place / fill the void / RSS is not dead! etc
I had a great time with my friends on it. I've never had that much good discussions with my friends about anything since.
They're awesome!

One common use case is REGEXP. SQLite has a keyword for regular expression matching, but it has no implementation for it. What your application needs to do is to take whatever regex library it's using, make (through whatever FFI method it's using) a C function that interfaces with it, and register it with SQLite.

A more advanced feature of this binding mechanism is that, if you provide a bunch of specific callbacks to SQLite, you can expose anything you like as a virtual table, that can be queried and operated on as if it was just another SQLite table.

See: https://www.sqlite.org/vtab.html. The plugin for full-text search is implemented in terms of this mechanism.
It was in the summer of 2008, three years after Google launched Reader and had at least 5 million users, when I decided to write my own RSS reader. There were just so many features I wanted that I knew Google would never build and for some strange reason I thought I could make money with my own opinionated take on a news reader.

Then at 4pm on March 13th, 2013, I got an email from Nilay at The Verge asking if I'd heard the news. That was a difficult month as I scaled (and wrote about scaling[0]), since by then Google Reader had 10 million active users. After Reader was sunset, about 5 million found their homes on the news readers that remained.

It's strange to think that naively competing with one of the big platforms paid off, but there's plenty of companies that did well in the wake of a giant choosing to ignore the ecosystem near their feet.

[0]: https://blog.newsblur.com/post/45632737156/three-months-to-s...
Everyone has to do paperwork, but is that 'admin overhead' it an essential part of safety culture? I'm struggling to see where the overhead is that significant.

It is a lot more obvious in other fields -- medicine and highly regulated/litigious professions.
I find https://feedbin.com/ almost identical (Feedly feels a bit too different for my liking, but is clearly the most popular) but it also feels like times have moved on and I don't find myself using it in the same way. The blogosphere isn't quite what it was back in the late 00s.
Newsblur also lets you subscribe to YT channels, which is much nicer experience than YT's own way of handling subscriptions
No more drama. Emacs + elfeed is the savior
"They told me computers could only do arithmetic" is attributed to Grace Hopper.
Hmm, I haven't read that book this millennium, but I had thought I first encountered the quote in The Practice of Programming. Which, I mean, I also haven't read this millennium, but when I did read it it was after The Elements of Programming Style. I guess I should check...

It turns out that it is in The Elements of Programming Style, on the second page of Chapter 2, "Expression", in the second edition:

Suppose that you were trying to teach a novice programmer how to count the blanks in a string. How would you do it? Surely not by this elegant but mystifying method [omitted] — instead you would say “Look at each character, and if it's a blank, count it.” Or, in PL/I,

DECLARE TEXT CHARACTER(200) VARYING;
GET LIST (TEXT);
N = 0;
DO I = 1 TO LENGTH(TEXT);
IF SUBSTR(TEXT, I, 1) = ’ ’ THEN
N = N + 1;
END;
PUT LIST (N);

This too uses the built-in functions PL/I provides, but it uses them in a way that clarifies the method of solution, rather than obscuring it. Everyone knows that debugging is twice as hard as writing a program in the first place. So if you're as clever as you can be when you write it, how will you ever debug it?

I think this is, if anything, truer now than it was in 01978 when the book was published, even if not many of us have to deal with PL/I nowadays—thanks, in significant part, to Kernighan's efforts. And it's probably thanks in part to reading this book that today I would more likely write that as

sum(1 if c == ' ' else 0 for c in text)

or

sum(1 for c in text if c == ' ')

or

(loop for c across text if (eq c #\space) sum 1)

rather than

sum(c == ' ' for c in text)

which also works.

Being too clever is what almost always trips me up in Forth. It's not so much the stack-effect bugs or the type
errors themselves, although of course those require more
care to avoid than in C; it's the constant temptation to
bum the code down to something smaller and simpler by, for example, keeping more crap on the stack.

I think I did manage to use Forth effectively and avoid being so clever in, for example, https://dercuano.github.io/notes/forth-assembling.html#addto....
Sophomoric Parallelism and Concurrency
When using an external db every query needs to cross the connection boundary and thus perform network IO and deal with the threading implications for that IO. With SQLite running in-process a round trip just means a function call, and when data is available in the cache it won’t even hit the disk.
Elon's tweet looked satirical to me, especially in context, but it was a stupid thing to post. Anyone who looks over Elon's twitter can see that he constantly trolls and posts stupid shit.

That being said, it was a really dumb thing to post. Twitter seems to be where the rich and powerful make asses of themselves.
I think that the majority of people chuckled and moved on. The people who were, for whatever odd reason, perturbed or galvanized by the amusing little article compose the group that self-selected to comment.

I think this is a peril of reading the comment section before checking out links. If it's not worth talking about, you'll only find unhinged or pedantic conversations about it.
> So I could subscribe to a feed in Google Reader, then use a 3rd party app (like Reeder or any number of others) to view the feeds I was subscribed to, and it would provide all the tracking and syncing so to speak.

Can you explain what this means? What's involved here? How does it differ from dumping all your RSS feeds into an ordinary RSS reader?
Actually, that project still has the nostalgia Reader interface online: http://readerisdead.com/reader/view/#overview-page
Seems to me like it's a matter of gauging the other person's willingness to change their mind (an admittedly difficult task in itself). If there is no argument or evidence that you could present which would be good enough to do so, the entire conversation seems to be pointless and it's probably best to just walk away. If they are in fact open to being proven wrong, doing so politely may still not work (i.e. they may be able to counter any point you make), but the odds are better than if one does so rudely. All other things being equal, we're more likely to be persuaded by someone we like (or at least are neutral toward) than someone we dislike.
Probably not affected since this bug was introduced after version 1.0.1 that is the version where the fork happened.

> Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check.

> An error in the implementation of this check meant that the result of a previous check to confirm that certificates in the chain are valid CA certificates was overwritten. This effectively bypasses the check that non-CA certificates must not be able to issue other certificates.
I just noticed this feature in Plex on the PS4 recently (it only shows up when you pause, so I'm not sure how long ago they pushed it in there). It's surprisingly handy!
Smells like computer generated text, GPT-3, anyone?
I guess I've lost track of your point. You were trying to suggest cars don't phone home, based on your experience and assumptions, but the fact is that nearly all major manufacturers are selling cars today with systems that phone home for various reasons, whether you're aware of it or not. How does you not knowing anyone with new cars meaningfully inform this thread? The manufacturers are becoming aware of privacy issues, and trying to make some kinds of collection and access opt-in, but basically all of them now offer some services that phone home by default and are opt-out or not optional. Hopefully that data is reasonable and private and protected... hopefully.

A lot of consumers (I would guess most) prefer to have default-on connectivity to provide services like theft protection, automatic emergency support in case of accidents, and up-to-date navigation maps, among many other modern conveniences.
I maintain a corp Ghost blog that's backed by SQLite, it's been solid for years.
What Science Forgot About Airborne Pandemics
>so I have a bunch of links some of you might find interesting if you want to dig further

oooh, thank you! I'm starting to see SQLite the same way!
Was a huge disappointment when google made a decision to close it. I remember lots of services appeared pick up the audience. I switched to BazQux back then and still using it (bought lifetime license after several years and enjoying it every day).
Shout out to https://bazqux.com, a modern Google Reader replacement and the only SaaS I pay for. I'm not affiliated, just really love it. It's been solid and awesome for me for over 7 years now.
> Is it supposed to reflect the simplicity of a back-to-nature lifestyle and the characters therein?

I'm inclined to suspect is the latter of the two; especially if kana is only employed in character speech while other parts of the game use Kanji.

This, but it’s the other way around. When characters speak to the player, who exists outside of the game world, it is in a mix of kanji and kana. When they write within the game world, it is in kana only.
That's my point? Unless there was a typo in your response? In this case, the shooter's name has a very distinct cultural connotation attached to it that would indicate non-whiteness.

I'm not even white, but it seems to me that there is a very concerted effort by the media in the United States to push a race angle on everything, with whiteness being specifically stigmatized.
https://go.dev/solutions/google/ lists three Google projects
I thought they started going to hell when they had that botched too-early integration of (resource-sucking, to add insult to injury) PulseAudio, in... '08? '09? I remember it was back when Flash was still big, and opening Flash content on that Ubuntu release would, IIRC, crash X, reliably, because of PulseAudio, in addition to its general bugginess, lots of audio stuff that had "just worked" for years suddenly being fiddly and broken, and absurd levels of memory & processor cycle use for PA (I'm not sure whether PulseAudio ever got those under control, or we just started using faster computers so no-one cares about the audio subsystem sucking up tens of MB of memory while idle, anymore).

Flash was still big enough that there's no possible way they didn't know they were crashing with it. Zero chance no-one at Canonical had tried it, and discovered the problem. Released it anyway.
I can't and don't blame tramp, per se. My internet has regular hiccups of being completely disconnected. Pretty sure that is not fixable. :(
I see your point. "... sounds like a catchy slogan" would have been nearer to what I meant.
I'd expect this to be unnecessary in WAL mode (which you should use, when possible), since WAL allows concurrent readers while permitting up to one writer. In the old undo-log mode (which remains the default for compatibility) writing excluded readers.
There were multiple options you could migrate your feeds to when it was shutdown. So I wouldn't say "no competition", but more some specific features that the competition didn't have.
PostgreSQL is not a toy database. MySQL is not a toy database. I feel like the "toy database" part is clickbait
I have not much idea of web dev, although I'll probably learn by myself react and node for jumping careers. Preact looks like a tiny lib I could use to train myself, thanks for the reference.
> the poor would be taxed proportionally the highest

No, they would be taxed proportionally the same. You're starting from the assumption that income is what should be taxed. Income comes from productive activity (labor or investments) and is what you want more of, not less.

> and the richest few percent would love this as their proportion of income that goes on consumption is the lowest.

And what is happening with the rest of the money? It's being reinvested, which is something you want in society.

At the end of the day, the money is only ever used/enjoyed personally by rich (and poor alike) when they consume.
Ronalds Vilciņš did his homework. He also gives Stroustrup's original quote.
Lockdown Dad Project: An AR Donut Hunt
The United States was the first country to approve the Moderna vaccine. If the US "wasn't able to use it" then neither was any other country.
>It seems to me that a lot of Americans have adopted the heuristic that all good Covid news is a trick to get people to "half-ass it", and see relentless negativity as the only responsible posture

I've noticed this as well among many in my social circles. Every time I discovered some new scientific study which helped to dispell some degree of the FUD surrounding covid, the people who had adopted that heuristic always responded with more negativity and FUD, and never relief.

A great example of this was how early on, when looking at data from Italy, there was FUD suggesting that the death rate could be 10-15%. When more data was collected which dispelled that great fear, Fauci said "It’s a false narrative to take comfort in a lower rate of death".
Good question. I found this, release 17-03-2021, that seems to be the same bug. So yes, they had the same vulnerability.

https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.2.5-...

Update: AAAACHCHC!! Dates! Always the dates. OK, Very well. For your viewing pleasure:

* Americans: Patch was released on 03-17-2021

* Europeans: Patch was released on 17-03-2021

* World inhabitants: Patch was released on 2021-03-17
I've been running a Twitter account hoovering up and regurgitating such things for the past ten years as well: https://twitter.com/codewisdom
Interesting! Do you need Apple's permission to write a kernel module? Have you tried running this kind of instrumentation on Linux on M1?
Well, perfect inefficiency would be 50%, right? Assuming standard routes / no repositioning. I.e. towing an empty back for every container you shipped full.

I have no idea what percent is needed to cover repositioning, but 20% sounds decent. Especially for a dynamic demand system (little ability to micro forecast flows).
This is a good point. However, I'm sure if you presented proof to a venue that you already have a large number of paying showgoers ready to see you in this city if you perform in the near future, convincing the venue to book you will be much easier than just an estimated head count or trying to use the numbers from your last area performance.

We're planning on working assistance to cover the venue/promoter costs as well. So given that the demand is high enough for the performer, I don't see why the venue would turn them down if they could present info like this.

Thanks for the feedback btw!
SQLite: The Database at the Edge of the Network with Dr. Richard Hipp
https://www.youtube.com/watch?v=Jib2AmRb_rk
"To make sure you can minimize the impact of our single-homed loadbalancer being down"[1]

Interesting. I'm surprised that's how their CDN works.

[1] https://answers.netlify.com/t/support-guide-minimizing-impac...
Majority of Commuters Say They Only Feel Safe in Single-Occupancy Vehicles
Huh? SQLite is public domain.[0] There are paid extensions for encrypted and compressed databases[1], but those cost a flat fee for unlimited devices:[2] "Your license is perpetual. You have paid a one-time fee that allows you to use and modify the software forever. You can ship as many copied of the software to your customers as you want so long as you ensure that only compiled binaries are shipped (you cannot distribute source code) and that your customers cannot make additional copies of the software to use for other purposes."

[0] https://www.sqlite.org/copyright.html

[1] https://www.sqlite.org/prosupport.html

[2] https://sqlite.org/see/doc/release/www/readme.wiki
I disagree. Gnome3 for me is perfect. I think tastes are tastes but gnome 3 gives me the function as well aesthetics.

The zoom out functionality to show all windows open is essential given i have a lot of windows open at the same time. Alt-tab icons are a huge cognitive load.
Also because killing Google Reader single handedly killed a bustling and fast growing RSS based ecosystem.

Google Reader was the first RSS client to incorporate social features with RSS. To that it added an extremely fast web client (I can't think of any web client that even existed before), and syncing across devices.

A LOT of software in the RSS ecosystem relied on Google Reader for their syncing capabilities. It had basically become the defacto backend for the majority of RSS readers. As an example, I used NetNewsWire for my RSS reading, and while I rarely (never?) used the Google Reader interface, NNN relied on my Google Reader account to backup and sync my feeds.

Google Reader had basically become essential infrastructure in the RSS ecosystem.
The social features were actually killed off before the product itself: a few years earlier they did a redesign which removed all of the social features. The social features were cool, I remember following a couple of journalists i really like who commented on the articles and discussed it with each other, it was a really nice thing.

The reason people are so bitter is that Google Reader was the kind of thing that if you liked it, it became part of your daily routine. It became the thing you checked in the morning over coffee, the thing you checked when you were procrastinating at work. Today that is social media, but Google Reader really felt like your own little curated space in a way (say) Twitter does not: with Twitter, you always feel at the mercy of The Algorithm. It also was essentially totally free of the toxic stuff you see on social media today.

They took this cool and personal service, ripped all social features out, did zero development on it for years, and then unceremoniously killed it in some insane attempt to make Google+ into the next Facebook. I'm still pissed about it, and it was the last time I've ever made myself rely on a Google Service like this.
I also enable march=native for the compile. My guess is it is mostly placebo, but I feel it helps.
That's right. Also, as with most hierarchical engineering teams, the senior engineers are expected to push the boundaries of a project and define new stuff for the junior engineers to work on. However, the senior engineers might not care about growth anymore and end up maintaining the status quo. This could hamper the growth of the junior engineers on the team.
I see availability as orthogonal issue to scale/size. You might be processing one transaction per day but it can still be super important that the service is available for that one transaction.
If I recall correctly it didn't have a dock. Everyone seems to have settled on the dock being the best paradigm for managing open apps, and launching favorites, for most users. You might disagree, but the ux people at Apple, Microsoft, Google, Gnome, and KDE seem to think it's the best approach for the vast majority of users.
> You'd still end up with the middle paying proportionally a lot more than the wealthiest.

Again, everyone ends up paying proportionally the exact same on what they personally benefit from: consumption.

What isn't consumed regardless of income goes back into circulation in the economy via investment.
Judging by your downvotes with no replies, the typical HN user finds your post much more worthy of suppression than RMS' pro-child-sex comments.
Complaining about Google killing Reader and Google's monopoly power in the same page is strange. Actually killing reader made Reader competitors the chance to develop, didn't it?

I think there was a trend for content providers to share content on multiple platforms directly instead of with RSS, that's what people may not like.
I agree that high availability features are outside of the goals of an embedded database. There's an ecosystem of tools SQLite to provide these benefits though. There's dqlite & rqlite for providing HA over SQLite. I'm the author of Litestream[1] which provides streaming replication to S3 for SQLite databases so folks can safely run a single node instance.

[1]: https://litestream.io/
Masks don’t help for privacy, and already privacy advocates are becoming aware of this. The extensive networks of surveillance cameras in e.g. Russia and China are now able to identify people wearing masks – this was recently used in Moscow to go to the homes of masked demonstrators a couple of days after the protests and arrest them there, for example.

Modern surveillance software can draw on things like gait analysis, the person’s mobile phone’s IMEI, and tracing people’s movements around the city in order to identify people even if they are masked.
On the performance/stability of Elisp front, I just heard about remacs, which is a fork that's starting by porting all the C to Rust: https://github.com/remacs/remacs

Still in early stages, but I think that's one to keep an eye on.
Stitches in Time: 100 Years of Machines and Sewing
In retrospect Reader's death marked a turning point in how Google was perceived. There were grumblings before that but Google was still the darling of the web.

As you say, Google+ was consuming Google at that time. So when they killed Reader it was not just killing a beloved service. It also acted like a lightning rod for the discontent that had started to swell. A lot of people would never again view Google through a rose tinted lens.
Boghossian never says anything about 'revealing the truth' in that block of text, he merely expresses concern about what's being taught in the university classroom. Please do not misquote people like that.
It depends a bit on what you do and use. If you primarily use a terminal, Firefox and thunderbird there isn't much of a difference between those. Yeah, taskbar etc look a bit different but not much.

If you switch between KDE and Gnome apps (kedit vs gnome-edit, kmail vs gnome evolution, KDE dolphin vs. Gnome nautilus, kmines vs. Gnome mines game ...) you see more of the differences in App Design principles.
Think of Google Reader as a 3rd party sync API, and a variety of tools use this API.

lets use Twitter as an example.

Google Reader is Twitter with their API

Reeder (or your RSS reader with support for the API) is like Tweetbot.

This isn't a great example, because read status of feed items and all that is handled by Google Reader. But it's close.
>> Literally just listen to the women who have had to work along side him on the MIT campus for decades.

I would like to listen to what they have to say. This is the first I'm hearing of this, and I've been following RMS and the FSF since their inception. The term "dealing with it" is too vague - are we talking sexual assault, sexual harassment, or RMS being difficult to work with? These are dramatically different scenarios yet they all require a means for "dealing with it."

I'm taking you to task because you're now crossing the line from things RMS has said to things he may have done. If you're going to accuse RMS of sexual harassment then you're going to need to help bring this to light, not just spread hearsay. His alleged victims deserve that and the free software community needs to know the details of any alleged misconduct.