pushcx

There's a couple dozen at Midewin, too: https://www.fs.usda.gov/r09/midewin/animals-plants/bison-pro...

It must be part of a larger marketing push; their boss(?) appeared on the Odd Lots podcast a couple days ago to talk about this work: https://podcasts.apple.com/us/podcast/scott-kupors-new-plan-... He spent a lot of time promoting this new National Design Studio's attempt to attract tech works for 2-year commitments to drop into existing orgs, which is basically how the 18F PIF program worked before it was dissolved earlier this year. Perhaps abruptly terminating a program to reinvent it from scratch six months later is very efficient.

18F: https://en.wikipedia.org/wiki/18F Overview of the related programs: https://willslack.com/pif-18f-usds/

(A warning about Odd Lots: the hosts never question or push back on people talking their book. This especially bad with politicians and political appointees, who are often very creative during their interviews.)

The scrapers will not attempt to discover and use an efficient representation. They will attempt to hit every URL they can discover on a site, and they'll do it at a rate of hundreds of hits per second, from enough IPs that each only requests at a rate of 1/minute. It's rude to talk down to people for not implementing a technique that you can't get scrapers to adopt, and for matching their investment in performance to their needs instead of accurately predicting years beforehand that traffic would dramatically change.

Asking as a newbie in this area, could you share any pointers to language design for performance?

I'm aware of the early difference between compiled and interpreted languages. Luau has to be interpreted to meet its security goals, and I'm asking with similar goals in mind, so I guess I'm starting from that significant limitation.

The answer to all your scenarios is yes. There is no amount of free labor someone can give away that entitles the recipients to more free labor.

> The idea is that users were relying on a functionality to be maintained (the "rug"), and the Datastar developers decided to continue maintaining it behind a paywall (the "pull").

Why were the users so entitled to free ongoing maintenance that its end is worth describing using a term from financial fraud?

It's also getting a lot flakier. Around October or November of last year I realized that every week I see another bit of SPA jankiness. I lose my scroll position because some component has appeared or disappeared above view. The issues list shows hours-old state and does not refresh. A button doesn't work. A page loads but everything below the header is unstyled. I expand the build details but it collapses closed every time a stage finishes. A filename header appears twice. New comments don't appear. On and on.

It's very frustrating to have a tool that has spent 15 years fading into the background of reliable infrastructure become an intrusive, distracting mess.

After a couple months with jujutsu it's almost completely replaced my use of git. It’s a lot to hope for, but just as jujutsu surveyed a couple decades of VCS to syncretize a huge improvement, I do hope someone will do the same for collaborating with jujutsu. GitHub PRs feel very unfortunately frozen in amber because their popularity makes it very hard to fix the core UI design problems it has with multiple tabs, incoherent timeline, edited commits, missing "8 more comments", and now a steady drip of SPA jank.

The big remaining feature of GitHub is the network effect of coworkers and potential contributors already being logged in, and there could be a race between a competitor neutralizing that with bidirectional sync (see git-bug) and GitHub getting their usability problems sorted. Microsoft's legendary resistance to breaking changes means there's a very big window available.

Yep: https://github.com/bishopfox/unredacter

Could anyone who runs Rails with sqlite in production share some scale numbers like r/w per second, # rows in the db, and vps size? I have used it at trivial scale for SolidQueue and SolidCache, but I can't find experience reports for the primary OLTP db.

Incredible missed opportunity to cite the parable of the broken window: https://en.wikipedia.org/wiki/Parable_of_the_broken_window

I remember XBConnect and GameSpy for playing Xbox Halo 1 over the internet. I think a couple were invented for every big game or console before 2010 or so.

Tailscale doesn't really address connecting to strangers, though.

You know, you've told me that about views and components before, and I keep forgetting. I am so used to getting burned by software that has two names for things because a couple months or years later, ah yes, now that you mention it there is this one tiiiiny distinction that happens to be why the app is on fire now.

It would be great if you could expand your explanation of the metaprogramming into a comment in the code. When I read it, I didn't immediately recognize the technique and its tradeoffs, so it seemed like an odd decision rather than an informed one.

Having two versions of phlex would be a strong negative to me. I don't like to see dev teams spread themselves out, it's one more choice I'd have to make when adopting, if switching between them I have new risks that they've slipped out of sync in some way, and it's altogether another odd decision that has to be explained.

What I was trying to say about the code is that I share the previous commenter's experience of "welp I guess if we want that bug fixed we have to click 'fork' on github... while we write up our plan to migrate away". Having had that experience several times, Phlex looks like an acceptable risk.

The thing I really like about Phlex is that it's not a full DSL, it's not its own language. It's an expressive Ruby API and the resulting code has the regular Ruby toolbox available. Ruby devs often call this a "DSL" and I lean away from that use of the term because I think it adds confusion in situations like this. But Phlex feels like a breath of fresh air because it's composable, testable, "just ruby", and has a lot fewer opportunities to footgun myself.

I agree on your criticisms of Erb and ActionView. I'd add that Erb is just really noisy jumping in and out of Ruby with <%= %> constantly. I'm regularly running down basic errors in producing well-formed HTML.

I'm still only experimenting a little with Phlex. I'm not sold on some of its design like the distinction between views and components, but maybe that's a practice/docs issue. I'd also like to see a performance test that's not a microbenchmark and I may try to make one this month. Similar to your note about haml, I've told the project devs that I'd be really encouraged by a phlex -> erb tool to reduce the perceived risk of getting locked into the dep.

EDIT: Oh, and I read the phlex code because I have similar experience outliving a dep. The library is ~1,600 loc with same again in tests. There's a little metaprogramming in SGML::Elements I dislike but it's not a dealbreaker. The library is small and straightforward enough that I'd be surprised if it broke without going unmaintained 5+ years, and I'd be fine maintaining a private fork for a year or so while migrating off.

In addition to the "you're not fooling anyone" bit about piercing the corporate veil that's already well-addressed, you missed provisions of the OSA.

There's a requirement to name a senior manager: https://www.legislation.gov.uk/ukpga/2023/50/section/103

There's personal liability attached to being the named senior manager: https://www.legislation.gov.uk/ukpga/2023/50/section/110

Other nearby sections have additional personal liabilities. Like Sec 109 (5) (a) probably criminalizes your exact suggested response of walking away from Ofcom's inquiries: https://www.legislation.gov.uk/ukpga/2023/50/section/109 It depends on the legal definition of "permits the suppression of... any information required". We'd have to hire a UK lawyer for a confident answer.

All this is a couple sentences in the law. The law is 250 pages long. Ofcom's guidance was rounding 3,000 pages the last time I counted.

If you want to understand the OSA, I think the most accessible and valid writing available is by Neil Brown: https://onlinesafetyact.co.uk/ There's a lot developing as Ofcom continues to publish new rules and ignore questions, so I suggest reading the 'Replies' tab of his fediverse account.

They block numbers from any provider considered to be voip.

A useful term here is "labor share" and the included chart of the last ~80y: https://en.wikipedia.org/wiki/Labor_share

And then when I pan the map, maybe 90% of the time it doesn't load new results for the visible area. It makes Apple Maps pretty unusable for finding things in unfamiliar areas.

(I'm the Lobsters admin.)

Comments from merged stories do have a label showing where the came from... but only before the merge; afterwards top-level comments are always attached to the primary story which is when things get especially confusing.

For this and other reasons, I'm in the middle of revamping UI for the feature and the database model: https://github.com/lobsters/lobsters/issues/1456

If anyone is real curious about the fine details, I've done almost all of this feature work on Lobsters office hours streams: https://push.cx/tags#story-merging I plan to continue that work in about four hours on today's stream so it's a great time to ask questions: https://push.cx/stream

As a (much) smaller community, story merging has been valuable for allowing us to build the critical mass of a good discussion. We also avoid rehashing the basics/easy misunderstandings. It's a pretty similar to dang's motivation about wanting to promote novel discussions. I have joked for a couple years that I'd love to see HN copy the feature so that HN can teach everyone how the feature works.

This is pretty much the premise of Bob Altemeyer's work: https://en.m.wikipedia.org/wiki/Bob_Altemeyer His book The Authoritarians is the one that most elaborates on it, so works that cite or respond to it would probably be exactly what you're looking for.

I don't have a lot of mental model for how this works, but I was surprised to note that it seems to maintain continuity on the shapes of the bushes and brown spots on the grass that track out of frame on the left and then reappear as it pans back into frame.

Yeah. It's fairly likely the ads link to a URL with a recognizable pattern. Failing that, if an ad is reproducible we can iterate with a site owner to detect the DOM modification a few different ways. I've drafted a blog post to collaborate with others on reverse engineering this: https://push.cx/google-ad-injection

Does anyone have a reusable signature for the injected ads so a side can detect the tampering?

Yes. Mercury, which is not a bank and has never publicly claimed that it plans to become a bank, is reportedly trying to recover $30 million in missing customer funds from Synapse: https://www.forbes.com/sites/emilymason/2023/12/20/with-syna...

I've held a (trivial) business account at Mercury since before Synapse collapsed. Mercury has never attempted to notify me about missing customer funds, potential customer losses, or the lawsuit stemming from the collapse of their banking partner.

This article mostly talks about full-time recruiting, but a friend recently went through this while getting recruited to the reserves. One purpose of the reserves is to allow the military to hire mid-career professionals with specific in-demand technical skills.

My friend had used a telehealth counseling service during acutely stressful events and Genesis demanded records that the service couldn't really be bothered to produce. It refused records from the actual doctor. Genesis's nitpicky follow-ups really went poorly with the modern standard for customer service, which is mostly nonexistent outside of billing. The back-and-forth went on for 8 months until my friend gave up.

[Org mode](https://orgmode.org/) is a popular emacs plugin for organizing notes and todos. I don’t use it so I can’t be sure, but the reference to review is [probably this](https://orgmode.org/manual/Stuck-projects.html) about doing a weekly review of one’s tasks and projects, probably in line with [the practice](https://gettingthingsdone.com/wp-content/uploads/2014/10/Wee...) from the Getting Things Done productivity system. [Sketchnotes](https://rohdesign.com/sketchnotes) are an artistic visual summary.

It seems this is excerpts from a video or screenshare. Does anyone have a link for that? I’m curious to see some of the things the speaker refers to.

If one would like to subscribe to a national paper owned by a billionaire who supposedly only interferes with editorial and not reporting, the Wall Street Journal is cheaper.

Google Voice will also be unworkable for your needs. More and more businesses prohibit customers from using anything except a cell phone number from a major carrier or MVNO reseller, perhaps assuming anything else is criminal activity. Customer service agents are never trained about this, so they'll say a number is "invalid" or "voip" (regardless of the actual service used) and cannot be used.

I was curious about the syntax of this signature:

> List.first : List a -> Result a [ListWasEmpty]

I found this section of the tutorial useful (and the preceding example of calling List.get): https://www.roc-lang.org/tutorial#error-handling

The `a` is the type from the `Ok` constructor (similar to Haskell's Left constructor in Either) and the brackets mean "List", not "optional" as in CLI docs, it's a list of types that might be used in the `Err` constructor (similar to Right). So `List.first` either returns `Ok a` or `Err ListWasEmpty`. For a slightly larger example, the tutorial has a `getLetter` that shows two error types.

If the company were to be sued, would you be happy turning over your laptop to your company’s lawyer indefinitely for them to search and find documents that might be relevant to the lawsuit?