Sebastian Krzyszkowiak @dos@librem.one

The power of desktop #Firefox in your pocket with the #Librem5 https://puri.sm/posts/desktop-firefox-in-your-pocket-with-the-librem-5/ #mozilla #Linux #GNOME #PureOS #phosh #freeyourphone

#phosh 0.2.0 got released:

https://source.puri.sm/Librem5/phosh/-/tags/v0.2.0

featuring first quick settings (for battery, rotation and feedback), proximity sensor support and more ground work for better notifications and translation updates.

#librem5 @purism #gtk #wayland

Julian's quick setting work landed on #phosh master (#librem5 @purism):

What is Mobile #PureOS? A walk through of what is included in PureOS, the default #GNU/#Linux distribution installed on the #Purism #Librem5 https://puri.sm/posts/what-is-mobile-pureos/ written by our @dos

The next merge request will make #phosh cross the 1000 commit boundary:

```
$ git log --pretty=oneline | wc -l
999
```

Multiple GTK apps open in the same environment and all fitting nice in the screen.
Thank you #libhandy

After adding proximity sensor-support to #iio-sensor-proxy (https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/merge_requests/298) and adding runtime-pm support for the chip used in the #librem5 (and it's devkit) (https://lore.kernel.org/linux-iio/cover.1580721204.git.agx@sigxcpu.org/) we can now wire it up to #phosh to fade the screen and prevent keyboard input:

A lot of people are confused by git. Most of these people, I reckon, learned it from the outside in - from the command-line interface down. If you started with git by asking "how do I sync up my changes with my peers", then you might get the answer, but you will be missing the foundation on which that answer is built. This is the main source of confusion with git.

The better way is to learn git from the inside out. You should first learn about what objects are and how they're stored and identified, and how they relate to each other. You should learn what blobs, trees, and commits actually are, and how they relate to each other, and how commits form a linked list from which a graph of all objects can be derived.

Then you should learn how the ref database gives friendly names like "master" and "feature/foobar" to objects, and how the reflog tracks changes to references over time.

THEN, and only then, should you learn how to use the CLI. Then you can learn about using the staging area to add objects to the database and create commits, and how doing this updates the reflog.

Git makes total sense when you approach it from this angle. Supposedly hard tools like git rebase are totally understandable when you view them with the appropriate foundational knowledge.

Git is a tool which you will reach for hundreds of times a day, every day, for your entire career. Maybe it's worth learning about properly.