/cyber/ - Cyberpunk & Science Fiction

just lurk more.

you will absorb all necessary knowledge through cultural osmosis evenually.

>>40623

>encryption

Practical side of it (how to use PGP for example) sure. You probably don't want to go into the math of it.

>computers

That's pretty broad topic. If you mean basics principle of computing technology… well, it's interesting, but probably not that useful if you don't plan to make a career in computer science.

>networking

That might be pretty useful nowadays. Governments are planing to make new internet regulations laws, so it's pretty useful to know how to evade them.

>programming

Well, it's always advantageous to know how to program. But, you see, it pays off only if you're good at it. If you know only basics of some programming languages.. it really won't make that much of a difference in your life. The question is: how far can you take it.

>steps to enhance anonymity

That is useful no doubt. For the same reasons i've mentioned above in a paragraph about networking.

Sorry for being a little sceptical, but if you expect to become Neo as your image suggests, you could be easily disappointed.

This'll get you started.

http://programming-motherfucker.com/

http://www.freeinfosociety.com/

https://cdn.preterhuman.net/

http://jon-jacky.github.io/home/links.html

https://sin.thecthulhu.com/library/

https://www.khanacademy.org/

>>40631

I recommend to use tutorial channels on youtube like these

https://www.youtube.com/user/thenewboston

https://www.youtube.com/user/derekbanas

It's easy way how to start program imho

Also as my first programming language i would choose JavaScript.

disregard >>40635, install NoScript

>>40641

>implying that JavaScript can be used only as frontend web tool

How new can you be.

You don't know much about the subject, do you?

>>40641

You know, JavaScript isn't just browser scripting language for a long time now.

You can also use it for backend (node.js) web development, developing desktop applications or even in game engines.

Your NoScript is only a tool for blocking frontend JavaScript executed in your browser. It doesn't affect backend server script in any way.

You can write some web app completely in node.js (which is JavaScript) and it will work fine even with your NoScript tool.

So before you say some bullshit, learn some stuff about the subject kid.

OP: https://www.torproject.org/docs/documentation.html.en

>>40645

yada yada.

>>40644

>>40645

Problem with JS is that it's not a very good language.

We kinda stuck with it because web is the frontier right now,

but it might be not a very good choice as a first language.

and running it in the backend is absolute maddness

>>40650

>Problem with JS is that it's not a very good language.

You can say that about almost any modern language.

It's still much better than those oversimplified languages like Python or Ruby which are made so even gurls would understand them, so they have very non-standard syntax.

>We kinda stuck with it because web is the frontier right now,

JavaScript is the most used programming language of all now. And not only on the web. That's why it's a good language to start imho.

>but it might be not a very good choice as a first language.

Why not?

>and running it in the backend is absolute maddness

Nonsense. Node.js websites run faster than PHP websites.

OP here

>>40625

That's on my list

>>40626

>You probably don't want to go into the math of it

You sure its not necessary?

>That's pretty broad topic

I'm specifically looking for info on the inner workings and parts of a computer,if that makes sense

>Governments are planning to make new regulations laws, so it's pretty useful to know how to evade them.

That's the main reason why I want to know how

>The question is: how far can you take it.

Excellent question. But I'd might as well try first, right?

>This is useful no doubt. For the same reasons i've mentioned above in a paragraph about networking

That's what I'll focus on first

>Sorry for being a little sceptical,

skeptical of what exactly?

>but if you expect to become Neo as your image suggests, you could be easily disappointed

Pic wasn't that related to what I was asking.

>>40631

>>40635

I'll look through these. Thanks.

>>40641

>disregard >>40635

Do you mean I should not bother learning Javascript, or do you not recommend the tutorials?

>install Noscript

Will install. Thanks.

>>40645

>>40650

>>40656

I don't have to learn Javascript first. What are the pros and cons of it as a first language?

>>40646

Thanks for the link.

>>40663

pros of JS:

It's omnipresent in modern web.

Big community, lots of resources and tools and books and help around.

Boilerplate of I/O is taken care of by the browser, so GUI is easy,

cons of JS:

If you are going to write for the web, you'll have to learn about the web. html, css, http, etc. Entry barrier is higher.

There are a lot of weird behaviors that hard to debug without external tools.

And I just don't like dynamic, interpreted languages, because they are far too removed from hardware by layers upon layers of abstractions, and I think it's important to learn early how machine works wirh hands on expiriencs.

Srsly, they should teach assembly at schools.

>>40667

this is awesome.

I seriously should try writing an OS too. With QEMU it shouldn't be that hard.

>>40664

edgy

>>40623

If you want to do shit with computers, no matter the speciality, and be decent at it, you simply have to learn to program. You don't have to be a supreme software architect who develops the full stack, that would be the best thing, but also very much impossible. Learning a programming language is the best way to learn how computers work, but don't be a cargo cult programmer, actually learn your shit.

Some niggers will be telling you not to 'reinvent the wheel', but they're ignorant niggers. It's okay to use the wheel, but understand the wheel.

Pick a language and just start fucking around, see what you can get your computer to do. Then get comfortable with the language, write shit to automate stuff for you. Doing this you will find out if you'll be a real programmer, or someone who is proficient enough to write some code to do shit for him. I assure you this will give you a lot of insight in things like security, encryption and computers in general.

Oh, and be prepared to get angry at your computer. Especially when setting up your developing environment.

>>40623

Learn Assembly language. It's not super useful for your career but will teach you more about programming and computers than most developers know coming out of school today.

If you just want to screw around making websites, I would agree with others that Javascript is a good first step.

>>40712

why start at such a low level language? I would start at C.

>>40713

I agree, assembly is a useful skill to have, but I think C is a much better better place to start at.

And if you're all about the 'low-level', why not straight up machine code, or better yet, control those electrons with your mind?

>>40713

>why start at such a low level language? I would start at C.

Assembly language is as close as you can get to understanding how exactly a computer is working behind the code you'll write in higher level languages. It's not a practical choice, but as a learning tool I found it invaluable.

OP's stated goal is to learn more about computers and programming. Assembler can teach you a whole lot about computer architecture that you won't learn from C.

>>40715

I guess academ-teir would be to crank up a pen and paper and simulate Turing machine in your brain, but there's no actual point in doing that, when we have actual physical Turing machines on our table.

>>40724

Fair point, but it might be out of reach for some, especially when one is just starting out.

I personally began to see the light once I started using Linux. With Windows hiding everything behind dialogs and obscure registry references diving into Linux was like diving into the rabbit hole, and as time passes I just go deeper and deeper. Assembly is one of those things I still need to check out when I have the time to do so.

>>40715

Why would you go from 0 to a billion. It is much better to first learn something easy then work your way down to assembly then to brainfuck yourself into thinking programming is really hard and is not worth perusing.

>>40690

This is a fairly common answer when someone says they want to be more /tech/ and being able to program will make you more /tech/. However, knowing how to program and knowing how to operate a computer are two different things. They overlap, but they aren't the exact same thing.

I've known programmers who couldn't navigate and fully use a computer, and I've known computerists who couldn't program for nothing.

So my advice to OP is to learn a bit of programming, but don't neglect computing either.

Learn programming, but also learn networking, shell commands, shortcuts, hardware, software, data transfer, protocols, etc.

Be prepared to be bored, too. It won't always be exciting, but it will be worthwhile in the end.