jorams

There's a ton of those platforms, varying from extremely unknown to fairly well established. I'm pretty sure multiple of them end up as a Show HN every year. The only thing on your list they generally don't do is domain registration, but keeping that separate is generally a good thing. Sibling mentioned bearblog.dev, I'll mention write.as[1].

[1]: https://write.as/

No, rg looks inside files. find . | grep just lists all files and directories and then filters it down using grep.

Note that in the questions at the bottom it says the following:

> If you are on a Free or Pro plan, full setup is the only one available. This is the recommended and most common option.

That means to use this partial setup you need to be on at least the Business plan, which is $200/month when billed anually ($250 monthly).

It does that because it's required to. The system is called Certificate Transparency[1] and browsers require certificates to be in CT logs to be accepted.

If you want to hide what subdomains you have you can use a wildcard certificate, though it can be a bit harder to set up.

[1]: https://developer.mozilla.org/en-US/docs/Web/Security/Certif...

Since everything you need to run "a full SPA" is to serve some static files over an internet connection I'm not sure how that tells you anything interesting about the platform. It's basically the simplest thing a web server can do.

> All of this presupposes that whatever you implement yourself will be more secure

No, this thread is about Azure in particular having a bad security posture, not the cloud in general.

That doesn't change what they're saying. The self-hosted backend you're linking is a network-accessible version of the local SQLite backend. The hosted backend is transparently globally replicated and built on FoundationDB, with a very different (better) scaling story.

This is an interesting article, but also rather unsatisfying. It very quickly jumps to conclusions and goes right back to opinion. I agree with several of those opinions, but opinion was explicitly not the point of the article.

> Prefer to not use language-specific operators or syntactic sugars, since additional constructs are a tax on the reader.

I don't think this follows from the metric. If a function contains three distinct operators, a language-specific operator that replaces all three of them in one go would reduce the "effort" of function. It's highly scenario-specific.

> Chaining together map/reduce/filter and other functional programming constructs (lambdas, iterators, comprehensions) may be concise, but long/multiple chains hurt readability

I don't think this follows either. One effect of these constructs when used right is that they replace other operators and reduce the "volume". Again this can go both ways.

> ...case in point, these code snippets aren’t actually equivalent!

That's a very language-specific diagnosis, and arguably points at hard-to-read language design in JS. The snippet otherwise doesn't look like JS, but I'm not aware of another language for which this would apply. Indeed it is also commonly known as a "null-safe operator", because most languages don't have separate "null" and "undefined".

> variable shadowing is terrible

> long liveness durations force the reader to do keep more possible variables and variables in their head.

These can arguably be contradictory, and that is why I am a huge fan of variable shadowing in some contexts: By shadowing a variable you remove the previous instance from scope, rather than keeping both available.

Seems so, a quick search turned up this[1]

[1]: https://registry.terraform.io/providers/rootlyhq/rootly/late...

Note that they said (emphasis mine):

> they're still so small that they must protect themselves by requiring that macs be used for publishing iPhone and iPad applications.

They're not talking about Apple's silicon as a target, but as a development platform.

No, I stand by my statement. I consider Apple extremely user-hostile and in many ways worse than Microsoft and Google. Those ways are just less broadly agreed upon.

Relative to Mozilla: on the advertising front I can't judge whether Apple is worse or about the same. On most other fronts I don't think there's much of a question. Others disagree, the extent to which Apple's actions are user-hostile is an often debated topic I'm not particularly interested in re-threading.

Google and Microsoft aren't really a comparison, both have been openly anti-user on many fronts for many years.

They are[1][2]. It makes them billions every year[3]

[1]: https://ads.apple.com [2]: https://support.apple.com/guide/iphone/control-how-apple-del... [3]: https://appleinsider.com/articles/22/06/15/apple-ad-business...

> it's a add company now

Note that "any other major browser vendor" is a short list of ad companies with a much worse track record.

The Google Cloud Terraform provider includes, on Cloud SQL instances, an argument "deletion_protection" that defaults to true. It will make the provider fail to apply any change that would destroy that instance without first applying a change to set that argument to false.

That's what I expected lifecycle.prevent_destroy to do when I first saw it, but indeed it does not.

That's covered by

> I did a thorough combing of the code base when I forked. Just did another audit and still not seeing anything suspicious.

> The only drawback of Markdown is images.

> GitHub-flavored Markdown is so popular because you can really easy inline them.

I'm not sure what you mean. GitHub-flavored Markdown has pretty much exactly the same image syntax as every other Markdown flavor.

That makes a lot more sense than the Saba I initially thought of[1]. The "specific geographies" seemed a bit overly specific.

[1]: https://en.wikipedia.org/wiki/Saba_(island)

From [2] RFC 9576 § 4.1 "Shared Origin, Attester, Issuer", right before the sentence you quoted:

> In this model, the Attester, Issuer, and Origin share the attestation, issuance, and redemption contexts.

I haven't read the RFC in detail, but I believe this is where the nuance is: When you enable the privacy pass setting in the extension/browser the redemption context is changed relative to the attestation context by removing the session cookie, to just the information sent by the browser for someone who is not logged in. What remains is your IP address and browser fingerprinting, which can be countered by using Tor.

> I'm not going to figure out the US tax system just to know how much I actually to shell out

You pay the amount of VAT based on where you live. I agree it would be better to display that on the pricing page though.

As for the privacy claims they have a fairly easy to read privacy policy that goes into details about what they do and particularly don't do with your data. There is no vague wording to hide behind.

> This has been brought up with freedesktop and they handwaved it away. They claim they want to DIY with donation money

You are making all of this sound way more definitive than the ticket. The donation money approach is the personal opinion of the sysadmin. The OSUOSL is brought up, some explanations are added that make it more attractive and remove some doubts, and beyond that it's waiting for the board to decide what's next.

> In 2015 YouTube was separated from Google with both owned by Alphabet.

That is incorrect. When Alphabet was introduced YouTube remined part of Google, and still is.

> There are credible people out there insisting that Kick is losing money and only exists to funnel new customers to Stake's online gambling services.

This is trivial to determine without even needing to defer to credible people: Its entire business model outside of funneling people into gambling addiction is taking a 5% split of subscription revenue. This while it is paying Amazon for the actual (expensive) streaming tech[1], in a market that's notoriously hard to be profitable in for companies taking both a larger cut and running ads.

[1]: https://aws.amazon.com/ivs/

If "some buggy ML classifier" is allowed to make decisions that trigger broad enforcement, that classifier is, for all intents and purposes, a policy maker. The claim made by the article is somewhat broad relative to the evidence presented, but whether policy decisions are automated or not doesn't really matter.

Is it? The word means the same in English as it does in Dutch.

> requires you to gift them the rights to your code (not just license it).

The legally binding section only talks about giving them an infinite free license to it. It does not say you hand over your copyright, so the summary seems correct.

I still don't think you should sign it. The editor code seems to be variously under GPL, AGPL and Apache 2.0, all of which would be fine without one.

Yeah they did. They added his email as a secondary email to a Google Workspace user account, with the plus-address-suffix including a "Case ID". Then they reset the password of the user account, triggering this notification.

It's specifically a password reset email. A Google Workspace admin can send a password reset to any of their users, and it will pass DKIM and SPF. The trick here is that apparently you can sign up for Workspace with a g.co subdomain and, without verifying the domain, can trigger a password reset to be sent.

For what it's worth gp is a reference to this post[1], in which the author does not.

[1]: https://news.ycombinator.com/item?id=42579873

> The only situation dark mode is better than light mode is when you're sitting in a dark room with your screen as your only light source

It's really not that extreme. Dark mode is more comfortable as soon as it's dark outside (this time of year that starts between 3 and 4 pm) unless I'm flooding my entire room with enough light to replace the sunlight. I still have the lights on, but none of that light is as bright/white as an average white webpage. Even with screen brightness turned down and a blue light filter, an all-white webpage is usually just too much white.

> Light mode might be annoying to read in no-light environments, but dark mode is nigh impossible to read in high-light environments.

This is just completely opposite for me. Reading in dark mode is only uncomfortable if there's sunlight basically directly behind the screen, while light mode is only really comfortable in high-light environments.