social.noyu.me

@hikari integrated source viewer that just gives you nested UIKit list views and when you select a file, you get a full-screen view of the source code with no syntax highlighting

@hikari To what end? It’s not verifiable or anything.

@jrose i'm assuming laziness or ignorance rather than malice

@hikari But what is an end user going to do with that source code?

@jrose the average user? nothing, but what were they gonna do with the rest of the dead bytes in the executable

@hikari I really don’t know what your goal is. Is it that someone who makes a fork will be “open-sourcing” their changes by default if they put the build up anywhere?

@jrose yes

@hikari honestly, it seems like kind of a cool way to make a statement. we kind of want this to exist just on general principles.

it does seem unlikely to result in practical change, but who knows :) we don't feel able to predict what would happen without trying it, which seems like a good reason to try it

@hikari at the very least it would let you distinguish the forks that don't spend any time worrying about the stuff they're supposed to do with the code, from the forks that take the time to look closely and turn the feature off

@hikari make sure it doesn't accidentally include credentials or anything

@hikari next time my boss asks me to enable reproducible builds I'm doing this

@hikari Will that then feature a parameter like --extract-source or will a script be needed to extract the source code from the executable?