ruff @ruff@librem.one

@dnkl @mntmn Thanks for reminding, I don't use helpers but rather clone+makepkg when needed, but this might be one of those cases :)

@mntmn
```
# pacman -Su foot
Fehler: Ziel nicht gefunden: foot
```
:(

@geary@floss.social someone who builds from source when need to test various features not in the packaged build. So my build will always be specific. but my expectations normally is if i don't provide any options (only defaults) I'd get so called vanilla build.

@geary@floss.social well then I don't quite understand the problem statement in the OP. To me it looks consistent and right - by default continuity is maintained, if someone wants to jump ahead - he should explicitly ask for that.

@geary@floss.social I meant packagers (or rather packaging scripts) for general public. If they are not providing build profile in majority - would still make sense to default to stable and drop a line in INSTALL about development to likely prefer development profile instead of default stable. So from developer perspective I'm fine to explicitly ask for bleeding edge and build package-like release otherwise.

@geary@floss.social well, ok if choosing dev profile is undesirable for general public then shouldn't it default to stable, and then when someone needs _something specific_ like a dev profile, they provide options?

@geary@floss.social to me it looks counter-intuitive to provide options to do _something_. Usually options are required to do _something specific_ which is different from mere _something_

@geary@floss.social Please, don't. Is it possible just to create versioned DB for each schema version and then execute migration script which will find latest previous one and copy the data over?

@purism s/piece of mind/peace of mind/

@kyle while we were (are) frantically jumping out of the fear of 1984 boiling waters we're steadily accepting the raising temperature in the broth of the brand new world

@geary@floss.social "Geary also saves *on your device* sender and recipient email addresses *on your device*" - excessive "on your device"

@Goffi @byron @debacle @0 In XMPP encryption/authentication is always a policy decision, not protocol. So up to you to enforce TLS by not exposing any features except starttls on cleartext stream.
In general Collabora invested quite a lot of effort into that for OLPC (http://wiki.laptop.org/go/Activity_sharing, http://wiki.laptop.org/go/Telepathy_Salut) but it's abandoned since 2010 either.

@mntmn Wow! Sounds cheesy, congrats!

@dos absolutely, I have it as well for app development and it fits the purpose perfectly well (can even build many projects right on it). The reply was exactly to ridicule the meme.

@dos Nah did you try it on almost similarly specced but 5 times cheaper PinePhone? Oh wait...

@kyle figured it long ago on my own experience in Ingress game which is able to pick the location unless you really turn it off and spoof location. Stopped using it afterwards.

@lwriemen yes but the goal is not to find everyone infected, but to track the trend. You test 10 people and have 1 case so you have 10% ratio, you test 100 and has 10 cases so you still have 10% ratio, you test 1000 and have 177 - now you have 17% and raising trend.

@milo @lunduke
sorry what is the AT command to show the speed?

@lunduke does RaspberryPI v1.2 B count as retro-computing or it is limited strictly to 8-16bit platforms 16-32 years old?

@kyle while I'm open-source developer I want to note - when we speak of proprietary we mostly speak of 'technology', 'protocol' or 'product', not the code. Proprietary code is never in discussion as everyone knows how it's done.