quickenparalysespunk

it will most likely run steam, so it will not be any kind of steam deck "killer". more like "sibling".

funny.

I'm right there with you.

my parents came to USA before i was born and i was born here. i don't know how cheetoh face would do it, but i have no doubt it would try its best to kick you and i both out, even if it's obviously illegal.

unlike some others in the thread, i don't think this is a trivial worry. I've also been silent on certain issues out if concern for my loved ones being targeted for surveillance or worse. i respect you for posting about this. I'm afraid too.

keep talking to trusted friends and take care of your mental health! touch grass, drink water, get the best quality of sleep you can.

ご教示ありがとうございます。

I only mentioned MS Edge to highlight that it's a chrome(-ium) browser and ~~therefore~~ Edge probably has a paid team of developers.

That team probably has enough quantity of members (or coding work hours) to overwhelm the upstream chromium code contributions of volunteer developers of foss projects.

Because of Edge's volume of contributions, they could accidentally/intentionally decide the direction of Chromium, even without owning it officially. That's one of the ways I heard that Google controlled Chromium, accidentally or intentionally.

edit: wording mistake

it's not their job, i agree. not under the current constitution and laws.

i meant to highlight that no one is going to guarantee anything (other than Google losing ownership of Chrome/Android).

I've been trying to keep less tabs open.

it's not easy while test-driving multiple search engines for every search lol

i really distrust Google and I'm glad about the verdict. I do agree that chrome and android should be ~~cut off models~~.

edit: cut off from advertising business models

on the other hand, like with Firefox, I'm worried about the instability and changes that are coming, mainly in the effect on fork projects Like Graphene, Calyx, Lineage, any privacy-focused Chrome forks, and of course Chromium.

DOJ probably isn't able to guarantee chrome & potentially android are taken over by totally ethical, stable companies/NPOs who will keep the projects open source, or allow an open source offshoot project to which the new organization would still contribute coding people-hours.

I'm sure there will be some sort of guarantees for stock chrome and android users, like paid services/subscriptions will be continued or refunded.

but what about users of community projects based on chrome and Android?

many other Lemmy users have commented how community projects don't really have the resources to keep browser engines up to date, let alone innovate. without Google (which i think is a good thing), Microsoft Edge team could become the de facto direction-setter of Chronium (which i think is really really really bad).

TL;DR the foss mobile OS community, and especially the foss browser community (considering Firefox funding shortfall and AI/ad revenue pursuits) are possibly f*ed in the a for the near term.

i see the original poster (on Twitter? mastodon?) can read the kana and is aware of some of the irony.

i hope everyone here is also aware that

• to people in Japan this is a worthless (doesn't accomplish anything) use of kana because it communicates nothing to Japanese speakers
• for East/Southeast Asian people in western countries, this type of font is a reminder of how they are constantly asked by non-Asians to read/translate Chinese or any and all non-roman non-arabic script languages, regardless of where they were born/raised or their families' relation/lack of relation to countries that use Chinese script.

not saying the pic can't be enjoyed, but enjoying without being aware is just contributing to the ignorance being spread by the (probably) ignorant coffee shop.

maybe it's caused by graphene+ironfox+some other setting or other app

i agree with the headline. strongly. didn't read the article.

btw is tech dirt still funded by (one of) Koch bros?

edit: honestly, just checking. won't complain, whatever the answer.

yeah, on graphene.

hmm can't find mention of a bug for this combination. barely even the two mentioned in the same webpage.