IRC log for #neo900 on 20190404

00:05.42*** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
00:05.42*** mode/#neo900 [+v DocScrutinizer05] by ChanServ
00:05.43*** join/#neo900 neo900 (~office@neo900/coreteam/joerg)
00:05.44*** mode/#neo900 [+v neo900] by ChanServ
00:32.00*** join/#neo900 him-cesjf (~cesjf@unaffiliated/himcesjf)
00:51.10*** join/#neo900 DocScrutinizer05 (~saturn@openmoko/engineers/joerg)
00:51.10*** mode/#neo900 [+v DocScrutinizer05] by ChanServ
00:51.18*** join/#neo900 neo900 (~office@neo900/coreteam/joerg)
00:51.18*** mode/#neo900 [+v neo900] by ChanServ
01:30.52*** join/#neo900 ArturShaik (~ArturShai@212.112.100.88)
03:21.42*** join/#neo900 gareth__ (sid240321@gateway/web/irccloud.com/x-ljemcoogyifhvswj)
05:09.09*** join/#neo900 chainsawbike (~chainsawb@unaffiliated/chainsawbike)
06:11.38*** join/#neo900 houkime (~houkime@gateway/tor-sasl/houkime)
06:11.55*** part/#neo900 houkime (~houkime@gateway/tor-sasl/houkime)
07:20.25*** join/#neo900 illwieckz (~illwieckz@unvanquished/developer/illwieckz)
07:42.29*** join/#neo900 _Chris_ (~Chris@p5DE1A6CD.dip0.t-ipconnect.de)
09:28.10*** join/#neo900 arm_guy (bdca4f06@gateway/web/freenode/ip.189.202.79.6)
09:53.06*** join/#neo900 Chris_ (~Chris@p5DE1AF73.dip0.t-ipconnect.de)
14:06.54*** join/#neo900 ossguy (~denver@conservancy/staff/ossguy)
14:46.32*** join/#neo900 Kabouik (~kabouik@2a01:e35:2fd3:5030:ebd:59c2:cdd:e2f8)
14:47.15*** join/#neo900 Szeraton (~Person@unaffiliated/guyperson)
15:15.01*** join/#neo900 dderby (~dderby@dynamic-186-31-169-206.dynamic.etb.net.co)
15:27.17clapontJoerg-Neo900: the specs are higher and higher to me, is something bad that I miss? all I'm interested in a modern phone is -given that I install LneageOS/variants- not to have hidden backdoors/trojans - like the LoJack firmware found in a large category of laptops' BIOSes (for Computrace it seems.. or not only?)
15:29.18clapontafaik, the Nexus 6 is the latest Motorola in US..  given the Huawei events on US/CA, I stay away of Huaway.. or Xiomi.. but still, I wish a modern phone
15:44.21*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
17:10.17*** join/#neo900 illwieckz (~illwieckz@unvanquished/developer/illwieckz)
18:01.48*** join/#neo900 how900 (~Neo900@vm8.ganeti.dyne.org)
18:01.48*** join/#neo900 how900 (~Neo900@neo900/coreteam/communications/how)
18:01.48*** mode/#neo900 [+v how900] by ChanServ
18:01.52*** join/#neo900 xmn (~xmn@user-0cdft2n.cable.mindspring.com)
18:08.14*** join/#neo900 himcesjf_ (~cesjf@unaffiliated/himcesjf)
18:48.18*** join/#neo900 pagurus (~user@i59F7A732.versanet.de)
20:28.34*** join/#neo900 wpwrak (~werner@196-163-231-201.fibertel.com.ar)
20:28.34*** mode/#neo900 [+v wpwrak] by ChanServ
20:29.17sixwheeledbeastDevices only need to be powerful enough to run the software they need. Times when less is more?
20:54.06Joerg-Neo900the problem is that any device meant to use the internet needs to be able to cope with what comes in to your device from this internet. I'll try to construct an example: when my email provider (not offering any other interface than webmailer. OK, let's just assume this to be the case) comes up tomorrow with news like >>we overhauled our web portal, all new, more shiny and much smarter<< but you find that this new webpage needs 10 times the
20:54.08Joerg-Neo900memory and also newest javascript features and your phone neither has that much memory nor is it compatible with those new JS functions... You're between a rock and a hard place.
20:54.09Joerg-Neo900Of course this webmailer example is made up and silly (is it?), but actually for example the maemo microB browser can't deal with most of the websites you find in web, anymore, since they are just too bloated for this browser to render them on this system with this amount of free RAM and CPU power
21:27.00Joerg-Neo900Neo900 approach to backdoors always been: For user to be sure there are no backdoors there, we use a completely FOSS "master" OS: Linux (or, if you like, any other "ROM" you trust and that is free for development of drivers), loaded, started by (and replacing instead of running under) an open bootloader that doesn't lend itself to Tivo-ization (locked bootloader) neither to any virtualization that runs your "master" OS as a sort of "VM" under
21:27.01Joerg-Neo900an invisible almighty hypervisor (the bootloader code/process). This leaves the "invisible second OS" on your phone: the firmware *inside* modem. For that we - unlike virtually all other projects with similar goals - do NOT rely / hope for any full audit of that firmware, since that never will fly in the end. Instead we consider the modem a backdoored rogue blackbox, to start with, and we rather sandbox and tightly monitor it comprehensively
21:27.03Joerg-Neo900and completely, so in one hand it can't do any harm to "us" and on the other hand we *notice* whenever it tries to do any such rogue activity. The latter is what makes Neo900 absolutely unique and way more practically useful than any simplistic hardware switches that not sandbox but bury the blackbox when engaged so you can't use the modem function, and when you need a modem you need to throw the switch and open up all the backdoors to your
21:27.04Joerg-Neo900system that the modem might have
21:33.09Joerg-Neo900the full modem firmware audit is an illusion and the hardware switch is a delusion ;-)
21:34.23Joerg-Neo900first can never be done and the latter will never do what you hope it would
21:38.31Joerg-Neo900.
21:39.16Joerg-Neo900hmm, I probably should put this tedious monologue ^^^ of mine to the Neo900 preamble ;-D
21:54.28*** join/#neo900 paul_boddie (~paul_bodd@host-37-191-184-62.lynet.no)
21:56.56paul_boddieWeb platform bloat is a really damaging thing that drives obsolescence. It's getting to the point where not even 1GB RAM is enough for some overdesigned "enter your name" Web sites.
21:57.31Joerg-Neo900yep
21:58.15paul_boddieI guess Google and Mozilla have the attitude that you just throw your hardware in the trash and buy new and shiny. Screw the planet, in other words.
21:58.29Joerg-Neo900it's driven by the "you need to exploit the 4 seconds of attention the average visitor is able to sustain" approach
21:59.11paul_boddieAnd you're being watched for all of those four seconds.
21:59.19Joerg-Neo900yep
22:01.48Joerg-Neo900the foundation problem of internet/WWW: til this very day the only proven-to-work method to monetize any service you offer is commercial ads to sell useless crap to visitors
22:02.50Joerg-Neo900alas this approach works so good it made google the #1 power on this planet, directly followed by facebook
22:03.27paul_boddieOr to target people on a personal level in order to corrupt democracy.
22:03.47paul_boddieFacebook makes a lot of money that way.
22:04.11Joerg-Neo900I don't know if it's a lucky fate or the worst detail in it that beither of both is really interested in accepting and using this power - yet
22:04.34Joerg-Neo900neither*
22:05.23Joerg-Neo900farcebook might have monetized it by leasing a tiny bit of it to Russia lately
22:05.25paul_boddieDifficult to know. Currently, such actors are useful idiots for more unpleasant interests.
22:13.35paul_boddieThinking about RAM provision, I guess it would be easier to get SBCs with 1GB RAM these days for prototyping a Neo900-like project. That BeagleBone variant seemed like an awkward thing to obtain.
22:15.26Joerg-Neo900sure. The whole idea of staying 100% code compatible to N900 has rapidly dwindled into oblivion and irrelevance. Including the use of an OMAP3 which been the only reason for BB-xM
22:16.44paul_boddieDo you know if there any off-the-shelf SBCs which are even close to fitting inside a N900 shell?
22:16.44Joerg-Neo900right now the i.MX8 probably is the only SoC you reasonably might pick for such a project
22:17.57Joerg-Neo900"SBC" is a very generic term. There are SBC that "fit under a postage stamp" ;-D
22:18.21paul_boddieWell, SBC in the required performance class, not ATmega. ;-)
22:18.44paul_boddieAlthough I'm sure someone could do an Arduinophone thing, too.
22:19.08Joerg-Neo900note that the BB-xM never been meant to "fit *into* a N900 case"
22:19.37Joerg-Neo900it's the SoC chip it's all about
22:19.57Joerg-Neo900and not even the OMAP4 would fit into N900 case
22:20.06paul_boddieNo, I understand that it drives the "solution" externally. Like some kind of donor hardware.
22:24.00paul_boddieI just wondered if we'd ever get to the point where the size of some generic, capable SBC was not an issue, but I guess especially the thickness is a huge factor.
22:24.41paul_boddieAnd where the generic board would need mating to another board, this would demolish the size budget.
22:26.43Joerg-Neo900yes, and also the "area" in a N900 is way more fragmented than you'd think on first guess. There is stuff like kbg, battery connector, camera, SIM holder cutout etc
22:27.04Joerg-Neo900kbd even
22:27.25paul_boddieYes, it's always interesting/horrifying to see things poked into different spaces.
22:29.25Joerg-Neo900needs to make some decisions about how to proceed. With the project, own carreer etc. Last remaining support/funding for Neo900 ended, and funding from own pocket is beyond feasibility
22:31.30varu:(
22:36.06paul_boddieIt's difficult, especially with a certain amount of competition for attention at the moment.
22:36.46paul_boddieIn the "people making phones" department, that is.
22:37.15Joerg-Neo900yeah sure
22:38.12paul_boddieThat fxtec thing looks a lot like a N900, for instance. Maybe they'll deliver, maybe not.
22:38.55paul_boddieIt would be nice to see a community-originating thing like Neo900 succeed, though. That's why I support it.
22:39.33paul_boddieIt being Neo900, of course. I don't follow random phone campaigns of which we know very little as potential customers.
22:43.44Joerg-Neo900it's a damn pity how Jolla failed on a very few core features like unbrickability and openness to tinkering with the system
22:44.34Joerg-Neo900they had all the resources to develop something really great
22:44.54Joerg-Neo900INCLUDING all the N900 experience
22:46.34paul_boddieThe Nokia mindset, maybe? That not locking the product down is somehow giving things away.
22:48.41Joerg-Neo900yeah, I see it like they just tried to create a successor to N9 while they better had focused on creating a successor to N900
22:51.56paul_boddieWell, I hope that the work that has gone into Neo900 can continue and/or lead to other things. All the documentation alone is more than we will ever have for other devices and projects.
22:52.11Joerg-Neo900from a OS perspective the Jolla was a N9-improved, made to run on a HAL which itself based on (closed) android of whatever hw platform they want
22:52.44Joerg-Neo900>>All the documentation alone<< indeed
22:54.05Joerg-Neo900a template to make any new community driven phone project a success, at least on the documentation level
22:57.14paul_boddieThe downside is that the audience able to make good use of it is rather small.
22:57.30paul_boddieOr it needs teams of people with a range of skills, just like with Neo900.
22:57.58Joerg-Neo900yes
22:58.50Joerg-Neo900I'm hoping for eventually some company realizing that they could buy in competence from Neo900 to completely cover that aspect
22:58.53paul_boddieI was moaning at someone recently about how it isn't enough to merely advocate Free Software on phones. There needs to be fundamental structural change in the way devices are developed.
22:59.24Joerg-Neo900:nod:
22:59.57paul_boddieBut like everything now, people want companies to solve all their problems.
23:00.20paul_boddieI do wonder who the fxtec people are, though.
23:00.43Joerg-Neo900how about a community of a few 1000s of users signing a petition to Samsung or whomever to build a device to specs they deliver
23:02.31Joerg-Neo900I think this could actually work if that company could overcome their first panic attack
23:04.29paul_boddieAnyway, it's getting late. I hope things start to become clearer about all of this. Keep up the good work, as always!
23:06.26paul_boddieBye for now!
23:32.01*** join/#neo900 him-cesjf (~cesjf@unaffiliated/himcesjf)
23:52.12*** join/#neo900 _whitelogger (~whitelogg@uruz.whitequark.org)
23:52.12*** mode/#neo900 [+v _whitelogger] by ChanServ

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.