PMOS is probably broken for it, so I’d probably lean toward lineageos.

Perfectly fine, doesn’t change my question or that others may benefit from being aware.

I don’t do DRM, so the majority of my workflow is simplified. Download to the correct directory, auto-imported by Calibre and flagged for review of metadata, manually review metadata, convert to epub3 (even if its v3 to v3, I’ve removed wonky behavior before by doing so), export to appropriate directory for the OPDS server.

Basically the same for audiobooks, but dropped into the directory for AudioBookShelf.

What phone do you have that the jellyfin app and the jellyamp app are unavailable?

Edit: Also you can support subsonic with jellysub acting as a go-between. Considering its not a music-first solution, I’m not surprised that it doesn’t support subsonic natively, personally.

Edit 2: Its unmaintained but works as of the last time I tried it out, fwiw. It isnt exactly a complex codebase either if something got tripped up by minor changes.

Broad-market funds like the Vanguard Total Stock Market ETF (VTI) and the iShares Core S&P Total U.S. Stock Market ETF (ITOT) include SpaceX.

SpaceX was added to the Nasdaq-100, meaning funds that track it, such as the Invesco QQQ ETF, hold the stock.

Benchmarks like the Russell 1000 also hold SpaceX, automatically populating funds like the iShares Russell 1000 ETF (IWB)

https://www.investopedia.com/spacex-stock-joins-major-index-funds-what-regular-investors-need-to-know-spcx-ipo-vanguard-blackrock-vti-itot-12004764

I mean… it still might be cleaner than outside. Which says more about everything else in the world right now than anything else.

Considering the air quality for many right now, probably better off in your car than outside, as long as it has a cabin filter.

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”.

That is an absolutely wild take IMO.

Posts removed had nothing to do with homelab efforts, and included issues with self hosting. So unless you are defining a homelab as “Anything that isnt the software itself being discussed”, which would be a really odd definition for a homelab, then no.

That may have been their intention, but it doesn’t reflect the moderation at all.

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 :)

Well… Thats saved for later.

I bought the sidewinder joystick because of it!

I should play games that use a joystick again. Or, you know, games in general.

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.

@[email protected] please add [AIP] to the title, and reference the example here for how to format the disclosure

Thanks!