I'm doing some training stuff for work thats eating up my week, but I'll help work through that with you later on if you'd like
The wiki itself is a slightly different bit, its the repo with .wiki at the end and it is its own thing (one of the oddities of codeberg wiki I mentioned)
You can also comment here or send me a message, or write it in your fork and let me know, whichever works. I don't believe there is anything that I'd consider "uninteresting input" fwiw :)
Great idea! Putting it on the list, hopefully doing this update to the bar this weekend (I've got a few days of yet-another-cert training left still)
I firmly disagree. The issue has nothing to do with the endpoint. They have done very little with the play store relative to this massively impactful change to installation practices in creating a walled garden - precisely the reason many, myself included, chose not to go with iOS in the first place.
So the very idea that this is an endpoint security issue rather than an app store issue is, to me, laughable at best.
Except you have it backwards. The play store is the primary vector. The play store is also pre-installed on Android devices, and even without the whole verification nonsense, you still need to allow a different app repository to install.
Not cleaning their own play store up first means it has nothing to do with what they are claiming. And lets be candid - they have absolutely not.
The analogy is bad specifically because its not reflecting the issues anywhere near accurately. This is closing a window on the second floor while the front door is wide open with a sign that says "Come on in!".
So with your career in ITSec, you're aware of the massive amount of malware found in the play store? That it has historically been the main distribution vector for malware?
You have to jump though extra hoops.
You are downplaying the hoops here by a lot. To install software on my own phone.
Stop calling installing software "side loading". Its nonsense.
Elevator manufacturers sell the displays with their elevators more often than not. The PC is not installed in the elevator, but in the machine room, and the video is being extended alongside the cabling used for the elevator itself.
Yeah, you can also just make a PR
I'll be able to get on there a little later today, doing a cert class today and tomorrow
Just go ahead and let me know what's in the too advanced territory, and I'll be happy to rework it
Edit: For the record, this is how we make it better and more accessible, which is the goal
Pfft I'd spin up a wiki before I'd do that!
Thats the biggest issue for me.
I would carry around something with the thickness of a textbook and a 7+" screen, but under 6" is a nonstarter for me. I'd end up with text so large I'd be reading one sentence at a time.
So I'm going to suggest something slightly different - put it on both github and codeberg, then note that its synced from your local repo as a mirror and link it in a readme.
Gives you a few things
As for the server itself I'd say forgejo personally.
@somegeek@programming.dev please add [AIP] to the title, and reference the example here for how to format the disclosure
Thanks!