Sebastian Krzyszkowiak @dos@librem.one

@janvlug There's a spare bootloader in NOR you can access by holding AUX while powering it on; provided that it actually gets power. I don't remember if it's able to boot with no battery though, so if the battery is dead you may have to kickstart it first (you can use standard Nokia BL-5C or BL-6C batteries to boot and swap afterwards).

@christian It was my main and only phone for a few years. It was suuuuper sloooow and you could switch WiFi modes between "unstable" and "power hungry", but it worked well as a phone for me.

@christian I wonder - which OS have you used on it? I think my one was from one of the earliest batches and still shipped with Om2007.2. Later ones shipped with Om2008 which I never switched to as I didn't like it at all; I kept using Om2007.2 until FSO and SHR came around. Maybe it wasn't the most reliable thing I've ever used, but it wasn't really unreliable either - everything worked fine if you treated it well ;)

@blindcoder I couldn't even solder two wires together back then, but gave it to a friend who did the rework for me. IIRC it was just a matter of placing a capacitor and some bodge wires, so not that hard after all - I think that was actually the easiest one to perform out of fixes for GPS, buzz and #1024 (thankfully I was never really affected by the last one, and GPS had software workaround). Later units had all those applied right from the factory.

@blindcoder Voice quality was fine after fixing the buzz and enabling echo cancellation! Judging from message list I've used it as a main phone up until Sep 2014 (although not continuously, pretty sure I've been using N900 for some time meanwhile too).

This month 15 years have passed since I've received my Openmoko Neo FreeRunner, which started my personal adventure with mobile GNU/Linux 😊

I remember wondering back in 2008 whether I should invest myself and my money in Openmoko or Android as both were at their infancy and looking interesting. In hindsight, even though Openmoko does not exist anymore, I'm convinced that I've made the right choice!
#openmoko #mobile #linux #gnu #phone #smartphone #shr #linuxmobile #mobilelinux #linuxsmartphones

@Lumpbucket Most importantly, do it on Android (if you use it).

Same thing in static form 😺 #librem5

Me: Is a photo taken with a phone a representation of what its camera saw or what its software believed to be there? 😼
Dyzio:

#catsofmastodon #shotonlibrem5 #darktable late #caturday #mobile #photography

@gamingonlinux I even see *developers* having that expectation when presented with complex systems.

@ptrc potrójna ściana ognia

@aeva It's true! Just browse itch.io and you'll quickly stumble upon them all 😁

@mcc @passcod Not exactly; it only updates remote-tracking branches, and there are no remote-tracking tags to update. So after `git fetch origin main` you would have it in `origin/main`, not in `main`.

I rarely use pull in git myself, I usually fetch and then decide what to do (merge, rebase or do nothing if not needed). Fetching tags has some special logic meant to make things simpler, but this sure can make things confusing too, especially when 99% of what you explicitly fetch are branches 🤪

@mcc @passcod You can specify the local ref to write to by using `:` notation, just like with git push. In general fetch doesn't touch local refs unless told to (though tags are a bit special, but not in this specific case).

@passcod @mcc Fetching branches works the exact same way.