Post APydyshKq9a9YunSdc by matchboxbananasynergy@infosec.exchange
(DIR) More posts by matchboxbananasynergy@infosec.exchange
(DIR) Post #APyZm8pt82ry22T1ZA by adam@hax0rbana.social
2022-11-25T22:28:44Z
0 likes, 0 repeats
@GrapheneOS Can you say more about the requirements for an app to potentially be bundled?Here's what I expect:- Open source- Private (no telemetry, etc.)- Maintained- Simple design- SecureI expect you already considered the Simple apps (e.g., https://github.com/SimpleMobileTools/Simple-Calendar#), but if we can understand what requirement that doesn't meet, we can perhaps start an app that will fit the bill.
(DIR) Post #APycc7Mk2VgERHkJSi by asparagi@hax0rbana.social
2022-11-25T23:00:24Z
0 likes, 0 repeats
It looks like @grapheneos@infosec.exchange is the official #GrapheneOS account on fedi, but I see Twitter posts via the unofficial @GrapheneOS@aspiechattr.me bot that do not show up on infosec.exchange, and people trying to interact with the bot's posts.@grapheneos@infosec.exchange, when you have time, can you let us know what to expect from your infosec.exchange account? In particular, do we still need to follow the bot as well if we want to see everything the project says?
(DIR) Post #APydyshKq9a9YunSdc by matchboxbananasynergy@infosec.exchange
2022-11-25T23:15:44Z
0 likes, 0 repeats
@adam Hey there! The official project account is @grapheneos, so you'd need to tag that account for them to see it. The Simple Mobile Tools app are GPLv3 licensed, so they're incompatible with the licenses GrapheneOS can use.
(DIR) Post #APyfcio38WcaQAUyhs by grapheneos@infosec.exchange
2022-11-25T23:33:14Z
0 likes, 0 repeats
@adam @GrapheneOS@aspiechattr.meYou're responding to an unofficial account mirroring our content from Twitter against the wishes of GrapheneOS. We want this account to be turned over to us, but unfortunately whoever created it hasn't responded to our attempts to contact them. We'll have to contact the instance administrators next. Simple Mobile Tools apps do not meet our requirements. They're too barebones, missing compatibility with the standard Android intents and have anti-features include security theatre we don't want in GrapheneOS. The direction and approach taken by those apps isn't a fit for GrapheneOs.
(DIR) Post #APyfhNfBAoFEILZTVI by grapheneos@infosec.exchange
2022-11-25T23:35:01Z
0 likes, 0 repeats
@adam @GrapheneOS@aspiechattr.meYou're responding to an unofficial account mirroring our content from Twitter against the wishes of GrapheneOS. We want this account to be turned over to us, but unfortunately whoever created it hasn't responded to our attempts to contact them. We'll have to contact the instance administrators next. Simple Mobile Tools apps do not meet our requirements. They're too barebones, missing compatibility with the standard Android intents and have anti-features include security theatre we don't want in GrapheneOS. We aren't going to bundle a Calendar app that's not a replacement for AOSP Calendar as a frontend for the OS Calendar system. The direction and approach taken by those apps isn't a fit for GrapheneOS. They're heavily focused on legacy Android versions / devices too, which means they don't provide a great experience on modern Android. GPLv3 licensing is also not acceptable for GrapheneOS.
(DIR) Post #APyg6tH6mKzFZoTaca by adam@hax0rbana.social
2022-11-25T23:39:44Z
0 likes, 0 repeats
@grapheneos Thanks for the thorough explanation!