Javier Nesofsky

"How to argue better" qz.com/how-to-argue-b…

"Commission partners with private investors to set up multi-billion Scaleup Europe Fund" ec.europa.eu/commission/pre…

"ai hacking habits" qz.com/ai-hacking-hab…

Proud to support this petition for a unified pan-European startup entity. Let’s unite Europe's startup ecosystems! eu-inc.org 🇪🇺 eu-inc.org

"Odyssey Ventures comes out of stealth to close the transatlantic valuation gap" siliconcanals.com/odyssey-ventur…

The data center dividend mck.co/4o8PjKn via @McKinsey

"AI is coming for our jobs. AI titans say universal basic income will save us. Will it?" qz.com/universal-basi…

One person unicorns?: "Leaner, faster and powered by AI: A new breed of unicorn has arrived" qz.com/unicorn-entrep…

Excellent post: Why Most $1 Million Founders Never Reach $10 Million inc.com/bruce-eckfeldt…

Check out this article: The New Space Revolution: Geospatial Intelligence Reshaping All Fields of Engineering - engineersoutlook.com/the-new-space-…

Selling a Cryptokitty I purchased in 2017. Check out my item listing on OpenSea! opensea.io/assets/ethereu… via @opensea

@kikollan todo depende del objetivo y de quien es la audiencia objetivo que quieres o te importa :-)

@nesofsky ¡Gracias Javier! Creo que he descartado la segunda cuenta, porque no tengo tiempo. Incluso en auto. Es posible además que pronto todo sea lea traducido con IA. Por ejemplo, Reddit entras y te muestra la página traducida,

¿Me ayudáis con un dilema? 👋🙂 Me planteo twittear en inglés. Pero no sé si A) usar una segunda cuenta en inglés; B) usar esta en español/inglés; C) renunciar. Problema de A es que crecer exige tiempo. El de B es que no conozco cuentas duales: ¿Funciona¿ ¿El algoritmo lo odia?

@unrollthread unroll

For the super nerds… The EBA’s RTS on Strong Customer Authentication and Secure Communication •Full Title: “Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication.” •Articles 30 to 32 (especially Article 31) detail the requirements for a “dedicated interface” (i.e., the official “open banking API”) that banks must provide for TPPs. •Article 33 sets out a “contingency mechanism” or fallback if the bank’s dedicated interface fails or does not provide the same functionalities as the bank’s own consumer-facing channels. •Article 34 lays out a possible exemption from providing the fallback if a bank can show its dedicated interface meets specific high-level availability and performance criteria. Key Takeaway Under these RTS rules, banks must offer a dedicated interface for regulated third-party providers. Originally (during the legislative debates), “screen scraping” (i.e., connecting to the same web interface that humans use) was a sort of fallback approach. However, the EBA permitted national authorities to exempt banks from offering that fallback if they certified their dedicated interface worked reliably and supported the relevant PSD2 “account access” functionalities. In practice, a number of banks either: 1.Were granted “exemptions” from providing a fallback, thus disallowing TPPs (or “assistants”) from legally using the “normal web” route, or 2.Implemented partial or problematic APIs that hamper TPPs—but because an exemption was granted, TPPs do not have the legal right to revert to screen scraping without violating the RTS. That’s why you often hear it stated that “web UI/screen-scraping is effectively outlawed” in the EU for PSD2-related services (except in a few cases where no exemption was granted or local regulators allow it under strict conditions). Where to Look Up the Rules Directly 1.Directive (EU) 2015/2366 (PSD2) •Official text on EUR-Lex 2.Commission Delegated Regulation (EU) 2018/389 (RTS on SCA & CSC) •Official text on EUR-Lex 3.EBA Guidelines and Opinions •The EBA published various “opinions” clarifying how the RTS should be interpreted. For instance: •EBA Opinion on the implementation of the RTS on SCA and CSC (June 13, 2018) By reviewing Articles 30–34 of the RTS (EU 2018/389), you can see exactly how the rules oblige banks to provide an API and restrict fallback (screen-scraping) access—thus creating the scenario the original post complains about, where third-party “assistants” are forced to rely on a possibly subpar or incomplete official interface.

NOTE: Using OpenAi Operator at your bank in EU is illegal by law! Web access for assistants was banned years ago as part of “Open banking” Here is the story of why: 15 years ago I stumbled into Sofort in Germany. A company with the idea to build a digital assistant that would interact with your banks poor UI, so you as a user could avoid it. Just like operator. Back then it was script based, not AI but it worked. I was so impressed Klarna bought the company. It has since then processed billions of dollars. But of course banks got scared! What happens if people use the digital assistant only, instead of their bank. And what if the assistant says, stop paying those fees to your bank and let me help you switch? So German banks sued. They claimed privacy concerns. It went to Brussels and a long lobbying and legal fight pursued. This was the beginning of what we today call open banking! I and others spent years fighting over consumers right to use digital assistants, when accessing their banks. We knew this was critical to create real competition, in an industry that has been plagued by excess profits for years. At first Jonathan Hill from UK was responsible and very supportive. But then he left and a German guy came onboard. He was 100% aligned with incumbent banks and we thought the case was lost. However he did a mistake and let some Russian oligarchs take him for a ride on their private jet. And so he was out. Finally @VDombrovskis stepped in. He was smart and supportive but pressure from banks was intense. There was rumors that they were funding privacy groups in Germany, to have them use privacy concerns to kill Open Banking. What if the digital assistant accessed some of your private data? We were about to loose the vote, when the competitive authorities of EU started getting interested. They suspected the banks were lobbying and pursuing this matter for profit reasons to reduce competition(really…). A few weeks before the vote in parliament they raided the offices of some Dutch and Polish banks. Everyone got super nervous and the Open Banking regulation was passed! Almost… A small technical detail was left to EBA (European banking authorities). Should your digital assistant use an API for access to your bank account or the standard web UI you use yourself for accessing your bank? We pushed as hard as we could. We highlighted and said, if your assistant is mandated to use the API that your bank supplies. What if the API don’t support all the same features. Or the API is broken? Don’t worry said regulators. You can complain with authorities 😂 We said at least let the digital assistant, as fall back, use the web UI. Then banks cant cheat, as they will know we can always use the same UI as their human customers. It’s called self regulation. But EBA ignored us. Today web UI access for digital assistants as ChatGPT Operator is illegal by law. And surprise, surprise the open banking API of European banks, continue to be broken, lack functionality and banks add as much friction as they can. We report and see thousands of issues with these APIs every year. And people ask me why open banking has not become a larger success… What do you say @donaldtusk time for a change? Jest potrzebne!

"Sorry, No Secret to Life Is Going to Make You Live to 110" nytimes.com/2025/01/20/opi…

I continue to think this is one of the most important cartoons of recent years. @marketoonist