That’s great and I’m glad that works for you.

But most people buying portable gaming handhelds are not doing that. And the people looking for things like that are likely landing closer to a surface or standard laptop, which Windows already supports well.

I don’t know that Microsoft has any business trying to make Windows support these devices better…

Windows is entirely built around two pillars:

1. Enterprise support for corporations, and team machine management
2. Entirely open compatibility so they can run almost any hardware you put into it, plug into it, and backwards compatibility for all that for as long as possible.

Portable game machines are not an enterprise product. Nor do you care about broad hardware support or upgradability. Nor do you care about plugging in your parallel port printer from 1985. Nor do you care about running your ancient vb6 code to run your production machines over some random firewire card.

Windows’ goal is entirely oppositional to portable gaming devices. It makes almost no sense for them to try to support it, as it’d go against their entire model. For things like these, you want a thin, optimized-over-flexible, purpose built OS that does one thing: play games. Linux is already built to solve this problem way better than Windows.

But, Microsoft will probably be stupid enough to try anyway.

Now we just need that GFX software from intel / amd / nvidia that is available on windows, taking advantage of that newly supported hardware

Stop, you’re making me too hard. I might be able to like, ditch Windows if that happens.

If you’re an engine developer, it’s a reasonably common problem.

If you’re a game developer using a cross platform engine, it’s pretty uncommon, as the engine developer has already accounted for most of it.

If you’re somewhere in the middle, it’s probably somewhere in the middle.

It surprises me how many indie devs avoid some of the higher level / more popular engines for this reason alone. But I assume they just must enjoy that sort of stuff much more than I.

If a Threads user posts an image, and Meta hosts it, and I scroll through my feed and see it, my client will hit their server for said image. And Meta can collect my IP.

Meta basically invented this shit.

Yes, but if you host an image, and my client prefetches it, it’s going to exposed my IP to your image server. And if you have clauses saying you’re collecting IPs…

Meta basically invented this shit. They’ll do it again. It’s what they do.

Yes, but many clients are going to go look up images manually. If it’s a Threads post, it’s likely hosted by Meta servers, and they can easily see your IP when doing that. And they’re saying they might collect IPs from you even if you’re not using their service directly.

Yeah, this. If you comment on a few different image posts, they just have to look for the IP that is in all of those pools. It’s not that hard and this is basically metas bread and butter.

Meta says, for Threads to federate, they access the same data any instance does when it federates.

Okay, but like, I don’t want Meta consuming that data? At least if they wanted to scrape through reddit to put that together, they’d be going out of their way. This data is now just coming through the same API “for free”.

If I didn’t mind Meta scraping through all this, why wouldn’t I just use Threads?

This is exactly the kind of shit that pushed me here - I don’t want Meta sifting through all my shit. Its unlikely that some other instance host is going to start building psychological advertising profiles on me and sell it to the highest bidder. But you bet your ass Meta will try.

Public? Idk, maybe. I wouldn’t generally consider my IP to username to be public. Comment and post stuff, sort of. But even if it’s public, I still wouldn’t want Meta consuming it.

That’s not how I read it, but I’m not going to claim to be a fediverse expert. That post specifically says:

Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:

To me, this reads as, even if a Threads user follows you, your info gets chewed up by Meta.

In other words, if you post somewhere on the Fediverse, and some Threads user bumps into it, they can follow you, and that will send all that data to Meta. And it looks to include data well beyond the post the Threads user saw.

To me, this is a “sound the alarm” moment. If you came here to avoid Meta’s data harvesting, this sounds like you at least need to be on an instance defederated from threads, but I’m not sure even that’s enough.

Provided that a Third Party User is followed by or following a Threads account, Meta will ingest these pieces of data specifically:

Username

Profile Picture

IP Address

Name of Third Party Service

Posts from profile

Post interactions (Follow, Like, Reshare, Mentions)

So if you follow a threads user or even if a threads user just follows you, they pull all this data?

IMO this seems like reason to defederate across the board. Someone else can leak your info to Meta.