SDF Chatter

http://archive.today/2026.02.14-124214/https://www.nytimes.com/2026/02/13/technology/dhs-anti-ice-social-media.html

The Department of Homeland Security is expanding its efforts to identify Americans who oppose Immigration and Customs Enforcement by sending tech companies legal requests for the names, email addresses, telephone numbers and other identifying data behind social media accounts that track or criticize the agency.

In recent months, Google, Reddit, Discord and Meta, which owns Facebook and Instagram, have received hundreds of administrative subpoenas from the Department of Homeland Security, according to four government officials and tech employees privy to the requests. They spoke on the condition of anonymity because they were not authorized to speak publicly.

Google, Meta and Reddit complied with some of the requests, the government officials said. In the subpoenas, the department asked the companies for identifying details of accounts that do not have a real person’s name attached and that have criticized ICE or pointed to the locations of ICE agents. The New York Times saw two subpoenas that were sent to Meta over the last six months.

In September, for example, it sent Meta administrative subpoenas to identify the people behind Instagram accounts that posted about ICE raids in California, according to the A.C.L.U. The subpoenas were challenged in court, and the Department of Homeland Security withdrew the requests for information before a judge could rule.

The Department of Homeland Security also sought more information on the Facebook and Instagram accounts dedicated to tracking ICE activity in Montgomery County, Pa., outside Philadelphia. The accounts, called Montco Community Watch, began posting in Spanish and English about ICE sightings in June and, over the next six months, solicited tips from their roughly 10,000 followers to alert people to the locations of agents on specific streets or in front of local landmarks.

On Sept. 11, the Department of Homeland Security sent Meta a request for the name, email address, post code and other identifying information of the person or people behind the accounts. Meta informed the two Instagram and Facebook accounts of the request on Oct. 3.

“We have received legal process from law enforcement seeking information about your Facebook account,” the notification said, according to court records. “If we do not receive a copy of documentation that you have filed in court challenging this legal process within ten (10) days, we will respond to the requesting agency with information.”

The account owner alerted the A.C.L.U., which filed a motion on Oct. 16 to quash the government’s request. In a hearing on Jan. 14 in U.S. District Court for the Northern District of California, the A.C.L.U. argued that the government was using administrative subpoenas to target people whose speech it did not agree with.

Two days later, the subpoena was withdrawn.

Silicon Valley has long had an uneasy relationship with the federal government and how much user information to provide it. Transparency reports published by tech companies show that the number of requests for user information from different governments around the world has climbed over the years, with the United States and India among those submitting the most.

Some social media companies previously fought government requests for user information. In 2017, Twitter (now X) sued the federal government to stop an administrative subpoena that asked it to unmask an account critical of the first Trump administration. The subpoena was later withdrawn.

Page 8 of the dot2texi manual gives this example:

\documentclass{article}
\usepackage{tikz}
\usetikzlibrary{arrows,shapes}
\usepackage{dot2texi}
\begin{document}
% Define layers
\pgfdeclarelayer{background}
\pgfdeclarelayer{foreground}
\pgfsetlayers{background,main,foreground}
% The scale option is useful for adjusting spacing between nodes.
% Note that this works best when straight lines are used to connect
% the nodes.
\begin{tikzpicture}[>=latex’,scale=0.8]
% set node style
\tikzstyle{n} = [draw,shape=circle,minimum size=2em,
inner sep=0pt,fill=red!20]
\begin{dot2tex}[dot,tikz,codeonly,styleonly,options=-s -tmath]
digraph G {
node [style="n"];
A_1 -> B_1; A_1 -> B_2; A_1 -> B_3;
B_1 -> C_1; B_1 -> C_2;
B_2 -> C_2; B_2 -> C_3;
B_3 -> C_3; B_3 -> C_4;
}
\end{dot2tex}
% annotations
\node[left=1em] at (C_1.west) (l3) {Level 3};
\node at (l3 |- B_1) (l2){Level 2};
\node at (l3 |- A_1) (l1) {Level 1};
% Draw lines to separate the levels. First we need to calculate
% where the middle is.
\path (l3) -- coordinate (l32) (l2) -- coordinate (l21) (l1);
\draw[dashed] (C_1 |- l32) -- (l32 -| C_4);
\draw[dashed] (C_1 |- l21) -- (l21 -| C_4);
\draw[<->,red] (A_1) to[out=-120,in=90] (C_2);
% Highlight the A_1 -> B_1 -> C_2 path. Use layers to draw
% behind everything.
\begin{pgfonlayer}{background}
\draw[rounded corners=2em,line width=3em,blue!20,cap=round]
(A_1.center) -- (B_1.west) -- (C_2.center);
\end{pgfonlayer}
\end{tikzpicture}
\end{document}

It’s a broken example. gives:

ERROR: Package pgf Error: No shape named `C_1' is known.

An example in a manual should just work. What’s the problem?

Seems like a dead project. These two locations are mentioned in the manual and non-existent:

https://www.ctan.org/tex-archive/help/Catalogue/entries/dot2tex.html
http://www.fauskes.net/code/dot2tex/

(edit) CTAN location apparently moved here, but it may be out of maintenance:

https://www.ctan.org/pkg/dot2texi

All similare graphviz pkgs were last modified in 2018.

TL;DR: .. hosting a website on a 25-year-old Sun Netra X1 SPARC server running OpenBSD 7.8. The setup includes: Noctua fan mods for quiet operation, httpd serving static HTML/CSS, OpenBSD’s pf firewall with default-deny rules, and Cloudflare tunnels to expose it safely without port forwarding. The server pulls ~55MB of RAM and serves pages from my garage. Check it out live at sparc.rup12.net - because why not?

Well, the guy licks Cloudflare’s boots. Fuck that. He doesn’t understand the problem with that. So perhaps the real answer is NO, if he depends on Cloudflare Inc.

We are pleased to announce [registration] is now open for BSDCan 2026 and the slate of papers and tutorials are as follows.

BSDCan 2026 Talks:
* Evolving a FreeBSD-Based Chaos Engineering Platform for Teaching – Andreas Kirchner
* Running Stock FreeBSD on Windows Subsystem for Linux 2 – Balaje Sankar
* Model Checking in BSD Userland and Kernel – Justin Handville
* Through MAC and Back – Kyle Evans
* Lightning Talks – Graham Percival
* A Two-Step FreeBSD Installer: Current Status and Future Plans – Alfonso Sabato Siciliano
* How FreeBSD 15 Landed – Colin Percival
* Universal Flash Storage on FreeBSD – Jaeyoon Choi
* Supporting hibernate (S4) on FreeBSD – Olivier Certner
* FreeBSD Implementation of the SMT transport protocol – Eugenio Luo
* geomman: Bringing GParted-like Partition Management to FreeBSD – Braulio Rivas Abad
* Getting Extended Error Messages from the FreeBSD Kernel – Marshall Kirk McKusick
* OpenNTPD – 20 years and a few milliseconds later – Henning Brauer
* Return of the Segment: Thread Local Storage – John Baldwin
* Heterogeneous Scheduling on FreeBSD – Minsoo Choo
* NetManager – Building products with NetBSD round 2 – Stephen Borrill
* Bringing memory safety to BSD with CHERI – Brooks Davis
* Don’t Freeze in the Cloud: Reclaiming Home Control with NetBSD – Stefano Marinelli
* What happens when you write to /dev/null – Martin Vahlensieck
* Low friction temporary VMs on FreeBSD – Martin Vahlensieck
* ZFS AnyRAID: Flexible Disk Layout – Allan Jude
* BSD Iterative Infrastructure with ZFS and Zelta: From Battle-Tested Backups to Zero-Cost Iteration – Daniel Bell
* BSD as a Foundational Platform for Nationwide Semiconductor Education in Japan – Hiroki Sato
* pkgbase in Production: A Practical Overview – Lukas Engelhardt
* Migrating from VMWare to FreeBSD bhyve – Sarder Kamal
* Geographically fault-tolerant SSH on OpenBSD – Rob Keizer
* Community Event Organizing – Michael Dexter
* OpenBSD and Temporary Blindness – Sean Howard
* Using Coverity Scan for static code analysis in NetBSD – Emmanuel Nyarko
* How Hard Could It Be? Modernizing XigmaNAS for OpenZFS 2.4.0 – Ken Wong
* “Escaping Plato’s Cave with Software Freedom: A Classical Greek Symposium with Fred – Puffy – and Beastie” – Corey Stephan

Tutorials:

* VPP on FreeBSD Tutorial – Building high capacity networks – Massimiliano Stucchi
* Introduction to TUI Programming using bsddialog – Benedict Reuschling
* Shell Scripting Tutorial for Beginners and Sysadmins – Mathias Eggers
* Build Your Own Secure Private Cloud with FreeBSD – Nils Imhoff
* Network Management with the OpenBSD Packet Filter Toolset – Peter Hansteen

BoFs
* Audio BoF – Michael Williams

Registration is now open! The closing reception, including drinks, is now included for everyone who registers before May 1st 2026. Please be sure to click the box during registration if you’re planning to attend so we can get an accurate count. Vegans, vegetarians, and omnivores will be catered to as we continue to improve conference food offerings.

See you in June!

https://www.bsdcan.org/2026/registration.html

Ever since I was a kid, I was obsessed with utility poles and transmission towers. I have tons of random photos of them, I painted them, drew them, made linocuts of them, 3d models in blender... I have utility poles enframed on the wall over my monitor... just below a linocut of a transmission tower.

I just drew a utility pole I saw in Seoul, I think it's spot on, it's in front of a black hole.