I’m in orange country currently so there aren’t any alternatives. It curve was here I’d probably be off iOS honestly. I genuinely use nfc payments that much that often that it’s a big necessity for me.

As far as I know Samsung is the worst option for security and privacy. Also good news iPad has the health app now

Can’t use graphene unless my primary because android because of the Intune stuff

I’m definitely skeptical of anything closed source in general but there isn’t too much on the contrary, so it’s just a matter of one company makes money on data and on doesn’t. I’m sure they both collect similar amounts of data though.

I guess I’m asking for thoughts on a solution. My options are basically A) Keep iPhone as main, use stock pixel 9 as work no changes. B) Use graphene + watch and somehow try to hack a way into Intune setup properly, lose a little bit of functionality. Probably would return pixel and trade in iPhone for pixel 10 and wait for graphene, since I value the MagSafe. C) Get a different iPhone as a second for or upgrade current phone to use current as old phone. Probably most expensive option if the latter. D) not care at all about having my personal device slightly managed and just put Intune on it.

Yeah you make a good point. I saw an article recently that Apple is considering using ads in Apple Maps so maybe the companies are moving closer together and it doesn’t really matter that much anyway. How would a degoogled stock pixel phone compare to an iPhone do you think?

Sorry perhaps I could have been a bit clearer. One of the devices is going to end up having Intune on it for work, is the somewhat complicating factor. I realize I could make the iPhone my “work” and just but Intune on there but I guess ideally I’d like to have 0 personal related stuff on a phone that has anything to do with work if possible. Perhaps if graphene worked with Intune work profiles I could just do 1 singular device of graphene + watch? But I looked through some threads and didn’t seem like it was super clear cut

Or maybe a dentist

This would be quite cool if this passed around every social media platform lol

I don’t have an explicit config file no, I don’t remember needing it before though. I’ve followed the steps https://docs.gitea.com/installation/install-with-docker which worked with gitea but doesn’t work with forgejo. I didn’t see anything that mentioned needing a config for the first method listed there at least. I suppose I could try some of the other methods listed there but I liked option A the best generally.

Logs for what the container?

I did check that first after a lot of googling and I think everything is all set there

Ok. The issues lies somewhere in the actual connection. Adding ssh keys to my instance shows up properly in the known keys. Whenever I attempt to connect either on the actual server itself as a test or via trying to clone over ssh or even connect via ssh itself I get public key denials. If you want I can provide you my ssh config on server, my docked compose file, the verbose output of the ssh connections in various facets although they haven’t appeared to be very helpful, or whatever else can be helpful

Edit would someone like to enlighten me why they’re randomly downvoting this? Would you all have preferred I just dumped logs? I genuinely don’t understand. My main question was actually whether there is a difference between gitea and forgejo since I’ve already verified this exact setup worked there. So if anything an answer to my original question would require 0 input from me. I do appreciate the help from everyone but to say that me saying “it doesn’t work” is unhelpful is missing the point