toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

227
active users

#soyes

0 posts0 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.games/@chris" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>chris</span></a></span> <span class="h-card" translate="no"><a href="https://lemmy.ml/c/fairphone" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fairphone@lemmy.ml</span></a></span> <span class="h-card" translate="no"><a href="https://mas.to/@fairphone" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>fairphone@mas.to</span></a></span> based off the security update stance basically almost all Android devices <em>with few exceptions</em> should be illegal to sell by <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>EUCommission</span></a></span> standards in the <a href="https://infosec.space/tags/EU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EU</span></a>.</p><ul><li>At least the cheap <a href="https://infosec.space/tags/shovelware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>shovelware</span></a> / manufactured <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eWaste</span></a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOYES</span></a> (they still sell Android 8.1 devices!) and <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unihertz</span></a> (they don't ever deliver update <em>at all</em>)…</li></ul><p>Maybe let the <a href="https://infosec.space/tags/OEM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OEM</span></a> of your choice know that and <em>pwn the market</em> for good?</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>sodiboo</span></a></span> <span class="h-card" translate="no"><a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tauon</span></a></span> <span class="h-card" translate="no"><a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>puppygirlhornypost2</span></a></span> <span class="h-card" translate="no"><a href="https://possum.city/@silly" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>silly</span></a></span> I don't think it's much of a <em>"<a href="https://infosec.space/tags/freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freedom</span></a>"</em> on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> but rather that the few devices and OS versions in circulation, alongside everyone from <a href="https://infosec.space/tags/jailbreaker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jailbreaker</span></a> to <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>malware</span></a> (espechally <a href="https://infosec.space/tags/govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>govware</span></a> <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>developers</span></a>) want to crack it open result in way more personnel <em>and</em> money behind it.</p><ul><li>OFC the fact that the <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Android</span></a> experience is worse from that POV is the lack of <a href="https://infosec.space/tags/regulation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>regulation</span></a> re: <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>repairability</span></a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openness</span></a> that would make shit work. Most cheap <a href="https://infosec.space/tags/phones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>phones</span></a> are done with even cheaper <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoC</span></a>'s by manufacturers who can't be assed (or frankly don't give a shit at all!) when it comes to <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mainline</span></a> support. (I mean, you've seen the video where <span class="h-card" translate="no"><a href="https://mastodon.social/@SexyCyborg" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SexyCyborg</span></a></span> demanded a vendor to give her the sourcecode as per <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a> for her device?)</li></ul><p>Granted <span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> does limit their support to devices that can comply with their <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> standards.</p><ul><li>The issues are mostly caused by <em>hostile app developers</em> that specifically decided to <em>knee-jerk</em> their users / customers for no good reason.</li></ul><p>I do wish for both vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fairphone</span></a> to up their game <em>and</em> regulators like <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>EUCommission</span></a></span> to actually push for more <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>transparency</span></a>, <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openness</span></a> and <a href="https://infosec.space/tags/LongTermSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LongTermSupport</span></a> of <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Smartphones</span></a>, because <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ManufacturedEwaste</span></a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOYES</span></a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiKo</span></a>, <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unihertz</span></a> and others that ship <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>outdated</span></a> <a href="https://infosec.space/tags/AndroidDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AndroidDevices</span></a> <em>and</em> never even a <em>single update</em> are a major problem!</p><ul><li>I don't blame projects like <span class="h-card" translate="no"><a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>LineageOS</span></a></span> that they can't cover <em>every device &amp; SoC</em> even tho they propably have the widest compatibility, I just think that there needs to be <em>pressure</em> that manufacturers don't just vomit stuff on the market and let customers frustratingly figure out the rest.</li></ul><p>I do have to give <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apple</span></a> credit where it is due, and that is that <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>iOS</span></a> does have consistency and accessibility nailed down very well. Something that they obviously are able being the <em>"<a href="https://infosec.space/tags/BenevolentDictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BenevolentDictator</span></a>"</em> of a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleVendor</span></a> &amp; <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SingleProvider</span></a> - platform. </p><ul><li>Obviously since they are the <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendor</span></a> for <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> and the sole [<em>"legitimate"</em> / <em>official</em>] <a href="https://infosec.space/tags/distributor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distributor</span></a> for any <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Apps</span></a> they do OFC cross-finance their relatively long <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>support</span></a> with their 15-30% cut from <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>App</span></a> <a href="https://infosec.space/tags/sales" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sales</span></a> &amp; <a href="https://infosec.space/tags/InAppPurchase" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InAppPurchase</span></a>|s they charge, which is why <a href="https://infosec.space/tags/AndroidPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AndroidPhones</span></a> suffer the <em>"<a href="https://infosec.space/tags/3DO" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>3DO</span></a> syndrome"</em>: Needing to charge more since they only get to make money once with hardware sales and not after that, so there's no incentive for them to give a shit beyond <em>"brand value"</em> to care. <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Google</span></a>, <a href="https://infosec.space/tags/Samsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Samsing</span></a>, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fairphone</span></a> and very few others do, but most don't as they close the books on the product once launched and sold out (<em>angrily stares at Unihertz</em>)...</li></ul><p>Maybe one day the folks at <span class="h-card" translate="no"><a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>frameworkcomputer</span></a></span> acquire Fairphone and decide to bring the same modularity to <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Smartphones</span></a> and get something done that makes it easy to maintain long-term and that even <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GrapheneOS</span></a> are willing to support.</p><ul><li>Until then the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Enshittification</span></a> is ruining everything as usual...</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://snapp.social/@alsutton" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>alsutton</span></a></span> <span class="h-card" translate="no"><a href="https://cloudisland.nz/@aurynn" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>aurynn</span></a></span> <span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> <span class="h-card" translate="no"><a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>EUCommission</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bsi</span></a></span> I disagree.</p><p>It'll merely force them to enable aftermarket support woth an unbloated experience.</p><ul><li>It won't prevent manufacturers from offering and implementing unique features in terms of hardware and software.</li></ul><p>It'll just make them responsible to not release products like <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unihertz</span></a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiKo</span></a>, <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOYES</span></a> and many others which refuse to deliver <em>any post-launch <a href="https://infosec.space/tags/updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>updates</span></a></em> and thus sell <em>manufactured <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eWaste</span></a></em>.</p><ul><li>Or has anyone seen Updates being released for the <a href="https://infosec.space/tags/UnihertzJelly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UnihertzJelly</span></a> series (including <a href="https://infosec.space/tags/JellyStar" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JellyStar</span></a>, <a href="https://infosec.space/tags/Jelly2E" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Jelly2E</span></a> and <a href="https://infosec.space/tags/JellyMax" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JellyMax</span></a>)?</li></ul><p><a href="https://infosec.space/tags/AOSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AOSP</span></a> support and <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>reproduceableBuilds</span></a> would at least allow <a href="https://infosec.space/tags/Aftermarket" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Aftermarket</span></a>-<a href="https://infosec.space/tags/ROMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ROMs</span></a> like <span class="h-card" translate="no"><a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>LineageOS</span></a></span> to support them when the manufacturer decides not to.</p><ul><li>Whether that happens is a different story, but at least <a href="https://infosec.space/tags/consumers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consumers</span></a> wouldn't be at the mercy of a <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendor</span></a> when it comes to <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@uint8_t" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>uint8_t</span></a></span> <span class="h-card" translate="no"><a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GrapheneOS</span></a></span> <em>exactly that</em>...</p><p>Even <em>"manufactured <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>eWaste</span></a>"</em> that never gets Updates like the <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SOYES</span></a> XS13, <a href="https://infosec.space/tags/Wiko" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wiko</span></a> Lenny and <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Unihertz</span></a>, <a href="https://infosec.space/tags/Ulefone" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ulefone</span></a>, ... garbage brands have it.</p>
Matt Willemsen<p>Fact Check<br>Trump's Name Appears 312 Times in Project 2025 Document?<br>Rating: Mixture<br><a href="https://www.snopes.com/fact-check/project-2025-trump-name/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">snopes.com/fact-check/project-</span><span class="invisible">2025-trump-name/</span></a><br><a href="https://mastodon.social/tags/Well" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Well</span></a> . . . . <a href="https://mastodon.social/tags/TrumpAdministration" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TrumpAdministration</span></a> <a href="https://mastodon.social/tags/PresidentTrump" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PresidentTrump</span></a> <a href="https://mastodon.social/tags/SoYes" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SoYes</span></a></p>