I thought it was a website that should exist during the pandemic, so I built it. It’s been slowly growing ever since, because most of the time you really only need to add the info once.
Ask HN: What are you building that's not AI related?
161–170 of 265 posts
Re: Ask HN: What are you building that's not AI related?
#162Named after my ‘96 Subaru Sambar kei truck, small and mighty. The other thing I’m constantly tinkering with :)
Re: Ask HN: What are you building that's not AI related?
#163Re: Ask HN: What are you building that's not AI related?
#164Re: Ask HN: What are you building that's not AI related?
#165We have created a permission system within our social worlds... time to apply the same standards to the digital realm.
Re: Ask HN: What are you building that's not AI related?
#166Re: Ask HN: What are you building that's not AI related?
#167I'm working on ghidra-delinker-extension [1], which is a relocatable object file exporter for Ghidra. The algorithms needed to slice up a Ghidra database into relocatable sections, and especially to recover relocations through analysis are really tricky to get right. My MIPS analyzer in particular is an eldritch horror due to several factors combining into a huge mess (branch delay slots, split HI16/LO16 relocations,…
Re: Ask HN: What are you building that's not AI related?
#168This seems a little bit of a duplicate of [1], but I can repeat my answer here as any views help! My wife and I continue to work on Uruky, a EU-based Kagi alternative [2]. Since last month we finally got our production API Key for EUSP/STAAN (it was certainly the slowest and most complicated search provider to adopt, so far), and that brought us to 5 search providers you can choose from and sort as you prefer. We alr…
Re: Ask HN: What are you building that's not AI related?
#169Re: Ask HN: What are you building that's not AI related?
#170I'm working on ghidra-delinker-extension [1], which is a relocatable object file exporter for Ghidra. The algorithms needed to slice up a Ghidra database into relocatable sections, and especially to recover relocations through analysis are really tricky to get right. My MIPS analyzer in particular is an eldritch horror due to several factors combining into a huge mess (branch delay slots, split HI16/LO16 relocations,…
Mad respect. I tried extracting a clean .o file out of a statically linked ELF once, and it's an absolute nightmare. How are you handling switch tables and indirect jumps? Without dynamic analysis, it's sometimes physically impossible to figure out what a register is actually pointing to
It does require a reasonably accurate Ghidra database to work properly, but I've had users delink megabytes of code and data from a program successfully (as in, relinking it at a different address results in a functionally identical executable) once they've cleaned it up. The accuracy warning in the readme is mostly because it's really complicated to describe exactly what inaccuracies you can get away with, there's a fair amount of wiggle room in reality as long as you know what you're doing.