λ - programming

Kleisli arrows of good fortune, really good functional pearl

Does anyone have anything on machine learning and image recognition?

>>10509
It's a book, but it fits.

https://github.com/papers-we-love/papers-we-love

Lots of good stuff here.

>>10498
>giving people the envy to read it

What?

>>11068
I figured that would be the case.

Should I use motif, gtk, or qt?

>>11069
If you just want a window you can render OpenGL to + user input glfw is pretty easy to use.

A lot of tutorials pick a library to use as a shim for cross-platform development. If you're following a tutorial just use whatever they are.

I'm getting started on glsl, need some knowledge for a js/webgl soykaf I'm doing. The same shaders will be portable to other platforms such as a c-opengl game? Recommended learning resources?

Also, I've always been fascinated about the demoscene. What are the skills required or learning path towards being a demoscener?

>>11075
>The same shaders will be portable to other platforms such as a c-opengl game?
GLES (what webgl uses) is mostly a subset of big GL so porting from GLES to big GL is fairly easy. The primary issue is versions because GLES versions don't correspond well to GL versions, even though pretty much every feature in GLES is present in some version of big GL. Porting from GLES to big GL is much easier than the other way.
>What are the skills required or learning path towards being a demoscener?
You have to be good at a lot of things, or else know people who are, or else have the patience to do things you're not good at. I've tried making demos a few times and I've made some cool effects but when it comes time to add music or choreograph it I lose interest. Also when you watch demos they often seem repetitive, but once you try to make one you'll see that there are usually a ton of different effects crammed into a short time so it takes a lot of work. You might spend days working on an effect that will only be visible for 2 seconds.

>>7117
I really like SDL 1.2 since it's super simple.
They made SDL 2 look more like OpenGL which should make some things easier in the long run but it made it harder to just make something quick.

The only way in to http://skullcode.com is a bit of reverse engineering.

It's certainly not worth figuring out the weird architecture just to deal with what that community thinks is "all in good fun" (hacking each other's VM code to bits), unless you seriously enjoy reverse engineering...

>>9467
How do you get started with skullcode?

I expected some kind of explanation, but are you really just dropped into the memory editor of a system that is accepting your exploration as input the entire time, with no help whatsoever?

>>9468
Well, sort of.

The beginner will find a hook to execute whatever code they like. Zero the byte at address 6666h. The jump address is already filled, and demonstrates that the machine is little endian. The next hint is usually another address. After demonstrating a few incremental reverse engineering feats the self modifying code may do just that...

The intermediary reverse engineer will probably think outside of the presented box. After jumping through a series of hoops in a different direction they'll discover a sort of "map" to potentially secure a mid level login.

Some skilled hackers think the skullcode landing page is too full of holes begging to be filled with exploits, but I disagree. Determined hackers can apparently get root if they're interested enough, but they attract attention from other pranksters so only the dedicated say root for long.

The lack of documentation is probably because the entry site has moved a few times in the past and the landing page architecture changes periodically making documented entry methods less than helpful. In fact, the underlying code changed last week, but the bytecode didn't. Internally, one's programs can specify which VM to use so as not to require recompilation.

Personally, I like skullcode for its persistent "stickyness". It's not an ephemeral completion like nearly every vuln group. The exploits developed therein don't have security ramifications for the real world so there's no ethical pressure to publish exploits, and there's no ready made library of exploits to deploy (see: Metasploit, which allows point and click skiddie tier cracking, and makes lots of CTFs unfun). There's a certain 16-bit era charm to skullcode, nowadays the security landscape is much different. The down side is there's not much help to be found on the external web. There's been talk of changing that, but this may fracture (or destroy) the community.

If you're looking for something welcoming, more mainstream, less challenging, and for popular chipsets with tons of documentation, that niche has already been filled to the brim by any of the existing security CTF (Capture The Flag) competitions.
https://www.vulnhub.com/
Post too long. Click here to view the full text.

>>9455
>Also, to any mods reading. I don't know what the proper board for this would be (I think /cyb/ works). So feel free to move this if you want.
It's at the end of the /cyb/ board now, so I'm going to move this to /λ/ like I should have by now.

There was a flaw in the thread-moving system and the images didn't survive.

I'm currently drudging through this:
http://beginners.re/

I haven't seen much I don't already know, but I'm keeping up with it. I think it will get better.

It's a shame x86 is the most popular instruction set for these things. MIPS is so much nicer.

>>9361
> stripping tabs from <code>
This engine never fails to amaze me with each step I get to know it.

>>9362
I'm pretty sure tabs are just a different width here.

This is why you should always use spaces. fuarrrk tabs.

>>9398
fuck spaces

while true; do espeak "rofl"; done

Here's something I never bother saving I use for when I add new books or whatnot to my organized book directory:

(map 'string (lambda (c) (case c (#\  #\-) (t (char-downcase c)))) "")

Example:

CL-USER> (map 'string (lambda (c) (case c (#\  #\-) (t (char-downcase c)))) "The GNU C Reference Manual")
"the-gnu-c-reference-manual"
CL-USER> 

>>10462
https://www.sevendays.co/

Really neat concept. I don't know how well it works from personal experience, but I've heard good things from others.

>>11000
we shouldn't need to agree cause it's obvious.

>>11014

Well that was more or less a rhetorical question but I had some hope about anons starting right off the bat and being successful at it.

>>11000
I mean, it depends really.

Giving John's Gun Shop a new static site that doesn't look like a GEO cities site is just fine.

But yeah, working on soykaf that isn't a static site is a good way to never want to do it again.

>>11000
Depends on the area you want to start in.

Webdev is actually possible.
On the other hand everyone does so you have quite the competition.

https://oeis.org/wiki/Disjunctive_numbers
>It is not known whether π = 3.1415926535897932384626433832795... is a disjunctive number.[3]
So we don't even know if it works. Useless.

Won't work.
This, and ideas like it, pop up all the time.

https://en.wikipedia.org/wiki/Kolmogorov_complexity

>>10831
the problem is that, assuming the digits are random, on average it takes a number of length n to point to a message of length n. And, since pi is iterative, you'd be incurring gigantic computational cost as well.

Proof:

let your message be m1, m2, m3, ... mn

the probability that a series of random digits matches your message is 1/10 * 1/10 * 1/10 * ... = 1/10^n

therefore if we take a sample of all messages of length n in the random sequence, on average you would have to sample 10^n sequences to get a matching sequence. (10^n * 1/10^n = 1)

It just so happens that it takes n digits to represent 10^n in a base-10 system. This could not be compressed to base-exponent notation because in most cases the number would not be 10^n.

Therefore, on average there would be no compression performed.

>>10953
It works, it is just unbelivealy slow, as I think your link was supposed to show. But the proposition is just for fun.

>>10847
The problem is, the indices would be massive - larger than the data itself, in most cases.

>>10955
>Your software doesn't have that feature.
Sounds like a bug.

>>10955
We want a board to be locked to people who aren't mods/admin.

>>10964
>Sounds like a bug.
Yes, in some sense.

>>10966
Sorry, I misunderstood. You want the entire board locked? I'll look at it.

>>10966
Why do you need to be able to post on a locked board?

>>10983
So they can scheme without the plebs knowing.

Yeah that's fine.

>>10932
You should really try searching for the solutions to your problems before making a thread.
You should also look in the catalog first for threads that may already cover your topic. This would have been more appropriate in the Beginner's General:
https://lainchan.org/%CE%BB/res/5683.html

Now that the thread's here, I suppose it should just be a general C thread.

>>10935

I tried searching for the solution, but found nothing on the interwebs.

>>10938
Yes, but you already had an example you could have tested yourself.

C has a standard, which is really a requirement for any serious language, and if you haven't read it yet I suggest you do. It will really help you as you go on.

>>10932
The i variable is being used for two numbers, iterations and successes. You're better off using a while loop and a meaningful variable name as a counter. break statement to exit the loop.

>>10693
http://gameprogrammingpatterns.com/ is pretty cool. I liked it so much I ended up buying a hard-copy of the book to support the author.

Start with this:
http://geometrian.com/programming/tutorials/write-games-not-engines/

>>10888
Reusing a variable name doesn't change the value of the old one. If you passed the original variable to a function the value will always be the same. It's more like redeclaring than overwriting.

> writing a gopher server
I like you :3
That's exactly what I planed to do next.

>>10888
I haven't yet, but if I really like Elixir I'll give it a shot.

IMO it is more important to understand the Erlang architecture, OTP, and its concurrency model than the language syntax itself.

A good book like Elixir in Action, which I posted earlier in this thread, does that.

That said, I've heard good things about "Learn You an Erlang".

>>10891
Correction, I did not post it earlier. Here it is.

>>10889
>Reusing a variable name doesn't change the value of the old one. If you passed the original variable to a function the value will always be the same. It's more like redeclaring than overwriting.

Yeah, that makes quite a bit more sense.

>>10892
Thanks, lainon!