We were at the playground and one of the other parents asked me about my bike because my wife told her how much I liked bikes.

He said he’d need to ask me some questions because of a problem, I told him it was easy and described it and said I could bring my tools by (the playground is like two blocks from me, his house is like 4), and he got excited and asked if I knew what sizes he needed and that he would do it.

He just kind of got into it after fixing his son’s bike, bought a set of on the go tools to take with him when they all went for a ride, and he just… Kept going with it lol

So if I’m there doing my thing and another kid needs help he gets his tools out and helps too.

This community has always been really friendly, and I think things like the portable bike repair just adds onto it! I’m hoping to see more stuff like this happen, though I’m not sure what just yet.

We did see a few little libraries put in around town at the parks recently, and I’ve been chatting with others about natural lawns, so we’ll see where it goes next!

Its fun! And I show the kids and parents what I’m doing, which tools I need to do it, etc. Its mostly simple stuff too, like adjusting tension on a brake, set screw for the limit on the derailleur, or patching a tube and pointing out to not forget to check the tire before you put the tube back in. More annoying tubes (or if I’m out of patches) I pop into a small bin to patch later, I have a couple spares for 20" (kid size), including the ones I patched up since the last time.

I also really like that everyone kind of learns that these tubes are for everyone, you won’t necessarily get the same one back, and it really doesn’t matter because you’ve still got a working tire again. Good for the kids to learn that it doesn’t matter, and honestly good for some of the parents to learn that too.

Since I started doing it another dad has been learning too, and started doing the same thing. Though anything he’s not sure about he tells them to ask me.

Plus a really good way to meet a lot of the people in the area, I like doing it

Let’s see…

• Ive got a bunch of small devices powered off USB battery banks that are solar rechargeable
• indoor and outdoor gardens, with sensors also powered by those little battery banks
• My kids do a bunch of sports throughout the year now, I bring my bike toolkit so I can help fixing bikes for the kids in their school that show up
• Sharing what we get from gardening with neighbors. Except potato. Potato is mine (seriously though, we go through them quick)

Nothing else I can think of off the top of my head

Yeah I’m not debating that there is fear mongering about this at all, just - as you noted - this is not about protecting users. Thats a farce.

This is about Google trying to close up their ecosystem, device first. That is the issue I take with this whole situation, its a clear step in that direction being marketed as something it decidedly is not.

And I think Android users should recognize what it actually is, and try to find a different option than Apple or Google going forward.

Good! I hope alternative mobile operating systems get traction out of this!

We’ll see. The plan for now is a tcl flip with hotspot and a clamshell linux box in my pocket.

And again, there is no verification need anymore!

Please read the very first sentence in that slide. Then read through those steps again (and look at the steps inside of those steps).

Yes, there is a need still, or there are a series of annoying, anti-consumer steps involved, in an effort to have a walled garden.

Android and Google are not worth supporting over this. Again, not dealing with the play store first and thoroughly tells me this has nothing to do with security. If it did, they wouldn’t be going this route.

Visible here - thanks!

we could make Google directly reliable for malware in the appstore.

There is no reason they shouldn’t be now. Developer verification for the play store is one thing. Developer verification for installing an application on your own device is wholly separate.

I declare both as a risk.

And one is substantially higher risk than the other. Namely, the play store. As we recently saw with tens of millions of downloads from just a handful of apps in the play store. Does requiring this developer verification on a device resolve that problem? No. Not even remotely, does it?

While this started as a very anti consumer change

As long as it impacts the device use (it does), it still is.

I’m leaving Android over this. I doubt I’ll be the only one.

@somegeek@programming.dev please add [AIP] to the title, and reference the example here for how to format the disclosure

Thanks!

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.

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

• Readily accessible and fast options for the recruiter to access, even if your power is out / motherboard blows up / whatever.
• Demonstrates your familiarity with a world beyond github
• Demonstrates you can stand up your own local repo (if this is a thing they care about - if not don’t bother with your own repo for just this)

As for the server itself I’d say forgejo personally.

Doing what I can!

I’m still behind on responding to a few folks who have made offers to help, in the pipeline but we’ve had other… fun events (plus personal responsibilities eating up my time) which have gotten in the way of progress here and there.

And for the record, I consider myself maintenance crew!

Why would you?

The important part is your VMs and LXCs. Your Proxmox server, at most, requires configuration for specific needs (GPU passthrough for example). The only thing you need for that would be notes on configuration (unless you have this automated, in which case you don’t generally need that, just the notes in your scripts).

So a more important question, to me, is why do you want to back it up in the first place?