Jankatarch@lemmy.world to Lemmy Shitpost@lemmy.world · 15 days agoTeserract may be opensource, but adding myself would feel disingenuouslemmy.worldimagemessage-square97linkfedilinkarrow-up11arrow-down10
arrow-up11arrow-down1imageTeserract may be opensource, but adding myself would feel disingenuouslemmy.worldJankatarch@lemmy.world to Lemmy Shitpost@lemmy.world · 15 days agomessage-square97linkfedilink
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up0·14 days agohint: it’s not open source. (the list is behind a wget call, and not editable; the proj lead is a butthurt douche who wouldn’t merge a pr anyway…)
minus-squareMr. Satan@lemmy.ziplinkfedilinkarrow-up0·14 days agoIsn’t it in a gziped file within the repo tho? policy.dat?
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up0·14 days agoi thought the code pulled from a hardcoded url and used that? maybe the url is a raw hit in the repo, “same same” but … i don’t reckon he was too open to merges regardless.
minus-squareMr. Satan@lemmy.ziplinkfedilinkarrow-up0·14 days agoWell there’s no real benefit to compressing and encoding the file in the repo, it’s a JSON config. Other than obfuscation, of course.
hint: it’s not open source.
(the list is behind a wget call, and not editable; the proj lead is a butthurt douche who wouldn’t merge a pr anyway…)
Isn’t it in a gziped file within the repo tho?
policy.dat?i thought the code pulled from a hardcoded url and used that? maybe the url is a raw hit in the repo, “same same” but … i don’t reckon he was too open to merges regardless.
Well there’s no real benefit to compressing and encoding the file in the repo, it’s a JSON config. Other than obfuscation, of course.