LightQR

981 posts

LightQR banner
LightQR

LightQR

@LightQR

https://t.co/SulnWcWzoR Ultra Low Latency Trading Market Data/Order in C++, Rust, FPGA, HDL. CME, US/EU equities, options, FX. https://t.co/CDECFSKpLy

Chicago Katılım Ağustos 2022
90 Takip Edilen165 Takipçiler
Sabitlenmiş Tweet
LightQR
LightQR@LightQR·
A critical warning to all U.S.-based creators on @substack You may be stepping into a hidden tax trap. Substack, partnered with Stripe, allows you to sell digital services globally without clear upfront alerts about VAT/GST obligations. For electronically supplied services like newsletters, non-EU sellers face immediate tax liabilities from the first sale in dozens of countries—yet many assume compliance is handled for them. This silent setup could leave thousands of creators vulnerable to back taxes, penalties, and audits. Stripe Tax collects the VAT, but remittance remains your responsibility, requiring registrations in each jurisdiction (e.g., EU OSS, UK VAT). Without action, what seems like a compliant platform could become a costly rabbit hole. Hiring a tax professional to manage payments in +50 countries could cost upwards of $20,000 USD per year—far beyond the reach of most independent digital creators. Compounding this, Substack does not allow web integrations, preventing the use of payment processors like Lemonsqueezy | Creative & Digital Solutions, which handles international taxes as a merchant of record. Substack is locked into @stripe , and Stripe relies on its partner @taxually , charging +$1,500 per month for a plan that covers only 10 countries. Very conveniently, Substack does not allow filtering subscriptions per country, leading unwary digital creators into this gargantuan tax trap by unknowingly accepting subscribers from jurisdictions with immediate tax obligations. As of today, October 14, 2025, creators are walking into this silent situation since Stripe and Substack give no warning about the potential non-compliance, perhaps in hopes that these individuals will become so tangled in this trap that they will start paying scorching prices charged by Taxually. Protect yourself: Let’s raise awareness and safeguard our creative businesses! #Substack #Stripe #VATCompliance #USCreators #TaxAwareness
LightQR tweet media
English
0
0
1
222
LightQR
LightQR@LightQR·
@EBaviation Jumento nao busca dados fica soʻ duvidando
Português
1
0
0
97
Honey 🛼
Honey 🛼@honeymoon250·
Can anyone?
Honey 🛼 tweet media
English
14.4K
355
2.9K
605.5K
JH Fonseca
JH Fonseca@JHdaFonseca·
### URGENTE: MERVAL PEREIRA (GLOBO) DIZ QUE GENERAIS JÁ FIZERAM CHEGAR AOS OUVIDOS DE LULA QUE MILITARES QUEREM SABER O QUE SERÁ FEITO DO SUPREMO. ### MILITARES ARGUMENTAM QUE FICARAM QUIETOS DURANTE JULGAMENTO DO 8 DE JANEIRO, MAS AGORA QUEREM EXPLICAÇÕES. eita!!!!!!!!!!!
Português
1.2K
1.2K
10.2K
221.3K
Open Source Intel
Open Source Intel@Osint613·
Hezbollah’s Qassem on Israel: “After the aggression against Iran and the killing of Khamenei, we decided the conditions were ripe to confront the enemy [Israel].”
English
16
23
252
57.2K
Open Source Intel
Open Source Intel@Osint613·
Tehran hit by US‑Israeli strikes, the aftermath.
English
27
114
617
49.2K
LightQR
LightQR@LightQR·
In 1965, three computer scientists at the Technische Hogeschool Eindhoven formalized something that every concurrent programmer eventually discovers: Courtois, Heymans, and Parnas gave us the readers-writers problem. The classic solution involves semaphores, monitors, or what we now call reader-writer locks. Every major operating system ships one. POSIX gave us pthread_rwlock. C++17 gave us std::shared_mutex. Problem solved, right? Not quite. This is Part 1 of a 5-part series on seqlocks. Part 2 covers the algorithm and its evolution. Part 3 surveys modern C++ implementations. Part 4 describes the benchmark methodology. Part 5 presents the results — including some numbers that surprised me. The Seqlock Shootout, Part 1: When Readers-Writers Locks Aren’t Good Enough, by @LightQR open.substack.com/pub/lucisqr/p/…
English
0
0
0
48
Independents For Trump
Independents For Trump@indyfor45th47th·
In Brazil, protesters shut down a road, but a car didn’t stop and drove through them. Was the driver's behavior justified? 🤔
English
602
166
1.7K
18.5K
Open Source Intel
Open Source Intel@Osint613·
The spokesman for Iran’s armed forces said that if Iran’s embassy in Lebanon is attacked, Israeli embassies worldwide will become legitimate targets.
Open Source Intel tweet media
English
134
78
463
196.4K
LightQR
LightQR@LightQR·
@taytarantula Com certeza alguma venda casada pra uma dessas industrias belicas.
Português
0
0
0
7
Lord Norman
Lord Norman@the_lord_norman·
@ricwe123 Did they deliberately let their entire government get killed to?
Lord Norman tweet media
English
112
28
2.5K
65.8K
Richard
Richard@ricwe123·
Up to this point, the Iranians have been deliberately sending out their outdated missiles and cheap drones as disposable decoys, fully aware they were expendable, just to bleed US and Israeli air defenses dry. And that strategy worked. Now they’re dropping the pretense. They’re moving on to their more sophisticated ballistic missiles and advanced drones, raising the stakes and tightening the pressure. Interceptor stockpiles are already running dangerously low, and the strain is hitting the United States, Israel, and their allies really hard.
English
2.9K
6.2K
28.6K
4.2M
LightQR
LightQR@LightQR·
@ricwe123 Do you think for a second this was a scenario they did not antecipate?
English
0
0
0
85
Truecaller
Truecaller@Samuelsworld·
🇺🇸🇻🇪 Como todos já sabiam, a captura do Maduro não tinha nada a ver com democracia, ditador, povo Venezuelano, liberdade, comunismo, ou pobreza. Os USA simplesmente precisava garantir o petróleo Venezuelano antes de atacar o Iran. O “novo” regime da Venezuela é exatamente o mesmo que antes, o mesmo partido, as mesmas pessoas… A única diferença que agora, por medo, são obrigado a dar o petróleo para os USA. O povo continua na mesma pobreza, com a mesma ditadura.
Bitcoin Teddy@Bitcoin_Teddy

Venezuela’s oil had to be secured before destabilising the Middle East If you know, you know

Português
451
4.2K
30.2K
982.3K