Native feature

Works with any openai compatible endpoint, I use local ollama on an m2 mac mini (I still need to move things over to llama.cpp fully on there). It can also do audio transcriptions for a video, though I only use it for images (usually a screenshot of something my wife got sent by a friend that came from instagram or whatever).

Meta in the context of a post is an “about the community” post. They are using the word “meta”, not the terrible company “Meta”.

While I’m glad this community is more welcoming now, we should avoid threads targeting individuals and focus on the positives going forward.

So I’d appreciate it if you deleted this thread, and if you instead wanted to post one about feeling more welcome now, that would be great!

Edit: and for the record, they weren’t removed. After criticism about the situation they made me a mod and left.

They were the moderator of this community, so that wouldn’t really help.

I mostly use it to track (and tweak) recipes that are safe for me with my food allergies, and from that perspective its great. Despite having all kinds of options to OCR recipes, import them, whatever, my wife just… hasn’t bothered.

So I haven’t really used the meal planner yet, I need to get her using it more often :)

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.