Sometimes it’s nice when you can do everything you need to do with just one single port. In this vein, [Nicola Strappazzon] whipped up a circuit to combine serial and UPDI programming in a very convenient way.

As an example, [Nicola] demonstrates the concept using an AVR128DA28 microcontroller. It’s paired with a 4052 multiplexer IC and a CH340 USB-to-serial chip. Everything is wired up such that the 4052 acts as a switch for the signal coming from the CH340. When the RTS flow-control signal is set high, it switches the 4052 to hook up the CH340’s RX and TX pins to the UDPI interface on the AVR microcontroller. Conversely, when the RTS signal is set low, the CH340 is instead hooked up to the serial UART on the microcontroller. From there, it’s a simple matter of configuring avrdude to properly set the RTS pin when attempting to program the attached device.

If you’re working with UPDI devices and you want to be able to talk to them and program them with a minimum of fuss, this project might be useful for you. We’ve looked at dedicated UPDI programmers before, too. If you’re cooking up your own nifty microcontroller hacks, don’t hesitate to let us know on the tipsline.

hackaday.com/2025/10/04/serial…

Un fornitore di servizi clienti di terze parti è stato compromesso dagli hacker, che hanno avuto accesso a informazioni parziali sui pagamenti e a dati di identificazione personale relativi ad alcuni utenti di Discord. L’attacco, avvenuto il 20 settembre, ha interessato un numero limitato di utenti che avevano avuto contatti con l’assistenza clienti di Discord e/o con i team Trust and Safety.

La società di messaggistica, nella notifica inviata agli utenti coinvolti, precisa che il 20 settembre si è verificato l’attacco e che “un soggetto non autorizzato ha acquisito un accesso ristretto ad un sistema di supporto clienti di terza parte usato da Discord”.

Originariamente concepito come mezzo di comunicazione per appassionati di videogiochi, che costituiscono più del 90% degli utenti iscritti, Discord si è trasformato in una piattaforma versatile accogliente varie comunità, offrendo la possibilità di scambiare messaggi tramite testo, intrattenere conversazioni attraverso chat vocali e effettuare videochiamate.

Venerdì, Discord ha reso pubblico l’incidente, affermando di aver preso provvedimenti immediati per isolare il fornitore di supporto dal suo sistema di ticketing e di aver avviato un’indagine. “Ciò include la revoca dell’accesso del fornitore di assistenza clienti al nostro sistema di ticketing, l’avvio di un’indagine interna, l’assunzione di una società leader di informatica forense per supportare i nostri sforzi di indagine e bonifica e il coinvolgimento delle forze dell’ordine”.

L’attacco pare avere una natura finanziaria, visto che gli hacker hanno richiesto a Discord un pagamento per non divulgare le informazioni trafugate. Secondo le statistiche della piattaforma, più di 200 milioni di persone utilizzano Discord ogni mese.

Le informazioni trapelate comprendono dati personali identificativi, quali nomi effettivi e nomi utente, indirizzi e-mail e ulteriori informazioni di contatto fornite all’équipe di supporto. Il servizio di comunicazione sociale ha reso noto che sono stati violati anche indirizzi IP, messaggi e allegati scambiati con gli agenti del servizio clienti. Gli hacker hanno avuto accesso anche alle foto dei documenti di identità rilasciati dal governo (patente di guida, passaporto) di un numero limitato di utenti.

Ad oggi, resta incerto il numero di utenti Discord coinvolti e non è stato divulgato il nome del fornitore esterno o del vettore di accesso. E’ importante sottolineare che numerose aziende hanno subito violazioni delle loro istanze Salesforce in seguito all’intrusione del gruppo di estorsione ShinyHunters, i quali hanno sfruttato token OAuth rubati da Salesloft e Drift per ottenere l’accesso.

L'articolo Discord conferma attacco hacker: informazioni sensibili a rischio proviene da il blog della sicurezza informatica.

It was one of those weeks last week at Hackaday’s home office. My mother-in-law handed me her favorite power bank and said “it’s not charging”. She had every expectation that I’ll open it up, desolder the weary pouch inside, scrounge a LiPo out of some corner of the basement, and have it back up and running before the weekend. And of course that’s what happened, although maybe it looks a little worse for wear because it was hard to open the sealed case without excessive force. Sorry about that!

Then on the weekend, I finally got fed up with the decomposing foam on the face seal on my FPV goggles. It was leaking light all over the place. Of course I could have bought a new seal, but then I’d have to wait a week or so for delivery. So I pulled the velcro backing off, tossed it in the bed scanner, pulled the image up in Inkscape, converted it to Gcode, and cut out a couple seals out of EVA foam on the laser. Not only are they essentially indestructible, but I was able to customize them a little bit, and the fit is now better than ever.

And then, one of our neighbors bought a new garage door fob, flipped the DIP switches into the right configuration, and couldn’t figure out why it wouldn’t open the garage door. Knock knock knock. Using the tried-and-true RF probe that everyone with a scope probe has sitting around, namely hooking the ground pin to the tip and putting the radio device in the loop, it was clear that the sense of the DIP switches was inverted from what it said in the instructions. That was a fun little puzzle.

It was the garage door opener that triggered me to think about how normal people would handle any of these situations. “How do the normies even get by?” were the exact words that went through my head. And let’s face it: we’re not entirely normal. Normal people don’t have a soldering setup just sitting around ready to get hot 24/7, or a scope to diagnose a garage door RF transmitter at the drop of a hat. But these things seem to happen to me all the time. How do the normal people survive? Maybe they all know someone with a scope?

I take it as my service to the world to be “that guy” for most of our friends and family, and I pretty much do it without complaint. “With great power” and all that. My wife is just about as gracious when she’s stuck debugging a parent’s Windows setup, so I’m not saying I’m the only saint in the world, either. Surely you have similar stories.

But last week it made me reflect on how good we’ve got it, and that does make me want to pay it forward a little bit. If you’re one of the people who can, try to help out those who can’t.

This article is part of the Hackaday.com newsletter, delivered every seven days for each of the last 200+ weeks. It also includes our favorite articles from the last seven days that you can see on the web version of the newsletter. Want this type of article to hit your inbox every Friday morning? You should sign up!

hackaday.com/2025/10/04/how-do…

It’s a well-known conundrum that while most computers these days are digital in nature, almost nothing in nature is. Most things we encounter in the real world, whether it’s temperature, time, sound, pressure, or any other measurable phenomenon comes to us in analog form. To convert these signals to something understandable by a digital converter we need an analog-to-digital converter or ADC, and [Igor] has built a unique one from scratch called a delta sigma converter.

What separates delta sigma converters apart is their high sampling rate combined with a clever way of averaging the measurements to get a very precise final value. In [Igor]’s version this average is provided by an op-amp that integrates the input signal and a feedback signal, allowing for an extremely precise digital value to be outputted at the end of the conversion process. [Igor] has built this one from scratch as well, and is using it to interface a magnetic rotary encoder to control digital audio playback.

Although he has this set up with specific hardware, he has enough detail in his video (including timing diagrams and explanations of all of the theory behind these circuits) for anyone else to build one of these for other means, and it should be easily adaptable for plenty of uses. There are plenty of different ADC topologies too, and we saw many different ones a few years ago during our op-amp challenge.

youtube.com/embed/xxEFUu-V63g?…

hackaday.com/2025/10/04/a-high…

La storia di SoopSocks è quella che, purtroppo, conosciamo bene: un pacchetto PyPI che promette utilità — un proxy SOCKS5 — ma in realtà introduce un impianto malevolo ben orchestrato.

Non stiamo parlando del solito script improvvisato; dietro SoopSocks c’è una catena di azioni pensata per ottenere persistenza, ridurre il rumore e stabilire un canale di comando/controllo stabile. Il pacchetto è stato pubblicato su PyPI (Python Package Index), il registro ufficiale dei pacchetti Python.

Il pacchetto ingannevole, denominato “soopsocks“, ha totalizzato 2.653 download prima di essere rimosso. È stato caricato per la prima volta da un utente di nome “soodalpie” il 26 settembre 2025, la stessa data di creazione dell’account.

Questa combinazione è pensata per massimizzare la percentuale di successo: componenti compilati per l’esecuzione, script per l’integrazione e meccanismi nativi per la persistenza. Il risultato è un pacchetto che funziona come “utility” e nello stesso tempo costruisce un punto di appoggio remoto.

Strategia dell’attaccante: stealth e affidabilità

SoopSocks si presentava come una libreria Python, riportano i ricercatori di sicurezza, per offrire un proxy SOCKS5. In realtà, su Windows metteva in piedi un piccolo impianto di backdoor persistente: si installava come servizio, apriva la porta giusta sul firewall, rimaneva attivo ai riavvii e inviava periodicamente informazioni all’esterno.

Come entra e si installa: dopo l’installazione, il pacchetto non si limitava ai moduli Python. In alcune versioni depositava un eseguibile compilato (scritto in Go) e uno o più script di orchestrazione (PowerShell/VBScript). Questi componenti servivano per:

• installare un servizio Windows con avvio automatico (così si riaccendeva ad ogni boot);
• predisporre un piano B di persistenza tramite un’attività pianificata, se la creazione del servizio falliva;
• eseguire comandi PowerShell in modalità “silenziosa” (bypassando le execution policy e riducendo i messaggi a schermo) per configurarsi e restare sotto traccia.

Cosa fa una volta attivo

Ufficialmente esponeva un proxy SOCKS5 (tipicamente sulla porta 1080). Dietro le quinte:

• aggiungeva regole al firewall per aprire la porta del proxy, così il traffico in ingresso non veniva bloccato;
• manteneva persistenza (servizio + task) in modo da sopravvivere a riavvii o tentativi di “pulizia” incompleti;
• avviava una telemetria a basso profilo: a intervalli regolari raccoglieva informazioni sulla macchina (nome host, versione del sistema, configurazione e stato della rete, indirizzi IP) e le spediva verso l’esterno usando canali comuni (HTTPS), di solito con pacchetti piccoli e frequenti per non dare nell’occhio.

Perché è difficile da notare

Molte azioni passavano per strumenti legittimi di Windows (PowerShell, Task Scheduler, gestione firewall). Agli occhi di un monitoraggio basato solo su firme, queste operazioni possono sembrare normali attività amministrative. Inoltre, offrendo davvero un SOCKS5 “funzionante”, il pacchetto abbassava la soglia di sospetto: chi lo provava vedeva che “fa il suo dovere” e raramente andava a controllare i componenti extra.

Il punto chiave

SoopSocks univa funzionalità utile (il proxy) e meccaniche di intrusione/persistenza ben note. Questo mix trasformava una libreria apparentemente innocua in un punto d’appoggio remoto: un host che l’attaccante può usare come proxy controllabile e da cui raccogliere dati, con un profilo di “rumore” di rete volutamente basso.

Questa strategia dimostra una conoscenza pratica di come operano team di difesa aziendali: gli attaccanti progettano le loro tecniche per apparire «normali» rispetto al profilo operativo quotidiano. L’utilizzo di ambienti di sviluppo, come punto di diffusione, permette di creare punti di persistenza per movimenti laterali. Inoltre l’utilizzo i repository interni/locali possono conservare versioni malevoli anche dopo che sono state rimosse online, perché restano in cache.
Senza regole di verifica e pulizia periodica, i team di sviluppo rischiano di continuare a usarle senza accorgersene.

SoopSocks non ha rivoluzionato il panorama delle minacce, ma ha mostrato come la combinazione di componenti legittimi e tecniche già collaudate possa trasformare una libreria in un serio vettore di compromissione. Per le organizzazioni la sfida non è solo tecnica, ma soprattutto processuale: difendere la filiera software richiede controlli e procedure

L'articolo SoopSocks: il pacchetto PyPI che sembrava un proxy ma era una backdoor per Windows proviene da il blog della sicurezza informatica.

Dear Friend of Press Freedom,

After over 100 days in U.S. Immigration and Customs Enforcement custody, Mario Guevara was deported today. Read on for more about this and other press freedom abuses, and take a minute to tell your lawmakers to stand up for journalists victimized by ICE.

ICE is on a violent rampage against the press

Federal immigration officers reportedly promised a “shitshow” last weekend in response to criticism from the mayor of Broadview, Illinois, who didn’t appreciate her city being invaded. They delivered, and journalists were well represented among their victims.

One journalist, Steve Held, was arrested. Others, including Held’s reporting partner at Unraveled Press, Raven Geary, were shot in the face with pepper ball rounds. According to lawyers on the scene, the protests the reporters were covering were peaceful and uneventful until ICE officers decided to unleash chaos.

A few days later at an immigration court in New York City, where ICE agents have been trying to intimidate journalists for months, agents assaulted at least three journalists, one of whom couldn’t get up and had to be hospitalized. You can read what we told Chicago’s The Triibe about the Broadview attacks and New York’s amNY about the New York ones.

More importantly, you can tell your lawmakers to speak out against ICE’s abuses using our new, easy-to-use action center. Take action here.

Journalist Mario Guevara deported to El Salvador

After months of hard-fought battles in both the court of law and the court of public opinion, the Trump administration deported journalist Mario Guevara today. This case wasn’t about immigration paperwork — Guevara had a work permit, and the administration argued in court that Guevara’s reporting on protests posed a national security risk.

“The only thing that journalists like Guevara threaten is the government’s chokehold on information it doesn’t want the public to know. That’s why he’s being deported and why federal agents are assaulting and arresting journalists around the country,” FPF’s Seth Stern said after Guevara’s family announced his deportation.

Read the statement here.

Guilty of journalism in Kentucky

Student journalist Lucas Griffith was convicted of one count of failure to disperse and fined $50 plus court costs after a jury trial on Thursday.

That’s unconstitutional — even the U.S. Department of Justice recognizes journalists’ right to cover how law enforcement disperses protesters.

But it also shows what a giant waste of taxpayer funds it is to prosecute journalists for doing their jobs. Before the trial, we led a coalition letter from press freedom advocates and journalism professors objecting to the charges. Read it here.

FPF and 404 Media sue DHS

FPF and 404 Media filed a lawsuit against multiple parts of the U.S. government, including the Department of Homeland Security, demanding they hand over a copy of an agreement that shares the personal data of nearly 80 million Medicaid patients with ICE.

It’s just one of several recent lawsuits we’ve filed under the Freedom of Information Act. We also surpassed 200 FOIAs filed in 2025 this week. Subscribe to The Classifieds newsletter for more on our FOIA work.

Read more from 404 Media.

FCC censorship moves from prime time to prison

Federal Communications Commission Chair Brendan Carr has taken a lot of heat for his “mafioso”-style extortion of ABC over Jimmy Kimmel’s show. But his latest censorship effort is even more dangerous. It could strip those inside America’s most secretive institutions — its prisons — of a tool that has proved extremely effective in exposing abuses.

We partnered with The Intercept to publish incarcerated journalist and FPF columnist Jeremy Busby’s response to the FCC’s efforts to allow prisons to “jam” cell phones. Busby used a contraband phone to expose and force reform of horrific conditions in Texas prisons during the pandemic. Read his article here.

Photography is not a hate crime

The arrest of Alexa Wilkinson on hate crime charges for photographing vandalism at The New York Times building has prompted hair splitting about whether they’re a journalist. It’s giving us flashbacks to the pointless obsession over whether Julian Assange was a journalist, and not whether his prosecution endangered press freedom.

Stern explains that regardless of how we categorize Wilkinson’s work, the charges set dangerous precedents that threaten the constitutional protections journalists depend on to do their jobs. Read more here.

What we’re reading

DC Circuit rejects Fox News reporter effort to duck subpoena over anonymous source (Courthouse News). “This decision does real damage to bedrock principles of press freedom, and we urge the Court of Appeals to re-hear this case with a full panel of judges,” FPF’s Trevor Timm said.

Can the US government ban apps that track ICE agents? (BBC). “That somebody might use the app to break the law doesn’t mean the app can be banned,” Stern told BBC. After the interview, news broke that the administration successfully pressured Apple to pull the app.

Reporter’s suit over access to Utah Capitol dismissed (U.S. Press Freedom Tracker). This dismissal is nonsense. FPF’s Caitlin Vogus explained why in the Salt Lake Tribune earlier this year.

Israel illegally boards humanitarian flotilla heading to Gaza (Dropsite). A U.S. journalist was on board. The U.S. Department of State should be all over this and it should be headline news. Neither is likely, because the government considers critics of Israel terrorists and the media often shuns reporters who oppose slaughtering their Palestinian colleagues.

FPF welcomes Adam Rose to bolster local advocacy

FPF is excited to welcome Adam Rose as the new deputy director of our advocacy team. Adam will primarily focus on protecting press freedom at the local level, where we have seen a sharp increase in arrests and assaults of journalists all around the country — many of which have not made national headlines.

Adam comes to FPF after serving as the chief operating officer of Starling Lab for Data Integrity and as the press rights chair of the Los Angeles Press Club, where he has been a tireless advocate for the press freedom rights of journalists in the LA area. He successfully lobbied for a California law that prohibits police from arresting or intentionally interfering with journalists as they cover protests. Most recently, as a plaintiff in multiple press freedom-related lawsuits, his efforts have resulted in landmark federal court orders against both the Department of Homeland Security and Los Angeles Police Department for violating the rights of the press. Read more here.

freedom.press/issues/ice-is-on…

404 Media

2025-10-01 14:25:57

404 Media and Freedom of the Press Foundation Sue DHS

Last week Freedom of the Press Foundation and 404 Media filed a lawsuit against the multiple parts of the U.S. government demanding they hand over a copy of an agreement that shares the personal data of nearly 80 million Medicaid patients with ICE. The data sharing marked a watershed moment for ICE and its access to highly sensitive data that is ordinarily siloed off from the agency. We believe it’s important for the public to see this unprecedented data sharing agreement for themselves.

As the Associated Press wrote when it first reported on the data sharing agreement between the Department of Homeland Security (DHS) and the Centers for Medicare and Medicaid Services (CMS), the agreement will give ICE the ability to find “the location of aliens.” The data shared includes home addresses and ethnicities, according to the Associated Press.

💡
Do you know anything else about this data sharing agreement? I would love to hear from you. Using a non-work device, you can message me securely on Signal at joseph.404 or send me an email at joseph@404media.co.

Both Freedom of the Press Foundation and 404 Media filed similar Freedom of Information Act (FOIA) requests with DHS and CMS seeking a copy of the agreement. Neither agency provided the requested records in time, so we have now filed the lawsuit. In 404 Media’s case, CMS acknowledged the request but has not provided the records, and DHS did not even acknowledge the request at all.

404 Media’s request asked for a copy of the specific agreement, and if the agencies were unable to locate it, to alternatively provide copies of all agreements between DHS and CMS from this year.

“Despite having received the FOIA requests, and despite their obligations under the law, Defendants have failed to notify Plaintiffs of the scope of documents that they will produce or the scope of documents that they plan to withhold in response to the FOIA requests,” the lawsuit reads.
playlist.megaphone.fm?p=TBIEA2…
Freedom of the Press Foundation is a non-profit organization that monitors press freedom issues in the U.S. and trains journalists on how to keep themselves and their sources safe. It regularly sues the U.S. government for access to records.

The data sharing agreement is just one of a growing list of ways that ICE is sourcing highly sensitive, and sometimes legally protected, information as part of the Trump administration’s mass deportation effort. ProPublica reported on the vast system the IRS is building to share millions of taxpayers’ data with ICE. 404 Media previously reported ICE has gained access to ISO Claimsearch, a massive insurance and medical bill database to find deportation targets. The database is nearly all encompassing and contains details on more than 1.8 billion insurance claims and 58 million medical bills.

Separately, 404 Media filed a lawsuit against ICE in September for access to the agency’s $2 million spyware contract.

If you want to support this work, become a paid subscriber here. If you would like to make a larger, tax deductible donation, please email us at donate@404media.co.

Membership

404 Media is a new independent media company founded by technology journalists Jason Koebler, Emanuel Maiberg, Samantha Cole, and Joseph Cox.

^{Outpost Staff (404 Media)}

The arrest of Alexa Wilkinson on felony hate crime charges for photographing vandalism at the New York Times building has prompted hairsplitting about whether they’re a journalist. The New York Times explained that Wilkinson’s “lawyers described them as a journalist, but did not name any publications for which Mx. Wilkinson works.”

Wilkinson certainly has a track record as a journalist. Whether the content they were charged for is journalism or PR is, I suppose, up for debate. But should we even bother debating it? Regardless of how we categorize Wilkinson’s work, the charges set dangerous precedents that threaten the constitutional protections journalists depend on to do their jobs.

As we all learned — or should have learned — from the Julian Assange prosecution, obsessing over whether a particular defendant meets someone’s arbitrary definition of journalism is a waste of time. What that case left us with at the end of the day is a Trump administration armed with a bipartisan consensus that routine journalistic acts, like talking to sources, obtaining government secrets, and publishing them, can be prosecuted as a felony under the Espionage Act. Those who change their tune when the next defendant is someone they like better than Assange will be easily discredited by their hypocrisy.

The same dangers apply when Wilkinson’s photography is treated as a hate crime. Wilkinson’s case stems from a July protest in which activists doused the Times headquarters in red paint and spray-painted “NYT lies, Gaza dies” on its windows. In addition to charging the vandals, New York prosecutors charged Wilkinson, who photographed the scene, with aggravated harassment as a hate crime.

New York authorities should be combating these cynical attempts to use antisemitism to justify authoritarianism. Instead, they’re fueling the trend.

But there was no hate crime. Vandalizing a building to protest perceived pro-Israel bias in news coverage is a political statement, not an antisemitic one. The vandalism may well be illegal, and we condemn it, as news outlets large and small are under increased threat in this charged political environment. We even documented the vandalism itself in our U.S. Press Freedom Tracker.

But labeling actions that criticize a newspaper’s editorial decisions as a hate crime conflates political views with bigotry. Many journalists object to Israel’s slaughter of their peers in Gaza — and the U.S. media’s relative silence about it — for reasons having nothing to do with anyone’s religion. And many Jews themselves oppose Israel’s actions in Gaza and object to coverage they view as excusing or normalizing Israel’s conduct.

I’m one of those Jews, and I think what’s antisemitic is to assume that we monolithically share the politics of Benjamin Netanyahu and his ilk, who I consider the worst thing to happen to Judaism since the 1940s. As the saying goes, one day everyone will have been against this. When that time comes, efforts to conflate anti-Israel or anti-genocide views with antisemitism will leave Jews holding the bag for Israel’s reprehensible actions, America’s role in supporting them, and whatever blowback follows. That’s when the real antisemitism will start.

New York authorities should be combating these cynical attempts to use antisemitism to justify authoritarianism. Instead, they’re fueling the trend. Wilkinson’s case, in a blue state, legitimizes the Trump administration’s un-American actions, like its efforts to deport Mahmoud Khalil over his criticisms of Israel and Rümeysa Öztürk for co-writing an op-ed arguing for boycotts of Israeli products. The administration baselessly argues that their constitutionally protected speech constitutes support for Hamas and threatens national security. And several Republican attorneys general have floated the idea that reporting critical of Israel could be punished as support for terrorism. Wilkinson’s case only gives cover to those advancing these absurd arguments.

Israel showed us exactly where conflating speech with violence leads. Last month, Israel killed 31 journalists in airstrikes on newspaper offices in Yemen — the deadliest single attack on the press in 16 years, according to the Committee to Protect Journalists. Israel has justified the strikes by characterizing the targeted outlets as publishing “terrorist” propaganda.

Should we debate whether those massacred in Yemen (or Gaza) followed the Associated Press Stylebook or strictly adhered to journalistic codes of ethics? Or should we just acknowledge that militaries shouldn’t blow people to bits over what they say and write, regardless of whether it’s bad journalism or even propaganda?

Even setting aside the hate crime charge, Wilkinson’s case has broader implications for the press that don’t hinge on whether they’re a card-carrying member. The complaint against Wilkinson reportedly emphasizes not just the photographs they took but also social media posts criticizing Times staff and alleged foreknowledge of the vandalism. This suggests prosecutors view Wilkinson as complicit because of proximity or sympathy to those who committed it and awareness of their plans.

But objectivity is not a precondition for constitutional protection. It’s a relatively recently developed journalistic norm — with its share of critics — that would have been seen as ridiculous when the First Amendment was written.

Should we debate whether those massacred in Yemen (or Gaza)...adhered to journalistic codes of ethics? Or should we just acknowledge that militaries shouldn’t blow people to bits over what they write?

As for embedding and foreknowledge, journalists routinely embed with groups whose members commit illegal acts. For example, the Israeli army, which, according to the United Nations, is committing genocide. Domestically, police reporters ride along with officers who may use excessive force. Investigative journalists cultivate sources involved in criminal activity. If foreknowledge of illegal acts or presence when they occur makes one legally complicit, journalism as we know it becomes impossible.

And for those concerned about journalistic ethics and objectivity, what impact do you think it’ll have if reporters are allowed to embed with government-approved lawbreakers, like soldiers and police, but not dissidents? Will that result in “fair and balanced” coverage?

Your opinion about Wilkinson’s work won’t change the trajectory of our democracy. But prosecutors in America’s biggest city validating the Trump administration’s criminalization of dissent very well might. Every journalist — and everyone who depends on journalism to hold power to account — should be alarmed.

freedom.press/issues/journalis…

Per testimonianze più vere, cercate sui social (di meta ahimè...)
cdt.ch/news/ticino/in-piazza-p… (ah! hanno cambiato l'articolo nel frattempo - stamattina c'era scritto diverse centinaia di persone)

#blocchiamotutto #Lugano #globalsumudflotilla #manifestazione #gaza #palestinalibera

In piazza per la Flotilla: un migliaio di manifestanti e disagi al traffico a Lugano

Da piazza Dante allo svincolo autostradale, tante persone hanno partecipato al corteo scandendo slogan a sostegno della Global Sumud Flotilla - Traffico bloccato in entrata e uscita a causa di un'ora di sit-in ai semafori di Lugano Sud - FOTO E VIDEO

^{Valentina Coda (Corriere del Ticino)}