I normally run this to get a slick and fast weather forecast for Amsterdam (over Tor) in a terminal:

curl -s --socks4a 127.0.0.1:9050 -A '' 'https://wttr.in/Amsterdam,Netherlands?lang=en&A='

It has been down for days now. I hope it’s temporary.

Suppose I have a fingerprint to a public key like this:

b1946ac92492d2347c6235b4d2611184

If I just drop that verbatim in a doc, it’s obviously an ergonomic struggle for someone who has to verify those numbers against what they see in an app. So it should be presented as something like this:

b194 6ac9 2492 d234 7c62 35b4 d261 1184

But if we manually add a space every 4 chars, that’s embarrassing manual labor for a nerd. Self-respecting nerds make the tool do the work for us.

This code does the job:

\newcommand{\mkergo}[2][$\cdot$]{% The mandatory arg is a fingerprint; the optional arg is the delimiter between 4-char groups
  \StrLen{#2}[\fplen]
  \newcounter{ilpos} % internal left position
  \newcounter{irpos} % internal right position
  \setcounter{irpos}{4}

  \whiledo{\not\value{irpos}>\fplen}{%
    \setcounter{ilpos}{\value{irpos}-4}
    \wlog{lpos::rpos is [\arabic{ilpos}..\arabic{irpos}]}
    \StrLeft{#2}{\value{irpos}}[\left]
    \wlog{left is \left}
    \StrGobbleLeft{\left}{\value{ilpos}}[\segment]
    \wlog{segment → \segment}
    \noindent\hspace{-32pt}\segment\ifthenelse{\value{irpos}=\fplen}{}{#1}% WTF, why do we need neg hspace?!
    \addtocounter{irpos}{4}
    }
}

calling it looks like this:

\mkergo[\,]{b1946ac92492d2347c6235b4d2611184}

or

\newcommand{\fingerprint}{b1946ac92492d2347c6235b4d2611184}
\mkergo[\,]{\fingerprint}

It works but it’s still not something to be proud of because if the readable version of the fingerprint is needed in multiple places, that loop must run everywhere it is needed. It’s also really ugly that I had to add \hspace{-32pt} -- what the fuck for? Why is there a huge space between segments?

How can that code be improved? I tried creating a \prettyfp (short for pretty fingerprint) command and then having the loop extend that, so the \prettyfp can be used without rerunning the loop. But it’s got a logical error.. the last 4 chars just gets repeated over and over. This is the code:

\makeatletter
\newcommand{\spaceout}[2][$\cdot$]{% The mandatory arg is a fingerprint; the optional arg is the delimiter between 4-char groups
  \StrLen{#2}[\fplen]
  \newcounter{lpos} % internal left position
  \newcounter{rpos} % internal right position
  \setcounter{rpos}{4}

  \whiledo{\not\value{rpos}>\fplen}{%
    \setcounter{lpos}{\value{rpos}-4}
    \wlog{S/O lpos::rpos is [\arabic{lpos}..\arabic{rpos}]}
    \StrLeft{#2}{\value{rpos}}[\left]
    \wlog{S/O left is \left}
    \StrGobbleLeft{\left}{\value{lpos}}[\segment]
    \wlog{S/O segment → \segment}
    \g@addto@macro\prettyfp{\segment\ifthenelse{\value{irpos}=\fplen}{}{#1}}
    \addtocounter{rpos}{4}
    }
}
\makeatother

That was inspired by the 1st answer on this page.

What’s my problem?

How can this be improved?

cross-posted from: https://lemmy.sdf.org/post/51259064

Shopping for airfare is clearly a game full of shenanigans. You find a cheap ticket, get a (likely fake) indicator warning how few seats are available with a countdown timer, rush through a lengthy process of being forced to make a shit-ton of decisions like whether you want to buy an neck wrap, selfie stick, a bad travel insurance deal, .. lots of shit to get through to slow you down. You finally get to the last screen and it says “price has increased since we first quoted you”. Motherfuckers.

Considering aircraft are quite shitty for climate, why not make the airlines shenanigans backfire against them? We have bots arbitrarily hit the air travel sites, enter bogus orders but never submit the last page. Just give the airlines a false indicator of demand. This games their dynamic pricing to quote prices higher than optimum. Any deviation from optimum prices translates into lower profit, likely a consequence of lower sales.

Perhaps an org like Greenpeace would be interested in this tactic.

Shopping for airfare is clearly a game full of shenanigans. You find a cheap ticket, get a (likely fake) indicator warning how few seats are available with a countdown timer, rush through a lengthy process of being forced to make a shit-ton of decisions like whether you want to buy an neck wrap, selfie stick, a bad travel insurance deal, .. lots of shit to get through to slow you down. You finally get to the last screen and it says “price has increased since we first quoted you”. Motherfuckers.

Considering aircraft are quite shitty for climate, why not make the airlines shenanigans backfire against them? We have bots arbitrarily hit the air travel sites, enter bogus orders but never submit the last page. Just give the airlines a false indicator of demand. This games their dynamic pricing to quote prices higher than optimum. Any deviation from optimum prices translates into lower profit, likely a consequence of lower sales.

Perhaps an org like Greenpeace would be interested in this tactic.

Apparently IPFS is having a slow adoption problem -- despite being an important solution to the enshitified gated centralised web.

Debian stands as the most popular among the well-supported distros. Debian has some degree of quality standards that (although not spectacular) relatively far surpass most distros. A package making it into the official Debian repos generally demonstrates that an app is up to scratch -- ready for prime time.

If I have not overstated things, it must be at least somewhat embarrassing for both the IPFS project and Debian that IPFS has no client in the official Debian repos. IPFS should have targetting Debian as a goal to get respect and adoption.. to get on the radar. It’s just a tarball now.

And from Debian’s standpoint, it’s not great that an important protocol to succeed HTTP is missing from official support.

(ignore the above massive preview text if you are using the shitty stock Lemmy client)

The bombshell is that Elon exfiltrated the social security records of all Americans and shared it with Cloudflare, DOGE, and an outside advocacy group seeking to overturn election results.

The fuckup is not just SSNs (slave surveillance numbers), it’s the whole 9 yards:

“DOGE team members were given access to databases containing:

• Social Security numbers
• medical and mental health records
• bank and credit card information
• tax details
• work histories
• and home addresses for millions of Americans.”

I suppose getting a new SSN is futile, even if permitted, because all this data is aggregated into the data breach. So change your name, move your residence, new SSN, switch banks... fuck, just leave the country perhaps.

(edit) I accidentally updated an older version of my post and lost a paragraph where I conjectured that the databreach was legal since it only violates the 4th Amendment, which the US tends to brush aside as we know from the Snowden revelations. Hence the correction from @ReptilianCleric@lemmy.zip below. Sorry! No version control on Lemmy.

Lemmy is running but all pages present an error message. The site is wholly unusable.

Considering this community is hosted by infosec.pub, it will be interesting to see who sees this post. I suspect only sdf.org folks will see this.

cross-posted from: https://lemmy.sdf.org/post/50981571

2fa.directory catalogs services that use multifactor authentication. Of course the idea is to inform consumers of which services satisfy a basic standard of security. Services that are centralised on Cloudflare appear with a green checkmark, as if there is nothing wrong with sharing all your login details with a privacy abusing fiefdom in a country without privacy safeguards through a MitM arrangement.

If one of the auth factors has a MitM, that’s effectively 1 factor less. 2fa becomes like 1fa.

It’s a gross oversight and the bug tracker is limited to MS Github users. A Github user should raise an issue to point this out.

2fa.directory catalogs services that use multifactor authentication. Of course the idea is to inform consumers of which services satisfy a basic standard of security. Services that are centralised on Cloudflare appear with a green checkmark, as if there is nothing wrong with sharing all your login details with a privacy abusing fiefdom in a country without privacy safeguards through a MitM arrangement.

If one of the auth factors has a MitM, that’s effectively 1 factor less. 2fa becomes like 1fa.

It’s a gross oversight and the bug tracker is limited to MS Github users. A Github user should raise an issue to point this out.

cross-posted from: https://lemmy.sdf.org/post/50840810

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.

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.