| 00:28.13 | *** join/#maemo RST38h (~marat@tissa.komkon.org) |
| 00:48.58 | *** join/#maemo kabouik (~Kabouik@65.76.93.92.rev.sfr.net) |
| 01:18.25 | *** join/#maemo eMHa (~mh@p579DBE6D.dip0.t-ipconnect.de) |
| 01:43.03 | *** join/#maemo robotanarchy (~robotanar@x590f6d47.dyn.telefonica.de) |
| 02:02.02 | *** join/#maemo Defiant (erik@x4e36fe3c.dyn.telefonica.de) |
| 02:51.57 | *** join/#maemo Hurrian (~textual@49.149.228.72) |
| 02:52.51 | *** join/#maemo Hurrian (~textual@unaffiliated/rikanee) |
| 03:02.31 | *** join/#maemo lxp (~lxp@unaffiliated/lxp) |
| 03:08.31 | *** join/#maemo DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 03:26.32 | *** join/#maemo vahe1 (~funtoo@130.193.124.135) |
| 03:27.28 | *** join/#maemo yasnothil (yasnothil@2600:3c03::f03c:91ff:fe55:c675) |
| 03:32.22 | *** join/#maemo pagurus````` (~user@p548CAF18.dip0.t-ipconnect.de) |
| 03:38.01 | *** join/#maemo pagurus````` (~user@p548CAF18.dip0.t-ipconnect.de) |
| 05:43.37 | KotCzarny | hmm, i wonder why nobody found it earlier: Znaps or the copy ZEUSS Easy Connect |
| 05:45.28 | KotCzarny | seems like a magic pill to solve n900 usb port issue |
| 05:54.26 | *** join/#maemo LauRoman (~LauRoman@5.14.92.160) |
| 06:57.34 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 07:04.47 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 07:27.03 | *** join/#maemo Hurrian (~textual@unaffiliated/rikanee) |
| 07:27.12 | *** join/#maemo xelo (~xelo@ip-176-198-129-195.hsi05.unitymediagroup.de) |
| 07:58.15 | Pali | freemangordon: ping |
| 08:04.48 | *** join/#maemo louisdk (~louisdk@static-5-103-130-65.seas-nve.net) |
| 08:35.11 | *** join/#maemo Vajb (~Vajb@85-76-12-22-nat.elisa-mobile.fi) |
| 09:15.23 | Pali | freemangordon: n900 patches are rebased on top of 4.6-rc4 but now without camera and v4l patches |
| 09:19.03 | *** join/#maemo futpib (~futpib@37.113.248.174) |
| 09:19.14 | Pali | ~seen jonwil |
| 09:19.15 | infobot | jonwil <~jonwil@27-33-80-219.tpgi.com.au> was last seen on IRC in channel #maemo, 23h 3m 1s ago, saying: 'hi'. |
| 09:40.03 | *** join/#maemo salamisami (~Valle@a88-112-2-11.elisa-laajakaista.fi) |
| 09:43.07 | *** join/#maemo M4rtinK (~M4rtinK@77.48.149.46) |
| 10:04.53 | L29Ah | nvm i vote for Wizzup, Pali and freemangordon |
| 10:05.03 | L29Ah | make n900 great again! |
| 10:12.56 | Hurrian | guys, does the N900/N9 do binary PDU mode for sending SMSes? |
| 10:15.32 | Wizzup | L29Ah: to be fair, I've mostly done some testing, I haven't done much coding apart from some input code :) |
| 10:15.45 | KotCzarny | we need testers too |
| 10:19.57 | L29Ah | building a distro out of the meta distro is much work as well actually |
| 10:20.24 | L29Ah | especially with such an unusual hardware |
| 10:22.22 | Wizzup | I'm close to writing some blogs on where I am now, and where I want to go |
| 10:22.32 | Wizzup | Many driver things I'll try to just mention (mostly userland, how to config, etc) |
| 10:22.39 | Wizzup | It's probably on the net somewhere in most cases |
| 10:23.09 | DocScrutinizer05 | eeew vote, right? |
| 10:24.16 | L29Ah | huh? |
| 10:24.50 | DocScrutinizer05 | <PROTECTED> |
| 10:24.54 | *** part/#maemo wiewo (~wowie@fossencdi.org) |
| 10:25.22 | KotCzarny | l29ah, you know what are council tasks, right? |
| 10:25.41 | KotCzarny | devs shouldnt have to waste time on secretary work |
| 10:25.42 | freemangordon | Pali: great, thanks :) |
| 10:25.49 | freemangordon | KotCzarny: :nod: |
| 10:25.53 | DocScrutinizer05 | dang, tomorrow! |
| 10:26.29 | DocScrutinizer05 | this doesn't sound right!!! |
| 10:26.37 | DocScrutinizer05 | only 6 days |
| 10:28.02 | DocScrutinizer05 | Election period: 25 April 2016 - 01 May 2016 (23:59) |
| 10:28.49 | L29Ah | 13:25:22]<KotCzarny> l29ah, you know what are council tasks, right? |
| 10:28.49 | L29Ah | no |
| 10:29.13 | KotCzarny | l29ah: council tasks have nothing to do with code |
| 10:29.25 | KotCzarny | they arent even bug-fixing related |
| 10:29.49 | L29Ah | can they at least fix the "anti-spam" bullshit that pesters every other guy there? |
| 10:30.05 | freemangordon | no |
| 10:30.07 | DocScrutinizer05 | vs "Starting 2016-04-25 00:00:00 UTC: Community Council Election Q2 2016" on http://maemo.org/vote/ |
| 10:30.38 | L29Ah | meh ok, screw it then |
| 10:30.59 | DocScrutinizer05 | ohmy |
| 10:30.59 | L29Ah | i sell my vote for 0.01฿ |
| 10:31.18 | Pali | freemangordon: can you put on top of it all camera patches? |
| 10:31.35 | DocScrutinizer05 | council should put this on their agenda, to investigate solutions |
| 10:34.49 | DocScrutinizer05 | I have a very hard time to see how TOR exit nodes, when not blocked, could DDoS random pages of tmo by mass *reading* them :-( |
| 10:35.24 | DocScrutinizer05 | I easily can see how this is a fair bit of work to fix this in vBuletin |
| 10:37.50 | DocScrutinizer05 | stopforumspam is maybe nice, but only when used in a reasonable way |
| 10:38.09 | freemangordon | Pali: that's the idea |
| 10:38.20 | freemangordon | Pali: will take me some time though |
| 10:38.52 | freemangordon | so, once I have cameras working with that, I'll send a RFC patchset |
| 10:40.06 | DocScrutinizer05 | (spam) so the right concept would be to only block regiatration/login via stopforumspam blacklicsts, and handle all DDoS attacks by more generic means, e.g. in the firewals |
| 10:40.24 | DocScrutinizer05 | throttling, fail2ban, whatever |
| 10:41.10 | DocScrutinizer05 | in a post-snowden time it's a nogo to tell users they can't use TOR to *read* the forum |
| 10:42.09 | DocScrutinizer05 | L29Ah: I buy! |
| 10:42.31 | DocScrutinizer05 | unless that's BTC crrency |
| 10:43.42 | DocScrutinizer05 | silly GDR/USSR elections, we can chose one out of 6 who's NOT going to be council |
| 10:45.15 | KotCzarny | hmm, is there a tool similar to diff but smart enough to ignore whitespace, newlines etc in c code? |
| 10:45.25 | L29Ah | sure it's btc |
| 10:46.00 | ceene | you can use indent first |
| 10:46.10 | DocScrutinizer05 | if others had pondered my suggestion to have 5 "nobody" on every candidate list too, this would be more fun |
| 10:46.24 | KotCzarny | ceene, but without pre-processing? |
| 10:46.39 | KotCzarny | because i know i can tidy the files, but then i will lose some info |
| 10:46.41 | L29Ah | wtf karma |
| 10:46.48 | DocScrutinizer05 | hmm? |
| 10:46.55 | ceene | what info will you lose? |
| 10:46.59 | L29Ah | can i just reg a ton of bots to earn karma for me and my clones and be done? |
| 10:47.08 | KotCzarny | formatting, timestamps |
| 10:47.11 | DocScrutinizer05 | yes |
| 10:47.35 | L29Ah | startforumspam party |
| 10:47.35 | DocScrutinizer05 | thanksbots will go a long way |
| 10:48.06 | ceene | there's nothing that does that i think... maybe some statistical analysis tool |
| 10:48.08 | DocScrutinizer05 | but actualy wikiedits work great too |
| 10:48.10 | DocScrutinizer05 | ;-) |
| 10:48.27 | DocScrutinizer05 | ooh, my ignorelist |
| 10:48.46 | *** join/#maemo zap_ (~zap@178.130.40.87) |
| 10:49.27 | KotCzarny | ceene, if there is a tool that tidies code without touching the files to find which parts of the code changed |
| 10:49.57 | KotCzarny | it would be not that hard to write for c/c++ syntax |
| 10:50.32 | ceene | maybe clang has something like that |
| 10:50.54 | KotCzarny | ie. 'if things are in "" dont touch, else s/[ \n]+/ /' |
| 10:51.39 | KotCzarny | and maybe s/[\(\)\{\}]/ \1 / first |
| 10:51.53 | ceene | i still think indent is the way |
| 10:52.14 | ceene | my code doesn't change almost anything when passed through indent |
| 10:52.18 | KotCzarny | yes, that would work if diff could do it without touching the files |
| 10:53.05 | KotCzarny | maybe i'll just pass things through indent/diff as a hinter for changes |
| 10:53.05 | DocScrutinizer05 | there are quite a few options in diff already |
| 10:53.25 | DocScrutinizer05 | to ignore spaces, treat tabs and spaces alike, etc |
| 10:55.03 | DocScrutinizer05 | after all diff been written by c-coders, with c and git in mind |
| 10:55.07 | KotCzarny | simplest case: |
| 10:55.11 | KotCzarny | if() |
| 10:55.14 | KotCzarny | {do something} |
| 10:55.22 | KotCzarny | vs if() {do something} |
| 10:55.28 | DocScrutinizer05 | not really optimized for python, but should deal with c formatting |
| 10:55.31 | DocScrutinizer05 | ;-P |
| 10:57.20 | Pali | or: do_something if cond; |
| 10:57.21 | Pali | :D |
| 10:57.42 | DocScrutinizer05 | L29Ah: council can't fix bugs, but they can coordinate bugfixing and have a loud saying in maemo administration at large |
| 10:58.06 | KotCzarny | pali, well, that's an overkill |
| 11:03.54 | DocScrutinizer05 | thinks BTC are like Talents, which were ~30kg silver |
| 11:05.40 | DocScrutinizer05 | >>Ein Talent war generell in 60 Minen unterteilt. [...] Das Gewicht einer Mine betrug in der Zeit des Peloponnesisches Krieges ca. 430 Gramm<< https://de.wikipedia.org/wiki/Mine_(Münze) |
| 11:06.53 | DocScrutinizer05 | >>Ein typisches Segelschiff kostete ein Talent<< |
| 11:07.41 | DocScrutinizer05 | >>Marcus Licinius Crassus, der als reichster Römer zur Zeit Gaius Iulius Caesars gilt, hatte am Ende seines Lebens ein Vermögen von 7100 Talenten.<< |
| 11:08.45 | M4rtinK | So you can say "Romans had Talent" ? ;-) |
| 11:10.34 | DocScrutinizer05 | *many* :-D |
| 11:12.28 | L29Ah | oh there is combining "||" |
| 11:12.32 | L29Ah | B⦠|
| 11:12.45 | DocScrutinizer05 | some romans had many talents, many romans had some talents, no roman had no little fraction of talent ;-D |
| 11:13.24 | DocScrutinizer05 | L29Ah: gIbBerISh |
| 11:14.27 | DocScrutinizer05 | ฿B⦠|
| 11:14.59 | DocScrutinizer05 | http://wstaw.org/m/2016/04/24/plasma-desktopGn2219.png |
| 11:16.06 | DocScrutinizer05 | checks if xchat still alive ;-P |
| 11:35.54 | DocScrutinizer05 | uses the general rule of "don't use special chars like ⬠or B⦠or whatever, when you're not in control of the rendering" |
| 11:36.16 | DocScrutinizer05 | uses e.g EUR instead |
| 11:36.46 | DocScrutinizer05 | doesn't even use ö in 'joerg' |
| 11:38.07 | DocScrutinizer05 | some exception: |
| 11:38.12 | DocScrutinizer05 | â |
| 11:38.30 | DocScrutinizer05 | time for more â |
| 11:38.54 | DocScrutinizer05 | 12 648 430 |
| 11:39.17 | DocScrutinizer05 | ~0xc0ffee * 1 |
| 11:39.33 | DocScrutinizer05 | ~ping |
| 11:39.33 | infobot | 1 packet transmitted, 1 packet received, 0.0% packet loss |
| 11:39.41 | DocScrutinizer05 | ~useless |
| 11:39.41 | infobot | ACTION starts crying and hides from docscrutinizer05 in the darkest corner of the room. :( |
| 11:40.12 | DocScrutinizer05 | ~0xff * 2 |
| 11:40.27 | DocScrutinizer05 | ~#ff * 2 |
| 11:40.38 | DocScrutinizer05 | ~ffh * 2 |
| 11:40.46 | DocScrutinizer05 | ~0ffh * 2 |
| 11:47.07 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:0:decf:5ea9:e960:80dc) |
| 12:07.23 | *** join/#maemo dafox (~dafox@2a02:a448:c25a:0:decf:5ea9:e960:80dc) |
| 12:17.20 | DocScrutinizer05 | [notice] >>The voting period for the specified election starts on 2016-04-25 00:00:00 (UTC) and ends on 2016-05-01 23:59:59 (UTC). It is not possible to vote now.<< |
| 12:17.57 | DocScrutinizer05 | so voting starts in a little less than 10 hours |
| 12:18.20 | DocScrutinizer05 | the wiki is not correct |
| 12:19.59 | *** join/#maemo krnlyng (~liar@178.112.149.181.wireless.dyn.drei.com) |
| 12:20.15 | ceene | who should I vote? |
| 12:20.51 | DocScrutinizer05 | the question rather is who is the one you don't vote for ;-D |
| 12:21.01 | ceene | ok |
| 12:21.11 | ceene | so who shall be punished with my indiference? |
| 12:21.16 | DocScrutinizer05 | 5/6 will become council |
| 12:21.37 | KotCzarny | ceene: do a coin toss |
| 12:22.01 | DocScrutinizer05 | ceene: that's really up to you. I'd try to keep out the one who demonstrated poorest understanding of what council is all about |
| 12:23.04 | ceene | DocScrutinizer05: i don't understand what council is all about |
| 12:23.05 | DocScrutinizer05 | where in my book council is NOT: governance and leadership |
| 12:23.06 | ceene | so there's that... |
| 12:23.21 | KotCzarny | secretary/paper work |
| 12:23.26 | DocScrutinizer05 | council is a secretary/steward |
| 12:23.45 | DocScrutinizer05 | no leader |
| 12:24.38 | DocScrutinizer05 | also council is not about development or technical administration, but rather for moderation and coordination, in worst case delegation/assignment |
| 12:26.48 | DocScrutinizer05 | council for example should take care (or delegate task) to grant upload rights to repos, and worst case - in case something goes awry - remove packages from repos. For this a bit of general technical understanding would help |
| 12:27.50 | DocScrutinizer05 | right now council should take care about that very unfortunate TOR blocking on tmo, inquire suggestions for solutions and coordinate their evaluation and implementation |
| 12:28.30 | ceene | it sounds it all like a hassle :) |
| 12:28.59 | DocScrutinizer05 | for this also some technical understanding helps, to discern sound arguments pro/contra some solution from excuses |
| 12:29.12 | DocScrutinizer05 | council is hassle |
| 12:30.38 | DocScrutinizer05 | the more when some council members have funny agenda like "I'll reach out to jolla now, demand council reviews their source code and approves if it complies with maemo spirit" or the like |
| 12:32.16 | DocScrutinizer05 | in this regard my general advice: don't vote patent lawyers into council! ;-P |
| 12:33.36 | ceene | :) |
| 12:55.23 | *** join/#maemo vakkov (~vakkov@ic-s221n13.brunel.ac.uk) |
| 13:00.28 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 13:06.28 | *** join/#maemo ArGGu^^ (~ArGGu^^@89.106.52.253) |
| 13:12.27 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 13:16.01 | ceene | there's a qt library for telegram |
| 13:16.03 | ceene | that's a good thing |
| 13:16.10 | ceene | at least i could reuse yappari as gui for that |
| 13:17.37 | DocScrutinizer05 | one more thin g that comes to mind for council: official adoption of devuan instead of debian for recommended maemo base |
| 13:18.21 | DocScrutinizer05 | I.E. an official recommendation to devels |
| 13:21.26 | DocScrutinizer05 | and I guess an inquiry to techstaff resp warfare and xes about expected lifecycle of server HDDs until preemtive service swap would be in order to |
| 13:22.07 | DocScrutinizer05 | s/ to/ too/ |
| 13:22.14 | DocScrutinizer05 | dang |
| 13:22.43 | DocScrutinizer05 | s/ to$/ too$/ |
| 13:23.22 | luke-jr | ceene: last I checked you can't even really build telegram sanely |
| 13:23.34 | luke-jr | it requires a bunch of patches to other libraries |
| 13:23.40 | DocScrutinizer05 | ouch |
| 13:23.43 | ceene | :( |
| 13:23.54 | ceene | https://github.com/Kaffeine/telegram-qt |
| 13:23.58 | ceene | i was thinking about this |
| 13:24.12 | ceene | seems to support qt4 |
| 13:25.03 | ceene | although now that you say it, i don't know if it's an implementation of telegram or |
| 13:25.06 | ceene | argh |
| 13:25.08 | ceene | or just its bindings |
| 13:25.38 | ceene | i think it's a full implementation |
| 13:27.15 | DocScrutinizer05 | well, check if the lib you want to use actually depends on patches in other libs |
| 13:27.54 | DocScrutinizer05 | if so, you might need to "import" and rename those libs too |
| 13:28.41 | DocScrutinizer05 | -Dtelegram-glibc ;-P |
| 13:29.23 | ceene | it seems to be compiling just fine on scratchbox |
| 13:29.28 | ceene | oops |
| 13:29.28 | DocScrutinizer05 | sounds like the perfect candidate for static linking |
| 13:29.30 | ceene | except for this |
| 13:29.33 | ceene | Utils.cpp:42: error: integer constant is too large for 'long' type |
| 13:29.46 | DocScrutinizer05 | LOL |
| 13:29.50 | ceene | what the |
| 13:29.55 | DocScrutinizer05 | hehehehe |
| 13:29.58 | ceene | static const quint64 s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); |
| 13:30.04 | ceene | quint64 |
| 13:30.10 | DocScrutinizer05 | ROTFL |
| 13:30.24 | KotCzarny | good one |
| 13:30.31 | KotCzarny | almost as good as debian's rng |
| 13:30.52 | DocScrutinizer05 | "how to make your implementation platform-dependent" |
| 13:31.02 | ceene | ok, someone explain me why quint64 is not 64 bits long |
| 13:31.10 | DocScrutinizer05 | hehehehe |
| 13:31.24 | DocScrutinizer05 | wtf *is* quint64? |
| 13:31.39 | DocScrutinizer05 | #define quint64 long |
| 13:31.41 | DocScrutinizer05 | ? |
| 13:31.43 | ceene | from https://doc.qt.io/archives/qtextended4.4/qtglobal.html |
| 13:31.49 | ceene | typedef quint64 |
| 13:31.50 | ceene | Typedef for unsigned long long int (unsigned __int64 on Windows). This type is guaranteed to be 64-bit on all platforms supported by Qt. |
| 13:31.52 | ceene | Literals of this type can be created using the Q_UINT64_C() macro: |
| 13:31.55 | ceene | <PROTECTED> |
| 13:32.18 | ceene | i don't think their concept of "guaranteed" is the same as mine |
| 13:32.44 | DocScrutinizer05 | wonnders how to find a new word for ROTFL |
| 13:33.24 | ceene | ok, so all of qt is broken on maemo |
| 13:33.35 | DocScrutinizer05 | s/on maemo// |
| 13:33.38 | ceene | :) |
| 13:33.48 | ceene | so... |
| 13:33.54 | ceene | how do i fix that? |
| 13:34.03 | ceene | patch whole qt? |
| 13:34.08 | ceene | use inttypes.h |
| 13:34.14 | ceene | uint64_t |
| 13:34.24 | DocScrutinizer05 | maybe fix this one silly const? |
| 13:34.34 | DocScrutinizer05 | use strcmp()? |
| 13:34.50 | DocScrutinizer05 | or whatever |
| 13:35.42 | ceene | #include <inttypes.h> |
| 13:35.42 | ceene | static const uint64_t s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); |
| 13:35.45 | ceene | Utils.cpp:43: error: integer constant is too large for 'long' type |
| 13:35.51 | ceene | so |
| 13:35.55 | ceene | what's the thing that is broken? |
| 13:36.00 | ceene | maemo's glibc? |
| 13:36.20 | DocScrutinizer05 | doesn't grok s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); at all |
| 13:36.49 | DocScrutinizer05 | is s_hardcodedRsaDataFingersprint() a function or what? |
| 13:36.49 | ceene | i don't care about the meaning, at least now |
| 13:36.57 | ceene | i wanna know why uint64_t is not 64 bits long |
| 13:37.31 | *** join/#maemo pcfe (~pcfe@2a02:8109:8080:fa4:beee:7bff:fed9:8f1b) |
| 13:37.32 | ceene | i believe that's something from openssl |
| 13:37.34 | DocScrutinizer05 | I wanna know if the result/return of s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21) is 64bit at all |
| 13:37.34 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 13:38.44 | DocScrutinizer05 | aaah typecast? |
| 13:39.07 | ceene | $ rgrep s_hardcodedRsaDataFingersprint telegram-qt/ |
| 13:39.07 | ceene | telegram-qt/telegram-qt/Utils.cpp:static const quint64 s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); |
| 13:39.10 | ceene | telegram-qt/telegram-qt/Utils.cpp: result.fingersprint = s_hardcodedRsaDataFingersprint; |
| 13:39.13 | ceene | i |
| 13:39.14 | ceene | don't |
| 13:39.15 | ceene | know |
| 13:40.04 | ceene | google search for s_hardcodedRsaDataFingersprint only returns this very same source code |
| 13:40.07 | ceene | lol |
| 13:40.35 | DocScrutinizer05 | it needs to have a definintion/implementation somewhere, no? |
| 13:40.44 | ceene | i guess so |
| 13:41.26 | DocScrutinizer05 | my c(++) foo is extremely weak |
| 13:42.24 | DocScrutinizer05 | I don't understand what's the real meaning of the whole sourcode line static const quint64 s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); |
| 13:42.56 | DocScrutinizer05 | I'd expect sth like static const quint64 s_hardcodedRsaDataFingersprint = 0xc3b42b026ce86b21; |
| 13:43.56 | ceene | yep |
| 13:44.20 | *** join/#maemo zZap-X (~zZap-X@gateway/vpn/privateinternetaccess/zzap-x) |
| 13:44.39 | ceene | but |
| 13:44.42 | ceene | if quint64 |
| 13:44.45 | ceene | is not a basic type |
| 13:44.49 | ceene | but an object |
| 13:44.50 | DocScrutinizer05 | but a macro |
| 13:44.55 | ceene | nope, a c++ object |
| 13:44.58 | ceene | so |
| 13:44.59 | DocScrutinizer05 | or an object, yes |
| 13:45.04 | ceene | it's defining a object named s_hardcodedRsaDataFingersprint |
| 13:45.10 | ceene | initialized with 0xc3b42b026ce86b21 |
| 13:45.20 | DocScrutinizer05 | and hands the value to the constructor |
| 13:45.26 | ceene | that's right |
| 13:45.36 | ceene | so it'd be equivalent to static const uint64_t s_hardcodedRsaDataFingersprint = 0xc3b42b026ce86b21; |
| 13:46.12 | DocScrutinizer05 | but then the object needs definition/imlementation somewhere |
| 13:46.29 | ceene | quint64 is defined by qt |
| 13:46.38 | DocScrutinizer05 | aah |
| 13:46.38 | ceene | so that's just creating a quint64 object named s_hardcodedRsaDataFingersprint |
| 13:46.44 | DocScrutinizer05 | yep |
| 13:46.58 | ceene | there |
| 13:46.58 | ceene | solved |
| 13:46.59 | DocScrutinizer05 | so check the qint64 object implementation |
| 13:47.10 | ceene | s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21); -> s_hardcodedRsaDataFingersprint(0xc3b42b026ce86b21ULL); |
| 13:47.13 | DocScrutinizer05 | quint64 even |
| 13:47.23 | ceene | it's a compiler thing |
| 13:47.27 | DocScrutinizer05 | ouch |
| 13:47.42 | ceene | ok |
| 13:47.43 | ceene | well |
| 13:47.47 | ceene | i got libTelegramQt.so.0.1.0 :) |
| 13:47.54 | ceene | it was confusing for a while |
| 13:47.59 | ceene | but if that's all that is needed... |
| 13:48.03 | ceene | it's a hell lot easy |
| 13:51.35 | ceene | there's even a testApp included |
| 13:51.40 | ceene | i'll test that later |
| 13:52.03 | ceene | or maybe now |
| 13:52.20 | DocScrutinizer05 | where could I find the definition of quint64? |
| 13:52.20 | ceene | i can't still login on whatsapp with libwa |
| 13:52.52 | ceene | ./Qt/qglobal.h |
| 13:53.53 | *** join/#maemo Sicelo (Sicelo@gets.high.on.ircspeed.net) |
| 13:53.53 | *** join/#maemo Sicelo (Sicelo@unaffiliated/sicelo) |
| 13:55.30 | DocScrutinizer05 | idly wonders what's the compiler's notion of type of 0xc3b42b026ce86b21, versus *ULL |
| 13:55.44 | DocScrutinizer05 | string? |
| 13:56.00 | Linkandzelda | would anyone be interested in a google authenticator maemo app? |
| 13:56.15 | DocScrutinizer05 | errr |
| 13:57.47 | DocScrutinizer05 | please elaborate, maybe it's just me who doesn't get it since I don't use google |
| 13:58.22 | Linkandzelda | various websites offer a 2 factor authentication system which uses an app called google authenticator |
| 13:58.33 | DocScrutinizer05 | aah |
| 13:58.40 | DocScrutinizer05 | that thing |
| 13:58.41 | ceene | this telegramapp may work indeed |
| 13:58.45 | Linkandzelda | its basically a key store which then gets run through thier algo to produce a timed number every 30 seconds |
| 13:59.10 | Linkandzelda | you get to scan a qr code containing the name/key |
| 13:59.15 | Linkandzelda | or enter name + key manually |
| 13:59.32 | DocScrutinizer05 | Linkandzelda: I bet many users would consider that useful |
| 13:59.35 | Linkandzelda | <PROTECTED> |
| 14:00.16 | ceene | i've never used that thing, but i'm sure it's used by many people |
| 14:00.31 | Linkandzelda | im not an expert on security or encryption though, not sure how to store the keys safely |
| 14:00.33 | *** join/#maemo zap_ (~zap@178.130.40.87) |
| 14:00.39 | DocScrutinizer05 | https://talk.maemo.org/showthread.php?t=84243 |
| 14:01.32 | Linkandzelda | yea i saw that |
| 14:01.49 | Linkandzelda | https://talk.maemo.org/showthread.php?t=90274 this too |
| 14:02.29 | DocScrutinizer05 | https://talk.maemo.org/showthread.php?t=90274 yep |
| 14:02.48 | Linkandzelda | though it may work, maybe something more user friendly would be good |
| 14:03.14 | DocScrutinizer05 | sure |
| 14:04.14 | Linkandzelda | i get annoyed having to enter those codes all the time, so speed and access is important |
| 14:04.28 | Linkandzelda | i dont know, it might be a good first n900 project for me |
| 14:04.53 | DocScrutinizer05 | (safely store) maybe with a different owner and read permissions only for that owner, so you need a sudo to that other owner to read the file? |
| 14:05.37 | Linkandzelda | could work, i could make them enter the password for that user on startup |
| 14:06.16 | Linkandzelda | would basically act like a master password or master unlock code |
| 14:06.57 | *** join/#maemo Sicelo (Sicelo@unaffiliated/sicelo) |
| 14:07.00 | DocScrutinizer05 | yep, or even start a process that communicates with your main process via IPC (pipe?) but changes effective user from beginning to access the file |
| 14:07.19 | Linkandzelda | not sure how to even do that, but yea i could try |
| 14:07.23 | Linkandzelda | was going to use python |
| 14:08.28 | *** join/#maemo pcfe (~pcfe@ip5b403641.dynamic.kabel-deutschland.de) |
| 14:08.32 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 14:09.20 | DocScrutinizer05 | hmm, make the process be member of a unique group "gauth" and the file is owned by gauth and only group-readable for gauth |
| 14:16.27 | DocScrutinizer05 | implementing some obfuscation otoh is considered pretty useless and user-hostile |
| 14:17.26 | DocScrutinizer05 | when a rogue process already took over the system so it may read the file, then it also may read the program text of the app and find out how to decode the obfuscated key |
| 14:18.00 | DocScrutinizer05 | this sdoesn't apply when you use proper encryption that needs manual entry of the decryption key |
| 14:19.26 | DocScrutinizer05 | this would be another viable approach: decrypt the stored key at boottime, by entering the decryption key |
| 14:19.43 | DocScrutinizer05 | then keep the decrypted key in RAM in a var |
| 14:21.39 | *** join/#maemo yasnothil (yasnothil@2600:3c03::f03c:91ff:fe55:c675) |
| 14:24.46 | Sicelo | ceene: sounds like you're officially killing Whatsapp on N900? |
| 14:25.00 | DocScrutinizer05 | sec-hardcore folks will argue you should not keep such stuff in RAM, so not even root may reed it out. It's arguable |
| 14:25.23 | Sicelo | ceene: in favor of telegram? |
| 14:25.52 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 14:26.15 | ceene | Sicelo: i'm not doing anything yet |
| 14:26.24 | ceene | but i'm searching for a plausible alternative |
| 14:26.35 | ceene | in fact i'm right now trying to get libwa to login |
| 14:26.41 | ceene | by making it emulate Android instead of S40 |
| 14:26.43 | ceene | just in case... |
| 14:26.47 | ceene | yowsup does that and it works |
| 14:26.49 | Sicelo | okay :) |
| 14:26.51 | ceene | so why the hell can't i |
| 14:27.16 | ceene | this telegram thingie looks promising, though |
| 14:27.32 | zZap-X | can yowsup run on a n900? |
| 14:27.48 | ceene | maybe, yes |
| 14:27.51 | zZap-X | ace |
| 14:27.54 | ceene | it depends on python2.7 or better 3 |
| 14:28.07 | Sicelo | yesterday i was thinking about telegram: it has a public API, right? |
| 14:28.22 | ceene | yes, telegram is much free than whatsapp |
| 14:28.37 | zZap-X | how about this running on a n900 https://whispersystems.org/ |
| 14:28.56 | ceene | don't know |
| 14:30.16 | zZap-X | this might be useful https://github.com/mgp25/Chat-API |
| 14:31.21 | ceene | i know about that |
| 14:32.14 | zZap-X | even whatsapp-purple is dead :( |
| 14:32.24 | zZap-X | was using that with bitlbee |
| 14:34.19 | *** join/#maemo RedW (~redw@89-76-164-87.dynamic.chello.pl) |
| 14:34.26 | *** join/#maemo pcfe (~pcfe@ip5b403641.dynamic.kabel-deutschland.de) |
| 14:34.29 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 14:37.45 | *** join/#maemo Cor-Ai (~cor-ai@c-7597e355.06-922-7570702.cust.bredbandsbolaget.se) |
| 14:44.38 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 14:52.16 | ceene | this piece of shit won't login |
| 15:03.28 | *** join/#maemo at1as (~at1as@24-231-230-53.static.trcy.mi.charter.com) |
| 15:04.52 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 15:20.20 | *** join/#maemo kabouik1 (~Kabouik@106.16.88.79.rev.sfr.net) |
| 15:21.05 | *** join/#maemo kabouik2 (~Kabouik@65.76.93.92.rev.sfr.net) |
| 15:27.01 | *** join/#maemo RedM (~redw@89-76-164-87.dynamic.chello.pl) |
| 15:38.03 | *** join/#maemo Sicelo009N (~sicelo@unaffiliated/sicelo) |
| 15:50.17 | *** join/#maemo freemangordon_ (~ivo@46.249.74.23) |
| 15:55.58 | *** join/#maemo freemangordon_ (~ivo@46.249.74.23) |
| 15:57.12 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 15:58.39 | *** join/#maemo HRH_H_Crab (~crab@kowloontong.dim-sum.org) |
| 16:15.30 | *** join/#maemo realitygaps (~realityga@unaffiliated/realitygaps) |
| 16:15.37 | *** part/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 16:24.04 | *** join/#maemo L29Ah (~L29Ah@cl-154.led-01.ru.sixxs.net) |
| 16:37.54 | *** join/#maemo vakkov (~vakkov@s3n104.brunel.ac.uk) |
| 16:42.38 | *** join/#maemo krnlyng (~liar@178.112.210.237.wireless.dyn.drei.com) |
| 16:42.53 | *** join/#maemo trumee (~trumee@c-50-175-121-86.hsd1.tx.comcast.net) |
| 16:51.02 | *** join/#maemo kabouik (~Kabouik@65.76.93.92.rev.sfr.net) |
| 16:51.32 | *** join/#maemo futpib_ (~futpib@176.212.188.15) |
| 17:31.31 | *** join/#maemo vakkov (~vakkov@ic-s221n13.brunel.ac.uk) |
| 18:18.35 | *** join/#maemo pcfe (~pcfe@ip5b403641.dynamic.kabel-deutschland.de) |
| 18:18.39 | *** join/#maemo pcfe (~pcfe@redhat/pcfe) |
| 18:27.58 | *** join/#maemo xelo (~xelo@ip-176-198-129-195.hsi05.unitymediagroup.de) |
| 18:42.58 | ceene | i don't know what the fuck is wrong |
| 18:43.12 | ceene | i can't keep reading code in search of the truth |
| 18:43.21 | ceene | and i can't find anything that is different or wrong |
| 18:44.41 | L29Ah | sounds like a rock song |
| 18:45.48 | ceene | i also hate all the other WA coders |
| 18:45.56 | ceene | except for cepiperez, who has helped me before |
| 18:46.03 | ceene | but i think he lost his phone |
| 18:46.05 | ceene | and has no compouter |
| 18:46.08 | ceene | or something like that |
| 18:46.47 | L29Ah | Machinae Supremacy - Stand |
| 18:48.04 | ceene | i'm gonna try now chat-api instead of yowsup |
| 18:48.10 | ceene | to see if i can debug it somehow |
| 18:48.13 | ceene | and find differences |
| 18:59.56 | *** join/#maemo sicelo (~sicelo@unaffiliated/sicelo) |
| 19:14.16 | *** join/#maemo florian (~fuchs@Maemo/community/contributor/florian) |
| 19:21.24 | ceene | nobody here can help |
| 19:21.28 | ceene | i wonder |
| 19:21.36 | ceene | who are all those 170 people who never say even hi... |
| 19:21.56 | KotCzarny | ~~california hotel theme jingles in~~ |
| 19:22.18 | ceene | KotCzarny: you can code |
| 19:22.21 | ceene | help me! |
| 19:22.21 | ceene | :P |
| 19:22.32 | KotCzarny | i can code, but i hate c++ a bit |
| 19:22.35 | ceene | so do i |
| 19:22.46 | ceene | but you don't really need to code anything |
| 19:22.52 | ceene | just help me understand what's wrong |
| 19:22.57 | ceene | compare with other implementations |
| 19:22.59 | KotCzarny | task #1: RE the login protocl (in plain c or python) |
| 19:23.05 | KotCzarny | ignore everything else |
| 19:23.05 | ceene | and tell me why the heck this thing won't work |
| 19:23.10 | Sicelo | ceene: i had offered :) |
| 19:23.20 | ceene | that's true |
| 19:23.21 | KotCzarny | just make some proof of code that can login |
| 19:23.27 | ceene | i dind't get back to you |
| 19:23.28 | Sicelo | of course i can't code anything .. so maybe KotCzarny might be better |
| 19:23.39 | ceene | KotCzarny: that code already exists |
| 19:23.43 | ceene | written in python |
| 19:23.47 | ceene | but it's there |
| 19:23.48 | ceene | and it works |
| 19:23.52 | ceene | yowsup |
| 19:23.55 | KotCzarny | ceene: rewrite from scratch in c |
| 19:24.01 | KotCzarny | outside of anything |
| 19:24.06 | ceene | it's not that easy |
| 19:24.09 | KotCzarny | just rewrite and add logging everywhere |
| 19:24.12 | ceene | because |
| 19:24.13 | ceene | first step |
| 19:24.17 | ceene | is rewritting token translation |
| 19:24.30 | ceene | protocol is basically xmpp |
| 19:24.33 | KotCzarny | k, step pre#1: rewrite token translation |
| 19:24.39 | ceene | with keywords replaced by binary code |
| 19:24.46 | KotCzarny | dont try c++. just plain c. |
| 19:25.02 | KotCzarny | if it works, you will have a starting point |
| 19:25.25 | ceene | i don't want to reimplement all of that :s |
| 19:25.30 | ceene | that's why i'm trying to use libwa |
| 19:25.48 | ceene | i understand your reasoning |
| 19:25.52 | ceene | but it's daunting |
| 19:26.07 | KotCzarny | debugging someone's other code could be much worse |
| 19:26.27 | ceene | in either case |
| 19:26.28 | ceene | i have to do that |
| 19:26.34 | ceene | because reimplementing that |
| 19:26.39 | ceene | means having to read python or php code |
| 19:26.42 | ceene | and translate it to c |
| 19:26.57 | ceene | so... why not go directly to the implementation i need to fix? |
| 19:27.08 | KotCzarny | because qt. |
| 19:27.14 | ceene | qt is not the problem |
| 19:27.24 | ceene | login functions are 3 or 4 |
| 19:27.28 | ceene | which are not so big |
| 19:27.38 | ceene | so why the fuck do they not work |
| 19:27.39 | ceene | :'( |
| 19:27.49 | KotCzarny | because there is a bug somewhere |
| 19:28.03 | KotCzarny | but you cant pinpoint the exact location in the flow |
| 19:28.59 | ceene | i can also try with whatsapp-purple |
| 19:29.03 | ceene | it's only c++, without qt |
| 19:29.34 | KotCzarny | so if you dont want rewriting, you will have to do it step by step in some existing app |
| 19:29.53 | ceene | i hate it all |
| 19:36.33 | KotCzarny | nite nite |
| 19:39.00 | ceene | ok |
| 19:39.03 | ceene | let's change approach |
| 19:39.07 | ceene | forget about libwa |
| 19:39.10 | ceene | it's a piece of shit |
| 19:39.18 | ceene | i need to implement axolotl on yappari |
| 19:39.31 | ceene | my yappari version right now logins in |
| 19:39.40 | ceene | it's only missing encryption |
| 19:39.57 | ceene | i don't understand anything, yappari and libwa is basically the same code |
| 19:54.03 | *** join/#maemo IANUS (~Matthew@host86-176-173-62.range86-176.btcentralplus.com) |
| 20:00.17 | *** join/#maemo IANUS (~Matthew@host86-176-173-62.range86-176.btcentralplus.com) |
| 20:25.02 | *** join/#maemo keithzg_ (~quassel@198-48-129-100.cpe.pppoe.ca) |
| 20:27.12 | ceene | by the way |
| 20:27.15 | ceene | all WA implementations |
| 20:27.21 | ceene | are stupid in at least one way |
| 20:27.28 | ceene | in the same stupid way |
| 20:27.44 | ceene | <PROTECTED> |
| 20:27.46 | ceene | <PROTECTED> |
| 20:27.50 | ceene | etc, etc |
| 20:27.55 | ceene | with dozens of comparisons like that |
| 20:28.03 | ceene | when tag has been converted from a dictionary |
| 20:28.17 | ceene | so why the hell is there a need to decode that? |
| 20:28.26 | ceene | switch(dict[tag]) |
| 20:28.38 | ceene | case dict["stream_error"] |
| 20:28.44 | ceene | case dict["stream:features" |
| 20:28.46 | ceene | etc, etc |
| 20:28.51 | ceene | well, switch(tag) directly |
| 20:29.05 | ceene | that should be a hell lot faster |
| 20:29.16 | ceene | at least there wouldn't be dozens of strings comparisons |
| 20:29.27 | ceene | not to speak of O(1) search |
| 20:30.00 | ceene | https://www.youtube.com/watch?v=i3dY6aCUe9Y |
| 20:37.25 | *** join/#maemo vakkov (~vakkov@fh-s225n10.brunel.ac.uk) |
| 21:08.21 | Maxdamantus | Why would `switch` on strings have an O(1) search? |
| 21:09.08 | Wizzup | Maxdamantus: can be hash table like |
| 21:09.28 | Wizzup | like a python 'string switch': {'a': foo(), 'b': bar()}['a'] |
| 21:09.43 | Wizzup | actually, that is wrong |
| 21:09.48 | Wizzup | like a python 'string switch': {'a': foo, 'b': bar}['a']() |
| 21:09.50 | Wizzup | you get the idea |
| 21:10.24 | Maxdamantus | I doubt it's likely to do that. |
| 21:10.40 | Maxdamantus | Unless you actually have a large number of strings, it's going to be faster to just do the comparisons. |
| 21:11.09 | Maxdamantus | or if there are too many common prefixes. |
| 21:11.38 | Wizzup | I'm just suggesting a way it could be done |
| 21:11.42 | Wizzup | Not saying that it is doing that |
| 21:12.02 | Maxdamantus | hash functions are also O(n), not O(1). |
| 21:20.16 | *** join/#maemo l_bratch (~l_bratch@87.244.66.26) |
| 21:35.16 | ceene | read access to a dictionary is O(1) |
| 21:36.05 | ceene | this thing is receiving an index, say 7, translating 7 to say stream:error and then comparing stream:error with dozens of possible texts |
| 21:36.18 | ceene | why do that, when you can just switch(index) case 7 |
| 21:36.22 | ceene | that's O(1) |
| 21:36.34 | ceene | and not a back-and-forth mapping from hash to key and viceversa |
| 21:38.13 | Maxdamantus | Where do you get the 7 from? |
| 21:38.14 | Pali | Maxdamantus: there are hash functions which have access in O(1) |
| 21:39.08 | Pali | in worst case, not only approx |
| 21:39.57 | Maxdamantus | Sure. You can analyse the table and determine a unique set of character indices to compare. |
| 21:40.58 | Maxdamantus | eg, if you have `case "stream:error": ..; case "stream:features": ..`, you can determine that you only need to compare index 7 before checking that it matches the expected string. |
| 21:41.30 | Pali | yes, that "smart" compiler could do |
| 21:41.40 | Maxdamantus | (and create a jump table based on that single bit) |
| 21:42.15 | Maxdamantus | A compiler that smart would probably also do it with an if/else chain. |
| 21:42.53 | *** join/#maemo Cor-Ai (~cor-ai@c-7597e355.06-922-7570702.cust.bredbandsbolaget.se) |
| 21:53.01 | ceene | http://imgur.com/gL3tXTg |
| 21:53.11 | ceene | i've found this thing at my parents, from when i was little :) |
| 21:55.03 | DocScrutinizer05 | hihi, I once had to dealwith a 'smart' pascal compiler that for a >>var I : int16; case I of 1 : xfoo; -1 : ybar; end; << created a jump table of humble 32k words length |
| 21:55.56 | DocScrutinizer05 | well, at least it tried to, then segfaulted |
| 21:56.46 | DocScrutinizer05 | I had to redirect the compiler listing to printer, to find out which line it blew chunks |
| 21:56.49 | Maxdamantus | Although I'm suspicious of the test (since such tests are likely to trigger tangential compiler optimisations), a randomly generated 10k `if` table on strings seems to be about 10Ã faster than the equivalent `switch` table on a recent version of V8. |
| 21:57.24 | Maxdamantus | on an older version of Spidermonkey, the `switch` is about 6Ã faster, and on a newer version it's about the same. |
| 21:58.00 | kerio | ayy javascript lmao |
| 21:58.29 | Maxdamantus | but that should be enough information to be suspicious generally of picking some language feature over another language feature for performance reasons without actually having good reasons to. |
| 21:59.28 | Maxdamantus | https://gist.github.com/Maxdamantus/853b69b3bb900cad37c254a902b0ccc9 |
| 21:59.48 | Maxdamantus | input generated with: cat /dev/urandom | tr -dc 'a-zA-Z0-9 \n' | sed '/^\([^ ]\+\) \([^ ]\+\)$/!d' | head -10000 >input |
| 22:01.00 | ceene | i don't even know how to execute that thing |
| 22:01.43 | Maxdamantus | js genif.js <input >testif.js |
| 22:01.50 | Maxdamantus | js testif.js |
| 22:02.08 | Maxdamantus | node -e 'this.print = function(s){ console.log(s); }; require("./testif");' |
| 22:02.47 | ceene | only thing i've ever done on javascript is alert("This is a very cool web page") |
| 22:02.50 | Maxdamantus | where `js` is the program you can build from the gecko-dev/mozilla-central source tree. |
| 22:03.03 | ceene | i'll just believe you then :) |
| 22:03.32 | ceene | i agree that case vs if may not be faster |
| 22:03.57 | ceene | but i can't believe that arbitrary length string comparison is better than a look up table |
| 22:04.04 | ceene | when you already have that look up table |
| 22:05.05 | Maxdamantus | Should probably also try a preconstructed object. |
| 22:05.32 | ceene | https://wiki.archlinux.org/index.php/swap_on_video_ram |
| 22:05.41 | ceene | can this thing work on n900? |
| 22:08.13 | DocScrutinizer05 | no |
| 22:08.24 | ceene | oh :( |
| 22:08.30 | Maxdamantus | The actual map is a lot faster, indicating that the switch doesn't generate a hash table. |
| 22:08.38 | ceene | that's the kind of crazy thing that could have worked |
| 22:08.59 | Maxdamantus | (it gets different results though, since the map isn't ordered) |
| 22:09.12 | Maxdamantus | actually, it doesn't necessarily indicate that. |
| 22:09.42 | ceene | well, gotta go to sleep |
| 22:09.45 | ceene | night night! |
| 22:09.53 | DocScrutinizer05 | n8 |
| 22:31.12 | kerio | ceene: i don't think that our gpu has dedicated ram |
| 22:33.54 | *** join/#maemo ashley (~ashley@pluto.skizzerz.net) |
| 22:33.54 | *** join/#maemo ashley (~ashley@MediaWiki/Jack-Phoenix) |
| 22:50.43 | *** join/#maemo bredebid (~bredebid@es-217-129-26-160.netvisao.pt) |
| 23:07.18 | *** join/#maemo corvinux (~hashcore@unaffiliated/corvinux) |
| 23:23.32 | *** join/#maemo pagurus (~user@p548CAF18.dip0.t-ipconnect.de) |
| 23:46.45 | *** join/#maemo Venusaur (~wdwrwf@wikipedia/Antonio-Lopez) |
| 23:56.43 | *** join/#maemo salamisami (~Valle@a88-112-2-11.elisa-laajakaista.fi) |
