spacelord
- 0 Posts
- 12 Comments
spacelord@sh.itjust.worksto Android@lemmy.world•GrapheneOS is finally ready to break free from Pixels, and it may never look backEnglish452·19 hours agoDoesn’t seem “it’s finally ready” when they didn’t name the name.
spacelord@sh.itjust.worksto Selfhosted@lemmy.world•What are you all using for a 2FA token manager?English21·3 days agoAegis ♥️
spacelord@sh.itjust.worksto Selfhosted@lemmy.world•Linkwarden downloaded the whole flipping Internet ...English52·4 days agoLinkwarden stickin’ it to the man. 😁
spacelord@sh.itjust.worksto Selfhosted@lemmy.world•Getting old and would like a better way to track health the self hosted wayEnglish3·4 days agov0.0.7, i.e. who wants to be a bug catcher 😅
spacelord@sh.itjust.worksto Android@lemmy.world•Supreme Court deals Google a blow, forces major Play Store overhaulEnglish9·8 days agoMy thoughts exactly. That could be very comfy for us users, but many devs will be (and justifiably so) wary of verifying themselves.
spacelord@sh.itjust.worksto Android@lemmy.world•Supreme Court deals Google a blow, forces major Play Store overhaulEnglish1642·8 days agoSeems that google’s announced plans to restrict sideloading on Android are now in direct conflict with the Supreme Court’s order to open the Play Store to alternative app stores and reduce its control over app distribution.
How will this play out in the end… 🤔
spacelord@sh.itjust.worksto Privacy@lemmy.ml•Does anyone use SimpleX chat? Why or why not? Is it actually tangibly better for privacy than say, Signal, for example?0·10 days agoTangibly even less people use it than Signal.😅
spacelord@sh.itjust.worksto Android@lemdro.id•Google confirms Android dev verification will have free and paid tiers, no public list of devs - Ars TechnicaEnglish2·11 days agoNo, they aren’t.
My hope as well. 🤞🏼
spacelord@sh.itjust.worksto Android@lemdro.id•Google confirms Android dev verification will have free and paid tiers, no public list of devs - Ars TechnicaEnglish2·11 days agoThis potential cooperation only buys time and doesn’t solve the core dependency: if Google ever discontinues AOSP, both GrapheneOS and any OEM partners would face the same dead end.
Yep, definitely more in line with that reality. 😄