Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ksajadi
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
by
ksajadi
2y ago
wait, there are 400 social media networks?
92.
▲
by
ksajadi
2y ago
I'm curious as to how everyone deals with HTTP/2 requirements between the backend servers and the load balancer? By default, HTTP/2 requires TLS which means either no SSL termination at the load balancer or a SSL cert generat
93.
▲
by
ksajadi
2y ago
We also get those a lot for our service. I’m not sure if they are AI generated but many are low quality. The problem is as part of our processes we are required to respond and triage every report and keep an audit trail for them. As a resul
94.
▲
by
ksajadi
2y ago
No they do but the amount of work that’s required is much less most of the time. You can always define the problem in such a way that there is no difference between a cloud and non-cloud solution but 12 years being in the business of deploy
95.
▲
by
ksajadi
2y ago
Totally agree. Of course there are savings in monthly costs and perhaps a lot of learning on the way (the first time) but two factors are being missed here: cost of your time spent on this, and second, what I’ve been calling Day-2 costs: ba
96.
▲
A distributed KV store (standalone and Go lib)
(github.com)
3 points
by
ksajadi
2y ago
|
0 comments
97.
▲
by
ksajadi
2y ago
I'd really like to see a Go API backend / React frontend stack instead of using Go to render HTML directly.
98.
▲
by
ksajadi
2y ago
Same here. Go community has a tendency of not using frameworks as much (which I guess is confirmed by the lack of long term maintenance for a lot of Go frameworks), compared to say Ruby. I don't think that is a bad thing. We ended up u
99.
▲
Ubuntu Snap Packages install CUPS on servers
(blog.cloud66.com)
3 points
by
ksajadi
2y ago
|
0 comments
100.
▲
by
ksajadi
2y ago
I agree with you and at the risk of self-promotion, that's why we built Cloud 66 (which takes care of Day-1 (build and deploy) as well as Day-2 (scale and maintenance) part of infrastructure. As we all can see there is a lot to this th
101.
▲
by
ksajadi
2y ago
Docker is the container engine. Swarm is the orchestration, the same as Kubernetes. The concept of "Service" in k8s takes care of a lot of the proxying, while still using Docker (not anymore tho). In Swarm, services exist but only
102.
▲
by
ksajadi
2y ago
This primarily exists to take care of a fundamental issue in Docker Swarm (Kamal's orchestrator of choice) where replacing containers of a service disrupts traffic. We had the same problem (when building JAMStack servers at Cloud 66) a
103.
▲
Hetzner Connectivity Issues Due to Sanction Busting Activities
(blog.cloud66.com)
73 points
by
ksajadi
2y ago
|
18 comments
104.
▲
by
ksajadi
2y ago
This is not limited to Cloudflare. Google has the same issue and it turns out the IPs were being used by the Iranian hosting companies connected to internet surveillance but they keep moving around. So far we only observed this in Hetzner G
105.
▲
by
ksajadi
2y ago
I’ve been building and deploying thousands of stacks on first Docker, then Mesos, then Swarm and now k8s. If I have learned one thing from it, it’s this: it’s all about the second day. There are so many tools that make it easy to build and
106.
▲
by
ksajadi
2y ago
Unrelated, how’s MagicLeap doing?
107.
▲
by
ksajadi
2y ago
For all those new search projects named in my OC to be viable, ES had to stop being “open source”. Before that it was not worth trying because there was one single dominant player in the market giving search away for “free”. The same is hap
108.
▲
by
ksajadi
2y ago
The change of Elastic license resulted (or perhaps coincided) with the massive growth of other tools like Meilisearch, Quickwit, Loki, typesense, and more. In a way, their original open source license was suppressing innovation. I know this
109.
▲
by
ksajadi
2y ago
This is a good one for everything related to SB1047 https://pca.st/episode/44b41e28-5772-41c4-bcd7-5d7aa48d5120
110.
▲
by
ksajadi
2y ago
This is not fully up to date but is a good start https://www.herokualternatives.com/
111.
▲
by
ksajadi
2y ago
WSJ used local police reports and matched them with redacted Tesla reports of crashes to show what caused the crashes. Also there is content in the article stating that Tesla only uses vision whereas other manufacturers use radar and ladar
112.
▲
The Autopilot Data That Reveals Why Teslas Crash
(wsj.com)
13 points
by
ksajadi
2y ago
|
3 comments
113.
▲
React MDXEditor
(mdxeditor.dev)
1 points
by
ksajadi
2y ago
|
0 comments
114.
▲
by
ksajadi
2y ago
Kudos on making this, especially after the huge price hike Customer.io just dropped on their customers.
115.
▲
by
ksajadi
3y ago
wonderful. now the Iranian regime can stop their payments to China for their use of this tech to block Iranians from accessing open internet. funny how open source can do a full circle to prevent the very thing it set out to open.
116.
▲
by
ksajadi
3y ago
This looks very cool for embedding workflows in a native Go project. There is also Trackman ( https://github.com/cloud66-oss/trackman ) which is mostly built for workflow based commanline execution.
117.
▲
The Selling of America's Most Controversial Gun
(wsj.com)
1 points
by
ksajadi
3y ago
|
1 comments
118.
▲
Google says political adverts must disclose use of AI Published
(bbc.co.uk)
2 points
by
ksajadi
3y ago
|
0 comments
119.
▲
by
ksajadi
3y ago
Good to see tools like this. However, are you not affected by the recent change in the Terraform licensing?
120.
▲
by
ksajadi
3y ago
I look at it from a consumer of podcasts point of view not a producer. If the content is good and the voice quality is natural then this can only help unlock more good content, by lowering the barrier to entry. Can't see why that is a
More ›