| 02:08.23 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 02:20.37 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 02:44.45 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 02:52.06 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 03:13.51 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 03:15.35 | *** join/#maemo ashley (ashley@MediaWiki/Jack-Phoenix) |
| 03:21.54 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 05:25.06 | *** join/#maemo keithzg (~keithzg@198-48-134-113.cpe.pppoe.ca) |
| 05:45.44 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 06:19.18 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 06:37.17 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 06:50.27 | KotCzarny | https://www.cnx-software.com/2021/02/02/mutantc-v3-open-hardware-diy-umpc-works-with-raspberry-pi-and-compatible-sbcs/ |
| 06:50.37 | KotCzarny | pop some 3g usb modem, and voila! |
| 06:57.47 | Maxdamantus | Why does QR code scanning suck so much? |
| 06:59.01 | Maxdamantus | Keep having trouble trying to scan the COVID tracer codes on the bus here using mBarcode, but it seems to work if I take a photo instead, then display the photo on a large screen at home and again use mBarcode to scan that. |
| 06:59.39 | Maxdamantus | mBarcode is unable to scan that exact photo. Neither is a recent version of `zbarimg` or `zxing`. |
| 07:00.26 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 07:00.40 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 07:03.22 | Maxdamantus | Example image: https://maxdamantus.eu.org/qrfail.jpg |
| 07:08.42 | KotCzarny | maybe photo app uses some smart algos to stabilize image |
| 07:08.55 | KotCzarny | while app isnt that good at it |
| 07:09.30 | Maxdamantus | Maybe, but mBarcode/zbarimg can't even find the QR code in the image produced by the photo app. |
| 07:10.19 | Maxdamantus | I suspect there's some colour correction that happens by showing the image again from an LCD. |
| 07:11.24 | Maxdamantus | maybe random values of individual pixels are throwing the algorithm off. |
| 07:14.44 | KotCzarny | make it b&w and check if it changes anything? |
| 07:18.12 | Maxdamantus | afaict zbar already converts it to greyscale. |
| 07:18.24 | KotCzarny | convert to 2 colors b&w |
| 07:19.55 | KotCzarny | anyway, might be too noisy for app |
| 07:20.23 | KotCzarny | try zooming before taking pic? |
| 07:20.49 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 07:21.39 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 07:22.39 | Maxdamantus | mBarcode doesn't seem to let you zoom. It's always zoomed in. |
| 07:23.34 | Maxdamantus | Will probably have to add some debugging to zbar to figure out what it's actually struggling on. |
| 07:24.04 | KotCzarny | too few pixels for the app to work on, i guess |
| 08:19.50 | *** join/#maemo phlixi (~phlixi@ppp-46-244-186-107.dynamic.mnet-online.de) |
| 08:20.24 | *** part/#maemo phlixi (~phlixi@ppp-46-244-186-107.dynamic.mnet-online.de) |
| 08:51.03 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 09:08.12 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 09:17.35 | *** join/#maemo jskarvad (~jskarvad@redhat/jskarvad) |
| 09:22.56 | *** join/#maemo pagurus (~user@i59F5F525.versanet.de) |
| 09:28.57 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 10:03.21 | *** join/#maemo auenf (~David@2001:8003:3703:c100:20d9:f875:4921:3e5a) |
| 10:04.33 | sicelo | nice to see a number of people still using N900 as daily :) |
| 10:05.39 | sicelo | Maxdamantus: the 'app' has a website? i'm trying to understand how you would use N900 here, assuming the barcode scanning would have worked |
| 10:09.33 | Maxdamantus | sicelo: the QR code represents some base64-encoded JSON which contains information identifying the location, including a unique "gln" number. |
| 10:10.11 | Maxdamantus | sicelo: and I figured out from the Android app the URL where hashes of glns with positive cases are published. |
| 10:10.28 | KotCzarny | sicelo: you can always write app yourself, that takes qr data from that site and redirect to proper url |
| 10:10.36 | KotCzarny | s/site/qr/ |
| 10:10.42 | Maxdamantus | so just have to log those entries along with timestamps, then occasionally poll that URL to see if I'm a close contact. |
| 10:11.19 | KotCzarny | the whole point of n900 is hackability |
| 10:11.24 | Maxdamantus | The app doesn't send data to a website. It just logs it locally and checks against the known cases as explained above. |
| 10:12.15 | Maxdamantus | It was simple enough creating an mBarcode plugin to just append that JSON and current timestamp to a log, and the checking part will also be easy. |
| 10:12.42 | sicelo | that's nice! *me likey |
| 10:15.20 | sicelo | the android device was using Android version less than 7 (or 8?)? I noticed that after 7 or 8, mitmproxy doesn't work to get API calls an Android app makes, since it seems those version enforce certificate pinning |
| 10:15.50 | sicelo | or there's newer/better way to get around that, which i don't yet know of :) |
| 10:16.35 | KotCzarny | squid + manually added cert ? |
| 10:16.54 | Maxdamantus | That will presumably have the same problem as mitmproxy. |
| 10:17.14 | Maxdamantus | Since it's still not using the pinned public key. |
| 10:25.04 | Maxdamantus | From what I understand of certificate pinning, pinning itself is probably a bad idea. |
| 10:25.27 | Maxdamantus | I suspect if they're doing something reasonable, it's probably just changing the set of trusted certificates. |
| 10:25.45 | Maxdamantus | ie, only trusting a particular certificate, or only trusting certificates with particular public keys. |
| 10:27.01 | Maxdamantus | "pinning" to me sounds like where a key is set by a protocol, rather than provided as part of the OS/application, just like any "trusted" certificates are provided. |
| 10:28.50 | Maxdamantus | The question is just whether you're able to add your own trusted certificate/key. If it's using Android's default trusted certificates, I suspect that's a yes because you can probably add your own CA cert to be trusted, but if it's bundling its own cert and only trusting that, you'd need to replace that bundled cert. |
| 10:35.56 | sicelo | i also don't remember the details now, but iirc the apps contain some cert for sure |
| 10:37.14 | Maxdamantus | Right, so it just trusts its own cert instead of the Android-provided certs. |
| 10:37.36 | Maxdamantus | (which imo is a reasonable thing to do sometimes) |
| 10:38.18 | KotCzarny | edit the binary to insert own cert? |
| 10:42.05 | sicelo | yes |
| 10:42.11 | sicelo | a bigger job :p |
| 10:45.21 | sicelo | if you have older android, and the app works there, that's the quickest way around it. a rooted device also can help (but my Sprint S7 is unrootable) |
| 12:33.11 | *** join/#maemo jon_y (~enforcer@2001:f40:91b::9f8e) |
| 13:23.45 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 13:35.21 | *** join/#maemo Vajb (~Vajb@2001:999:80:cf92:2d7a:cf36:251a:7348) |
| 13:35.55 | *** join/#maemo drathir_tor (~drathir@gateway/tor-sasl/drathir) |
| 15:09.37 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 15:14.40 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 15:16.25 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 15:36.17 | *** join/#maemo sunshavi (~user@190.42.230.123) |
| 15:37.08 | *** join/#maemo Vajb (~Vajb@2001:999:80:cf92:2d7a:cf36:251a:7348) |
| 15:59.37 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 16:14.51 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 16:31.33 | *** join/#maemo luke-jr (~luke-jr@unaffiliated/luke-jr) |
| 17:10.44 | *** join/#maemo Wizzup (~Wizzup@a82-161-36-93.adsl.xs4all.nl) |
| 17:44.39 | *** join/#maemo halftux (~pi@87.122.106.43) |
| 17:48.26 | halftux | juiceme: I found the association rules for maemo e.V. it is in our wiki http://wiki.maemo.org/MaemoCommunity_eV I forgot about it. There you could find the rules about voting, and also a regular agenda of a meeting it looks like the last meeting was in 2017 |
| 17:52.41 | sicelo | yeah :( |
| 17:53.09 | sicelo | nice to see you here btw - slight nitpick - why the html emails? |
| 17:55.45 | halftux | not all were html only the replies I think sorry for that |
| 17:58.21 | halftux | I think if we would like to keep this e.V. we should act fast... |
| 17:59.46 | sicelo | +1 |
| 18:07.50 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 18:22.52 | *** join/#maemo xmn (~xmn@cpe-72-225-198-203.nyc.res.rr.com) |
| 18:35.35 | halftux | sicelo: do you have a droid 4 (XT894)? |
| 18:42.27 | sicelo | yes :) |
| 18:44.52 | halftux | and leste running fine? I wasn't able to get this kexecboot running :( Tried also different fastboot version. You did the same procedure from wiki? |
| 18:47.53 | sicelo | yes it's working fine (although these days i'm playing more with plain debian+sway on my N900 instead) |
| 18:48.44 | sicelo | i used the same procedure. there's also #maemo-leste if you want to join. you'll get quicker help there |
| 18:49.46 | halftux | oh I see. Never tried sway. Which debian version? |
| 18:49.52 | sicelo | sid |
| 18:51.14 | sicelo | at what point do you get issues with the droid 4 procedure? |
| 18:52.29 | sicelo | i'll move to debian on the droid 4 at some point since it's better/faster hardware - i just did it on N900 just for fun initially -just to see if wayland would really run on it |
| 18:52.34 | halftux | it looks everything fine only that I get no sign that kexecboot kicks in and is booting from sdcard |
| 18:53.12 | halftux | so it boots everytime to android :( |
| 18:53.46 | sicelo | ok. but do you see the kexecboot menu? i guess from your comment, no |
| 18:54.06 | halftux | no |
| 18:55.31 | sicelo | so i think the uSD card is fine. your issue is somewhere with kexecboot. |
| 18:55.58 | halftux | fastboot reports no error but I have the feeling that the bootloader is not replaced and I flashed this allow-mbmloader before |
| 18:58.25 | sicelo | i did this procedure more than a year ago, so i have forgotten some stuff. but i would recommend joinig #maemo-leste. they'll help |
| 18:59.21 | halftux | When I have some time I will try it again and therefore I will join maemo-leste channel... |
| 18:59.35 | sicelo | cool :) |
| 18:59.53 | sicelo | leste runs really well on it (droid 4) |
| 19:00.43 | sicelo | there are still a few issues here and there, but some refer to it as the Leste 'flagship' |
| 19:00.49 | halftux | I can imagine and I would really like to tried it |
| 19:00.58 | halftux | try |
| 19:02.07 | sicelo | i actually wanted to port some of the programs you maintain for Fremantle, e.g. cutenews - then sway happened and i got distracted |
| 19:02.25 | halftux | for development it is also better to have different screen sizes. For the N900 I was so lasy that I everytime choosed a fixed resolution |
| 19:02.38 | sicelo | Leste uses Qt5, which is quite nice, since more s/w can run |
| 19:06.20 | halftux | yes I tried already things in VM and N900 with leste. I can also use there things which I developed in qt5 (widgets) for sailfish |
| 19:07.54 | sicelo | maybe you would like to upload them to the Leste repos as well - it's open access |
| 19:15.45 | halftux | I think qt5 package needs still some fine tuning for leste (last time I tried, already long ago), but it is really time consuming to fix/expand qt5, I have the feeling everytime when I have some time I start from the beginning to analyse the source code. I uploaded already one application to leste repos. When I got this droid 4 running I suppose more will follow. |
| 19:20.23 | sicelo | oh great! |
| 19:20.56 | sicelo | heh, i just tried running mutter/wayland on N900. working good it seems - of course it's not full-blown gnome |
| 20:09.52 | *** join/#maemo florian (~florian_k@Maemo/community/contributor/florian) |
| 21:55.48 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 22:14.58 | parazyd | halftux: You might get more support in #maemo-leste btw ;) |
| 22:36.40 | *** join/#maemo Vajb (~Vajb@hag-jnsbng11-58c3a3-146.dhcp.inet.fi) |
| 22:55.18 | *** join/#maemo lukedashjr (~luke-jr@unaffiliated/luke-jr) |
| 22:58.59 | *** join/#maemo lukedashjr (~luke-jr@unaffiliated/luke-jr) |
