toad.social

Kevin Karhan :verified:<a href="https://social.linux.pizza/@midtsveen" class="u-url mention" rel="nofollow noopener" target="_blank">@midtsveen</a> Yes, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> needs to up their game, but that still does make them one of the better vendors.<ul><li>You've seen the <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#ManufacturedEwaste</a> by <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a> & other garbage brands? </li></ul>Now realize most <a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> <a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Normies</a> never update their devices even if they get updates at all!<ul><li>The only reason <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>, <a href="https://infosec.space/tags/Smasung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smasung</a>, <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> and other Vendors get their usera to update is to basically violate <a href="https://infosec.space/tags/consent" class="mention hashtag" rel="nofollow noopener" target="_blank">#consent</a> and force it down their throats because that's easier than teaching <a href="https://infosec.space/tags/TechLiteracy" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechLiteracy</a>.</li></ul>

Kevin Karhan :verified:<a href="https://gaysex.cloud/@sodiboo" class="u-url mention" rel="nofollow noopener" target="_blank">@sodiboo</a> <a href="https://possum.city/@tauon" class="u-url mention" rel="nofollow noopener" target="_blank">@tauon</a> <a href="https://transfem.social/@puppygirlhornypost2" class="u-url mention" rel="nofollow noopener" target="_blank">@puppygirlhornypost2</a> <a href="https://possum.city/@silly" class="u-url mention" rel="nofollow noopener" target="_blank">@silly</a> I don't think it's much of a "<a href="https://infosec.space/tags/freedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#freedom</a>" on <a href="https://infosec.space/tags/iOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#iOS</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">#jailbreaker</a> to <a href="https://infosec.space/tags/malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#malware</a> (espechally <a href="https://infosec.space/tags/govware" class="mention hashtag" rel="nofollow noopener" target="_blank">#govware</a> <a href="https://infosec.space/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>) want to crack it open result in way more personnel and money behind it.<ul><li>OFC the fact that the <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</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">#regulation</a> re: <a href="https://infosec.space/tags/repairability" class="mention hashtag" rel="nofollow noopener" target="_blank">#repairability</a> and <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> that would make shit work. Most cheap <a href="https://infosec.space/tags/phones" class="mention hashtag" rel="nofollow noopener" target="_blank">#phones</a> are done with even cheaper <a href="https://infosec.space/tags/SoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoC</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">#Linux</a> <a href="https://infosec.space/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a> support. (I mean, you've seen the video where <a href="https://mastodon.social/@SexyCyborg" class="u-url mention" rel="nofollow noopener" target="_blank">@SexyCyborg</a> 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">#GPLv2</a> for her device?)</li></ul>Granted <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> 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">#security</a> standards.<ul><li>The issues are mostly caused by hostile app developers that specifically decided to knee-jerk their users / customers for no good reason.</li></ul>I do wish for both vendors like <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> to up their game and regulators like <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> to actually push for more <a href="https://infosec.space/tags/transparency" class="mention hashtag" rel="nofollow noopener" target="_blank">#transparency</a>, <a href="https://infosec.space/tags/openness" class="mention hashtag" rel="nofollow noopener" target="_blank">#openness</a> and <a href="https://infosec.space/tags/LongTermSupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#LongTermSupport</a> of <a href="https://infosec.space/tags/Smartphones" class="mention hashtag" rel="nofollow noopener" target="_blank">#Smartphones</a>, because <a href="https://infosec.space/tags/ManufacturedEwaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#ManufacturedEwaste</a> like <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOYES</a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a>, <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a> and others that ship <a href="https://infosec.space/tags/outdated" class="mention hashtag" rel="nofollow noopener" target="_blank">#outdated</a> <a href="https://infosec.space/tags/AndroidDevices" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidDevices</a> and never even a single update are a major problem!<ul><li>I don't blame projects like <a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@LineageOS</a> that they can't cover every device & SoC even tho they propably have the widest compatibility, I just think that there needs to be pressure that manufacturers don't just vomit stuff on the market and let customers frustratingly figure out the rest.</li></ul>I do have to give <a href="https://infosec.space/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</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">#iOS</a> does have consistency and accessibility nailed down very well. Something that they obviously are able being the "<a href="https://infosec.space/tags/BenevolentDictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#BenevolentDictator</a>" of a <a href="https://infosec.space/tags/SingleVendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleVendor</a> & <a href="https://infosec.space/tags/SingleProvider" class="mention hashtag" rel="nofollow noopener" target="_blank">#SingleProvider</a> - platform. <ul><li>Obviously since they are the <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendor</a> for <a href="https://infosec.space/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#hardware</a> and the sole ["legitimate" / official] <a href="https://infosec.space/tags/distributor" class="mention hashtag" rel="nofollow noopener" target="_blank">#distributor</a> for any <a href="https://infosec.space/tags/Apps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apps</a> they do OFC cross-finance their relatively long <a href="https://infosec.space/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#support</a> with their 15-30% cut from <a href="https://infosec.space/tags/App" class="mention hashtag" rel="nofollow noopener" target="_blank">#App</a> <a href="https://infosec.space/tags/sales" class="mention hashtag" rel="nofollow noopener" target="_blank">#sales</a> & <a href="https://infosec.space/tags/InAppPurchase" class="mention hashtag" rel="nofollow noopener" target="_blank">#InAppPurchase</a>|s they charge, which is why <a href="https://infosec.space/tags/AndroidPhones" class="mention hashtag" rel="nofollow noopener" target="_blank">#AndroidPhones</a> suffer the "<a href="https://infosec.space/tags/3DO" class="mention hashtag" rel="nofollow noopener" target="_blank">#3DO</a> syndrome": 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 "brand value" to care. <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a>, <a href="https://infosec.space/tags/Samsing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Samsing</a>, <a href="https://infosec.space/tags/Fairphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fairphone</a> and very few others do, but most don't as they close the books on the product once launched and sold out (angrily stares at Unihertz)...</li></ul>Maybe one day the folks at <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> 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">#Smartphones</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">#GrapheneOS</a> are willing to support.<ul><li>Until then the <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> is ruining everything as usual...</li></ul>

Kevin Karhan :verified:<a href="https://snapp.social/@alsutton" class="u-url mention" rel="nofollow noopener" target="_blank">@alsutton</a> <a href="https://cloudisland.nz/@aurynn" class="u-url mention" rel="nofollow noopener" target="_blank">@aurynn</a> <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> <a href="https://social.bund.de/@bsi" class="u-url mention" rel="nofollow noopener" target="_blank">@bsi</a> I disagree.It'll merely force them to enable aftermarket support woth an unbloated experience.<ul><li>It won't prevent manufacturers from offering and implementing unique features in terms of hardware and software.</li></ul>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">#Unihertz</a>, <a href="https://infosec.space/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a>, <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOYES</a> and many others which refuse to deliver any post-launch <a href="https://infosec.space/tags/updates" class="mention hashtag" rel="nofollow noopener" target="_blank">#updates</a> and thus sell manufactured <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a>.<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">#UnihertzJelly</a> series (including <a href="https://infosec.space/tags/JellyStar" class="mention hashtag" rel="nofollow noopener" target="_blank">#JellyStar</a>, <a href="https://infosec.space/tags/Jelly2E" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jelly2E</a> and <a href="https://infosec.space/tags/JellyMax" class="mention hashtag" rel="nofollow noopener" target="_blank">#JellyMax</a>)?</li></ul><a href="https://infosec.space/tags/AOSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#AOSP</a> support and <a href="https://infosec.space/tags/reproduceableBuilds" class="mention hashtag" rel="nofollow noopener" target="_blank">#reproduceableBuilds</a> would at least allow <a href="https://infosec.space/tags/Aftermarket" class="mention hashtag" rel="nofollow noopener" target="_blank">#Aftermarket</a>-<a href="https://infosec.space/tags/ROMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ROMs</a> like <a href="https://fosstodon.org/@LineageOS" class="u-url mention" rel="nofollow noopener" target="_blank">@LineageOS</a> to support them when the manufacturer decides not to.<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">#consumers</a> wouldn't be at the mercy of a <a href="https://infosec.space/tags/vendor" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendor</a> when it comes to <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>!</li></ul>

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> <a href="https://muenchen.social/@thomas" class="u-url mention" rel="nofollow noopener" target="_blank">@thomas</a> <a href="https://chaos.social/@wonka" class="u-url mention" rel="nofollow noopener" target="_blank">@wonka</a> OFC <a href="https://infosec.space/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> abuses it to enforce their <a href="https://infosec.space/tags/monopoly" class="mention hashtag" rel="nofollow noopener" target="_blank">#monopoly</a> and choke alternative ROMs to death with this anti-feature <a href="https://infosec.space/tags/DRM" class="mention hashtag" rel="nofollow noopener" target="_blank">#DRM</a>.<ul><li>Granted <a href="https://ec.social-network.europa.eu/@EUCommission" class="u-url mention" rel="nofollow noopener" target="_blank">@EUCommission</a> & other <a href="https://infosec.space/tags/Watchdogs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Watchdogs</a> propably neither understand nor care about the seriousness of this issue...</li></ul>It's obvious <a href="https://infosec.space/tags/GrapheneOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#GrapheneOS</a>' devs rather refuse to support hardware than to do concessions in terms of <a href="https://infosec.space/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a>...<ul><li>But besides that I think that any decently maintained <a href="https://infosec.space/tags/Android" class="mention hashtag" rel="nofollow noopener" target="_blank">#Android</a> distro like <a href="https://infosec.space/tags/LineageOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#LineageOS</a> should be accepted when <a href="https://infosec.space/tags/unmaintained" class="mention hashtag" rel="nofollow noopener" target="_blank">#unmaintained</a> & <a href="https://infosec.space/tags/abandoned" class="mention hashtag" rel="nofollow noopener" target="_blank">#abandoned</a>-after-release <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a> producers like <a href="https://infosec.space/tags/Wiko" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wiko</a> and <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a> get past that <a href="https://infosec.space/tags/PlayIntegrity" class="mention hashtag" rel="nofollow noopener" target="_blank">#PlayIntegrity</a> check, which are the ultimate evidence pieces that "<a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>" isn't even a <a href="https://infosec.space/tags/figleaf" class="mention hashtag" rel="nofollow noopener" target="_blank">#figleaf</a> in this discussion!</li></ul>As <a href="https://chaos.social/@uint8_t" class="u-url mention" rel="nofollow noopener" target="_blank">@uint8_t</a> <a href="https://chaos.social/@uint8_t/112879917271144775" rel="nofollow noopener" target="_blank">said</a>: it's <a href="https://infosec.space/tags/SecurityTheater" class="mention hashtag" rel="nofollow noopener" target="_blank">#SecurityTheater</a> and has nothing to do woth either <a href="https://infosec.space/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> nor <a href="https://infosec.space/tags/integrity" class="mention hashtag" rel="nofollow noopener" target="_blank">#integrity</a>!

Kevin Karhan :verified:<a href="https://chaos.social/@uint8_t" class="u-url mention" rel="nofollow noopener" target="_blank">@uint8_t</a> <a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> exactly that...Even "manufactured <a href="https://infosec.space/tags/eWaste" class="mention hashtag" rel="nofollow noopener" target="_blank">#eWaste</a>" that never gets Updates like the <a href="https://infosec.space/tags/SOYES" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOYES</a> XS13, <a href="https://infosec.space/tags/Wiko" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wiko</a> Lenny and <a href="https://infosec.space/tags/Unihertz" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unihertz</a>, <a href="https://infosec.space/tags/Ulefone" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ulefone</a>, ... garbage brands have it.

SCDH MünsterDas nächste Treffen der AG <a href="https://fedihum.org/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a> findet am 21.3. von 12-13 Uhr über Zoom statt. Thema ist strategische <a href="https://fedihum.org/tags/Wissenschaftskommunikation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wissenschaftskommunikation</a> in den <a href="https://fedihum.org/tags/DH" class="mention hashtag" rel="nofollow noopener" target="_blank">#DH</a> mit Mareike Schumacher.Interessierte sind herzlich eingeladen!Mehr Informationen (u.a. die Zugangsdaten): <a href="https://www.uni-muenster.de/DH/blog/?p=407" rel="nofollow noopener" target="_blank">https://www.uni-muenster.de/DH/blog/?p=407</a>

SCDH MünsterNicht vergessen! Am 21.2. von 12-13 Uhr findet das nächste Treffen der AG <a href="https://fedihum.org/tags/WiKo" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiKo</a> über Zoom statt. Thema sind vektorbasierte <a href="https://fedihum.org/tags/Illustrationen" class="mention hashtag" rel="nofollow noopener" target="_blank">#Illustrationen</a>. Interessierte sind herzlich eingeladen! Mehr Informationen (u.a. über die Zugangsdaten) auf unserem Blog: <a href="https://www.uni-muenster.de/DH/blog/?p=407" rel="nofollow noopener" target="_blank">https://www.uni-muenster.de/DH/blog/?p=407</a>

Recent searches

Search options

Administered by:

Server stats:

#wiko