dedoussis

What if you are a merchant that needs to sell to O(10) countries? Integrating with each country's domestic payment rail is not feasible.

I've always wondered if part of the root issue is that Same-Origin Policy, and CORS by extension, were not very intuitively designed abstractions/APIs to begin with.

How do they determine whether a PR is AI-assisted and therefore requires senior review? A junior engineer could still copy-paste AI-generated code and claim it as their own.

FedNow is limited to domestic US transactions

Would this also affect chrome extensions? For example, when an extension makes a request to a 3rd-party domain, browsers by default pass all the cookies associated with that domain to the server. AFAIU, these cookies are considered to be 3rd-party.

Porting this extension to Firefox should be relatively straightforward using the webextension polyfill: https://github.com/mozilla/webextension-polyfill

Shameless plug: I've built the unofficial "Hide My Email" browser extension [0], available both in Firefox [1] and Chromium [2]. Tried to make it as frictionless as the Safari UX, which proved to be a challenge given the lack of native HME APIs.

[0] https://github.com/dedoussis/icloud-hide-my-email-browser-ex...

[1] https://addons.mozilla.org/en-US/firefox/addon/icloud-hide-m...

[2] https://chrome.google.com/webstore/detail/icloud-hide-my-ema...

It's funny that geohot/tinygrad chooses to not meet the PEP8 standards [0] just to stay on brand (<1000 lines). Black [1] or any other python autoformatter would probably 2x the lines of code.

[0] https://peps.python.org/pep-0008/

[1] https://github.com/psf/black

Source code: https://github.com/dedoussis/icloud-hide-my-email-chrome-ext...

I'd say 2-4 days is the median. There have been 2 instances of me needing to wait 2 weeks for a one-liner.

Well, in this instance remote code actually means remote. In V3 one can no longer use the tabs.executeScript API [1] in which you could pass an arbitrary server rendered string.

[1] https://developer.chrome.com/docs/extensions/reference/tabs/...

Benefits of the Manifest V3: none

V3 not allowing remote code execution is actually a serious benefit. Of course, this does not negate the fact that V3 is mainly there to boost the ad ecosystem of Google, but I'd never want my screen casting extension to be mining bitcoin on the background. That said, I'm not sure how this is going to scale long term, given that it sometimes takes 2+ weeks for the web store review team to approve a genuine one-line change. Lack of RCE is only going to make this review backlog bigger.

Oh actually SingleFile is not attempting to set the headers but modify them, which seems to not be possible with V3. That makes sense.

With Manifest V2, it was possible to inject a "Referrer" HTTP header if necessary. With Manifest V3, it's no longer possible.

Not entirely sure of how this is true. A recent V3 extension I've built is able to inject both the "Referer" and "Origin" headers using a declarative net request ruleset:

1. manifest.json (referencing the rules.json file): https://github.com/dedoussis/icloud-hide-my-email-chrome-ext...

2. rules.json: https://github.com/dedoussis/icloud-hide-my-email-chrome-ext...

3. Relevant docs: https://developer.chrome.com/docs/extensions/reference/decla...

How is this different to Stripe's Banking-as-a-Service product?

Was this Babylon?

https://dedouss.is

My personal blog.

Statically (and proudly) generated by Hakyll. Hosted on my personal AWS account, using Route53 + Cloudfront + s3. Source sits within a private GitHub repo of mine, along with some Actions workflow that compiles and pushes the build to s3.

To avoid any potential issue with signal propagation a good practice is to always use a lightweight init system such as dumb-init [1]. One could assume that the node process would register signal handlers for all possible signals, but I prefer to not have to make this assumption and use an init system instead.

[1] https://github.com/Yelp/dumb-init

I only have one humble request, if I submited 51k lines of code in January and my whole team submitted 68k, do not call me a "Least Effective".

  $ npm update

"There is no good and standardised way of expressing asynchronous APIs."

You may check: https://www.asyncapi.com/

What stops any developer of a large org using Docker Desktop through their personal license/account? How is such a restriction going to be imposed?

Yes I went down the same rabbit hole. `dir` is not found, whereas POSIX commands such as `ls`, `cd` and `cat` are available.

This is a great thread to plug my favourite crystal streamer: https://www.youtube.com/channel/UCaydNuV-VSO0gFSrvS9WgXg

Great idea! Just submitted my first pok.

Feature request: User groups and pok access levels. Restrict pok access down to a given set of users. I imagine that a large share of the pok volume does not (and should not) concern the wider public. For example, I could have a group with my buddies, and register a pok wrt my best friend breaking up with their partner.

This group concept could be exploited in the form of a plugin that can be hooked on Slack rooms or WhatsApp groups. Every time a pok is unsealed the Futuure bot could notify the room, letting others congratulate you upon a successful prediction (or the inverse).

Step 1: Do not sign up for the AWS certifications.

Looks very promising (although I have no API key)!

Feature request: I got surprised when I was asked to sign in. Introduce an anonymous mode where "Sign in with Google" is not enforced. History could be exported locally and imported from the file system.

I've been working in python roles for some years now and I never understood why the python dependency tooling is so poor.

Pip feels like an outdated package manager, lacking essential functionality that package managers of other languages have implemented for years. For example, credential redacting in pip was only introduced in 2019, 8 years after its initial release!

Not to mention the global-first nature of pip (package is installed globally unless the user explicitly requests for a local installation). You can still install packages locally, but this only shows that pip was not built with environment reproducibility in mind. As a consequence, the need for additional environment tooling (like venv) arose, which increased the complexity of the local python setup.

Tools wrapped around pip are also under par. I cannot see why Pipenv is that resource intensive, leading to long and noisy builds (my machine gets close to exploding on a pipenv lock), with very fragile lock files. Debugging an unsuccessful locking in the CI of an enterprise project is a mystery that could take an entire week to solve. Its javascript counter-part (npm) does the exact same thing, faster and with less CPU usage.

Trusting the OS community, I understand that there would be very good reasons for Pipenv to perform like this, but as the consumer of a package managing tool all I see is the same generation of file hashes I see on npm, but with npm doing it way more efficiently. I really see value in the principles that Pipenv is promoting, but to me the developer experience of using it is suboptimal.