Senselessly Tooted Disinformation

This host is mostly for my random stuff, and in little part acts like a well-intentioned placeholder for the typosquatted domain.

Discoverability and Archiving

Currently I'm using this host for saving the items from my own feeds to the Wayback Machine and provide in-links for search engines. I hate that I have to do this, but the non-sense ideology of Mastodon pretty much ruined the search feature for Fediverse as a whole, and this wasn't changed by the fact that they owned their mistake and implemented search eventually.

Yes, I (or anyone else) could do similar things with other peoples published feeds, regardless of the tantrum. No, you can't defederate this, because the process doesn't rely on an instance.

Gluttony Section for Search Engines

[RSS] Windows Heap Exploitation - From Heap Overflow to Arbitrary R/W

https://mrt4ntr4.github.io/Windows-Heap-Exploitation-dadadb/

User-mode tutorial

this post | permalink

Hook system calls on Windows by using Kaspersky's hypervisor

https://github.com/iPower/KasperskyHook

Epic project! :)

this post | permalink

The Internet needs a search filter that selects only images that were drawn with mspaint

this post | permalink

After I figured out this whole Gradle thing (just kidding, I only have a vibe-coded config that works by some miracle) I had dinner and decided it makes more sense to just do the whole thing in Python :P

#Saturday

this post | permalink

@Aron Good point! What I would expect is some form of namespacing that would force you to be explicit about where your identifiers are defined. E.g. in Python you would either write `Bar.Foo` or at least do a `from Foo import *` somewhere. This would be especially important, because Gradle examples consistently fail to give proper context (e.g. what plugins are in use).

I they would take the extra mile, they could build in some knowledge about the most common errors (like gcc).

this post | permalink

There are many things I hate in Gradle, but among the most offending ones is the fact that it has no notation of where things are declared.

Like `Foo` doesn't work, because you forgot adding the `Bar` plugin, but there is no indication `Foo` being defined by `Bar`, and obviously the error message won't give you any clues either.

gcc (which isn't exactly the champion of helpful error messages) at least tries to give you hints that you'd need `stdio` for `printf()`.

#programming #java #gradle