Pocket casts is really good, but their premium pricing has really climbed recently (device syncing, better organization options, and desktop/web clients). AntennaPod is almost as good and FOSS if that matters to you.
Yeah I was pulling Samsung from an article I found discussing the issue, not specifically your comment. It said that those system APIs only responded to Google or Samsung made apps, but that was from like 2021 tbf
Ah ok, other replies mentioned API access in relation to servers so I misunderstood the issue. It looks like that API is hardlocked to Google (and Samsung?) devices. Thanks for the info
Sure, but isn't that just complaining that Google runs the largest implementation of RCS? It would've been great if this was handled by carriers, but they never would pick up the task so Google just did it inhouse. I think if they hadn't rcs would just be dead by now (for better or worse)
Not really the topic, but why do you want to run owlbear alongside foundry? It seems like a slimmer alternative rather than something to use in conjunction.
To actually answer the title post I just run foundryvtt and I have a bunch of RPG manuals backed up in Nextcloud so I guess that too
Testability for one, but I would also argue that those functions are there for using. If some block of logic is sufficient to stand on its own, it should. I'm not saying do it arbitrarily, but it's been my experience that small functions lead to more readable code and better testing. Most people write a 15 line function treating it as if it does a single thing when in reality it's doing two or three discrete operations
Pocket casts is really good, but their premium pricing has really climbed recently (device syncing, better organization options, and desktop/web clients). AntennaPod is almost as good and FOSS if that matters to you.