@nobody Because bridges can obfuscate their connections. There are both public bridges and private (or semi-private) bridges.

@nobody There actually do exist bridge enumeration attacks, where an adversary runs a number of middle (non-guard and non-exit) relays and logs who connects to them. A connection from any IP which is not listed in the Tor consensus file as a guard must be a bridge. I believe China uses that as one technique to find popular bridges.

@belkarx It's incredible. The article weaves the adventurous story of the brave investigators and police on their holy and righteous mission, hunting the villains and sticking together through thick and thin, cracking the hardest case with their superior forensic knowledge. But the reality? A better article would be titled "Feds spend years being outsmarted by idiot pedo who literally revealed his real IP on every page of his shitty site".

I think we need a canonical post for the DRM thing.

Way too many people come and say I want to do $thing (which equivalent to DRM). You tell them its impossible, they just "Oh I know you can't have perfect security, how can I achieve the best balance?"

Did he even read the patent?

As far as I can tell, that patent is about attributing the telemetry to the source so that known unreliable sources can be filtered out. I can't find anything about preventing fake telemetry from being submitted in the first place.

@nobody Did the OP RTFM? The answer is (almost) always no.

The fact that micro-ITX is larger than mini-ITX will forever confuse me.

@MechMK1 it's mini ATX

Also ATX is Intel, ITX is I think via

There was also btx which was kinda wierd

Should questions like security.stackexchange.com/questions/261112/… be moved to Crypto.SE?

@FireQuacker Yes, that's the type of questions one can see on the NIST's PQC mailing list.

@FireQuacker Absolutely

Also I genuinely don't understand the obsession with Vim. 99.9% of programmers work in an IDE, and the other 0.1% are just salty they learned a skill that's now basically obsolete.

And further, most time programming is spent reading code, not writing it - and there, IDEs are definitely superior.

Vim is not for programming. It's for editing config files.

On remote servers without GUI.

Any other text editor does just as well and is more intuitive

More intuitive: yes, that's not hard. Just as well, I beg to differ.

A text editor should not require people googling how to use it, especially not 2.6 million times

How often do you really need to make complex changes to a config file

Just use Nano if you want simple

And not just insert a line, copy a line, edit "true" to "false", etc...

Use Vim if you want regexp included

How often do you change config files using regular expressions?

Often

%s/^/# /

So you comment out everything?

Or more likely:

:'<,'>s/^/# /

(I did not have the correct syntax in mind because Vim expends it automatically)

:D

And the syntactic coloration is nice too

nano has that too

Really? I never use nano, because I always add ":x" and such like characters.

When I just want to read a file, I use bat.

@MechMK1 Its very much a "Look! I am an old greybeard!'

@JourneymanGeek It feels more like "I'm so much better because I learned this thing" feeling

@MechMK1 same difference

Unlike the things I learned that are now obsolete.

They're way better

Fundamentally it should be down to the tools you're happy with/do the best job with

Yep

So I have nano with every box and am not embarassed to download and work on a config file with sublime text or VS code or some other newfangled text editor

SSHFS?

hm, actually no

try it :D

I'm a fan of cyberduck, or I just have a linux box at home I can rsync stuff from/to

99.99999% of the time nano is fine tho

I did not know of cyberduck and mountainduck. Thanks for the tip.

So like what I don't really understand is, why do people care what editor someone else uses? I mean, why does the editor war even exist?

@nobody feeling smug

"My workflow is better than yours"

or more precisely, my way is better than yours

@JourneymanGeek But of course it is. Isn't that already an established fact? :P

shrug

I have a toolbag

Its got random stuff ranging from a 2 dollar rubber hammer, to a handtool rescue wrench that's literally made by some guy with a CNC machine to the specs of a 1800 tool

Right tool for the job, and the workman :)

Which job though?

Well, I wouldn't use a basin wrench to screw on a light bulb

and in some environments you don't have a choice

Ah, you were referring to the whole range of tools. For some inexplicable reason I thought you were referring to the rescue wrench in particular :)

lol

Its an example of a pricy bespoke tool

as a counterpoint to my 2 dollar rubber hammer :D

So I vaguely know my way around Vi

since its often the only choice

gimme an option, it it might not be what I pick

(and I do have a basin wrench. Ended up not working, and I used something else...)

then dad managed to accidentally remove the bolty thing somehow, so I ended up using threadlocker...

so yes

whoooole bag of tools

@MechMK1 What are you talking about? *nix programs usually use vim, not an IDE.

You should read up on just how extensible vim is when you actually configure it properly (the default is just a text editor, but it can become an IDE with just a small config file change).

lol

One thing that I've noticed is that the only people who argue for IDEs are people who don't even know how to exit from vim.

@forest I think its the "YOU MUST USE THIS OR YOU SUCK" that's the issue

@JourneymanGeek IDEs have their place, but vim users really only fight with emacs users.

lol

@forest basically I'm saying, use whatever tool works best for you :D

Sure, but it's a good idea to learn how to really use a tool before making a decision.

I mean ffs, vim supports ctags.

Anyone who thinks vim is just for editing simple config files has never really used vim.

@forest But then if someone thinks vim is colossal waste of time and effort, why would they learn it?

@nobody Exactly. If someone thinks they have to jump through hoops just to edit files, they'll go with something that edits files and does syntax highlighting and other IDE-type features, without realizing that vim can do those too.

@forest that's hilarious... and frightening...

what I love from vim is the "prefix commands" (I don't know the real name): press 20, press up, you go up 20 lines.

this was back in '99, no internet, I spoke no English at all, and was one more on the category "Cannot even exit vim"... I ended up pressing reset

@ThoriumBR You can also use hjkl, so you could type 20j to go down by 20 lines. 5dj to cut 5 lines down, 9k to go up by 9 lines, and p to insert the cut lines. So it's just 20j5dj9kp to do all that.

I know those, but I can't remember when I am typing...

It takes some time to get used to, but it's worth it imo.

And I only use 5% of vim's true power. I really should spend some time getting used to more.

It's like sed and awk. They can do so much more, but I neglect learning.

99% of people only use awk for awk '{print $1}', and sed for only sed s/foo/bar/g.

the time I would take to learn is larger than the time savings, so the basics are enough

if you awk '{print $1}' file.txt instead of cat file.txt | awk, you are a power user

some colleagues still cat | grep | awk

@ThoriumBR Maybe for some people, but there are lots of times where they are really powerful.

I once saw an entire book (400+ pages) on awk.... most of it was to cryptic I had no idea what I was reading...

Awk is an entire programming language, after all.

Learning some very strong awk one-liners != learning the whole awk language.

I've written non-trivial programs entirely in awk, and it really is quite different from the kind of things you'd use it in the shell for. Of course, as a language it's optimized for text processing, sort of like Perl, but less general-purpose.