Hacker Newsnew | past | comments | ask | show | jobs | submit | alphabetter's commentslogin

Thanks for answering the one thing I wanted to know about this. It wasn't at all obvious to me how this might be possible using DNS only.

I guess it will work for some sites, but it would be interesting to know what fraction.


Relevant previous topic: https://news.ycombinator.com/item?id=43120186

"Test your adblocker" websites can harm users and the adblocker ecosystem (brave.com)


Honestly, I think what TFA calls "Kagi’s implementation of Privacy Pass" is the integration of the feature into their server and clients, not the RFC (which they acknowledge), or the protocol implementation.


[I work at Kagi]

Indeed, this is the intended interpretation of "Kagi's implementation of Privacy Pass" - we're talking about building out the server infrastructure, the UX, the browser extensions, the mobile applications, the Orion browser integration, the support and documentation, the Tor service, etc. The cryptography is obviously an extremely important piece, but it is far from the only piece.

As other commenters have noted, the code in question is MIT licensed [1] and we're pulling it in as a standard dependency [2], it's not like we've gone out of our way to obscure its origin. The MIT license does not require us to do anything more.

That said, I can understand the author wanting more visible attribution, and that's very reasonable, we'll add a blurb to the blog post acknowledging his contribution to Kagi's deployment of Privacy Pass.

[1] https://github.com/raphaelrobert/privacypass/blob/main/LICEN...

[2] https://github.com/kagisearch/privacypass-lib/blob/e4d6b354d...


Understood, and thanks for updating the blog post. The discussion in the comments was interesting, and I'd like to clarify a few points. From my side, there never were any doubts about licensing compliance. I picked MIT precisely so that folks can use the implementation without further obligations, I wanted the implementation to be as useful as possible. What startled me was the combination of a for-profit company writing a blog post about a new feature (that will likely further increase profit in the future), using my implementation as the core of the feature (and therefore likely save a bunch of money) and not giving any credit to either the IETF batched tokens draft or the implementation. Anyway, the blog post has been amended now – thanks for that. Case closed.

PS: If you want to go above and beyond, you can spell my last name right in the blog post – it's Robert, not Roberts.


> PS: If you want to go above and beyond, you can spell my last name right in the blog post – it's Robert, not Roberts.

That was on me, fixed!


Exactly this. As a British English speaker that works a lot with the US it was an early learning.

In British English a "scheme" has no negative connotations. It's commonly used in all kinds of legitimate places - for example the company you work at will have a "pension scheme".

In U.S. English it has a connotation that it is nefarious in some way.


Yeah, this always throws me off. In American English I’d always use the word “program” instead.


Not the OP, but I am opposed to the forced use of 2FA by GitHub for three reasons:

1) They are my repos. I should get to decide the appropriate level of security.

2) 2FA is often used as a pretext for identity harvesting which are then abused for other purposes.

3) If there is account recovery via email then the whole thing is a charade anyway.


> 2) 2FA is often used as a pretext for identity harvesting which are then abused for other purposes.

Okay, but there are many options, like TOTP code generators, that do not even require the internet to work.

> 3) If there is account recovery via email then the whole thing is a charade anyway.

You can disable all account recovery options in Settings.


Agreed with 2 in general, and it frustrates me endlessly, but github offers & encourages TOTP & U2F authentication which are privacy-preserving.


> They are my repos.

GitHub is not forcing you to use 2FA to store your repos elsewhere. Just to interact with their website.

> I should get to decide the appropriate level of security.

People are really bad at deciding the appropriate level of security.

GitHub hosts a lot of very important projects that have impact in the real world. Forcing people to use the bare minimum to keep that environment relatively secure is probably not a bad idea.

That way when you set your password as "batman123" and are given commit access to some obscure project that is included as a dependency in 1000 other projects, your account is much less likely to be taken over as a means of pushing a malicious commit.


  1) They are my repos. I should get to decide the appropriate level of security.
Can you really say they're yours if you host them on GitHub and it can restrict your access to them for basically any reason?


[2012] based on the copyright.

Note the disclaimer: "This course has not yet been updated to work with the Raspberry Pi models B+ and A+. Some elements may not work, in particular the first few lessons about the LED. It has also not been updated for Raspberry Pi v2."

And presumably not updated for the Pi 3,4,5 too!


The 3A fuse is due to the way the UK wiring system works rather than what is optimal for this device.

All appliances in the UK have a fuse where they connect to the building wiring, normally in the plug, but can be in a fixed fuse-holder like this device. Somewhere in the process it was recognized that having lots of different fuse values would be confusing and awkward for users, so these fuses are the same size and always one of three standard values: 13A, 5A, and 3A. As noted elsewhere, you can buy these particular fuses in UK supermarkets and convenience stores.

If 3A is too high for the appliance then what the designer has to do is to fit it with a flex rated at 3A so that is protected by the fuse at the plug-end and then add additional, lower current, protection at the device end.

The UK system is clever and has subtle details like the standard fuse values which were good at the time it was introduced. But, it is also rather over-engineered, and not optimized for modern homes that have a lot of low-current appliances.


Oh yeah the UK system.. I lived in Ireland for a long time and it was a bit archaic sometimes.

I like the idea of fuses in every plug, mind you. Because some equipment just can't be trusted. I didn't like the switches in every outlet (even though they're not mandatory, they are very common). And the way the plugs are so huuuge and always fall with the pins up do to the design so they are a foot-piercer.

In Ireland 1A fuses were available though even in the fuse kits in Tesco. With the same size as the others. And the practice doesn't always lead to actual safety, I've seen a lot of tinfoil and paperclips. Yes, really.

But the thing I really thought was the worst was the concept of having only one tap connected to the mains water line in the house, and having all the others fed by a huge dirty water tank in the attic, full of dead insects brewing away in the summer heat (yes even there it can get hot in summer). It seems like an ecological disaster and locals were always warning me to not drink the water from the bathroom or bedrooms taps. It's also a big possible cause of leaks. Here in Spain and in my home country of Holland we just feed all taps onto the mains.

But overall I tend to prefer EU standards rather than BS. The "Schuko" does have a few serious design flaws like the ability to plug it in upside-down so neutral and phase are reversed, but the French have found a solution for that :)


I think many cold water tank system in Britain have been removed in the last 20 years or so, as people install more efficient central heating / hot water systems.

No idea about Ireland.

(Here in Denmark there are switches on sockets. I find it useful on the rice cooker, which doesn't have its own switch and would otherwise need to be unplugged. The other sockets are generally left with the switch "on".)


Yes, the REM is the lookup table used in line 70.

Because BBC Basic had a built-in assembler it was pretty uncommon for BBC programs to inline machine code as raw data (unlike some other computers from BITD).


It is software-related, but also physical: pong with the bats moved by exercise bikes: http://lushprojects.com/cyclepong2/

It's been around more than 15 years in various forms now, but people still love playing it. If you're in London it is at https://www.novelty-automation.com/


What a clever idea! It got an exercise bike and noticed it was boring, so I hooked it up to a speed sensor and used that control VLC playback speed. Very motivating, to watch a movie like that because if you slack off it will slooowwww dooooowwwwnn.... And not nearly as boring :)

But I like yours better, it's more fun.


So you're in the same arcade as Tim Hunkin?


4'17 mostly because I was laughing so hard.

The captcha with the hononyms and the selection boxes where you don't expect them is genius.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: