Sebastian Krzyszkowiak @dos@librem.one

@wolnoscwkieszeni Ale dystrybucji na smartfony to już nie wymienia :(

@74 @alekajiya @deep @polamatysiak Nie wiem co myśleć o tym artykule, nie rozumiem motywacji za nim. Wypisuje pytania, często tendencyjne, no ale ok, jako "potencjalne argumenty, jakie będą podejmować przeciwnicy rozwiązań" ma to pewien sens. Tylko, że... nic się z tymi pytaniami potem nie dzieje? Ot tak wypisane w powietrze, by "ktoś" się nimi zajął? Do tego ogólne niezrozumienie czym i po co jest interpelacja poselska, a na końcu w update w ogóle wjeżdża syndrom oblężonej twierdzy na pełnej 🤨

@ihor Jeśli zaczniemy się zastanawiać nad drugą dopiero po zbudowaniu pierwszej to będzie słabo.

@bhyoram @chesterdott @opensourceopenmind Current versions of Firefox fall back to software WebRender because of lack of GLES3 and that shows. It used to be faster and is going to be again once etnaviv gets there.

@chesterdott @bhyoram @opensourceopenmind That said, I'm in the EU too (PL) - and while backing it was pricey indeed, it was not so bad after all considering that several years later I'm still not even looking for a replacement 😁

@chesterdott @bhyoram @opensourceopenmind Ultimately it all boils down to your own individual needs and capabilities. My bank's app works fine in Waydroid and lets me do all the stuff I need in it. The browser's still fast enough IME for the most part, though the Web getting heavier with time is a constant fact of life. I can deal with its battery life too. It serves all my needs as my daily driver - but that's me. Other people's needs are different and you have to do your own research.

@chesterdott @bhyoram @opensourceopenmind In my experience it's usually just a matter of setting the right user-agent string. It's hard to find one that works well everywhere, but with Epiphany you can change it per webapp so it's not a big deal (well, at least not for me 😂)

@opensourceopenmind @chesterdott I think the regular Librem 5 gives a bit better bang for the buck 😁 That's what I'm using and I'm still happy with it.

@agx Not today 😄

But sooner than later I think!

whooosh
#phosh #phoc #mobilelinux #linuxmobile

@hardpenguin13 Because people let them. Who cares if your solution is lazy and vastly overreaching if you can just get away with it?

@pocketvj Just some basic lens corrections, de-noising etc. gets you 90% there.

See https://social.librem.one/@dos/112408330992738904, https://social.librem.one/@dos/112988326413463557 and lots of my other photos here tagged as #shotonlibrem5

@mkljczk @janeq @m0bi @dzokero ...i Twitter, i Blip, i identi.ca... (w trochę inny sposób, ale miały)

@janeq @m0bi @dzokero Facebook miał kiedyś bramkę pozwalającą zalogować się do niego klientem XMPP, ale nie było tam nigdy żadnej federacji. Nazywanie tego serwerem XMPP to jednak trochę semantyczne nadużycie; to zupełnie inny przypadek niż Google Talk.

@bananarama @hacks4pancakes @simonmicro It can make things worse if you expose HCI over UART and don't expect it to effectively give access to device's memory.
That seems like a very niche case though.

@rolenthedeep @millihertz Not even over Bluetooth, but over Bluetooth's HCI - so actually over UART and only if you happen to expose HCI there...

@nelson If you use these to exploit other devices, then sure - just like you can with monitor mode and packet injection on a Wi-Fi card that allows you to do it.

Of course you could always use other tools to do the same thing, but probably not as cheap as ESP32.

@nelson Worth adding that the same thing could have been achieved by writing a free replacement for the blob, like it's already happening for ESP32's Wi-Fi: https://esp32-open-mac.be/

@nelson Define "against".

The binary blob has features that let you do more than the official API does.

If your code exposes these capabilities outside, you're in for a nasty surprise, as you may have not factored these capabilities into your threat model. Otherwise - nothing changes; there are features there that you never used cause you didn't know about them, and they still remain unused in your code.

But now that you know about them, you may want to use them creatively in your projects :)

@nelson There's a news story about "undocumented backdoor found in Bluetooth chip used by a billion devices" which turns out to be bunch of undocumented debugging commands accessible over HCI interface as implemented by the binary blob that's used to interface with ESP32's Bluetooth peripheral.

Which is a bad news for you if you exposed that HCI interface into untrusted contexts for some reason, I guess? Otherwise this development is actually empowering the users.