4 ms·

Hey, the site only lists iFixit guides. Are some of those missing? > Further, it appears that only official LineageOS versions are taken into account That's c

by onli 6y ago

Hey, the site only lists iFixit guides. Are some of those missing? > Further, it appears that only official LineageOS versions are taken into account That's correct. There are of course many more roms available on xda, unofficial lineage roms and other projects, but for one I do not know a structured way to list them, and second I think that if one decides on a device it should be based on official support by a bigger project. If there are more of those bigger projects that should be listed (and that have a list of devices they support published somewhere) I'm happy to add them to the list. It does not have to be only MoKee and LineageOS.

literallycancer 6y ago
The official LineageOS builds are not somehow better. It only means the maintainer went through extra hoops to have their build listed there. When fixing things it doesn't matter where you find the guide so I'm saying that if there are other videos available they should be linked. Obviously using iFixit only is easier to implement, but maybe there can be a way for the users to upvote arbitrary links?
- onli 6y ago
  I would expect the build being official at least raises the chances of the maintainer being catched if he slips some nefarious code into the ROM? > but maybe there can be a way for the users to upvote arbitrary links? Maybe if the foundation would be a bit different :) But this is a completely static site. One ruby script per data source creates a central .yml file, another custom ruby script creates the HTML based on that data and some .erb files, netlify is then serving those HTML files (pulls them directly from a gitlab repo). And after the holidays my time will be too limited to change that, especially for a noncommercial project. But if there is serious interest to create a fork with more features and data I would open source this. Edit: As someone on Reddit was asking for a repo and this comment planted the idea to open source it anyway, here is the repo: https://gitlab.com/onli/sustaphones https://gitlab.com/onli/sustaphones

by onli 6y ago

literallycancer 6y ago

The official LineageOS builds are not somehow better. It only means the maintainer went through extra hoops to have their build listed there. When fixing things it doesn't matter where you find the guide so I'm saying that if there are other videos available they should be linked. Obviously using iFixit only is easier to implement, but maybe there can be a way for the users to upvote arbitrary links?

onli 6y ago
I would expect the build being official at least raises the chances of the maintainer being catched if he slips some nefarious code into the ROM? > but maybe there can be a way for the users to upvote arbitrary links? Maybe if the foundation would be a bit different :) But this is a completely static site. One ruby script per data source creates a central .yml file, another custom ruby script creates the HTML based on that data and some .erb files, netlify is then serving those HTML files (pulls them directly from a gitlab repo). And after the holidays my time will be too limited to change that, especially for a noncommercial project. But if there is serious interest to create a fork with more features and data I would open source this. Edit: As someone on Reddit was asking for a repo and this comment planted the idea to open source it anyway, here is the repo: https://gitlab.com/onli/sustaphones https://gitlab.com/onli/sustaphones