/tech/ - Technology★

gnu nano

>best

patch

gnat

emacs

gforth

gdb

>should be by name, but aren't

alive (multiple hosts in "round-robin" fashion? nothing but ping? worthless. This should be a mini zabbix, not a bash script.)

womb (nothing to do with replacing women)

grep

>>1031199 womb

Dissipate your semen into your mom's womb! Rape her!

FreeDink

>>1031199

>gnat

I was racking my brain as to what this was for way too long, and then it hit me. I use the command like muscle memory as well.

t. Ada programmer

>>1031196 (OP)

midnight commander

>>1031287

You have memory loss gramps.

>>1031196 (OP)

http://ix.io/

brave browser

>>1031203

upvoted. If you dont use grep atleast once a week you don't know how to into linux.

>>1031292

https://www.gnu.org/software/moe/manual/moe_manual.html#Introduction

>Moe uses ISO-8859-15 instead of UTF-8 because an 8-bit character set (combined with romanization if needed) can convey meaning safely and more efficiently than UTF-8 can.

>UTF-8 is a great tool for tasks like writing books of mathematics or mixing Greek with Chinese in the same document. But for many other everyday computing and communication tasks, an 8-bit code like ISO-8859-15 is much more practical, efficient and reliable. There is no such thing as an 'invalid' or 'out of range' ISO-8859-15 character.

>UTF-8 is fine for non-parsable, non-searchable documents that must look 'pretty', but not so fine for things like filenames, configuration files or C++ source code. Invalid UTF-8 characters in filenames make archiving and filesystem operations unreliable. UTF-8 greatly hinders parsability (and may even become a security risk) by providing multiple similar-looking variations of basic alphabetic, punctuation, and quoting characters. UTF-8 also makes search difficult and unreliable. For example, searching for a word like "file" in an UTF-8 document may fail if the document uses the compound character 'fi' instead of the string "fi".

>UTF-8 allows user tracking by means of invisible text marking. Any string can be converted into its binary form and then recoded into a string of zero-width characters, which can then be invisibly inserted into the text. If the text is posted elsewhere, the zero-width character string can be extracted and the process reversed to figure out the identity of the person who copied it. Using moe and ISO-8859-15 such invisible marking is more difficult, more fragile, and easier to discover.

wtf is this shit?

>>1031341

#!/usr/bin/python
word_joiner = u"\u2060" #invisible chars
zero_width_space = u"\u200B"

def encode(id):
        binary_id = ''.join(format(ord(c), 'b') for c in id)
        binary_id = binary_id.replace("0", zero_width_space)
        binary_id = binary_id.replace("1", word_joiner)
        return binary_id
def decode(id):
        decoded_id = ""
        binary_id = id.replace(word_joiner, "1")
        binary_id = binary_id.replace(zero_width_space, "0")
        for x in range(0, len(binary_id), 7):
                char_bin = binary_id[x:x+7]
                decoded_id += chr(int(char_bin, 2))
        return decoded_id

id = "gorillamonkey" #eg. login name used when accessing top secret CIA doc
hidden_id = encode(id)
decoded_id = decode(hidden_id)
print("Original: %s, hidden: %s, decoded: %s\n" %(id, hidden_id, decoded_id))

cia_doc = "space aliens are real"
cia_doc_with_voodoo_id = cia_doc
cia_doc_with_voodoo_id += hidden_id
#now when u leak it, they know who did it.

I hope formatting isn't f'ed up again. Should have used moe to write this.

>>1031196 (OP)

Gnu True.

Gnome Disks

>>1031355

>muh zero width spaces

Install a plugin for your text editor that highlights those.

guix

>>1031196 (OP)

IceCat

>>1031355

>take picture of document

oops

>>1031341

UTF-8 is extreme bloat and cancer

>>1031341

It's more of Stallman's "I believe I know more than you so I will fuck shit up for you" mentality.

>>1031430

do you really need various shades of negro smiling face and thumbs up burned into your character set?

Either true/false or yes. Best as in does exactly what it's supposed to do.

>>1031431

Unicode is not UTF-8.

>>1031416

I proved my point that UTF-8 is botnet and privacy risk.

>deliver documents modified with combination of specific tag words, dates, fonts, formatting, images, spelling errors, added commas, meaningless filler phrases that can be added to any place without them standing out, synonym words from dictionary...

oops

If they cared they could make it impossible to leak docs without overhauling the whole document.

>>1031430

More like the authors were too lazy to implement support for UTF-8 and this was convenient cop out.

>>1031438

Unicode is not UTF-8.

>>1031439

You are probably right. Stallman always does this when he doesn't understand something; so he will call it evil, steal it anyways, and then tell everyone how his version is better because of the bloat he introduced.

>>1031416

Works for one page documents, if you're trying to leak a thousand pages good luck taking those pics with the camera you aren't allowed to have without anyone noticing.

>>1031442

>UTF-8 is a variable width character encoding capable of encoding all 1,112,064[1] valid code points in Unicode using one to four 8-bit bytes.[2] The encoding is defined by the Unicode Standard, and was originally designed by Ken Thompson and Rob Pike.[3][4] The name is derived from Unicode (or Universal Coded Character Set) Transformation Format -- 8-bit.

You are correct but it is semantics.

st

zathura

ranger

scim

groff

cp

>>1031416

>now image FULL of unneeded data needs to be sanitised (image metadata, lens scratches, do they make printer-dots equivalent? Who knows.)

gcc

>>1031427

>LARPer doesn't know the difference between UTF-8 and Unicode

>>1031430

>>1031442

Not every GNU program is made by Stallman you stupid faggots.

GNU Emacs is made by Stallman and guess what? Initial support for Unicode was added in version 21.1 (October 20, 2001).

>>1031196 (OP)

Clearly it's the GNU operating system.