quicksilver03's comments

On: So you want to build your own data center

[quicksilver03]

> P.S., I swear the certification PDFs used to include this information (e.g., https://cloud.google.com/security/compliance/iso-27018?hl=en) but now these are all behind "Contact Sales" and some new Certification Manager page in the console.

This is not good, I can't think of any actual reason to hide those certificates.

For comparison, AWS makes their ISO-27001 certificate available at https://aws.amazon.com/compliance/iso-27001-faqs/ and also cites the certifying agent, most of which have a search page from where you can find all the certificates they've issued.

On: Datadog acquires Quickwit

[quicksilver03]

I'm using Vector for my own infrastructure and at work, at the time it seemed the best option to ship logs to various destinations. Are there any alternatives?

[pranay01 → quicksilver03]

If you want to check out OpenTelemetry, Otel-collector does the same job - though it's tightly coupled to opentelemetry

On: I automated my job application process

[quicksilver03]

I'd prefer an application to automatically fill in my data in those junk ATS systems, such as WorkDay, that pretend to parse my LinkedIn profile or a PDF resume and inevitably makes me do all the copy-paste twice.

A couple of years ago it was so bad that I stopped applying as soon as I saw that WorkDay crap pop up, regardless of the company.

[ugurs → quicksilver03]

Workday is a hostile environment for applicants. Perhaps that is intended.

[hackernewds → ugurs]

If the domain of easy applications is automated entries and copy paste, then Workday is indeed the desired tooling. LinkedIn Easy Apply serves the applicant, but I can't imagine any recruiter loves it.

[itgoon → quicksilver03]

For Workday, use a very simple resume. No columns, no bullet points (use asterisks), no tables.

There's usually an option to upload another file near the end of the form. After it has filled in the fields using your plain resume, delete it and upload the nicer one.

On: Ask HN: Payment processing for micro SaaS outside USA?

[quicksilver03]

I'd avoid LemonSqueezy because the payouts fees if you're outside of the USA are too high (check out https://docs.lemonsqueezy.com/help/getting-started/fees ).

Paddle may be an option, depending on what your SaaS will sell, but if they start pretending that your business falls into a high-risk category they will demand 3 months of processing statements before allowing you to use their platform.

On: Ask HN: What are you working on (September 2024)?

[quicksilver03]

I'm working on https://www.ptrdns.net , a primary and secondary DNS hosting service built around the PowerDNS API.

The problems that are on my mind right now are 1. how to improve visibility on search engines and 2. how to add POPs on Anycast IPs to improve latency for resolvers without selling my right arm to obtain a /24.

On: Support for IPv6

[quicksilver03]

There's one list I know of at https://bgp.services/ (not sure how complete or accurate it is, but it's a starting point).

On: Linux 6.11 Released

[quicksilver03]

The amdgpu driver has been the main source of issues for me on 6.10, but I had issues on older 6.x versions as well: for example, on a desktop with 2 monitors, I had to turn on the 2 monitors simultaneously or the UI would freeze.

On: Migrating Mess with DNS to Use PowerDNS

[quicksilver03]

I wrote one such proxy, though mine is not open source: I found relatively easy working with zones and records, and a well-designed test suite helps building confidence that a key for an "account" A cannot read or write into "account" B.

I'm putting "account" between quotes because it isn't a PowerDNS concept, there is just a lonely varchar column in the 'domains' table where one can store some account-related information. To handle TSIG keys I had to extend PowerDNS's data model to represent the association between a TSIG key and an "account".

On: Don’t let your domain name become a sitting duck

[quicksilver03]

I've just launched a DNS hosting provider ( https://www.ptrdns.net ) and this is one of the problems I'm worried about. With the PowerDNS backend I'm using, once a zone is added PowerDNS will respond to queries for its record regardless of the nameserver the queries are sent to. One can, for example, query the IP address of the nameserver to get a response.

The Route 53 technique of assigning random server names looks a bit like the technique of creating virtual hosts in a nginx server, but it looks like this is a custom AWS implementation and not something that comes out of the box in any DNS server software I know.

On: We built our customer data warehouse all on Postgres

[quicksilver03]

You have just described Testcontainers [1] , and if you are a Java developer you may want to look into Testcontainers for Java [2].

For example, in one of my projects I use TestNG to instantiate a MariaDB container, run the Flyway migrations on it and then populating the tables with the test data:

  mAPIDBContainer = new MariaDBContainer<>(DockerImageName.parse(MARIADB_CONTAINER_TAG))
              .withDatabaseName("apidb")
              .withPassword("password")
              .withNetwork(containerNetwork)
              .withNetworkAliases("apidb")
              .withExposedPorts(3306);
      mAPIDBContainer.start();
      Flyway flyway = Flyway.configure()
              .dataSource(mAPIDBContainer.getJdbcUrl(), mAPIDBContainer.getUsername(), mAPIDBContainer.getPassword())
              .encoding("UTF-8")
              .locations("classpath:apidb/migrations")
              .load();
      flyway.migrate();
      ScriptUtils.runInitScript(new JdbcDatabaseDelegate(mAPIDBContainer, ""), "sql/apidb/apidb-test-data.sql");

[1] https://testcontainers.com/ [2] https://java.testcontainers.org/