pokoleo

They sent an email a few minutes after I posted, saying that their fulfillment centre dropped the ball and they're escalating internally. I guess complaining on HN worked.

Hope they can figure out the dispute with Rebble. Maybe they end up hosting apps on a package manager and create some binding contract?

Summarizing the dispute, for anyone interested:

Rebble's "one red line" is "there has to be a future for Rebble in there." They fear being replaced/made irrelevant after Core builds their own infrastructure using Rebble's work. They want guarantees that if they give Core access to the app store data, Core won't build a proprietary/walled garden that cuts Rebble out. There's also emphasis on "our work," "we built this," "we spent hundreds of thousands of dollars." They feel Eric isn't acknowledging where his infrastructure came from.

Core Devices' thing is explicitly stating concern about relying on a third party (Rebble) for "critical services" his customers depend on. If "Rebble leadership changes their mind," they can't guarantee customer experience. They wants the app store archive to be "freely available" and "not controlled by one organization." They don't want to need "permission from Rebble" before building features (like free weather, voice-to-text) that might compete with Rebble's paid services. The fundamental fear seems to be business risk: being at the mercy of a nonprofit's decisions when his company has customers and obligations.

Neither side seems to trust the other's long-term intentions, creating an impasse where both feel existentially threatened by the other's preferred arrangement.

My take: I bought a watch in 2014. After the pebble 2 duo black fiasco (they ran out of stock, offered a white instead which I accepted 2 weeks ago, never shipped, and have ghosted my emails asking for shipping timelines.) I had high hopes, but given the messy interaction with the OSS world I'm considering cancelling my order for the duo and time two.

From my experience working on SaaS, and improving ops at large organizations, I've seen that "on-call culture" often exists inversely proportional to incentive alignment.

When engineers bear the full financial consequences of 3AM pages, they're more likely to make systems more resilient by adding graceful failure modes. When incident response becomes an organizational checkbox divorced from financial outcomes and planning, you get perpetual firefighting.

The most successful teams I've seen treat on-call like a leading indicator - every incident represents unpriced technical debt that should be systematically eliminated. Each alert becomes an investment opportunity rather than a burden to be rotated.

Big companies aren't missing the resources to fix this; they just don't have the aligned incentive structures that make fixing it rational for individuals involved.

The most rational thing to do as an individual on a bad rotation: quit or transfer.

Needs (2015)

Wouldn’t be the first. See also Ecuador, El Salvador, Panama, and Bonaire (to name a few)

The usual answer to a DDoS from some users is to add rate limiting, not “remove the service”

I've been using Colemak for a little bit more than a decade now. Super happy with it.

I switched while interning at a ~failing startup. I was a Canadian in the US, and had forgotten to plan to do stuff over Thanksgiving weekend. I had nothing to do, so I switched to Colemak over the weekend. I spent the weekend doing typing training videos, then spent the remaining ~1mo of my co-op term working (almost) entirely in Colemak. I wouldn't switch back to qwerty without a really compelling reason.

Years later, I'm super happy. I can use QWERTY under duress, but rather not.

It's a nice way to say "Hello there :)"

Can you cite a source on the Japanese connection? I don't see anything obvious in their Wikipedia pages.

* https://en.wikipedia.org/wiki/The_Economist

* https://en.wikipedia.org/wiki/The_Economist_Group

I do see Exor (Agnelli), Rothschild, Cadbury, and Schroders families, but nothing clearly Japanese, nor Japanese far-right.

I once interned at an easily google-able Secondlife competitor. They fought against NSFW content for a long time, but then figured out how to fix it by:

1. Incentivizing users (with in-game currency) for reporting NSFW content, and 2. Restricting NSFW content to only people who bought an all-access pass (ID verified at time of purchase)

This opened up a new revenue stream for the company, and dealt with the NSFW content in one swoop.

Soft deletion always feels at odds with privacy-related "right to have data deleted" laws.

Would be super interested in a technical writeup on how they do this.

Will's a great communicator, and quite personable: I know this because I've worked with him for a few years. I don't think it's bravado, SRE is a common industry term.

@dang: here's a better version without scroll lag

https://citizenlab.ca/2022/04/catalangate-extensive-mercenar...

I've been wondering: if this robot is only flipping fries, could it be made by putting the basket on a simple track, and adding an actuator to move the basket along a track? Why need an arm?

My speculation: a robotic arm makes for a great press release. Actuator + track feels like a factory.

Does "tightly coupled with the database" work, in practice?

Interesting! Do you find that returning an array of errors works in practice?

Most validation I’ve seen looks like:

    raise error if foo
    raise other_error if bar

This pattern turns into one exception per response, and some foresight in architecting exceptions would be needed

The article is about REST API design, not JSON APIs! It’s a whole different ballpark.

The error messages could be better yet.

The example uses a different code per issue, for instance: "user/email_required". Most integrators will build their UI to highlight the input fields that contain an error. Making them parse the `code` field (or special-case each possible code) is pretty toilsome.

    // from blog post
    {
        "code": "user/email_required",
        "message": "The parameter [email] is required."
    }

Make it parseable:

    // improved
    {
        "message": "An email is required.",
        "error": "missing_parameter",
        "parameter": "user.email"
    }

In addition, I:

* rewrote `message` to be an acceptable error message displayed to (non-technical) end-users

* moved message to be the first field: some developer tools will truncate the JSON response body when presenting it in the stack trace.

---

As an added bonus, structured data allows you to analyze `error` frequencies and improve frontend validation or write better error messages: https://twitter.com/VicVijayakumar/status/149509216182142976...

Major difference in Canada is the # of banks. The big five dominate[1] unlike in the US where there are 100+[2]

[1] https://en.wikipedia.org/wiki/List_of_banks_and_credit_union... [2] https://en.wikipedia.org/wiki/List_of_largest_banks_in_the_U...

It is difficult to get a man to understand something when his salary depends upon his not understanding it. -Sinclair

Once as a new grad I asked (after he gave a talk on the virtues of oss) why the newly released Wolfram language wasn’t open source.

He called me naïve, said that my question was childish, then asked for the next question.

If dunking on a 23 year old makes him feel good about himself, so be it. I couldn’t imagine working anywhere near him.

I wonder what he does behind closed doors.

Some smart TVs already ship with sim cards. It just requires a deal with AT&T/Tmo/etc.

NFTs

@dang: can you change the title? Simple typo meterorite → meteorite

You should use cointracker: https://www.cointracker.io/

If you want to DIY instead, I think it's an invocation of wikihtmltopdf + a simple script that turns CSVs into PDFs.

For anyone looking to rent a car, I'd recommend using autoslash.com

It's an aggregator that allows you to pick from the other aggregators, and you don't pay until you pick up.

The prices are consistently within 10% of the lowest price that I can find online.

You fill out a simple form (pickup/dropoff times/location, car preference), and it emails you quotes. They don't spam me, which is nice.

I tend to request the same quote multiple times over the weeks before my trip. It'll frequently find you something for less than what you initially paid for.

Ignore their janky UI, it's the real deal.

Yet another case of competing standards

https://xkcd.com/927/

CRT displays and floppy disks