HN user

crescentfresh

722 karma
Posts0
Comments263
View on HN
No posts found.

Right. Unfortunately their right to request increases was removed. The exact wording: “Based on your service usage history you are not eligible for quota increase at this time” and then dead ends trying to reach someone.

They had billing accounts set up for all their projects. They were happy to hand over money but had no ability to.

Anecdotally, I know a paying GCP customer that recently got quota blocked on the number of global static IPs they are allowed to create. We could not figure out how to contact someone to increase it, and nobody knew why the quota was set so low (4). We just kept running into automated systems that gave circular information on how to request an increase. We kept getting links to sign up for a free tier account.

I feel like you inadvertently confirmed the authors point. In your “complicated” example, in order to visually show the baseline after rebase you removed the earlier C3, C5, C7 and C9 commits. But the authors point is that merge commits just need better tooling that can make it clearer what the baseline is!

I showed an interviewer a piece of something I built in a traditional page-per-view design, with some xmlhttprequest where appropriate, and a sprinkling of Vue where it added usability to some of the modal dialogs. Their only response was "why didn't you build it in React?".

I stopped interviewing for front-end work since then. The landscape changes frustratingly too often.

Okta Outage 5 years ago

Now that Okta bought Auth0 what's the developer experience like I wonder? I imagine the infrastructure of the two products are still completely isolated. But is it still a separate product you can use for identity management or are new customers forced to use Okta?

The majority of our errors stem from:

- writing to Firehose (S3-backed)

- publishing to eventbridge

- terraform commands to ECS' API are stuck/hanging

Other spurious errors involving kinesis but nothing alarming. us-east-1

Our local development environment has evolved to a complex enough sequence of steps to set up and troubleshoot that I spent 2 weeks creating tooling that you can simply point at source checkout locations and the tool will take care to setup that repo.

It broke on the first try on a jr hire's machine, the source checkout location was `C:\source code`.

Audit tables are awesome, this technique is great. We had one additional requirement that got us away from using a trigger for this: we wanted to know what user (in the application) caused the change. So we moved the logic of "insert into audit_table" into the application code itself using a CTE, roughly translated as:

    with affected_rows as (
        insert/update/delete into/from ...
        returning *
    )
    insert into my_audit_table
      select @op, current_timestamp, @userinfo, * from affected_rows
where @op is bound to one of "insert", "update" or "delete" and @userinfo is the user(name|id|various|etc) of the user that caused the change.

A big downside of vanilla database/sql or pgx is that SQL queries are strings

What's wrong with strings? The argument in the article is that they cannot be compile-time checked, but I'm confused as to the solution to that problem ("you need to write exhaustive test coverage to verify them"). Is this saying that if they weren't strings you wouldn't need test coverage?

Craftsmen who are willing to do a small job for me are so hard to find right now, they're busy enough NONE of them in my area need the business. Every quote I get is either overblown "to make it worth my time", or I simply get declined. Ontario, Canada.

OBS Studio 27.0 5 years ago

This fixes the black screen issues on laptops in particular

My youngest wanted to learn how to use OBS so he can begin making videos of his gaming. I tasked him with figuring out everything, from how to download it (I closely monitored this part), install it, and use it. He watched tutorials.

He got so far but got discouraged when he ran into the above issue and started the whole process over again because he thought he must have messed up. We eventually figured out the workaround but so happy to see they've fixed it!

The uploading channel is "Alice Violet Molland - Topic"

I went searching around using that info and came across a (similarly outraged) thread on google's support forums about this video, in which someone named longzijun seemed to make a reasonably sound counter-argument:

https://support.google.com/youtube/thread/108213944/a-posted...

Then she files a counter-notification. The appeals process has not been completed. She is only part-way through it.

Once she files that and if she does it properly, the claimant has 14 days to initiate a court action against her or the claim is released, the strike removed and the video goes back online.

Obviously, the claimant will not pursue legal action in this case.

False claims can cause inconvenience for sure, but with the counter-notification system, they don't do long-term damage.

Both the takedown system and the counternotification system are mandated by US law (specifically the DMCA).

YouTube is not supposed to intervene in copyright cases. If they do so, they will lose their safe harbor status (again under the DMCA) that protects YouTube from being sued for hosting copyright infringing content.

To sum up

1) the dispute process has not been completed in this case

2) your beef should be with US legislators, not YouTube