agwa

8 ms·

91.
by agwa 1y ago
No, the metadata is information like the modification time and permissions, not the directory entry. The next paragraph in the man page explains this: > Calling fsync() does not necessarily ensure that the entry in the directory containi
92.
by agwa 1y ago
OK, I just tested it: In terminal 1, I created a database and added a table to it: $ sqlite3 testdb sqlite> create table test (col int); In terminal 2, I attached gdb to sqlite3 and set a breakpoint on unlink: $ gdb sqlite3
93.
by agwa 1y ago
I read the whole document. It doesn't mention IDs anywhere. If you're not going to provide citations for your claims, yet criticize me for "picking out sections" when I provide citations, then continuing this conversatio
94.
by agwa 1y ago
The docs list 5 conditions that all must be satisfied for the journal to be considered hot: https://www.sqlite.org/atomiccommit.html#_hot_rollback_journ... I believe they would all be satisfied. I don't see any mention
95.
by agwa 1y ago
Yes, that's exactly right. Note that the comment by Richard Hipp is justifying why WAL mode is not durable by default. It's a completely reasonable explanation, and would be for DELETE mode too, yet his comment claims that DELET
96.
by agwa 1y ago
I'm pretty sure I understand what durability means; the definition is not hard - https://en.wikipedia.org/wiki/Durability_(database_systems) It's possible I've misunderstood how DELETE mode works. But h
97.
by agwa 1y ago
That document addresses atomicity, not durability, and is thus non-responsive to my concerns.
98.
by agwa 1y ago
PostgreSQL has the knobs and I find the documentation about them very clear: https://www.postgresql.org/docs/current/wal-async-commit.htm...
99.
by agwa 1y ago
My understanding of DELETE mode is that the transaction is not committed until the rollback journal file is deleted - if the rollback journal is present when sqlite opens a database, it applies the rollback journal to undo the changes that
100.
by agwa 1y ago
This is what the documentation ( https://sqlite.org/pragma.html#pragma_synchronous ) says about EXTRA: > EXTRA synchronous is like FULL with the addition that the directory containing a rollback journal is synced after tha
101.
by agwa 1y ago
It sounds like you're saying that it's not the proof-of-work that's stopping AI scrapers, but the fact that Anubis imposes an unusual flow to load the site. If that's true Anubis should just remove the proof-of-work part
102.
by agwa 1y ago
> It’s another “we listened the community and nobody told us no” moment. Like Go’s telemetry issue. Go changed their telemetry to opt-in based on community feedback, so I'm not sure what point you're trying to make with that ex
103.
by agwa 1y ago
This bug only affects a special form of RewriteCond where the first argument is literally "expr", so the rules that you quoted are unaffected. I have to assume that this form of RewriteCond is pretty rare or the bug would have bee
104.
The Randolph Public Telephone Operating Company(randtel.co)
1 points by agwa 1y ago|0 comments
105.
by agwa 1y ago
I wish there were bounties :-) There is systematic checking - e.g. crt.sh continuously runs linters on certificates found in CT logs, I continuously monitor domains which are likely to be used in test certificates (e.g. https:/&#x2F
106.
by agwa 1y ago
Sunlight and static-ct-api are a breath of fresh air in the CT log space. Traditional CT log implementations were built on databases (because that's the easiest way to implement the old API) and were over-complicated due to a misplaced
107.
by agwa 1y ago
As a small software business owner, I have to agree with Michele Hansen (who spent 2 years advocating on behalf of small software businesses for this very change): "we’re finally going to get Section 174 relief, and I couldn’t be angri
108.
by agwa 1y ago
First of all, the project in question (Sunlight) is not a Google project and its author (Filippo) is not employed by Google. Here's what actually happened: 2025-07-01 19:01 UTC: I suggest making some changes to Sunlight to improve usab
109.
by agwa 1y ago
The primary purpose of CT is to provide transparency into browser-trusted certificates. Since expired certificates are not trusted by browsers, having them in browser-trusted CT logs is purely a liability. Those who care about expired certi
110.
by agwa 1y ago
No. The purpose of temporal sharding is to allow log operators to reclaim storage space used for expired certificates, and to save monitors from having to sift through a huge number of expired certificates to get to the unexpired ones.
111.
by agwa 1y ago
deps.dev does an absolutely terrible job with Go dependencies. It thinks modules are the unit of dependency rather than packages. Consequentially, it reports vulnerabilities in packages that are never even imported. For example, https:&#x
112.
by agwa 1y ago
No, because the CAA record only has to be in place at the time of issuance, rather than the whole lifetime of the certificate. Even if the semantics of CAA were changed, the challenges described in paragraph 3 of this post would apply: htt
113.
by agwa 1y ago
Domain owners may find my CAA record generator < https://sslmate.com/caa/ > useful, as it can automatically generate a CAA policy that covers all the certificates found in CT logs for your domain. It's not alw
114.
by agwa 1y ago
This method may be more popular than you'd think, since it only requires the TXT record to be published once, whereas using the DNS method requires periodically updating the DNS record. Yes, that can be automated or delegated, but for
115.
by agwa 1y ago
Random third parties can't verify if domain validation was performed properly; only the domain owner knows. Which is why domain owners should monitor Certificate Transparency logs: https://certificate.transparency.dev/
116.
by agwa 1y ago
Historically, singular domain validation bugs have not killed CAs.
117.
by agwa 1y ago
You omitted key portions of that section. Here's the full quote (emphasis added): > The foregoing requirements of this Section 2.10(c) shall not apply for (i) purposes of determining Renewal Pricing if the registrar has provided Re
118.
by agwa 1y ago
> gTLDs just subject you to an additional layer of incompetence, namely from the company running it. ccTLDs also have to be run by some organization, which is often a private company. Maybe the country's oversight over this organ
119.
by agwa 1y ago
Although the .org price caps are gone, the registry has to raise prices uniformly for all domains. They can't target popular domains for discriminatory pricing. ccTLDs can.
120.
by agwa 2y ago
> I worked on compilers at FAANG for quite a while and know quite well how these teams justify their existence. Telling executives "we cost the company $1M a quarter, but good news, we made the semantics of the language easier for

More ›