Honestly… I kinda can. This is an extreme and unlikely scenario, but there’s a few things that make me think it’s not impossible.

A) Trump has publicly promised to back out of NATO.

B) Trump is generally very pro-Russia.

C) Trump has generally had poor relations with Canada.

If the US backed out of NATO, they’d have a lot of military power sitting idle, and NATO would be significantly weaker, as well as doubly occupied in Ukraine. Russia would certainly be interested in such a thing happening, given the strategic importance of Antarctica, and how much it would take eyes away from them. I also don’t doubt for a second that Trump would love to exploit our natural resources, especially oil, and the military importance of the top of the world. Not to mention it’d be an excuse to continue creating expensive military contracts and posturing as tough.

This is of course, mostly fantasy, but Trump is nothing if not unpredictable.

I think it is a problem. Maybe not for people like us, that understand the concept and its limitations, but “formal reasoning” is exactly how this technology is being pitched to the masses. “Take a picture of your homework and OpenAI will solve it”, “have it reply to your emails”, “have it write code for you”. All reasoning-heavy tasks.

On top of that, Google/Bing have it answering user questions directly, it’s commonly pitched as a “tutor”, or an “assistant”, the OpenAI API is being shoved everywhere under the sun for anything you can imagine for all kinds of tasks, and nobody is attempting to clarify it’s weaknesses in their marketing.

As it becomes more and more common, more and more users who don’t understand it’s fundamentally incapable of reliably doing these things will crop up.

Honestly, makes sense, the active voice version is just… more efficient and easier to parse quickly.

Eh, this is a thing, large companies often have internal rules and maximums about how much they can pay any given job title. For example, on our team, everyone we hire is given the role “senior full stack developer”, not because they’re particularly senior, in some cases we’re literally hiring out of college, but because it allows us to pay them better with internal company politics.

Asahi Linux is a project to get Linux running on M-series macs, which has taken a bunch of difficult reverse engineering, since Apple doesn’t really provide public documentation on how they work.

Running Linux means they can run steam games like a Linux machine. This is a pretty impressive landmark in terms of their OpenGL rendering support.

I don’t necessarily disagree that we may figure out AGI, and even that LLM research may help us get there, but frankly, I don’t think an LLM will actually be any part of an AGI system.

Because fundamentally it doesn’t understand the words it’s writing. The more I play with and learn about it, the more it feels like a glorified autocomplete/autocorrect. I suspect issues like hallucination and “Waluigis” or “jailbreaks” are fundamental issues for a language model trying to complete a story, compared to an actual intelligence with a purpose.

I’d be very surprised if anything functional actually comes out of this. Far more likely they get scammed out of the money by garbage like the current “AI writing detection” methods, with terrible success rates that cause more societal problems than they solve.

Eh, that is kinda the appeal of Reddit, and its alternatives. Finding smaller communities of likeminded individuals that you can group into a tailored feed.

I always say the magic of this model is that it’s not just a firehose of every possible interest, it’s more like a shower of dozens of tiny handpicked jets. It just happens that on Lemmy, the “All” feed is still reasonably tailored to the main demographic here. That being tech nerds who dislike Reddit’s recent decisions enough to make a change.

Mine is still that (on Mac, at least) the only way to update Apple apps is by updating the whole system. Work requests we don’t update our macs, and now I still can’t edit texts from my computer.

Exactly, my wife mentioned just last week that she doesn’t like her AirPod 3’s due to the fit, and that she’s considering asking for a new pair of 2’s this Christmas instead. Glad to hear they might be going back on that design change, for her sake.

Oh, fantastic! Glad you used some of the quiet time to get some work done without us all breathing down your neck lol.

I’ve still been kicking around on TestFlight, both out of laziness in not wanting to test and find something else, and hopes you might return, so this is wonderful news!

Seems like a sensible overhaul, hitting the major issues with the fee, but still going ahead with a version of it. Big points for me:

• Not retroactive. Only affecting the next version of Unity, and you can even opt out of updating to skip the fee.
• Data is now reported by the customers. Still not sure how that plan to enforce this, but it’s a hell of a lot better than some arbitrary data collection scheme being baked into the game.
• Free version is excluded. No charging tiny side projects, or students or something, it only affects already paying customers.

Still not sure I love charging per install as a concept, and they’ve already overplayed their hand and burnt many bridges, but at least this implementation isn’t insanely hostile. Guess we’ll see how this plays out from here.

Having used tailwind a little bit, I have nothing but praise for it. Effortless copy/pasting of components with confidence, really nice look by default, easy tweaking, absolutely no management or planning required to organize your CSS, and it’s all right there, directly on your html, never anywhere you have to hunt for it. Feels very freeing to just… not think about CSS at all.

And the “clutter” really is fine, modern IDEs with good syntax highlighting, plus a tailwind extension to help complete the class names and clean up accidental duplicates or conflicting properties, and you’re good.

Dang, this just makes me impressed at what you’ve managed on your first outing with React Native. You’ve got impressive design sensibilities to get so much right that you’re still one of the best apps out there.

Hopeful this rewrite gives you the technical foundation you’ve been looking for, so that this can continue building into the best app it can be!

This is very intriguing… I actually work in CBC (nowhere near content or with the social media people who’d make these kinds of decisions), but as a developer I get 20% time to dabble with anything I think might be useful. I haven’t used it in a while, but a CBC ActivityPub instance may be just the right project, especially if it can auto-publish our content from the same feeds that power our site.

I also feel like a lot of the value of chronological is lost if I think it’s algorithmic recommendations. If I don’t know I’m browsing the latest? I’ll likely just think the algorithm is serving up some garbage. Especially somewhere like Facebook, where people haven’t really been curating their feed for years, just… following whoever to be polite and letting the algorithm take care of it.

Yeah, I think lots of people had FOMO about missing updates whenever the App Store version dropped, and mistook the stability of “preparing for release” as what the stability would be long term.

Makes sense, and I think you’ve got the right idea. The development pace has been incredible, but Memmy for iPhone can still get better, and should, as that’s the primary customer base.

I’d say, once Memmy is excellent, supports all different kinds of sites and image viewers, handles different kinds of content, is super accessible, has themes, filters, settings, and just generally everything you’d reasonably want to build, then maybe take your time and use the tools Apple provides to give a great iPad experience. Then once that’s done and battle tested, maybe even a great Mac experience.

iPad, and hell I believe even MacOS on M1 if you allow it, can both use the iOS version until then.

TestFlight is beta. Faster, more frequent updates, with a higher chance of receiving a broken update. Everything that comes to beta will go to the stable version eventually, once it’s polished and cleaned up.

If you like living on the cutting edge a little bit, and giving feedback to the developer, stick with TestFlight. If you’d prefer a more stable experience, and get really annoyed by bugs or issues, go with the App Store version.

Eh, I’d assume the comparison isn’t flattering. I think the point of this article is to argue you don’t need ElasticSearch to implement a competent Full Text Search for most applications. Splitting hairs over a few milliseconds would just distract from that point, when most applications should be prioritizing simplicity and maintainability over such tiny gains in a reasonable dataset.

Might be interesting to try to analyze at exactly what point elasticsearch becomes significantly useful, however. Maybe at the point where it saves a full tenth of a second? Or where it’s returning in half the time? Could be an interesting follow up article.