_____

joined 6 months ago
[–] _____@lemm.ee 1 points 19 minutes ago

I specifically said this advice because dual booting windows with Linux is a terrible idea.

Although you are right, if you USB read/write is slow it will be a sluggish experience.

[–] _____@lemm.ee 1 points 4 hours ago

I use like less than a tbsp of coffee creamer for coffee.

The flavour is so artificial that any more will make me feel sick. It just tastes like soap.

Many coffee creamers also taste terrible, I'm very surprised at the popularity of them overall.

I get a specific kind that I can bear and I put a very small amount and it works for me. I don't like milk. Black coffee is okay but I do like it with creamer more.

[–] _____@lemm.ee 1 points 7 hours ago (2 children)

You should just test run it from a bootable usb.

Install steam. Mount your NTFS drive which contains your windows games. If you have sims on steam use steam. If not take a look at lutris before doing any of the above.

Your experiment ends when you've tested all games you want to play.

Now: You cannot use NTFS (windows) drive for games, although you did it in the experiment long extended usage is discouraged.

So you will need to find a way to transfer your games to a different formatted drive. (ext4, btrfs for example)

If you don't need that advice you will eventually run into frustrating issues.

[–] _____@lemm.ee 8 points 8 hours ago

"grug try watch patiently as cut points emerge from code and slowly refactor, with code base taking shape over time along with experience. no hard/ fast rule for this: grug know cut point when grug see cut point, just take time to build skill in seeing, patience

sometimes grug go too early and get abstractions wrong, so grug bias towards waiting

big brain developers often not like this at all and invent many abstractions start of project

grug tempted to reach for club and yell “big brain no maintain code! big brain move on next architecture committee leave code for grug deal with!”

https://grugbrain.dev/

[–] _____@lemm.ee 3 points 8 hours ago

Honestly, if they want to go full enterprise at least use the javabeanfactoryfactoryfactory pattern

[–] _____@lemm.ee 5 points 9 hours ago (4 children)

I have nothing to add except: man's really wrote like 7 classes to just have 1 function each

[–] _____@lemm.ee 2 points 20 hours ago
[–] _____@lemm.ee 1 points 1 day ago

I love stupid exploits like the patapon demo exploit where you use a specific save file as the payload entry point. That's what I like the most about exploits. Or how for Nintendo consoles all the Smash games can be used to install cfw.

[–] _____@lemm.ee 7 points 1 week ago* (last edited 1 week ago) (4 children)

Ah the nostalgic days of obsessing over wololo to see if my firmware was finally going to be supported.

IIRC for the PSP there came a day where you could run code straight from the external storage card without needing anything else. Which led to bootable game ISOs from the vanilla UI.

I could be remembering things wrong as it has been over a decade.

[–] _____@lemm.ee 19 points 1 week ago

SQL injection is like this: you have something you can interact with on the browser like a form containing different values.

You hit a button and that value is sent and merged into a SQL query.

Say the value is an user ID and you're deleting an account, perhaps your own.

If the coder is incompetent the API will run this query: "DELETE FROM USERES WHERE ID = "

Which means that if you open the developer console, change the value field for that html ID you can break that SQL line and write more SQL, or you can delete other users based on their ID.

Essentially editing a frontend input allows that input to be ran directly by the SQL engine. It's like having full access.

So through that ID field you can inject more SQL code. There's multiple ways to do this, sometimes the URL itself on a website uses these query parameters like "&search=something” and the "something" is injected into the SQL string.

SQL injection is baby's first exploit, this method is like granting everyone DB access.

view more: next ›