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


The "digital signature" description gives the impression that the signed message is encrypted with the private key and later decrypted with the public key.

Is this how message signing works in reality? I had a different mental model.


They are separate operations.

  - encrypt with public, decrypt with private
  - sign with private, verify with public


Baby brezza. It's like a coffee machine but for baby formula. It really improves my family's night sleep!


Pretty off-topic, but:

> I hope that Pocket Casts can do for podcast clients what Firefox in the early days and Chromium now does for browsers — push the state of the art, be manically focused on user control, and grow a more decentralized and open web.

It's pretty funny to see the claim that Chromium is "manically focused on user control" and "is growing a more decentralised and open web" :-)


That bit caught my eye as well. I read it as a backhanded swipe at Mozilla, which given the news is unnecessary. But then he goes further and strokes his buds at Google with statements of questionable validity?

Why?

Why go so far as to distract from his news? Why not mention how being OSS should ideally mean improvements in sec and privacy?

It just seems weird.


it's true though isn't it? Some people keep complaining about chromium related apps, but from different browsers to electron based apps it has without a doubt pushed open source like almost nothing else, it's sort of the OS of the web.


The OS of the web crippling extensions and plugins because it hurts its ad-business is not what I would call "being focused on user-control". They're focused on control, yes, but not in our favour.


Users of Chromium have announced that they will reenable those extensions and plugins - so what, exactly, is the problem there?

This is opensource working as intended - someone else can build it with feature set you want.


The problem is that OP used Chromium as an example of a project "focused on user control" when in fact it is actively trying to remove control from the users's hands.

I was citing extensions and Manifest v3 as an example of that, I don't care about the feature and what people can do to go around this.


It's an OS for the web, but the web is increasingly in control of the same entity that controls chromium. And chromium helped them a lot in getting that much power over the web. I don't think that qualifies as improving openness or user control.


I love the programmable web!

I wanna give a shoutout to Stylus[0] for offering userstyles (basically the same thing as TamperMonkey but for .css files)

[0] https://addons.mozilla.org/en-US/firefox/addon/styl-us/




OT, but I see a lot of these archive links here. How do I go the other way? If I see an article I want to read, how do I find it on archive.is?


Goto https://archive.is/

Enter your url in the second field

If that doesnt turn up anything enter it in the first


You don't have to bother with the second field, I think. Just enter into the first.


Gotta be a browser extension that does this for you?


Surprised and happy to see this! I was an avid user of the old Turntable.fm which sadly shut down. (I would love to get an invite for the new service if anyone has any ;) )

Related, there is also jqbx.fm which integrates with Spotify which is basically the same thing, can recommend.


“Speakeasy"


We are using Cypress at my workplace and we're quite happy with it. It also has endpoint mocking, mobile emulation etc.

Out of curiosity, does anyone know of any advantages of Playwright when compared to Cypress?


Cypress appears to have more features dedicated specifically to making testing easier, such as a user interface and various debugging additions and integrations into various other tools.

Playwright is just an API for controlling the browser, and appears to be far more powerful in that regard.

Compare the api documentation, and it's not even close: https://docs.cypress.io/api/table-of-contents

https://playwright.dev/docs/api/class-playwright


It looks like Cypress added Firefox & Edge support last year but initially it was just Chrome.

Playwright also has a python version (https://github.com/microsoft/playwright-python)

And I just discovered that they now have a real nifty debugger you can use to inspect/step-through tests as they run (https://playwright.dev/docs/next/debug/#playwright-inspector)


They also have a code generator that can record your actions and turn them into scripts


If cypress works for you that’s great, playwright doesn’t have all of the same tools but it does excel at cross browser testing. It runs safari, Firefox, and chrome.

We’re working on plugging in playwright into a cloud service for visual testing @superadmin.so, running multiple browsers in Linux can be pretty hairy to setup.


"Bombay Beach (2011)" is a documentary that depicts life in a once-bustling settlement by the Salton Sea, can recommend: https://www.imdb.com/title/tt1758576/


See also “Plagues and Pleasures on the Salton Sea”: https://www.imdb.com/title/tt0438327/

I’ve watched it several times after becoming fascinated by the place upon watching this (much) shorter piece on Youtube: https://youtu.be/otIU6Py4K_A

Thanks OP for posting this article, I always eagerly enjoy new pieces about the area.


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

Search: