Jankatarch@lemmy.world to Lemmy Shitpost@lemmy.world · 2 days agoTeserract may be opensource, but adding myself would feel disingenuouslemmy.worldimagemessage-square98fedilinkarrow-up1559arrow-down19
arrow-up1550arrow-down1imageTeserract may be opensource, but adding myself would feel disingenuouslemmy.worldJankatarch@lemmy.world to Lemmy Shitpost@lemmy.world · 2 days agomessage-square98fedilink
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up11·edit-22 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-up2·1 day agoIsn’t it in a gziped file within the repo tho? policy.dat?
minus-squareflandish@lemmy.worldlinkfedilinkarrow-up1·1 day 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-up3·19 hours 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.