| 00:03.24 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 00:04.14 | *** join/#maemo Agge (~Durand@ghs/durand) |
| 00:21.28 | ShadowJK | DocScrutinizer05; they're probably going to do it like Samsung does |
| 00:21.40 | ShadowJK | separate model for every country/area |
| 00:22.33 | ShadowJK | Samsung on top of that regionlocks to prevent devices meant for asia working in europe even if the frequency support was compatible |
| 00:24.02 | ShadowJK | They need TDD for china anyways :/ |
| 00:28.40 | *** join/#maemo xray256 (~xray256@149.241.43.82) |
| 00:30.27 | *** join/#maemo cyborg-o1e (~cyborg-on@85-238-116-212.broadband.tenet.odessa.ua) |
| 00:32.11 | *** join/#maemo eijk (~eijk@e178216126.adsl.alicedsl.de) |
| 00:43.39 | *** join/#maemo at1as (~at1as@kurios.r4780y.com) |
| 00:50.00 | *** join/#maemo amonk (~amonk@unaffiliated/amonk) |
| 01:02.33 | SpeedEvil | Happy 2014 everyone! |
| 01:02.54 | *** join/#maemo amonk (~amonk@unaffiliated/amonk) |
| 01:07.35 | *** join/#maemo amonk (~amonk@unaffiliated/amonk) |
| 01:30.56 | *** join/#maemo LaoLang_cool (~LaoLang_c@183.32.180.218) |
| 01:35.17 | ShadowJK | \o/ |
| 02:02.28 | *** join/#maemo triggerhappy (~quassel@112.209.21.95) |
| 02:09.56 | *** join/#maemo mschlens (~mschlens@p5DC161D3.dip0.t-ipconnect.de) |
| 02:11.02 | *** join/#maemo ccxN (~ccxCZ@156.200.broadband11.iol.cz) |
| 02:15.36 | *** join/#maemo Sazpaimon (wat@pool-173-49-22-36.phlapa.fios.verizon.net) |
| 02:18.55 | *** join/#maemo flo_lap (~fuchs@Maemo/community/contributor/florian) |
| 02:29.31 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 02:36.04 | *** join/#maemo Defiant (erik@g231164106.adsl.alicedsl.de) |
| 02:54.32 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 02:57.55 | *** join/#maemo ShadowJK (~jk@212.7.198.194) |
| 03:18.12 | *** join/#maemo FlameReaper (~assassin@115.132.66.166) |
| 03:32.19 | *** join/#maemo valerius (~user@185.3.35.169) |
| 03:32.35 | *** join/#maemo valeriusL (~valerius@185.3.35.169) |
| 03:36.06 | *** join/#maemo ced117 (~ced117@opensuse/member/ced117) |
| 04:06.48 | *** join/#maemo uen| (~uen@p5DCB1E4D.dip0.t-ipconnect.de) |
| 04:20.46 | *** join/#maemo Gh0sty (~ghosty@212.71.7.165) |
| 04:33.33 | *** join/#maemo maybeWTF (~cl@p5B162032.dip0.t-ipconnect.de) |
| 05:12.58 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0bd4f7.pool.mediaWays.net) |
| 06:59.27 | *** join/#maemo Ninja (~ninja@74.61.222.224) |
| 07:21.26 | *** join/#maemo hubutm20 (~hubutm20@79.113.84.182) |
| 07:54.13 | *** join/#maemo zammy (~zammy@ppp-105-144.98-62.inwind.it) |
| 08:05.07 | *** join/#maemo ZogG_laptop (~ZogG_lapt@109.64.169.161) |
| 08:05.07 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 08:11.27 | *** join/#maemo thedead1440_ (~thedead14@unaffiliated/thedead1440) |
| 08:16.28 | *** join/#maemo dhbiker (~dhbiker@APN-123-145-244-gprs.simobil.net) |
| 08:24.49 | *** join/#maemo Loke (~user@106.76.81.197) |
| 08:25.13 | Loke | hi |
| 08:27.41 | Loke | http://pastebin.com/hR7kRbXP getting error |
| 08:38.33 | *** join/#maemo Loke (~user@106.76.81.197) |
| 08:54.04 | DocScrutinizer05 | Loke: the preremove script fails since the jonh file etc isn't in /usr/bin but optification moved it to /opt/*/* and created a symlink |
| 09:04.33 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 09:09.44 | *** join/#maemo zammy (~sammy@ppp-105-144.98-62.inwind.it) |
| 09:12.20 | *** join/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 09:12.54 | *** part/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 09:14.37 | DocScrutinizer05 | ShadowJK: quite possible their OEM isn't offering anything different to this. But they _again_ created a communication MCA by "countries that Jolla can operate will get defined later" (OWTTE) and then "works on 6 continents"(OWTTE) and now the already anticipated fsckup re US UMTS |
| 09:15.53 | DocScrutinizer05 | honestly, Murphy cup in Platinum. It's incredible how they spot every single opportunity to screw up something |
| 09:16.40 | DocScrutinizer05 | particularly when that opportunity is faintly related to their communications policy |
| 09:23.07 | DocScrutinizer05 | poor devil tehdely will probably be locked in to his 900/2100 version, even when Qualcom/OEM eventually will flash a US version to the same snapdragon chipset, this version can't get flashed to devices already sold to customers, since Qualcom prefers to not allow distribution of that modem firmware |
| 09:23.55 | DocScrutinizer05 | (and of course the device would need new calibration when switchng it to other firmware/bands) |
| 09:25.16 | DocScrutinizer05 | it's pretty funny to see how the Jolla design in a strange way resembles OM Neo1973 |
| 09:26.01 | DocScrutinizer05 | only that Openmoko always provided debug board to flash new bootloader via JTAG, and properly documented how to do that |
| 09:28.17 | DocScrutinizer05 | well, actually meanwhile the basic system architecture regarding booting almost resembles Freerunner, with the auxiliary NOR-boot to recover from catastrophic damage of main bootloader by powering up while holding AUX button |
| 09:30.47 | *** join/#maemo Loke (~user@106.77.193.153) |
| 09:32.48 | Loke | hi doc |
| 09:40.25 | Loke | got it but how can I remove it |
| 09:49.38 | Loke | its killing me dude please help me |
| 10:05.51 | *** join/#maemo solofight (kvirc@115.242.180.126) |
| 10:15.38 | *** join/#maemo OkropNick (kuba@host-n2-75-80.telpol.net.pl) |
| 10:16.00 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 10:25.07 | DocScrutinizer05 | yay, (s)he's not very persistent, eh? |
| 10:28.27 | *** join/#maemo shentey (~shentey@g225075240.adsl.alicedsl.de) |
| 10:29.10 | DocScrutinizer05 | anyway, I also had a hard time to tell what's the best method to fix broken uninstall. Might install again, them de-optify the files (i.e. move back the files from /opt/ to the original location, thus nuking the symlinks), then maybe edit the .prerm in /var/*/dpk/*/<packagename> somewhere to fix any messup in there. Then uninstall again. But I'm pretty sure there's a hardcore method - maybe a parameter --force or sth - to make apt/dpkg " |
| 10:29.11 | DocScrutinizer05 | succeed" with uninstalling john |
| 10:29.35 | DocScrutinizer05 | ooh, and somebody might open a ticket against john: "doesn't uninstall" |
| 10:29.40 | DocScrutinizer05 | ~pkg |
| 10:29.40 | infobot | i guess pkg is http://maemo.org/packages/ |
| 10:35.36 | *** join/#maemo SAiF (~SAiF@117.213.57.6) |
| 10:36.29 | *** join/#maemo wotan147 (~max@224.223.25.93.rev.sfr.net) |
| 10:41.25 | *** join/#maemo sequantz (~sequantz@agbk223.neoplus.adsl.tpnet.pl) |
| 11:09.13 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 11:10.24 | *** join/#maemo Venemo (~Timur@fedora/Venemo) |
| 11:37.34 | *** join/#maemo robink (~quassel@unaffilated/robink) |
| 11:40.59 | *** join/#maemo NIN101 (~NIN@n900.quitesimple.org) |
| 11:59.40 | *** join/#maemo MohammadAG (~MohammadA@Maemo/community/contributor/MohammadAG) |
| 12:17.17 | *** join/#maemo MrPingu (~MrPingute@ip503c83e7.speed.planet.nl) |
| 12:47.26 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 12:50.48 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 12:55.23 | *** join/#maemo LauRoman (~LauRoman@5-14-90-40.residential.rdsnet.ro) |
| 13:01.42 | *** join/#maemo sunny_s (~sunny_s@business-092-079-020-027.static.arcor-ip.net) |
| 13:17.22 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0bd4f7.pool.mediaWays.net) |
| 13:29.05 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 13:30.31 | *** join/#maemo solofight (kvirc@101.63.167.139) |
| 13:31.24 | solofight | people, where can i find a material to learn how to use appmefo ? i installed it and created a folder and added all games into it but the folder is not visible on my menu and all games that i added are still lying outside on the main menu |
| 13:31.28 | solofight | dont know what i am missing |
| 13:36.50 | *** join/#maemo muellisoft (~muelli@port-32842.pppoe.wtnet.de) |
| 13:42.19 | *** join/#maemo cityLights (~nivw@bzq-218-29-26.cablep.bezeqint.net) |
| 13:45.07 | *** join/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 13:49.17 | *** join/#maemo dafox (~dafox@ip51cc571d.speed.planet.nl) |
| 13:50.48 | *** join/#maemo dos1 (~dos@unaffiliated/dos1) |
| 13:52.00 | *** join/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 14:04.57 | *** join/#maemo eijk (~eijk@e178216126.adsl.alicedsl.de) |
| 14:05.53 | *** join/#maemo arcean (~arcean@aacr222.neoplus.adsl.tpnet.pl) |
| 14:08.56 | DocScrutinizer05 | solofight: that sounds pretty starnge |
| 14:09.08 | DocScrutinizer05 | solofight: have you saved your setup in apmefo? |
| 14:09.46 | solofight | DocScrutinizer05: the mistake is mine - i saved but did not press the activate button |
| 14:09.53 | solofight | tried it and it worked |
| 14:10.03 | DocScrutinizer05 | solofight: open apmefo settings, create a folder, name and icon and all, store and quit |
| 14:10.06 | *** part/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 14:10.35 | solofight | one hard factor is that it did not create its own folders and put icons accordingly like cateroise does |
| 14:10.48 | solofight | we need to manually create all folders and its icons and then add apps |
| 14:10.56 | solofight | is that correct ? DocScrutinizer05 ? |
| 14:13.47 | DocScrutinizer05 | yes |
| 14:13.59 | DocScrutinizer05 | that's the feature of apmefo |
| 14:15.03 | DocScrutinizer05 | I discarded catorize after a week since I never could get used to the silly sorting that it automatically creates |
| 14:15.34 | DocScrutinizer05 | and back in that time at least, catorize didn't allow user to create own folders and sort apps to her liking |
| 14:16.39 | FIQ | catorize base its' sorting on HAM I think |
| 14:16.52 | solofight | DocScrutinizer05: yes "It did not allow me to customize" and thats the reason i ditch it |
| 14:16.53 | DocScrutinizer05 | solofight: just NEVER try to drag an icon on hildon applauncher dirextly |
| 14:17.04 | DocScrutinizer05 | FIQ: correct |
| 14:18.25 | DocScrutinizer05 | if you do nonetheless, you'll instantly lose all apmefo created submenus, and you have to start apmefo (possibly via cmdline) and hit activate again |
| 14:19.33 | DocScrutinizer05 | I wonder if eventually somebody could intergarte apmefo and Hildon Applauncher |
| 14:20.02 | DocScrutinizer05 | I.E. make apmefo a part of hildon-home or hildon-desktop or whatever |
| 14:20.07 | DocScrutinizer05 | for CSSU |
| 14:20.34 | FIQ | hildon applauncher? what's that? |
| 14:20.42 | DocScrutinizer05 | this would fix the "must not drag icons" issue |
| 14:21.03 | DocScrutinizer05 | FIQ: the way you start your apps on hildon? |
| 14:21.15 | FIQ | oh ok |
| 14:22.23 | DocScrutinizer05 | instead of "must not drag icons" you could then allow to drag icons to submenus even |
| 14:22.49 | DocScrutinizer05 | instead of doing that in generic apmefo interface |
| 14:23.52 | solofight | DocScrutinizer05: you mean do not drag an icon from the hildon app manager to a folder created using apmefo ? (like dragging chess icon from games folder) correct ? |
| 14:24.26 | DocScrutinizer05 | I mean "do not drag any icon, EVER, ANYWHERE" |
| 14:24.34 | DocScrutinizer05 | in applauncher |
| 14:25.40 | DocScrutinizer05 | you quite obviously can't drag an icon out of a subfolder since there's nothing to drag it to |
| 14:26.10 | solofight | so if i want to rearrange an icon within the hildon manager, how do i do i t? |
| 14:26.20 | DocScrutinizer05 | and you can't drag an icon into a submenu folder since hildon desktop/applauncher doesn't support that |
| 14:26.26 | FIQ | you don't @ solofight |
| 14:26.32 | DocScrutinizer05 | exactly |
| 14:26.38 | DocScrutinizer05 | you sue apmefo to do that |
| 14:26.45 | solofight | ohh |
| 14:27.10 | DocScrutinizer05 | use* |
| 14:27.16 | solofight | guess thats the tradeoff |
| 14:27.20 | FIQ | DocScrutinizer05: btw, can I still *access* the interface (and then leave it) without hurting apmefo? |
| 14:27.35 | DocScrutinizer05 | hmm? |
| 14:27.36 | FIQ | because when device starts up, there's slight lag |
| 14:27.43 | DocScrutinizer05 | which interface? what access? |
| 14:27.50 | FIQ | and I occasionally invoke that move thing accidentally |
| 14:28.06 | FIQ | the hold="give new place" thing |
| 14:28.16 | solofight | DocScrutinizer05: can i drag the icon in the desktop ? to arrange my widgets and stuff ? |
| 14:29.04 | DocScrutinizer05 | FIQ: I somehow disabled that on my device |
| 14:29.22 | FIQ | you can do that? |
| 14:29.25 | FIQ | TIL |
| 14:29.27 | FIQ | ...how |
| 14:29.50 | *** join/#maemo antithesis_ (~antithesi@82-168-60-132.ip.telfort.nl) |
| 14:32.17 | DocScrutinizer05 | I *guess* in tweakr |
| 14:32.28 | DocScrutinizer05 | or in CSSU settings |
| 14:32.28 | antithesis_ | Where can I get a list of devices that run on Maemo or something based on it? |
| 14:32.49 | DocScrutinizer05 | N900, N810, N800 |
| 14:32.56 | DocScrutinizer05 | here you are |
| 14:33.02 | DocScrutinizer05 | :-) |
| 14:33.19 | DocScrutinizer05 | well, some say N950, N9 |
| 14:33.20 | solofight | :P |
| 14:33.35 | DocScrutinizer05 | some disagree |
| 14:33.42 | antithesis_ | Why do some disagree on that? |
| 14:33.56 | DocScrutinizer05 | in my book HARM!=maemo |
| 14:34.15 | antithesis_ | HARM? |
| 14:34.18 | antithesis_ | Does it harm me? |
| 14:34.39 | DocScrutinizer05 | possibly |
| 14:34.48 | DocScrutinizer05 | it for sure harms *me* |
| 14:35.10 | FIQ | N770 too afaik |
| 14:35.30 | DocScrutinizer05 | i left that out since I guess pretty few of them exist and still work |
| 14:35.52 | FIQ | pretty sure the same case applies for N8x0 :p |
| 14:36.25 | antithesis_ | > N810, N800 |
| 14:36.28 | antithesis_ | Why do they always add 10 to it when there's an update? |
| 14:36.30 | antithesis_ | Same with Blackberry Torch 9800 / 9810 |
| 14:36.31 | DocScrutinizer05 | nah, I have two N810 here, one powered up and fine |
| 14:36.54 | FIQ | and the other? |
| 14:37.14 | DocScrutinizer05 | the other is pretty pristine |
| 14:37.59 | antithesis_ | DocScrutinizer05 what's so harmful about MeeGo? |
| 14:38.12 | DocScrutinizer05 | ~aegis |
| 14:38.13 | infobot | http://www.developer.nokia.com/Community/Wiki/Harmattan:Developer_Library/Developing_for_Harmattan/Harmattan_security/Security_guide , or "The purpose of this framework is: ... to make sure that the platform meets the requirements set by third party software that requires a safe execution environment.", or http://en.wikipedia.org/wiki/Trusted_Computing#Criticism, or http://en.qi-hardware.com/w/images/1/10/ME_382_LockedUpTechnology2.gif |
| 14:38.21 | DocScrutinizer05 | to start with |
| 14:38.57 | DocScrutinizer05 | and the "can't downgrade firmware" policy resulting from it |
| 14:39.07 | DocScrutinizer05 | ~malf |
| 14:39.07 | infobot | extra, extra, read all about it, malf is http://maemo.cloud-7.de/Aegis-kills-device.jpg |
| 14:39.37 | FIQ | it offers no real security and is mostly a roadblock to be able to do what you want |
| 14:40.03 | DocScrutinizer05 | yes |
| 14:40.25 | DocScrutinizer05 | and I hate devices with built-in self-destruct function |
| 14:41.08 | antithesis_ | Hmpf |
| 14:41.08 | DocScrutinizer05 | particularly when the trigger button is integrated into a random number of ordinary files that you mustn't touch |
| 14:41.29 | antithesis_ | As horrible as I find that, I can't live with a resistive touch screen |
| 14:41.29 | DocScrutinizer05 | ~may-i-edit |
| 14:41.30 | infobot | mayIedit () { grep "`basename $1`" /var/lib/aegis/refhashlist && echo "probably not" && return; echo "edit if you feel venturous"; } |
| 14:42.02 | antithesis_ | Should I expect the N9's touch screen to be as responsive as, say, that of a modern Samsung Galaxy? |
| 14:42.34 | antithesis_ | Or a slightly less modern one for that matter, like the Galaxy S I / II |
| 14:42.37 | DocScrutinizer05 | err, it's a capacitive touchscreen. I guess they all are pretty much the same |
| 14:42.50 | antithesis_ | Nah |
| 14:42.59 | antithesis_ | I ordered a chinkphone once and its screen was horrid |
| 14:43.04 | DocScrutinizer05 | they are, since I hate them all ;-P |
| 14:43.10 | antithesis_ | Yeah, same |
| 14:43.20 | antithesis_ | But there aren't really many options when it comes to keyboards |
| 14:43.38 | DocScrutinizer05 | huh? |
| 14:43.59 | antithesis_ | Too few smartphones have keyboards so I'll succumb |
| 14:44.20 | jaska | im the other way around, ill sooner stop using a phone than get a keyboardless phone. |
| 14:44.36 | FIQ | while technically true, it's not relevant to touch screen technology |
| 14:44.48 | FIQ | @ antithesis_ |
| 14:44.54 | DocScrutinizer05 | :nod: |
| 14:45.05 | ShadowJK | N810W was left from that list |
| 14:45.09 | DocScrutinizer05 | just was about to ask how touchscreen is related to kbd |
| 14:45.14 | FIQ | what's N810W |
| 14:45.16 | FIQ | ? |
| 14:45.21 | ShadowJK | I wonder how many of those were made, couldn't have been many |
| 14:45.23 | DocScrutinizer05 | that's a weird device |
| 14:45.25 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 14:45.25 | DocScrutinizer05 | and rare |
| 14:45.46 | ShadowJK | Though more than the 3D display N810 for sure :) |
| 14:45.48 | DocScrutinizer05 | N810 with errr, how's it called? |
| 14:45.51 | FIQ | (I was never around in N770-N810 days allthough I did consider a N810 back in the day) |
| 14:45.57 | DocScrutinizer05 | WAN? |
| 14:46.02 | jaska | wimax? |
| 14:46.06 | DocScrutinizer05 | wimax! |
| 14:46.08 | antithesis_ | jaska I'm kinda the same, actually. I sold my Chinkphone because it was too shitty, but just now I tried out some note-taking on my mom's Sony device and it was actually quite pleasant, better than I'd expected |
| 14:46.12 | FIQ | huh? |
| 14:46.16 | FIQ | what is this :D |
| 14:46.23 | FIQ | @ DocScrutinizer05 ShadowJK |
| 14:46.24 | jaska | i had to think hard to remember what was the name of that hypedup wlan/wwan tech :( |
| 14:46.28 | antithesis_ | So maybe it was just the touch screen on that one chinkphone that was so shit, not 'all touchscreens' |
| 14:46.31 | DocScrutinizer05 | glorified WiFi |
| 14:46.42 | antithesis_ | That being said, I never checked if it was because of the screen protected I'd placed over it or not |
| 14:46.44 | jaska | and to consider i was involved in some of that shit ages ago. |
| 14:46.54 | jaska | (wlan/wwan, not n810) |
| 14:46.59 | antithesis_ | I don't know, do screen protectors make the screens less responsive? |
| 14:47.09 | ShadowJK | I'd actually like if wifi used wimax type media access control |
| 14:47.24 | DocScrutinizer05 | screen protector on a capacitive touch? LOL! |
| 14:47.27 | ShadowJK | wifi more or less copies ethernet csma/cd |
| 14:48.04 | DocScrutinizer05 | cd? |
| 14:48.15 | DocScrutinizer05 | hardly ;-) |
| 14:48.27 | DocScrutinizer05 | well, RX side maybe |
| 14:48.33 | DocScrutinizer05 | not even that |
| 14:48.37 | antithesis_ | DocScrutinizer05 what's so funny about it? >_< |
| 14:48.39 | ShadowJK | So weak stations can hog the channel for ages.. wimax gives each station a time slot, when time is up next station gets the channel regardless if first got through any data or not |
| 14:49.30 | DocScrutinizer05 | antithesis_: c-ts and protectors don't go together well |
| 14:49.46 | DocScrutinizer05 | physics |
| 14:49.48 | FIQ | a couple of friends with jollas use them w/o issues afaik |
| 14:49.57 | FIQ | but I never tried myself |
| 14:50.11 | FIQ | since I don't own a device with capacitive ts |
| 14:50.11 | antithesis_ | Hm |
| 14:50.23 | antithesis_ | And all capacitative touch screens are on-par? |
| 14:50.29 | antithesis_ | with each other |
| 14:50.32 | DocScrutinizer05 | some protectors may have less negative impact than others, but all of them do no good to capacitive touch |
| 14:50.42 | ShadowJK | "Responsive touchscreen" is pretty complex topic really, because there's two sides to it. The delay between finger touching, and the electronics detecting it and passing it on to CPU, and the time it takes for CPU and OS to process it, and the time it takes to display something on screen |
| 14:51.03 | DocScrutinizer05 | antithesis_: for sure not, there are better and inferior controller chips |
| 14:51.26 | antithesis_ | I'm not talking about how fast it is, ShadowJK , but how accurate |
| 14:51.29 | DocScrutinizer05 | also what ShadowJK said |
| 14:51.32 | ShadowJK | My firefox os phone just about manages to detect which quadrant of the screen is touch ;p |
| 14:51.49 | antithesis_ | lol |
| 14:52.02 | ShadowJK | It also does something I havent seen since mid 90s Nokia: Dust collecting between the layers of the screen |
| 14:52.12 | DocScrutinizer05 | OMG! |
| 14:52.29 | antithesis_ | So, to rephrase the question: are all capacitative touch screens as accurate? |
| 14:52.37 | ShadowJK | no |
| 14:52.47 | DocScrutinizer05 | that largely depends on particular build |
| 14:52.51 | ShadowJK | There are tests |
| 14:53.16 | ShadowJK | where people have used capacitive stylus and rulers to draw grid pattern on screen in some paint program |
| 14:53.39 | DocScrutinizer05 | there are remarkably more designs on c-ts than you can read about on wikipedia |
| 14:53.39 | FIQ | can't use capacitive screens with his nails, therefore they are annoying |
| 14:53.47 | ShadowJK | the worst show a wavy grid, many have distortion at the edges |
| 14:54.18 | DocScrutinizer05 | while for resistive ts wikipedia seems to almost have a comprehensive list of known technologies and variants |
| 14:55.32 | DocScrutinizer05 | btw i recently found out about SG Note-2: it has c-ts plus wacom style inductive hybrid |
| 14:56.22 | DocScrutinizer05 | so yes, you can use stylus on note-2, but not arbitrary sylus but only special inductive type |
| 14:56.34 | ShadowJK | antithesis_; http://mashable.com/wp-content/uploads/2010/01/diytouchscreenanalysis3.jpg |
| 14:57.07 | ShadowJK | http://mashable.com/2010/01/11/touchscreen-comparison/ |
| 14:57.29 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 14:59.04 | DocScrutinizer05 | ^^^ ROTFL!! |
| 14:59.19 | DocScrutinizer05 | now that's pretty bad |
| 15:00.31 | jaska | worst touchscreen ive ever used: sph-m550 |
| 15:00.55 | jaska | (yes its a cdma phone, didnt use the cdma parts in .fi) |
| 15:01.40 | ShadowJK | DocScrutinizer05; you disassembled your jolla? |
| 15:01.44 | DocScrutinizer05 | nope |
| 15:01.50 | DocScrutinizer05 | shall I? |
| 15:02.03 | ShadowJK | or was the antennae comments from exterior inspection? |
| 15:02.09 | DocScrutinizer05 | yep |
| 15:02.12 | ShadowJK | ah |
| 15:02.25 | DocScrutinizer05 | looks nasty to disassemble |
| 15:02.29 | *** join/#maemo MrPingu (~MrPingute@ip503c83e7.speed.planet.nl) |
| 15:02.39 | DocScrutinizer05 | but... that#s probably always the case |
| 15:02.44 | ShadowJK | I suspect the design has some nasty flex issues.. |
| 15:02.46 | *** join/#maemo sequantz__ (~sequantz@agbl224.neoplus.adsl.tpnet.pl) |
| 15:02.49 | DocScrutinizer05 | yep |
| 15:03.23 | DocScrutinizer05 | what makes me wonder: it has no visible testpads *anywhere* |
| 15:03.31 | ShadowJK | judging by the number of "sim card is lost when phone is in pocket", and battery contact glitches |
| 15:04.23 | *** join/#maemo xes (~xes@unaffiliated/xes) |
| 15:04.30 | DocScrutinizer05 | pulling off TOH is a major PITA anyway |
| 15:04.54 | ShadowJK | Mine is loose in one corner, so it's easy to start there |
| 15:05.18 | DocScrutinizer05 | can't figure how any PCB mounted to that wobbly TOH plastic shall survive that procedure |
| 15:05.51 | ShadowJK | I was very amused yesterday when jolla cellmo stopped working :) N900 feature-parity with autosuicide modem :D |
| 15:06.37 | ShadowJK | Anyone making TOH with any features would have to do a new design, and make phone thicker.. |
| 15:06.38 | DocScrutinizer05 | really? |
| 15:06.58 | FIQ | oh joy |
| 15:07.17 | FIQ | apparently my ext3 is corrupted again |
| 15:07.21 | DocScrutinizer05 | just tested the RFID tag in TOH: N9 says "this tag has no content" - as usual |
| 15:07.25 | ShadowJK | There's a hundred or so people with modem issues, judging by the number of votes "disappearing SIM" has |
| 15:07.34 | FIQ | and I'm positive that I did not shutdown the device incorrectly |
| 15:07.46 | FIQ | perhaps my eMMC is simply starting to fail |
| 15:07.55 | DocScrutinizer05 | FIQ: that's annoying |
| 15:08.26 | DocScrutinizer05 | ShadowJK: sounds like I should get rid of the thing ASAP |
| 15:08.36 | FIQ | this time it seems only xchat scrollback was affected |
| 15:08.46 | FIQ | hmm |
| 15:08.47 | ShadowJK | There seems to be a sensor/switch in the sim bay, which touches the side of sim card.. seems tolerances in sim cards are much bigger than what the switch is designed for |
| 15:08.52 | ShadowJK | and also frame flex |
| 15:09.03 | FIQ | DocScrutinizer05: can I somehow make a full FS check to which files are having issues? |
| 15:09.06 | FIQ | without repairing that is |
| 15:09.34 | DocScrutinizer05 | FIQ: err, fsck has a check-only option |
| 15:09.38 | ShadowJK | FIQ; cd /home ; ls -lhRa > /dev/null |
| 15:09.44 | FIQ | so I know if I can just make a backupmenu backup (and having it fail to save files with issues) and restore from that right away |
| 15:10.03 | FIQ | ShadowJK: yeah something like that, ty |
| 15:10.34 | ShadowJK | wont detect files with garbage in them, but i dont know what would |
| 15:11.08 | DocScrutinizer05 | umm, ls? |
| 15:11.23 | DocScrutinizer05 | will ls detect broken inode chains? |
| 15:11.38 | FIQ | it only managed to find these scrollback files I mentioned |
| 15:11.39 | DocScrutinizer05 | ls is only reading dir inodes, no? |
| 15:11.52 | FIQ | "stale NFS file handle" |
| 15:11.58 | DocScrutinizer05 | ouch |
| 15:12.02 | ShadowJK | -lh makes it access inodes |
| 15:12.06 | FIQ | this is interesting |
| 15:12.12 | FIQ | because |
| 15:12.13 | ShadowJK | instead of jsut listing directory contents |
| 15:12.18 | FIQ | I've had this issue 4 times |
| 15:12.24 | DocScrutinizer05 | standard filesystem response when an inode is of fubar "type" |
| 15:12.26 | FIQ | *all* of them has been related to xchat |
| 15:12.47 | FIQ | does xchat do something weird with files on maemo? |
| 15:13.03 | DocScrutinizer05 | not really, just writing like mad |
| 15:13.13 | FIQ | hm |
| 15:13.24 | FIQ | perhaps I should disable scrollback and logging |
| 15:13.25 | DocScrutinizer05 | I seriously discourage doing IRC logs on embedded |
| 15:13.31 | ShadowJK | I noticed I started experiencing "ext3 corrupt after unexpected shutdown" much more frequently after I enabled browsed disk cacehe... And if the fs is damaged once, it often gets worse from use even without more unexpected crash/reboot |
| 15:13.40 | FIQ | DocScrutinizer05: well this time it was scrollback |
| 15:13.52 | FIQ | and afaik that is on by default |
| 15:13.58 | FIQ | (logging isn't though) |
| 15:14.18 | FIQ | all right |
| 15:14.27 | FIQ | so let's turn that xchat setting off |
| 15:14.40 | ShadowJK | oh... |
| 15:14.41 | FIQ | and backup/restore via backupmenu |
| 15:14.45 | ShadowJK | do you have cssu? |
| 15:14.50 | FIQ | yes ShadowJK |
| 15:14.52 | DocScrutinizer05 | I guess xchat does several dozen writes per second, for logs |
| 15:15.12 | ShadowJK | I have cssu thumb, and noticed /home mount options are different from stock |
| 15:15.47 | FIQ | I'm not sure if the corruption issues arised from cssu |
| 15:15.49 | ShadowJK | So, if I remember (which I havent since last boot), I do mount /dev/mmcblk0p2 /home -o remount,noatime,nodiratime,commit=1 |
| 15:15.53 | FIQ | but I never had issues w/o cssu |
| 15:15.56 | ShadowJK | iirc that's how it was in stock |
| 15:16.48 | DocScrutinizer05 | noatime,nodiratime for sure |
| 15:17.02 | DocScrutinizer05 | commit=1 I'm not sure |
| 15:17.30 | DocScrutinizer05 | anyway I start to feel unhappy with CSSU |
| 15:17.31 | FIQ | k logging turned off and verified off |
| 15:17.41 | ShadowJK | I always assumed it came from Nokia QA battery-removal tests |
| 15:18.38 | DocScrutinizer05 | anybody familiar with fail2ban? |
| 15:18.46 | FIQ | I'll shut down xchat nicely, re-do ls "scan" to verify that it didn't break anything else (especially not system important files) as of we speaking, and let backupmenu do its' thing |
| 15:18.54 | Ashley` | ...kinda |
| 15:19.00 | FIQ | kthxbai |
| 15:19.21 | DocScrutinizer05 | FIQ: oh yes! you must quit xchat proper, otherwise settings are not saved |
| 15:19.48 | DocScrutinizer05 | Ashley`: any hints what to check/customize after installation? |
| 15:20.04 | Ashley` | vim /etc/fail2ban/jail.conf |
| 15:20.05 | Ashley` | :v |
| 15:20.24 | Ashley` | add your home IP address to "Exclude" section |
| 15:20.48 | DocScrutinizer05 | that's exactly the sort of hint I hoped for |
| 15:20.57 | Ashley` | write some customized jails for your nginx v: |
| 15:21.12 | Ashley` | (oh, not using nginx? install nginx then xD) |
| 15:21.27 | *** join/#maemo MrPingu (~MrPingute@ip503c83e7.speed.planet.nl) |
| 15:23.26 | DocScrutinizer05 | what about that weird auto-mailing |
| 15:23.42 | DocScrutinizer05 | is that actually a good idea to keep/use? |
| 15:23.50 | DocScrutinizer05 | mailto-whois etc |
| 15:24.20 | DocScrutinizer05 | seems like it's more a way to make my own box look rogue |
| 15:24.23 | Ashley` | uses another program for sending logwatches |
| 15:24.39 | Ashley` | i don't remember its name |
| 15:24.49 | Ashley` | it sends me summary of logs every day |
| 15:24.52 | DocScrutinizer05 | mailto-whois doesn't send logs but complaints |
| 15:25.14 | DocScrutinizer05 | sounds pretty weird. and scary |
| 15:25.52 | DocScrutinizer05 | # Sends a complaint e-mail to addresses listed in the whois record for an |
| 15:25.53 | DocScrutinizer05 | # offending IP address. |
| 15:25.58 | Ashley` | oh |
| 15:26.00 | Ashley` | hm |
| 15:26.11 | Ashley` | I don't have it turned on. |
| 15:26.45 | DocScrutinizer05 | at least I guess that's what "sendmail-whois[name=sasl, dest=you@example.com]" does |
| 15:27.41 | DocScrutinizer05 | oh, judging by the mailaddr template, it isn't |
| 15:28.14 | DocScrutinizer05 | so wtf means sendmail-whois? |
| 15:29.17 | Ashley` | maybe it sends whois output of banned IPs to you |
| 15:29.19 | DocScrutinizer05 | <PROTECTED> |
| 15:29.29 | DocScrutinizer05 | aah, maybe |
| 15:31.05 | DocScrutinizer05 | I guess I don't want an email for each scanner hammering my box |
| 15:31.19 | Ashley` | yeah |
| 15:31.23 | solofight | already added apps are still showing in the list of apps to be added for a new folder in apmefo |
| 15:31.24 | DocScrutinizer05 | sometimes 3 or 5 per day |
| 15:31.24 | solofight | :( |
| 15:31.47 | ShadowJK | Such email reports used to be marked "Idiot with firewall" |
| 15:31.52 | DocScrutinizer05 | solofight: they don't vanish there |
| 15:31.53 | ShadowJK | at ISPs |
| 15:32.05 | Ashley` | daily log summary (including fal2ban.log) is better v: |
| 15:32.11 | DocScrutinizer05 | otherwise you couldn't add them to multiple submenus |
| 15:33.29 | DocScrutinizer05 | ShadowJK: yep, that's however my least worry |
| 15:33.56 | DocScrutinizer05 | ShadowJK: my box on blacklists would be worse |
| 15:34.40 | ShadowJK | yes |
| 15:35.13 | DocScrutinizer05 | the huger the ISP the higher the probability of my box sending multiple complaints and the higher the impact/damage from getting onto the blacklist of that ISP/provider |
| 15:38.10 | solofight | DocScrutinizer05: what i mean is if an icon is already selected to be a part of a folder it should not be in the list of appls which i can add to for another folder ... right ? |
| 15:38.39 | DocScrutinizer05 | wrong |
| 15:38.54 | DocScrutinizer05 | solofight: they don't vanish there otherwise you couldn't add them to multiple submenus |
| 15:40.17 | DocScrutinizer05 | I admit that's a bit of a hassle to sort out which app is already "used"/covered |
| 15:40.32 | solofight | exactly |
| 15:41.08 | DocScrutinizer05 | I used to do that by saving one folder's config, then switching between apmefo settings and that folder in appstarter |
| 15:41.59 | DocScrutinizer05 | there's also a trick of directly editing the apmefo local config files, I guess |
| 15:43.06 | DocScrutinizer05 | or you print out a list of all existing apps - to paper copy - and checkmark each single one you handled |
| 15:43.32 | DocScrutinizer05 | on the bright side: that problem is a clear one-time issue |
| 15:44.13 | DocScrutinizer05 | later installed apps are relatively easy to handle |
| 15:44.29 | DocScrutinizer05 | since you deal with only one app at a time |
| 15:44.46 | DocScrutinizer05 | so this is a 60 min of hassle that really pay back |
| 15:45.09 | DocScrutinizer05 | doonce, profit forever |
| 15:45.46 | DocScrutinizer05 | when you get lazy, you end with some few apps in root menu, see my screenshot ;-) |
| 15:46.13 | DocScrutinizer05 | I eventually should move bq27-monitor to system, and Opera to utils |
| 15:46.26 | DocScrutinizer05 | and maybe opera also to core apps? |
| 15:47.59 | DocScrutinizer05 | Ashley`: is "exclude" actually named "ignoreip"? |
| 15:48.32 | Ashley` | oh |
| 15:48.32 | *** join/#maemo arcean (~arcean@aacr222.neoplus.adsl.tpnet.pl) |
| 15:48.34 | Ashley` | yeah |
| 15:48.41 | solofight | DocScrutinizer05: apmefo local config files ! ? how to edit them ? |
| 15:48.49 | Ashley` | I edited it a long time ago... |
| 15:48.50 | DocScrutinizer05 | solofight: no idea |
| 15:49.09 | DocScrutinizer05 | Ashley`: the problem is: I have dynamic local IP |
| 15:49.12 | Ashley` | oh |
| 15:49.22 | Ashley` | so, you've no problem with bans |
| 15:49.28 | solofight | apmefo settings and that folder in appstarter ? here do you mean the folder which i created and the root menu ? |
| 15:49.33 | Ashley` | ban -> reconnect (another ip) -> you're not banned :D |
| 15:49.39 | DocScrutinizer05 | not THAT dynamic |
| 15:49.45 | Ashley` | hm... |
| 15:49.59 | DocScrutinizer05 | like "changes every other week" |
| 15:50.01 | Ashley` | Maybe you can make some script that autoupdates config :v |
| 15:50.33 | Ashley` | Or hope you'll not get banned |
| 15:50.34 | DocScrutinizer05 | I guess I can't use IP ranges or URLs there? |
| 15:50.35 | *** join/#maemo dhbiker (~dhbiker@95.87.145.172) |
| 15:50.44 | Ashley` | You can use IP ranges |
| 15:50.54 | DocScrutinizer05 | that's fine for me then |
| 15:51.01 | Ashley` | I don't know about URLs... you're thinking about domains? |
| 15:51.17 | DocScrutinizer05 | a /16 is better than nothing already |
| 15:51.27 | DocScrutinizer05 | yep |
| 15:51.32 | DocScrutinizer05 | dyndns |
| 15:52.36 | DocScrutinizer05 | prolly can even use a /24 |
| 15:52.45 | DocScrutinizer05 | or at least a /20 |
| 15:53.02 | FIQ | worked just fine |
| 15:53.06 | FIQ | nice |
| 15:56.57 | FIQ | I lost 18 files |
| 15:57.07 | FIQ | all related to scrollback |
| 15:57.16 | FIQ | otherwise backup went seamless |
| 15:57.33 | FIQ | apart from a million timestamp errors as I didn't bother to set system time |
| 15:58.35 | Ashley` | DocScrutinizer05, # "ignoreip" can be an IP address, a CIDR mask or a DNS host. |
| 15:58.45 | *** part/#maemo antithesis_ (~antithesi@82-168-60-132.ip.telfort.nl) |
| 15:58.51 | Ashley` | DocScrutinizer05, so, I think you can use dyndns or somthing like that |
| 16:00.06 | DocScrutinizer05 | \o/ |
| 16:04.06 | DocScrutinizer05 | Ashley`: where the heck are the manpages? |
| 16:04.16 | Ashley` | dunno :v |
| 16:04.22 | DocScrutinizer05 | Ashley`: what is a <JAIL>? |
| 16:04.51 | Ashley` | ~$ ssh ashley.re man -k fail2ban |
| 16:04.51 | Ashley` | fail2ban-client (1) - configure and control the server |
| 16:04.51 | Ashley` | fail2ban-regex (1) - test Fail2ban "failregex" option |
| 16:04.51 | Ashley` | fail2ban-server (1) - start the server |
| 16:04.54 | Ashley` | here |
| 16:04.57 | DocScrutinizer05 | fail2ban-client is pretty complex |
| 16:05.32 | Ashley` | jail is... uh... my english skills suck... :f |
| 16:05.42 | DocScrutinizer05 | funny enough man -k fail2ban doesn't yield anything for me, seems there's missing some re-indexing |
| 16:06.46 | DocScrutinizer05 | is JAIL each of the [ssh-iptables] etc sections? |
| 16:07.13 | DocScrutinizer05 | so, is ssh-iptables a <jail>? |
| 16:09.07 | DocScrutinizer05 | or is the complete jail.conf one <JAIL>? |
| 16:09.46 | Ashley` | see etc/fail2ban/jails.d or something like that |
| 16:09.52 | Ashley` | jails are defined there |
| 16:10.08 | Ashley` | they're... rules for banning |
| 16:10.40 | *** join/#maemo jmlich (~jmlich@ip-78-102-111-118.net.upcbroadband.cz) |
| 16:10.41 | Ashley` | fail2ban works by parsing logs and comparing lines to regexps and counting occurences AFAIK |
| 16:11.07 | *** join/#maemo arcean (~arcean@aacr222.neoplus.adsl.tpnet.pl) |
| 16:11.20 | DocScrutinizer05 | I have no etc/fail2ban/jails.d or similar, just filters.d and action.d |
| 16:11.38 | Ashley` | `oh |
| 16:11.41 | Ashley` | sorry |
| 16:11.43 | Ashley` | filters.d |
| 16:11.45 | DocScrutinizer05 | yes, that's what I thought |
| 16:12.05 | DocScrutinizer05 | aaah, ok, filters.d jas the JAILs then |
| 16:14.12 | *** join/#maemo Aggese (~Durand@ghs/durand) |
| 16:17.45 | DocScrutinizer05 | this package could use some docs/HowTo |
| 16:19.32 | DocScrutinizer05 | <PROTECTED> |
| 16:19.33 | DocScrutinizer05 | <PROTECTED> |
| 16:19.48 | DocScrutinizer05 | from man fail2ban-client |
| 16:26.52 | DocScrutinizer05 | the dest=<maladdr> on every section is pretty weird. you'd exopect that to be a macro or global setting or default |
| 16:32.39 | DocScrutinizer05 | http://privatepaste.com/abc7fd3239 \o/ |
| 16:34.48 | *** join/#maemo mx32 (~max@ip98-165-75-131.ph.ph.cox.net) |
| 16:35.32 | mx32 | hi i wondered what were you guys thoughts on jolla? |
| 16:40.14 | *** join/#maemo jdoles (~jdoles@unaffiliated/jdoles) |
| 16:40.55 | jdoles | How do I disable all e-mail for a particular account during a particular time period? I would like to control this either via some UI or via a script. |
| 16:41.21 | jdoles | (N900) |
| 16:52.15 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 16:52.21 | *** join/#maemo arcean (~arcean@aacr113.neoplus.adsl.tpnet.pl) |
| 16:53.22 | *** join/#maemo goldkatze (~nobody@188-192-253-130-dynip.superkabel.de) |
| 16:53.27 | *** join/#maemo goldkatze (~nobody@unaffiliated/goldkatze) |
| 17:00.48 | DocScrutinizer05 | jdoles: diable all email? |
| 17:02.30 | ShadowJK | Presumably he'd like to disable auto-update for a single account, for a specific time period |
| 17:07.09 | DocScrutinizer05 | that seems hard to accomplish |
| 17:11.41 | *** join/#maemo bugzy (~bugzy@99.191.138.94) |
| 17:13.59 | jdoles | DocScrutinizer05: I just want an API to disable a particular account between two dates (or in general a set of dates). |
| 17:14.54 | jdoles | The previous CSSU upgrade was noticably better than anything before; the RAM improvements are noticable. |
| 17:15.20 | jdoles | So, to whoever is responsible for that: good job. |
| 17:22.57 | *** join/#maemo SmilyOrg (Smily@149.126.154.203) |
| 17:23.35 | *** join/#maemo nox- (noident@freebsd/developer/nox) |
| 17:29.09 | *** join/#maemo oniongarlic (~milang@tori.tal.org) |
| 17:37.37 | *** join/#maemo emma (~em@unaffiliated/emma) |
| 17:40.20 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 17:46.45 | *** join/#maemo oniongarlic (~milang@195.16.220.82) |
| 17:51.02 | *** join/#maemo Timmy (~quassel@unaffiliated/timmyt) |
| 17:59.51 | *** join/#maemo bugzy (~bugzy@99-191-138-94.lightspeed.irvnca.sbcglobal.net) |
| 18:13.57 | DocScrutinizer05 | o.O |
| 18:23.52 | DocScrutinizer05 | jdoles: (mail) I think that's not supported |
| 18:24.41 | jdoles | DocScrutinizer05: what's there to o.O about? |
| 18:24.45 | *** join/#maemo freemangordon (~freemango@46.249.74.23) |
| 18:25.13 | DocScrutinizer05 | I don't know of any RAM savings in latest CSSU |
| 18:25.30 | jdoles | DocScrutinizer05: not the latest. |
| 18:25.33 | jdoles | DocScrutinizer05: the one before that. |
| 18:25.36 | DocScrutinizer05 | except of course you're on cssu-thumb |
| 18:25.40 | jdoles | DocScrutinizer05: yeah, that one. |
| 18:25.46 | DocScrutinizer05 | aaah |
| 18:26.13 | jdoles | They should have done this when the phone was released. |
| 18:26.31 | DocScrutinizer05 | htey didn't know how to do it |
| 18:26.44 | freemangordon | about 2-3MB less code in latest -thumb |
| 18:26.57 | freemangordon | or even more |
| 18:27.09 | DocScrutinizer05 | it's been freemangordon who was the awesome genius to find out how to implement the thumb-bugfix |
| 18:27.18 | freemangordon | :) |
| 18:27.29 | jdoles | How is it possible that a bunch of open-source hobbyists are better than 100,000 employees? |
| 18:27.36 | freemangordon | despite those saying it is impossible :P |
| 18:27.40 | jdoles | Or just freemangordon by himself, that's it. |
| 18:27.52 | jdoles | er that is. |
| 18:28.03 | freemangordon | jdoles: I can afford it |
| 18:28.07 | DocScrutinizer05 | well, basically nobody did care |
| 18:28.24 | freemangordon | noone will want his money back from me ;)( |
| 18:28.30 | jdoles | freemangordon: are you a millionaire with too much time on your hands? |
| 18:28.35 | freemangordon | no |
| 18:28.36 | ShadowJK | The experts were "It's fixed in newest chip version" or smth |
| 18:28.52 | DocScrutinizer05 | yes |
| 18:29.03 | *** join/#maemo ZogG_laptop (~ZogG_lapt@funtoo/user/ZogG) |
| 18:29.08 | DocScrutinizer05 | this is a bug only on some of our CPUs |
| 18:29.25 | freemangordon | jdoles: If I were, I'd have funded the neo900 project :)( |
| 18:29.41 | freemangordon | WTF is with that bracket? |
| 18:29.43 | DocScrutinizer05 | and nobody at Nokia or anywhere else wanted to invest the time to find a better bugfix than "don't use thumb" |
| 18:30.04 | jdoles | It sounds like a billion dollar mistake. |
| 18:30.13 | DocScrutinizer05 | TI did it |
| 18:30.24 | *** join/#maemo somedude238 (~mebus@port-92-196-100-231.dynamic.qsc.de) |
| 18:30.37 | jdoles | Someone didn't write the contracts correctly then. |
| 18:30.49 | freemangordon | jdoles: afaik Nokia planed to use thumb, but it turned out that chips are buggy |
| 18:30.52 | DocScrutinizer05 | who knows |
| 18:31.02 | freemangordon | *planned |
| 18:31.12 | ShadowJK | Also SR |
| 18:31.17 | freemangordon | :nod: |
| 18:31.17 | ssvb | DocScrutinizer05: it was just decided not to take the risk, all the thumb issues and available workarounds were known and taken into account when making the decision :) |
| 18:31.20 | DocScrutinizer05 | the best contract can't fix a chip |
| 18:31.39 | jdoles | DocScrutinizer05: no, but it can fix billions of dollars. |
| 18:31.45 | DocScrutinizer05 | ssvb: sounds sensible |
| 18:31.53 | jdoles | Then again, probably TI doesn't want to take on such contracts. |
| 18:32.16 | freemangordon | ssvb: hmm, I beg to disagree (all were known), binutils were fixed somewhere in late 2010 or 2011 |
| 18:32.29 | jdoles | It would have been interesting if some spy agency would turn out to have sabotaged the chips. |
| 18:32.47 | ssvb | freemangordon: hmm, are you really sure? |
| 18:32.56 | freemangordon | lemme check it again, but iirc |
| 18:32.59 | jdoles | (to eliminate another mobile player from the market) |
| 18:33.20 | jdoles | (and in particular a non-American company) |
| 18:33.48 | ShadowJK | TI did exit the market |
| 18:33.49 | freemangordon | ssvb: hmm, I am mistaken |
| 18:33.57 | freemangordon | it is 2009 |
| 18:34.15 | freemangordon | ssvb: but why then? |
| 18:34.20 | freemangordon | makes no sense |
| 18:34.32 | somedude238 | With all the Privacy Issues Today, I wonder why are you still using Maemo? I mean, with the non-free bits it more or less sure that meamo does spy on you like any other mobile os. So.... how will you react to this? |
| 18:34.33 | ssvb | freemangordon: in any case, I remember that the errata list from arm included the recommendations to patch the linker, and the preliminary patches were available at the time |
| 18:36.20 | freemangordon | somedude238: broadband modem in n900 does not have access o the APE memory |
| 18:36.25 | freemangordon | *to |
| 18:36.28 | ShadowJK | Funny that, with all the privacy issues today, I wonder why more people aren't using maemo |
| 18:36.33 | freemangordon | :nod: |
| 18:36.58 | ssvb | freemangordon: the thumb issues were discovered one after another, it was not like a nice and *complete* list of thimb issues was available right from the start |
| 18:37.27 | freemangordon | ssvb: I see |
| 18:37.57 | freemangordon | there was a fear there will be some undiscovered issue? |
| 18:38.37 | ssvb | freemangordon: yes |
| 18:39.15 | ShadowJK | vaguely recalls mru discovering new hw bugs every week |
| 18:39.25 | freemangordon | ssvb: yep, makes sense. though if it was me to decide, I'd have taken the risk. |
| 18:40.16 | freemangordon | as "the risk" is some application crashing once a month, which happens anyway, with or without thumb :) |
| 18:40.46 | somedude238 | freemangordon: seeing only modem is narrow for a perspective. Let me give you an example. If I put in my simcard, suddendly I recive various "configuration" sms, then meamo doesn something I don't know what and I'm suddendly subscriber to some "mynokia" service I have to opt out after.... sound like an privacy issue to me. |
| 18:41.26 | freemangordon | somedude238: that "issue" is well known for, how much, 3 years? |
| 18:42.24 | DocScrutinizer05 | freemangordon: (take the risk) that's the difference |
| 18:42.39 | freemangordon | and is actually the only known privacy issue. And believe me, there are people who known what is inside maemo, I doubt a real privacy issue would have passed unnoticed so far |
| 18:43.23 | freemangordon | DocScrutinizer05: I did something similar in my RL job |
| 18:43.41 | DocScrutinizer05 | and notmynokia issue is even implemented into maemo in a pretty obvious way |
| 18:43.46 | ShadowJK | Maemo might be an exception in that it tells you when operator has sent conifugration data |
| 18:44.03 | DocScrutinizer05 | ~notmynokia |
| 18:44.09 | DocScrutinizer05 | damn |
| 18:44.25 | DocScrutinizer05 | ~listvalues mynokia |
| 18:44.37 | DocScrutinizer05 | meh |
| 18:45.15 | DocScrutinizer05 | anyway mynokia issue is not related to inbound config SMS |
| 18:45.19 | DocScrutinizer05 | not at all |
| 18:45.30 | somedude238 | freemangordon: so thinking about secret laws, secret contracts and not so secret NDAs, do you think who ever did work for nokia and knows about privacy issues is allowed to talk about it without facing serious legal issues? just saying |
| 18:45.32 | DocScrutinizer05 | N900 actively sends out a SMS |
| 18:45.50 | freemangordon | somedude238: I don;t talk about ex-nokians |
| 18:46.06 | DocScrutinizer05 | somedude238: we know our shit |
| 18:46.19 | DocScrutinizer05 | we don't need sekrit info from inside Nokia |
| 18:46.26 | freemangordon | right now on the channel there are at least 10 people who know almost everything on how the suff in maemo works |
| 18:46.38 | freemangordon | stuff even |
| 18:46.48 | ShadowJK | Even so, question is why would maemo be any more exposed to agency meddling than other systems |
| 18:47.03 | DocScrutinizer05 | hah, rather less |
| 18:47.18 | freemangordon | anyway, /me is back to REing fmtxd |
| 18:47.23 | DocScrutinizer05 | \o/ |
| 18:47.33 | DocScrutinizer05 | gooo freemangordon GOOOOO! |
| 18:47.57 | freemangordon | DocScrutinizer05: for some strange reason I was thinking there is only ARM binary |
| 18:48.10 | DocScrutinizer05 | hm? |
| 18:48.15 | DocScrutinizer05 | oh |
| 18:48.20 | DocScrutinizer05 | x86? |
| 18:48.28 | freemangordon | I was like WTF?!? yesterday when I discovered there is x86 binary too :) |
| 18:48.31 | freemangordon | yep |
| 18:48.52 | freemangordon | and it is easy to RE some 30k x86 binary |
| 18:49.00 | DocScrutinizer05 | :nod: |
| 18:49.34 | freemangordon | with the almighty hexrays armed :D. BFG9000, you know ;) |
| 18:50.07 | DocScrutinizer05 | however watch out that it#s not a fake/dummy to make maemo work on platform without FM |
| 18:50.44 | freemangordon | DocScrutinizer05: rephrase please, can't parse |
| 18:50.44 | DocScrutinizer05 | on some ends they must have sneaked in dummies |
| 18:51.20 | freemangordon | (still some hangover left over :) ) |
| 18:51.24 | DocScrutinizer05 | maemo x86 supposed to run on a platform that has no FM chip thus no sysnodes for it. Rest of system want's to emulate this |
| 18:51.53 | DocScrutinizer05 | so fmtxd might be a dummy stub that doesn't do anything |
| 18:52.08 | freemangordon | DocScrutinizer05: naah, it is ok, it searches for some files in /tmp if it can't find the real files :) |
| 18:52.11 | DocScrutinizer05 | just gives an API that returns "OK, whatever you say" |
| 18:52.20 | freemangordon | no, the code looks just ok |
| 18:52.22 | DocScrutinizer05 | HAH! |
| 18:52.27 | DocScrutinizer05 | :-) |
| 18:53.23 | freemangordon | '/tmp/dummy.vbus', '/tmp/dummy.charger' :D |
| 18:53.37 | freemangordon | likes the names |
| 18:53.43 | DocScrutinizer05 | so they redirected the sysfs nodes to tmp/dummy.txt files? smart? |
| 18:53.54 | DocScrutinizer05 | LOL? |
| 18:53.55 | freemangordon | :nod: |
| 18:54.04 | DocScrutinizer05 | my guessing is good, isn't it? |
| 18:54.07 | freemangordon | yep |
| 18:54.42 | DocScrutinizer05 | #IFDEF ? |
| 18:54.51 | DocScrutinizer05 | or actually code? |
| 18:55.05 | DocScrutinizer05 | i.e. would the armel binary do the same? |
| 18:55.09 | freemangordon | no, it tries to open the real sysfs node and falls back to "dummy" one |
| 18:55.46 | DocScrutinizer05 | so strings armel bin | grep tmp/dummy.charger ? |
| 18:56.10 | DocScrutinizer05 | :-D |
| 18:56.12 | freemangordon | try it |
| 18:56.21 | DocScrutinizer05 | dafilenam? |
| 18:56.34 | freemangordon | "/usr/sbin/fmtxd" |
| 18:56.38 | DocScrutinizer05 | tnx |
| 18:56.40 | freemangordon | or "/sbin/fmtxd" |
| 18:56.43 | freemangordon | not sure |
| 18:56.51 | DocScrutinizer05 | which * ;-9 |
| 18:57.01 | freemangordon | no ssh open to the device |
| 18:57.13 | freemangordon | and it is about 3 meters away :) |
| 18:57.39 | DocScrutinizer05 | IroN900:~# strings `which fmtxd`|grep tmp |
| 18:57.40 | DocScrutinizer05 | /tmp/dummy.vbus |
| 18:57.42 | DocScrutinizer05 | /tmp/dummy.charger |
| 18:57.51 | freemangordon | see :) |
| 18:57.56 | DocScrutinizer05 | :-D |
| 18:58.39 | DocScrutinizer05 | that mynokia kills me |
| 18:58.46 | DocScrutinizer05 | ~listkeys nokia |
| 18:58.57 | DocScrutinizer05 | ~mynokia |
| 18:58.57 | infobot | well, mynokia is a digital robbery courtesy Nokia, or http://wiki.maemo.org/PR1.2_compulsory_My_Nokia_subscription, or https://bugs.maemo.org/show_bug.cgi?id=10366 |
| 18:59.00 | povbot | 04Bug 10366: MyNokia SMS sent after update without any action from the user |
| 18:59.06 | DocScrutinizer05 | LOL |
| 18:59.30 | somedude238 | DocScrutinizer05: okay... knowing stuff does imply you know how non-free bits in maemo work. logicaly it can be assumes you can replace it with free software. then whey didn't I read about the free software meamo version for download? maybe because you don't know all about it? oh, but that would be like.... you cannot gurantee meamo doesn't have a lot more privacy issues. no offence. |
| 18:59.48 | ecc3g | clear |
| 19:00.03 | ecc3g | hands self a / |
| 19:00.42 | *** join/#maemo sequantz (~sequantz@agbl224.neoplus.adsl.tpnet.pl) |
| 19:00.47 | DocScrutinizer05 | somedude238: we have other means than knowing the sourcecode to check what a system does or possibly could do |
| 19:01.34 | DocScrutinizer05 | I just can tell you I *KNOW* my N900 isn't "spying on me" the way you suppose |
| 19:01.55 | DocScrutinizer05 | since I'd notice when it did |
| 19:02.23 | DocScrutinizer05 | and most probably I'd meanwhile even noticed when it had the ptential to do |
| 19:02.59 | DocScrutinizer05 | we disassembled and analyzed ~99.8% of all binaries on that device |
| 19:03.23 | DocScrutinizer05 | and I'd notice immediately when my device starts acting unusual |
| 19:03.41 | DocScrutinizer05 | processes not expected to run |
| 19:03.54 | DocScrutinizer05 | causing CPU load not expected to be seen |
| 19:03.56 | NIN101 | what about baseband etc.? |
| 19:04.05 | DocScrutinizer05 | causing battery drain that is hated a lot |
| 19:04.19 | *** join/#maemo Kilroo (~Kilroo@cpe-065-188-184-174.triad.res.rr.com) |
| 19:04.26 | DocScrutinizer05 | what could baseband do except already contacting BTS? |
| 19:04.43 | *** join/#maemo bef0rd (~bef0rd@unaffiliated/beford) |
| 19:04.45 | DocScrutinizer05 | sth it's built for and I hope it does reliably anyway |
| 19:05.39 | DocScrutinizer05 | spy on my internet traffic? well that can be done on BTS as well, just like anywhere else in world wide internet on any cisco router that happens to forward my data |
| 19:06.08 | DocScrutinizer05 | modem reporting to NSA about charging state of my battery? |
| 19:06.10 | DocScrutinizer05 | ;-P |
| 19:06.57 | DocScrutinizer05 | ok, they *can* activate the GPS on N900 and get a somewhat more precise fix than they could with mere triangulation from 3 BTS |
| 19:07.08 | DocScrutinizer05 | when I'm outdoor |
| 19:07.24 | DocScrutinizer05 | NIN101: what's "etc"? |
| 19:07.40 | DocScrutinizer05 | ooh, we have NOLO |
| 19:07.41 | NIN101 | DocScrutinizer05: http://www.heise.de/newsticker/meldung/30C3-SIM-Karten-Angriffe-bleiben-bedrohlich-2072666.html |
| 19:07.56 | DocScrutinizer05 | who knows what evil daemons hide in there ;-) |
| 19:08.07 | DocScrutinizer05 | NIN101: ooooooold |
| 19:08.29 | NIN101 | not the point. |
| 19:09.06 | DocScrutinizer05 | and yet to get tested if N900 BB5 maybe is a clean SAT implementation that actually rises an exception of sorts on JS programs running on SIM |
| 19:09.39 | DocScrutinizer05 | or if it actually simply can't and will not do SAT at all, like Nokia admitted |
| 19:09.54 | ShadowJK | You're all looking in the wrong place. The agency would obvioisly modulate the powergrid frequency, to create audio and video, which when we use camera, triggers an exploit in the emmc |
| 19:10.09 | DocScrutinizer05 | that however it pretty much completely unrelated to the phone |
| 19:10.33 | somedude238 | DocScrutinizer05: Nobody is perfect. I mean I do not say I don't belive you have the ability and the means to do as you say you do. Do you have a scientific paper explaining you methods and more or less proof there no more privacy issues than mynokia subscribtion? So other people can check your results and stuff. .... Okay, that would mean a lot of work but today trust needs a bit more then just a "because we say so". |
| 19:10.33 | DocScrutinizer05 | heheheharrrrhaha |
| 19:11.22 | DocScrutinizer05 | somedude238: no, and I'm not doing that paper without payment |
| 19:12.05 | NIN101 | also, do you track your CPU load and processes 24/7 :-)? |
| 19:12.14 | DocScrutinizer05 | yes |
| 19:12.39 | NIN101 | but what about my evil kernel module? |
| 19:12.58 | somedude238 | DocScrutinizer05: how much money do you want for doing such a paper? |
| 19:13.02 | DocScrutinizer05 | oh, the one pali kicked out of KP last week? |
| 19:13.12 | ShadowJK | heh |
| 19:13.38 | NIN101 | DocScrutinizer05: not "my" in particular, an attackers evil kernel module, how would you detect that? |
| 19:13.42 | DocScrutinizer05 | somedude238: lemme see.... 2 weeks == 10 man-days * 8h * 80bucks |
| 19:14.13 | DocScrutinizer05 | I first instance have no evil kernel modules on my device |
| 19:14.23 | NIN101 | how do you know? |
| 19:14.31 | DocScrutinizer05 | and my last lsmod is prolly 2 weeks ago |
| 19:14.45 | NIN101 | your lsmod is not reliable if your system is infected. |
| 19:14.53 | DocScrutinizer05 | meh |
| 19:15.00 | ShadowJK | NIN101; by that metric, there is not a single device in the world that can be trusted |
| 19:15.11 | NIN101 | yep. |
| 19:15.15 | ShadowJK | Not even SD cards :-) |
| 19:15.31 | NIN101 | yeah, I saw that talk on the 30c3. |
| 19:16.10 | DocScrutinizer05 | NIN101: so you just proved that ... you can't watch CPU operating |
| 19:17.11 | DocScrutinizer05 | and my system ISN't infected |
| 19:17.20 | ShadowJK | Also Samsung patching their cards so they don't bug out and overwrite their own firmware. Imagine an attacker that knew the sequence and conditions that trigger that bug, could potentially replace the firmware with his own, and have the card modify the operating system stored on it :-) |
| 19:17.29 | somedude238 | DocScrutinizer05: you sure that's enough? seems a bit fast to me or you are very confident you can do a paper for other people to check. |
| 19:18.41 | *** join/#maemo shentey (~shentey@e179073114.adsl.alicedsl.de) |
| 19:19.08 | *** join/#maemo oniongarlic (~milang@tori.tal.org) |
| 19:19.18 | NIN101 | " so you just proved that ... you can't watch CPU operating" Please rephrase. if you mean that you can't trust CPU load values reported by the kernel when your system is infected, then ineed, you can't. |
| 19:19.23 | DocScrutinizer05 | somedude238: I'm not interested in that whole discussion, it's like little Fritz going to chocolate factory asking for a quote for 30.000 kg of nougat chocolate |
| 19:19.52 | DocScrutinizer05 | why would I waste my time doing a proper quote? |
| 19:20.04 | *** join/#maemo SpeedEvil (~quassel@tor/regular/SpeedEvil) |
| 19:20.36 | ShadowJK | As kernel is typically only read at bootup, it'd be trivial for the compromised memory card to serve a compromised kernel at poweron, and return the original kernel later if anyone tried to read verify :D |
| 19:21.06 | DocScrutinizer05 | ShadowJK: 7here's /dev/mem though |
| 19:21.12 | NIN101 | ShadowJK: :-). |
| 19:21.36 | *** join/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 19:21.48 | *** part/#maemo {lol} (~zammy@ppp-105-144.98-62.inwind.it) |
| 19:21.53 | DocScrutinizer05 | ShadowJK: and how the heck did my 27 updates work? |
| 19:22.01 | somedude238 | DocScrutinizer05: I'm saying I try to get the money for you to do contracted work doing that paper. |
| 19:22.42 | DocScrutinizer05 | somedude238: if you're really interested in that, contact me on my commercial addr per email please |
| 19:22.50 | ShadowJK | OH, and let's not forget the led controller, it's a turing complete chip afterall, it might modulate he notification light with a datastream :s |
| 19:23.34 | ShadowJK | somedude238; would be more interesting in the context of Neo900 really |
| 19:24.11 | DocScrutinizer05 | ShadowJK: hehe, indeed |
| 19:24.11 | ShadowJK | The stock Maemo5/N900 concerns will go away automatically as the modem tends to suicide eventually anyway |
| 19:24.53 | DocScrutinizer05 | why do a security audit for a device that's fading away? |
| 19:24.57 | somedude238 | ShadowJK: that's also the point. I read neo900 does want to make use of meamo. first the it must be deemed safe or it's not usable. |
| 19:25.26 | DocScrutinizer05 | o.O |
| 19:25.52 | ShadowJK | somedude238; I think the majority of the closed telephony stuff is entirely incompartible anyway, and would have to be thrown out |
| 19:26.01 | somedude238 | DocScrutinizer05: I'll contact you in the next few days about the contracted work. |
| 19:26.15 | DocScrutinizer05 | do you have a faint idea what you mean by "safe"? |
| 19:26.35 | DocScrutinizer05 | and any idea how to accomplish that requirement? |
| 19:26.57 | DocScrutinizer05 | honestly, I#m curious what it is you want to see getting done |
| 19:28.01 | DocScrutinizer05 | on Neo900 you can have the security audit for half the price of N900 |
| 19:28.04 | ShadowJK | it's not doable unless you build every chip yourself, and xray them to confirm nobody tampered with them during manufacture, etc.. But then, you're doing the design work on an insecure machine in the first place, and can't trust the design software to synthesize your design |
| 19:29.00 | DocScrutinizer05 | ShadowJK: that#s why I ask about the level of "security" he's interested in resp talking about |
| 19:29.14 | ShadowJK | right |
| 19:29.52 | DocScrutinizer05 | I mean "all software from FOSS" doesn't say anything about security anyway, really |
| 19:30.01 | DocScrutinizer05 | not immanently |
| 19:30.35 | somedude238 | DocScrutinizer05: my Idea of "safe" in meamo context is first and foremost there is no remote access posibility by "nokia" or other thirdparty. from there apps "leaking data to the cloud" and down to sqashing bugs that could make previous things said possible. |
| 19:30.42 | DocScrutinizer05 | I can't do a full 100% security audit of even just the linus kernel |
| 19:31.06 | DocScrutinizer05 | somedude238: that's feasibe :-) |
| 19:32.00 | NIN101 | depends. If we include "remote exploits" in "no remote access posibility for third parties", then probably not. |
| 19:32.06 | ShadowJK | If you take as a given that the hardware which the maemo software runs on behaves as documented |
| 19:33.22 | DocScrutinizer05 | NIN101: since standard system doesn't expose any servies, there's hardly any exploit of such services for anybody to make use of |
| 19:34.12 | NIN101 | speaking about user space servers. |
| 19:34.31 | NIN101 | there also clients, and the kernel. |
| 19:34.35 | DocScrutinizer05 | you'd need to find an exploit in e.g. pop3 |
| 19:34.45 | DocScrutinizer05 | or - of course - web browser |
| 19:34.58 | ShadowJK | It's for sure not going to prevent you from installing and/or using random software |
| 19:35.07 | DocScrutinizer05 | :nod: |
| 19:35.27 | NIN101 | yeah, we can stretch this as far as we want. A very detailed definition of "safe" must be provided. |
| 19:35.51 | DocScrutinizer05 | aiui it's up to me to provide that |
| 19:36.13 | DocScrutinizer05 | I'll valuate what's safe and what's not safe, and that's the definition |
| 19:36.21 | DocScrutinizer05 | evaluate even |
| 19:36.26 | NIN101 | aiui he wants you do to an audit to confirm maemo is safe. In this case, he must. |
| 19:37.05 | DocScrutinizer05 | browser for example is NOT safe. Microsoft, netscape, firefox and opera didn't manage to define a safe browser |
| 19:37.12 | DocScrutinizer05 | so how could I? |
| 19:37.55 | DocScrutinizer05 | NIN101: we're not selling pink ponies. sorry |
| 19:38.31 | NIN101 | whatever. |
| 19:38.59 | DocScrutinizer05 | but sure, I'll be happy to answer a request "prove that any arbitrary software on maemo is safe" with a "it's not" and invoice 1 man-week for that ;-P |
| 19:41.40 | DocScrutinizer05 | but I for sure can define what's needed to make a few different levels of security work. Like cryptfs for example. OR - for lowest level - explain why stock maemo considered free of spyware but still has week spots that open up vulnerabilities, like e.g. said browser |
| 19:42.15 | DocScrutinizer05 | weak spots even |
| 19:42.39 | DocScrutinizer05 | you could sandbox the browser |
| 19:42.53 | somedude238 | DocScrutinizer05: isn't oviously not neccesary anymore. you just said the opposite. and meamo is not safe. thus it's not neccesary to pay you for contracted work to proof it's not safe. |
| 19:43.00 | DocScrutinizer05 | accepting the limitations in usability that comes with |
| 19:43.23 | DocScrutinizer05 | somedude238: aaah I knew it |
| 19:44.08 | DocScrutinizer05 | yeah, maemo (incl the 1600 apps in maemo-extras) definitely is NOT safe |
| 19:44.39 | DocScrutinizer05 | I know i#m talking to lil jimmy asking for 30 ons of chocolate |
| 19:44.51 | DocScrutinizer05 | tons* |
| 19:45.17 | kerio | yay chocolate :3 |
| 19:45.58 | somedude238 | DocScrutinizer05: what did you knew? first you say one thing and then the other. what do you expect? |
| 19:46.35 | DocScrutinizer05 | somedude238: and - just FYI - the browser for example definitle will NOT make it on fremantle running on Neo900, OOTB. You have to install it yourself, as user, and we will leave no doubt about the security risk that comes with such thing |
| 19:48.59 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 19:50.57 | somedude238 | DocScrutinizer05: I don't care anymore. it's like saying "it can do nothing at all but it's safe until you actually install software....." you just destroyed any credibility and trust I was willing to invest. just stop. |
| 19:51.25 | *** join/#maemo StyXman_ (~mdione@ant06-1-82-242-111-163.fbx.proxad.net) |
| 19:51.25 | *** join/#maemo StyXman_ (~mdione@grulic/root/StyXman) |
| 19:51.28 | ShadowJK | This applies to everything? |
| 19:51.53 | DocScrutinizer05 | somedude238: sorry we have no pink ponies for you |
| 19:51.58 | DocScrutinizer05 | and no chocolate |
| 19:52.07 | *** join/#maemo Sc0rpius_ (~naikel@ec2-54-196-227-78.compute-1.amazonaws.com) |
| 19:52.25 | *** join/#maemo MikaT_ (~mtapoja@projects.sse.fi) |
| 19:52.42 | *** join/#maemo cehteh_ (~cehteh@pipapo.org) |
| 19:53.06 | DocScrutinizer05 | and no OS that refuses to install carefully crafted malware, even when original user asks with stern voice, and waving with root permissions |
| 19:53.10 | *** join/#maemo mattaustin (mattaustin@gateway/shell/blinkenshell.org/x-ibqlrvbjodgivwgy) |
| 19:53.40 | *** join/#maemo kraft_ (kraft@gateway/shell/blinkenshell.org/x-jhwfdmovxakpkdrx) |
| 19:53.54 | DocScrutinizer05 | or did you think I could evaluate 1600 apps for their safety? |
| 19:54.03 | somedude238 | that all brings me back to the inital question.... With all the Privacy Issues Today, I wonder why are you still using Maemo? I mean, with the non-free bits it more or less sure that meamo does spy on you like any other mobile os. So.... how will you react to this? |
| 19:54.14 | ShadowJK | This was one of the huge criticisms regarding Nokia N9 / Maemo6 actually, that root wasnt root, and phone would kill itself if you tried to tweak it.. |
| 19:54.22 | *** join/#maemo nikosapi (~nikosapi@nikosapi.org) |
| 19:54.39 | DocScrutinizer05 | somedude238: please stop spreading bullshit |
| 19:55.12 | *** join/#maemo sfa_ (~sfa@208.66.156.12) |
| 19:55.35 | DocScrutinizer05 | it#s more or less sure that there are no "non-free" - as of your definition - bits on maemo |
| 19:55.41 | *** join/#maemo fizzie` (fis@unaffiliated/fizzie) |
| 19:56.14 | ShadowJK | Maemo 5 came before the adware age, and before people saw money in personal data, so there's much less data transfer going on by default, which makes it easier to spot if anything suspicious were to happen |
| 19:56.17 | *** join/#maemo RedM (~redw@89-73-179-171.dynamic.chello.pl) |
| 19:56.22 | *** join/#maemo somedude2381 (~mebus@port-92-196-114-111.dynamic.qsc.de) |
| 19:56.27 | *** part/#maemo somedude2381 (~mebus@port-92-196-114-111.dynamic.qsc.de) |
| 19:57.24 | DocScrutinizer05 | ShadowJK: it would be *pretty* obvious when e.g. the PVR opengl-3D driver would try to talk to internet, or do random fopen() |
| 19:57.43 | DocScrutinizer05 | we don't need sourcecode to know it doesn't |
| 19:57.50 | *** join/#maemo qwazix_nc (~qwazix@Maemo/community/council/qwazix) |
| 20:59.23 | *** join/#maemo infobot (~infobot@rikers.org) |
| 20:59.23 | *** topic/#maemo is Happy whatever doesn't offend you | Welcome to #maemo http://maemo.org/intro/ | N9/harmattan related questions please in #harmattan ! | Please see http://wiki.maemo.org/Maemo_Weekly_News | http://wiki.maemo.org/Community_Council | Source: http://wiki.maemo.org/Sources | Chanlog: http://mg.pov.lt/maemo-irclog | #maemo-ssu is where the (few) devels and maintainers of the maemo-future meet |
| 21:01.44 | *** join/#maemo hbib (~wurmel@pD9E0F580.dip0.t-ipconnect.de) |
| 21:08.26 | *** mode/#maemo [+v infobot] by ChanServ |
| 21:10.25 | *** join/#maemo zamn900 (~zammy@ppp-105-144.98-62.inwind.it) |
| 21:10.38 | *** part/#maemo zamn900 (~zammy@ppp-105-144.98-62.inwind.it) |
| 21:28.47 | *** join/#maemo bennypr0fane (~ben@1360030539.d-dsl.at) |
| 21:42.42 | *** join/#maemo amizraa (~amizraa@gateway/tor-sasl/amizraa) |
| 22:13.32 | *** join/#maemo Herbstbert (~Herbstber@drms-4d0bd4f7.pool.mediaWays.net) |
| 22:17.24 | *** join/#maemo Venemo (~Timur@fedora/Venemo) |
| 22:24.58 | *** join/#maemo robotanarchy_ (~robotanar@f048071115.adsl.alicedsl.de) |
| 23:23.13 | *** join/#maemo valeriusL (~valerius@185.3.35.224) |
| 23:25.41 | *** join/#maemo Ori_553 (~user@dynamic-adsl-94-38-2-40.clienti.tiscali.it) |
| 23:32.50 | *** join/#maemo triggerhappy (~quassel@112.209.21.95) |
