I think the reasoning was that there was a race condition between the code causing the bluescreen and the code updating to avoid the bluescreen so rebooting 15 times would give a lot of opportunities for the updater to win the race.
There are still more restrictions however on spending on other candidates and they would have to act like any other PAC, only helping via donating/running ads in support of (but importantly not directly by) any other candidate.
Hey, Lemmios developer here, what do you mean by cutting off images? It’s a known bug (I’m not sure that’s the right word because it’s working as intended just looks odd when people embed images in the body of a post) that Lemmios will only show the begging of a text post in the main feed, but once a post is clicked on there shouldn’t be any cut off images? The image loads fine for me and I would love a screenshot of it getting cut off if you can?
It does not mean that lemmy is less secure, but yes, it means that malicious app developers will have a much easier time stealing login credentials because entering them inside the app is already the norm. However this is definitely a feature that can be added so it does not mean anything bad long term
Even though they are both fediverse they still are quite different and one of the important differences is that lemmy does not support oauth so apps don’t have that option, as for why all mastodon apps use it: it’s because of the security benefits to the user and (as a lemmy app developer) implementing auth is hard lol
I sent out the post just as the app released so Apple still says they're working on getting it distributed, I have it enabled for all App Store regions so check back soon!
It's still crashing on the app store version? That's very interesting, apple is telling me the app store version has not crashed yet, just to verify this crash occurs when submitting a comment?
Yes, it should be much more stable, may I also ask when the testflight version is crashing for you? I am seeing very low crash numbers for the latest versions
Hmm... registration is closed on that server so I cannot attempt to reproduce here, would you mind going to settings -> About -> Get Logs and email those to alex@lavallee.one?
mrlavallee @ mrlavallee @lemmy.world Posts 4Comments 24Joined 2 yr. ago 
I think the reasoning was that there was a race condition between the code causing the bluescreen and the code updating to avoid the bluescreen so rebooting 15 times would give a lot of opportunities for the updater to win the race.