toad.social

Kevin Karhan :verified:<a href="https://infosec.exchange/@cesarpose" class="u-url mention" rel="nofollow noopener" target="_blank">@cesarpose</a> <a href="https://mastodon.social/@mrmasterkeyboard" class="u-url mention" rel="nofollow noopener" target="_blank">@mrmasterkeyboard</a> depends on the model and <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> has something more sinister:<ul><li>In many <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProBook</a>|s they literally do a "soft" <a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> re <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a>, so if the stick's ain't hp-branded (as per SPD-EEPROM) the <a href="https://infosec.space/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#UEFI</a> will brick <a href="https://infosec.space/tags/UnattendedBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnattendedBoot</a>, <a href="https://infosec.space/tags/UnattendedReboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#UnattendedReboot</a> & <a href="https://infosec.space/tags/PXEboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXEboot</a> by popping up an error message every boot that needs to be dismissed by hitting F1 on the internal keyboard (!!!) and can't be dismissed permanently.</li></ul>I literally had this with a client in the past and it's the reason a <a href="https://infosec.space/tags/refurbisher" class="mention hashtag" rel="nofollow noopener" target="_blank">#refurbisher</a> I know didn't offer RAM-<a href="https://infosec.space/tags/Upgrades" class="mention hashtag" rel="nofollow noopener" target="_blank">#Upgrades</a> for HP machines at all…

Jan Vlug<a href="https://mastodon.nl/@bert_hubert" class="u-url mention" rel="nofollow noopener" target="_blank">@bert_hubert</a> Wat ik fascinerend vind is dat het nu alleen maar gaat over Amerikaanse providers versus Europese aanbieders. Vrije <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>-software wordt in het hele artikel niet genoemd. Ik heb moeite met het in machtsblokken / unies denken. Wat mij betreft zou de focus op <a href="https://mastodon.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> en <a href="https://mastodon.social/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> moeten liggen. Dan heb je pas <a href="https://mastodon.social/tags/DigtaleSoevereiniteit" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigtaleSoevereiniteit</a> en <a href="https://mastodon.social/tags/DigitaleAutonomie" class="mention hashtag" rel="nofollow noopener" target="_blank">#DigitaleAutonomie</a>. Veel <a href="https://mastodon.social/tags/gemeenten" class="mention hashtag" rel="nofollow noopener" target="_blank">#gemeenten</a> hebben nu bijvoorbeeld ook een <a href="https://mastodon.social/tags/vendorlock" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendorlock</a> bij het Nederlandse <a href="https://mastodon.social/tags/Centric" class="mention hashtag" rel="nofollow noopener" target="_blank">#Centric</a>. Dat is net zo problematisch.

Alexey SkobkinRegarding latest changes in Bambu Lab firmware:<a href="https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/" rel="nofollow noopener" translate="no" target="_blank">https://blog.bambulab.com/firmware-update-introducing-new-authorization-control-system-2/</a>Here's my complaint ticket to them with small changes removing some personal information.> Hi. > > I'm writing you to let you know that I'm disappointed by recent changes in the firmware for your printers. > > This change doesn't affect what I am **currently** doing as a beginner 3D printing enthusiast. But I'm also advocating for ability to self-host automations and other stuff. I was also planning to check out possibilities of automation of my printer via self-hosted smart home solutions and using my printer without cloud. > These changes indicate that the company moves in the direction I can't personally approve and support. > > When I was buying your product, I disliked that your firmware is proprietary and very cloud-oriented. But since you were advertising LAN-only mode, I decided to still try. I really liked the quality of your product. But if you're now moving in the direction of making usage of LAN mode and external tools less convenient, I personally will avoid buying your products in the future. > > I own an A1 and was thinking of buying P1S. But now I'm going to reconsider my choice if I don't see any changes. > I was also planning to record an episode of my podcast to talk about 3D printing also recommending your products to beginners. But I'm going to reconsider that too unless something changes in a good way. > > This is not an ultimatum of any kind. It's just an honest feedback from your customer who was very glad with his purchase just yesterday and now thinks that he probably made a mistake. > > P.S. In my personal opinion, all restricting changes should be completely Opt-In so my printer won't force me to have "a better security" at the cost of my ability to use it as I want to. I was calling you "Apple of 3D printers, but in a good way" when talking with my peers. Now last part is probably going to change to "in a bad way". And I'm not an Apple user. > > Thank you for your time.Now I'll be waiting for their response when they return from Chinese New Year holidays.P.S. If you own a Bambu Lab printer and doesn't approve those changes, I recommend writing them ticket too.<a href="https://lor.sh/tags/Bambu" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bambu</a> <a href="https://lor.sh/tags/3D" class="mention hashtag" rel="nofollow noopener" target="_blank">#3D</a> <a href="https://lor.sh/tags/printing" class="mention hashtag" rel="nofollow noopener" target="_blank">#printing</a> <a href="https://lor.sh/tags/DIY" class="mention hashtag" rel="nofollow noopener" target="_blank">#DIY</a> <a href="https://lor.sh/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#firmware</a> <a href="https://lor.sh/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a> <a href="https://lor.sh/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> <a href="https://lor.sh/tags/log" class="mention hashtag" rel="nofollow noopener" target="_blank">#log</a> <a href="https://lor.sh/tags/quotes" class="mention hashtag" rel="nofollow noopener" target="_blank">#quotes</a> <a href="https://lor.sh/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#support</a> <a href="https://lor.sh/tags/cloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#cloud</a>

Kevin Karhan :verified:<a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> Q: Aside from asymetric / non-exponential modules, have you tested 64GB & 128GB sticks?<ul><li>Cuz Ideally I'd have 128-256GB on a <a href="https://infosec.space/tags/Framework13" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framework13</a>... </li></ul>I guess I've to check your <a href="https://infosec.space/tags/QVL" class="mention hashtag" rel="nofollow noopener" target="_blank">#QVL</a> then...<ul><li>Jist please don't pull a <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProBook</a> and "<a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a>" <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a> Sticks!</li></ul>

Kevin Karhan :verified:<a href="https://kitty.haus/users/lamp" class="u-url mention" rel="nofollow noopener" target="_blank">@lamp</a> I mean in terms of reliability.<ul><li>I had cheap 3rd party RAM be unstable on me even at it's designated ratings...</li></ul>Since then I'd rather pay a few cents more to get something more stable.<ul><li>But that's just bias from past experiences...</li></ul>Tho I wounder if one could easily reflash the SPD-EEPROM on those cheaper sticks to circumvent <a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a>|s from like <a href="https://infosec.space/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProBook</a>|s that will complain and demand to have F1 pressed every bootup when non-HP-branded sticks are installed!

Kevin Karhan :verified:<a href="https://sfba.social/@mvilain" class="u-url mention" rel="nofollow noopener" target="_blank">@mvilain</a> <a href="https://mastodon.social/@dangillmor" class="u-url mention" rel="nofollow noopener" target="_blank">@dangillmor</a> <a href="https://mamot.fr/@pluralistic" class="u-url mention" rel="nofollow noopener" target="_blank">@pluralistic</a> yeah...The only reason I still have my DeskJet 6122 hooked up is because that lil shit refuses to die!<ul><li>Like its glycol ink refuses to clog and it's easy to refill and reset the cartridges...</li><li>Otherwise I would've already replaced it with a WorkCentre multifunction laser...</li></ul>Worse are their <a href="https://infosec.space/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProBook</a> line of <a href="https://infosec.space/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptops</a>: They literally "Soft-<a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a>" their <a href="https://infosec.space/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a> to <a href="https://infosec.space/tags/HP" class="mention hashtag" rel="nofollow noopener" target="_blank">#HP</a>-branded sticks, bricking <a href="https://infosec.space/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXE</a>-boot and requiring people to manually press F1 on the device keyboard EVERY SINGLE BOOTUP / REBOOT with <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> messages.<ul><li>Unlike with like <a href="https://infosec.space/tags/WiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#WiFi</a> and <a href="https://infosec.space/tags/WWAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWAN</a> chips where one can figleaf argue that those need allow-listing for "spectrum regulatory compliance", this doesn't apply to RAM!</li></ul>On the flipside I use a bunch of <a href="https://infosec.space/tags/fanless" class="mention hashtag" rel="nofollow noopener" target="_blank">#fanless</a> hp <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThinClient</a>|s as <a href="https://infosec.space/tags/MiniServers" class="mention hashtag" rel="nofollow noopener" target="_blank">#MiniServers</a>, but that's because in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> <a href="https://infosec.space/tags/electricity" class="mention hashtag" rel="nofollow noopener" target="_blank">#electricity</a> is absurdly expensive and for just doing <a href="https://infosec.space/tags/backups" class="mention hashtag" rel="nofollow noopener" target="_blank">#backups</a> and <a href="https://infosec.space/tags/MediaSharing" class="mention hashtag" rel="nofollow noopener" target="_blank">#MediaSharing</a> doesn't draw much power...

Fab :verifiedpurple:<rant> Ok, it seems to me to be more and more difficult to buy ebooks. Wiley ? You endup needed a dedicated software (vitalsource), Oreilly ? You need a subscription and the oreilly app. Amazon ? Kindle.And for people without macOS, Windows, or a Kindle, forget it.Yes, I'm aware of DRM free ebooks, but sometimes you need or want a specific book which is DRM protected. </rant><a href="https://infosec.exchange/tags/ebooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#ebooks</a> <a href="https://infosec.exchange/tags/vendorlock" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendorlock</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@xdydx" class="u-url mention" rel="nofollow noopener" target="_blank">@xdydx</a> <a href="https://infosec.space/@CppGuy" class="u-url mention" rel="nofollow noopener" target="_blank">@CppGuy</a> <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> my only complaint re: <a href="https://linuxrocks.online/@tuxedocomputers" class="u-url mention" rel="nofollow noopener" target="_blank">@tuxedocomputers</a> is that they went out of their way to <a href="https://infosec.space/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> their <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> tools so that they don't run on other <a href="https://infosec.space/tags/Clevo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Clevo</a> barebones...<a href="https://infosec.space/@kkarhan/112836454805825342" translate="no" rel="nofollow noopener" target="_blank">https://infosec.space/@kkarhan/112836454805825342</a>

Kevin Karhan :verified:<a href="https://as200950.social/@stanford" class="u-url mention" rel="nofollow noopener" target="_blank">@stanford</a> yeah, that's what I know for like a decade...Also it's not a simple <a href="https://mstdn.social/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> but a <a href="https://mstdn.social/tags/Whitelist" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whitelist</a> of PCI-IDs, MAC Adress- and IMEI Number Ranges, so it's not enough to have i.e. a <a href="https://mstdn.social/tags/Lenovo" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lenovo</a>-rebranded <a href="https://mstdn.social/tags/Fibocom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fibocom</a> <a href="https://mstdn.social/tags/850GL" class="mention hashtag" rel="nofollow noopener" target="_blank">#850GL</a> which is a rebadged <a href="https://mstdn.social/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://mstdn.social/tags/XMM7360" class="mention hashtag" rel="nofollow noopener" target="_blank">#XMM7360</a>, but only the version offered for i.e. the <a href="https://mstdn.social/tags/ThinkPad" class="mention hashtag" rel="nofollow noopener" target="_blank">#ThinkPad</a> <a href="https://mstdn.social/tags/P15v" class="mention hashtag" rel="nofollow noopener" target="_blank">#P15v</a> will be accepted and initialized.<a href="https://mstdn.social/@kkarhan/111431218976786632" rel="nofollow noopener" translate="no" target="_blank">https://mstdn.social/@kkarhan/111431218976786632</a>

Kevin Karhan :verified:<a href="https://mstdn.social/@anarresti" class="u-url mention" rel="nofollow noopener" target="_blank">@anarresti</a> <a href="https://social.weho.st/@Fairphone" class="u-url mention" rel="nofollow noopener" target="_blank">@Fairphone</a> <a href="https://fosstodon.org/@frameworkcomputer" class="u-url mention" rel="nofollow noopener" target="_blank">@frameworkcomputer</a> Bzgl.<a href="https://mstdn.social/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> bin ich nicht gut zu sprechen weil die <a href="https://mstdn.social/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> mitels 'softem' "<a href="https://mstdn.social/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a>" auf <a href="https://mstdn.social/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a> machen:Wenn das RAM nicht hp-branded ist brickt es <a href="https://mstdn.social/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXE</a>-Boot und automatische Starts und wirft bei JEDEM (!!!) [Re-]Boot ne Bullshit-Fehlermeldung die stets manuell per F1 auf der Gerätetastatur ümnestätigt werden muss.Ich finde das ne absolute Gängelung und <a href="https://mstdn.social/tags/AntiRepair" class="mention hashtag" rel="nofollow noopener" target="_blank">#AntiRepair</a>-Maßnahme welche anders als z.B. Allowlistings für <a href="https://mstdn.social/tags/WLAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#WLAN</a> & <a href="https://mstdn.social/tags/WWAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWAN</a> keine valide Begründung hat!

derPUPEFirmen & Behörden, welche das Thema <a href="https://chaos.social/tags/Souver%C3%A4nit%C3%A4t" class="mention hashtag" rel="nofollow noopener" target="_blank">#Souveränität</a> mit <a href="https://chaos.social/tags/Mircosoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mircosoft</a> besprechen und das stolz auf <a href="https://chaos.social/tags/Linkedin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linkedin</a> posten.Ihr könnt Euch nicht vorstellen wie sehr das sucked, wenn man weiß wie viele davon schon längst in der <a href="https://chaos.social/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a>-Hodenpresse von MS sind.Ja der <a href="https://chaos.social/tags/azure" class="mention hashtag" rel="nofollow noopener" target="_blank">#azure</a> cloud stack ist super duper, aber von Unabhängigkeit zu sprechen, wenn eine <a href="https://chaos.social/tags/CIO" class="mention hashtag" rel="nofollow noopener" target="_blank">#CIO</a> damit erstmal begonnen hat ist mindestens putzig naive.

IzzyOnDroid ✅Oh wow: <a href="https://ec.europa.eu/commission/presscorner/detail/en/STATEMENT_23_3674" rel="nofollow noopener" target="_blank">https://ec.europa.eu/commission/presscorner/detail/en/STATEMENT_23_3674</a>No more enforced apps on your smartphone, no more lock-in to their services… That sounds nice! Now please, someone call the delivery service 🤩 <a href="https://floss.social/tags/vendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#vendorLock</a> <a href="https://floss.social/tags/systemApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemApps</a> <a href="https://floss.social/tags/softwareFreedom" class="mention hashtag" rel="nofollow noopener" target="_blank">#softwareFreedom</a>

Kevin Karhan :verified:Since <a href="https://mstdn.social/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a>'s devices are literally designed to be <a href="https://mstdn.social/tags/fragile" class="mention hashtag" rel="nofollow noopener" target="_blank">#fragile</a>, I do think it's safe to assume if not demand that having parts from a donor machine should allow one to fix an issue...Just like on any major brand laptop.Even <a href="https://mstdn.social/tags/hp" class="mention hashtag" rel="nofollow noopener" target="_blank">#hp</a> and it's <a href="https://mstdn.social/tags/ProBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProBook</a> <a href="https://mstdn.social/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptops</a> with their <a href="https://mstdn.social/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a>-based <a href="https://mstdn.social/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> for <a href="https://mstdn.social/tags/RAM" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a> that literally bricks <a href="https://mstdn.social/tags/PXE" class="mention hashtag" rel="nofollow noopener" target="_blank">#PXE</a> and remote/headless/timer-based booting don't literally lock up unbootable if you were to take a differen ProBook's RAM sticks, WIFI, WWAN, SSD, Keyboard, Screen.

The one with the headscarf 🧕Okay, the new FS Box very approved : After less than 30 seconds after unboxing, had my transceivers flashed.Finally 10 Gbit out of my proprietary modem thanks to <a href="https://alpaka.social/tags/VendorLock" class="mention hashtag" rel="nofollow noopener" target="_blank">#VendorLock</a> : Now spoofing Cisco.

Recent searches

Search options

Administered by:

Server stats:

#vendorlock