New #pentest and #bugbounty tool written in golang: Goctopus 🐙 - a fast, open source GraphQL endpoint discovery & fingerprinting tool 📡
Congrats @NoheHf for this very nice project!
https://t.co/UwCPy8FWhv
@XorDev What would you recommend to get started ?
Little book of shaders ? Recreating things ? Shadertoy ?
I have a good programming and math background
@MichaelArnaldi Are you mainly referring to the first pass being slow ? Because on the 2nd+ run you can use cached 1st iteration and only re compute branches that have changed no ?
@mewtyunjay@ludwigABAP@kristofgazso I don’t really get why raycast does not implement the search too
Also big issue for me is not being able to configure it via a file
@AdamAugustinsky@HSVSphere Twitter gotta be Twitter
Zig and rust and go are great, they’re just not meant for the same use case at all
Constantly opposing languages / frameworks is useless, just get shit done and swap it if it doesn’t fit your needs
@HSVSphere What’s wrong about channels tho, used them a lot, even in complex situations (channels in channels, high frequency / data volume, with all sorts of atomic / mutex / semaphores), and never had issues
🇩🇪 Meet the Escape team in Berlin!
Come to meet our team - @iCarossio & @nohehf , at BSides Berlin this Saturday and learn how to secure your GraphQL APIs.
Check out the conference schedule 👉 https://t.co/q0te89Sxkn
Not all records you’re happy about breaking: @Cloudflare recently mitigated the largest ever reported hyper-volumetric #DDoS attack. 3.8 terabits per second (Tbps) and 2.14 billion packets per second (Bpps). Handled automatically any without any customer impact. Details to come.
Yo, I recently worked on cloudfinder, a little cli / golang package to detect which cloud provider an IP / host / url / domain belongs to.
It's static, offline and very fast + bonus, it allows to track those cloud providers IPs over time.
Check it out :) https://t.co/TrBBUOBnsx
This is the biggest mindset issue that many, many devs suffer from imo.
"Why would you roll your own lib? Just [popular lib instead]"
"Why are you building your own game engine? Use Unity/Godot"
"Rolling your own JS frameowrk? Just use React bro."
"Why would you write your own compiler? That's useless"
The majority of people who think like this have completely different objectives than the people who'd roll their own OpenGL implementation. One is not better than the other, mind you, but I have been hearing people telling me to not reinvent the wheel since I'm ~11, so I'll wanna share my thoughts.
If the objective is "get to the end result as fast as possible" and the success criteria are "how much money will you make" vs "how long did it take you / how efficient were you on the way", then yeah -- don't roll your own implementations. Build your app in React. Build that game in Godot or Unity.
But if your objective is to learn and develop your skills, why stand on the shoulders of giants forever and never develop an intuition as to what happens underneath? Harness your unbridled energy by deep diving into something. Write your own game engine. Write an interpreter. Write a compiler backend.
There is simply no better way (or harder) to truly develop your skills and understand. Not only that, but knowledge transfers. Low level programming will make you a substantially better programmer. Your entire way of seeing things will permanently change. You will develop real taste on how things work, and over time, you will realize you can apply that taste to problems you never thought you could tackle.
A lot of people advise new programmers to learn whatever framework is the most employable. I would say, if you are a young person trying to enter the job market ASAP, it is efficient on the short term. But I can ensure you that you will make more money, be 10x more confident and go much further in your career if you swap your mindset from "just re-use [popular tool or framework" to "fuck it, I am rolling my own. I wanna really understand this."