Are we assuming we’re allowed to use defines and templates? 😏

Not sure whether to laugh or cry at this one…

Forking a repo is not the same as developing it. Any idiot can rehost the existing source code, but all the developers with knowledge of the code base and project just got axed by Nintendo.

I miss regular old web forums, mailing lists and that sort of thing. Discord / Slack / etc have zero discoverability. The ability to google your question is gone, and knowledge is ephemeral, when a chat is the central source of community.

Does that mean you can’t downvote comments outside of Beehaw too?

Likely no different as they’re both derived from Ubuntu which is an officially supported and sanctioned Steam platform

Actually with a Synology NAS you don’t need Plex, they have a built in equivalent called DS Video with apps for Apple TV, iOS, Android, etc!

I’ve had an Nvidia shield in the past as well and it works reasonably well, but the video experience is definitely better on the Apple TV. The Android boxes make more sense if you want a place to install emulators that also occasionally streams.

Keep your Apple TV and use it as a streaming client for whatever you stand up on the backend. Personally I have a Synology NAS that I love and I use the net to get all my content. Use the net. 😉

It’s more than slight! I ran a 3090 in an eGPU for a while and it lost around 40% of performance compared to when it was in my case.

Former Apple engineer here. This architecture isn’t ideal if you intend the service to be portable - but we didn’t! Knowing the messages can only originate from a sealed application on a first party device eliminates a whole class of spam and security problems.

Beeper’s implementation spoofs Mac keys and requires you trust them with your Apple ID credentials if you want to be able to take full advantage of iMessage.

It’s just pointless. A huge security risk for Apple users and to zero benefit for Android users. Let Apple implement RCS as they promised and move on. Isn’t everyone on Telegram or WhatsApp anyway…?

Well, none. One assumes the aspiration is to implement Cocoa, to allow GUI apps to run.

Well, none. One assumes the aspiration is to implement Cocoa, to allow GUI apps to run.

Former Google and current Apple engineer here; this is definitely an insecure workaround with a lot of flaws. I think Beeper is basically doing the same.

The reality is that while we do have a lot of walled garden policies for business reasons (which I don’t love), iMessage and FaceTime are a bit more complicated than that, tightly coupled around the hardware encryption and keystore in the TPM in our devices. Unwinding this would be undesirable from a compatibility perspective as it would break any Apple devices not updated immediately to new OS versions that change the encryption scheme.

So the only way to plug into iMessage per se is a weird workaround like this where you basically AppleScript automate the Messages app on a Mac with its shields down.

There’s not a great way to fix this problem which is largely why we are bringing RCS support to iOS 18 to hopefully make such things moot.

But that said even as an employee I don’t think iMessage is a great example of a modern chat app. I mean, it’s better than SMS which is what it sought out to replace. But compared to an actual chat app - something like Telegram - it doesn’t hold up.

This is a really disingenuous argument even for /c/android. iOS has many pitfalls with the walled garden effect but it also has many advantages with regard to software quality, consistency and performance (particularly at an API level, speaking as a developer for both platforms). If we write them off as bad, dumb or irrelevant then we forego the opportunity to improve our own apps and Android as a platform. Google does not have a monopoly on good ideas nor on technical users - one could note that Android itself is developed on Macs, as Silicon Valley developer workstations are almost universally Apple hardware…

What? My point is that I wonder if there are hardware and bootloader level back doors that survive flashing a new ROM or if you can be truly clean flashing a trusted AOSP one.

Tbh I wonder if flashing an aosp rom changes that at all

You may want something like https://porteus-kiosk.org/

Some of those are true I don’t think it’s fair to say Android is easier to develop for. I’ve been developing software for both professionally since 2012, and I would argue iOS may be slightly easier, due to the maturity of the tooling and ubiquitous, predictable, and mature system frameworks. I often find myself reaching for some dependency on Android to provide what a one-liner on iOS can do. Just my two cents.

deleted by creator

I think the point is rather the opposite, what can Android do that iOS can’t? And the honest answer is effectively nothing. It can’t side load unsigned apps. Literally nothing else. So to claim that Android is so super advanced in the article is disingenuous.

As power users we should be watching both mobile platforms closely and honestly, and demanding parity and improvements in both. The moment we declare one “better” and the other one trash is the moment we stop holding our own platform of choice to account for bettering itself.