doopen@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 9 days agoSince when does a clock need a privacy policy?lemmy.worldimagemessage-square52fedilinkarrow-up1426arrow-down111
arrow-up1415arrow-down1imageSince when does a clock need a privacy policy?lemmy.worlddoopen@lemmy.world to Mildly Infuriating@lemmy.worldEnglish · 9 days agomessage-square52fedilink
minus-squareadsche@lemmy.worldlinkfedilinkEnglisharrow-up8·edit-28 days agoA pull request for that issue is open since April with no comments from the developers. Not a good sign :/ https://github.com/FossifyOrg/Clock/pull/62 EDIT: Looking further into it, the only merges and commits seem to be translations and GitHub metadata stuff, there has been no development since the fork :( - https://github.com/FossifyOrg/Clock/commits/master/
minus-squareCethin@lemmy.ziplinkfedilinkEnglisharrow-up1arrow-down1·8 days agoWhile inconvenient, you could build it yourself if it’s a feature you really care about and don’t want to wait and hope it gets merged.
A pull request for that issue is open since April with no comments from the developers. Not a good sign :/
https://github.com/FossifyOrg/Clock/pull/62
EDIT: Looking further into it, the only merges and commits seem to be translations and GitHub metadata stuff, there has been no development since the fork :( - https://github.com/FossifyOrg/Clock/commits/master/
While inconvenient, you could build it yourself if it’s a feature you really care about and don’t want to wait and hope it gets merged.
Ping it then