IRC log for #neo900 on 20180218

00:09.29*** join/#neo900 knttl (~knttl@dyndsl-085-016-176-191.ewe-ip-backbone.de)
01:20.02*** join/#neo900 infobot (ibot@rikers.org)
01:20.02*** topic/#neo900 is http://neo900.org | CCCAMP15 lightning talks at http://neo900.org/stuff/cccamp15/ - major: http://neo900.org/stuff/cccamp15/ccc2015talk/neo900-wpwrak_CCC2015.webm | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900 | Welcome newest team member metacollin! https://neo900.org/news/neo900-update-2017-09-03
01:20.02*** mode/#neo900 [+v infobot] by ChanServ
02:02.04*** join/#neo900 illwieckz (~illwieckz@unvanquished/developer/illwieckz)
02:11.44JuestoDocScrutinizer05: is the production halted? which OSes has it been tested on? is the device itself finished?
02:12.20Joerg-Neo900we wait for layouter metacolin to finish layout of prot_v2
02:12.37Juestohow many prototypes it'll have?
02:12.54Juestois the first one not good?
02:13.30Joerg-Neo900Juesto: developing a design usually needs incremental evolutionary steps of prottypes
02:14.13Juestowell, still would like some insight on the first, Joerg-Neo900, such as what's the goal, how it turned out, pro and cons, etc
02:14.40Joerg-Neo900we got a proto_v1 fro mechanical stuff and modem testing, we are about to do proto_v2 and we hope to have a golden production-ready sample with proto_v3
02:15.39Joerg-Neo900there are photos of proto_v1 on tmo
02:16.26Juestohow many people are in it? how long did proto_v1 took?
02:18.52JuestoLink? is it difficult to find?
02:19.17JuestoAh used google
02:19.20Juestothink i found it
02:20.17Juestowelp, a bit too long to find :(
02:22.19Juestopage at least?
02:27.03Joerg-Neo900sorry, busy in a meeting
02:27.12Joerg-Neo900http://talk.maemo.org/showthread.php?t=91142
02:28.50Juestooops
02:29.07Juestoyeah found that thread
02:29.10Joerg-Neo900http://talk.maemo.org/showthread.php?p=1412240&highlight=proto#post1412240  around there somewhere
02:29.59Juestothanks
02:32.07*** join/#neo900 knttl (~knttl@dyndsl-091-096-022-190.ewe-ip-backbone.de)
02:50.11*** join/#neo900 xes (~xes@unaffiliated/xes)
04:27.33*** join/#neo900 Kabouik (~kabouik@ks3100825.kimsufi.com)
06:11.02*** join/#neo900 chomwitt (~chomwitt@2a02:587:dc08:a00:9d6c:1d0c:2780:b73f)
07:50.38*** join/#neo900 freemangordon (~ivo@46.249.74.23)
09:25.03*** join/#neo900 himcesjf_ (~himcesjf@unaffiliated/himcesjf)
09:33.14*** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali)
10:10.18*** join/#neo900 louisdk (~louisdk@5.103.138.205)
10:34.20*** join/#neo900 pkill9 (~pkill9@unaffiliated/pkill9)
11:30.05*** join/#neo900 cc_1 (~cc_laptop@2001:910:1033:0:56ee:75ff:fe00:97ac)
11:30.16cc_1hello people
11:30.18cc_1_o/
12:13.02enycmeows
12:13.27enyccc_1: iirc DocScrutinizer05 is awaiting the return of metacollin to complete layout work.. not sure exactly whtat else is goin on
12:25.16cc_1enyc: is he well health-wise ?
12:29.20*** join/#neo900 him-cesjf (~himcesjf@unaffiliated/himcesjf)
12:36.34*** join/#neo900 him-cesjf (~himcesjf@unaffiliated/himcesjf)
12:38.58enycdifferent people... different situations
12:39.06enyci got impression metacollin got some toher job
13:27.27*** join/#neo900 louisdk (~louisdk@5.103.138.205)
13:49.13sn0wmonstersadly, i don't think that's the case
13:49.28sn0wmonsteri think it's more to do with personal issues. we all run into them sometimes, the timing was just poor.
14:16.26*** join/#neo900 NitroNills (~User9@2001:4643:c45c:0:f846:ffd3:2453:2a1c)
14:29.46NitroNillsHow is it w/ metacollin - back in business?
14:56.03sn0wmonsternope, still MIA
15:16.24atkI also noticed
15:16.26*** join/#neo900 him-cesjf (~himcesjf@unaffiliated/himcesjf)
15:16.32atkFSF is funding some silly android phone
15:16.36atkwtf
15:17.10atkI've cancelled my membership recently because I would like to save up every little bit of cash I can for the next year or so
15:17.16atkso I don't have that leverage anymore
15:17.22atkI think I'll email them about this BS though
15:17.40atkthey have an android phone where presumably the baseband and the CPU are merged and share address space
15:17.41*** join/#neo900 xmn (~xman@user-0cdft2n.cable.mindspring.com)
15:17.50atkand they think that's "good enough"
15:18.14atkIf this boils down to the "can't replace the firmware because instructions aren't provided" BS then they're absolute plonkers
15:27.29sn0wmonsteratk, in all fairness, there are no legitimate options on the table
15:27.41sn0wmonsterthat doesn't excuse them for suggesting or supporting smoething though
15:28.22atksure, but I would say that the Neo900 is at least borderline better than the samsung phone they promote
15:29.08atkI mean, it's a different kind of niche all things considered
15:29.11sn0wmonsterfor security and privacy? probably
15:29.15sn0wmonsterfor the average end user? probably not
15:29.22sn0wmonsterthey need something *stupid* that works too
15:29.29sn0wmonsterby they i mean stupid people
15:29.50atkstupid is not quite right
15:29.59atkmore like not as privacy focused
15:30.09sn0wmonsterno i mean literally stupid people who dont understand how phones work
15:30.15sn0wmonsterand won't take the time to learn
15:30.22sn0wmonsterthose people aren't going to like a linuxy phone
15:30.26sn0wmonsterthey're going to want something apply
15:30.27atkI think most people don't understand how phones work, or do you mean how to use a phone?
15:30.30sn0wmonsterapple-y
15:30.38sn0wmonsterhow to use a phone properly yes
15:31.16atkWhat's maybe a more interesting thing than phones is cars these days.
15:31.45atkI wonder if FSF has anything to say about those
15:34.56atkand here's the other thing
15:35.14atkif they're interested in an appley phone, why are they pushing laptops which are borderline out of date at this point
15:35.59atkUnless something like the X220 with nerfed IME is on their RYF list
15:47.56sn0wmonsteri second your frustration
16:37.05*** join/#neo900 ctag_ (~ctag@user-24-214-210-2.knology.net)
16:44.21*** join/#neo900 threebar` (~user@pool-71-105-108-82.nycmny.fios.verizon.net)
16:44.21*** join/#neo900 threebar` (~user@unaffiliated/threebar)
16:51.29cc_1atk: are you talking about the purism phone ? or some replicant device ?
16:51.49atkno, it was a replicant device
16:52.43cc_1I'm surprised they are giving some money then
16:53.03cc_1with all nonfree software removed it's not even a phone
16:54.44atkWell yeah, they're keeping the baseband modem firmware
16:55.00atkthat's the caveat in the description iirc
16:55.05atklet me try to find the page
16:56.27cc_1I think replicant does not even try to hack some phones anymore
16:56.34cc_1they are working on tablets now
16:56.46cc_1because no GSM firmware
16:57.02atkhttps://www.fsf.org/givingguide/v6/
16:57.33atkSo it's not direct funding, but it's advertising and endorsement
16:57.42atkat least I don't think there's any direct funding
17:19.59cc_1oh I see
17:20.17cc_1yes that's because technoethic started selling those
17:33.22sixwheeledbeastLooks like they needed a device in production to tick the "smartphone" box on the website to me.
18:29.58Joerg-Neo900in all fairness, it's a "giving guide" - they need to list stuff that is available there
18:35.37sixwheeledbeastexactly the way I see it.
18:38.04Joerg-Neo900it's still a pathetic kob of FSF to not even mention Neo900
18:38.11Joerg-Neo900job*
18:41.02Joerg-Neo900except the >>  I am > strongly in favor of it, and I am willing to say so. Where and how > should I say so?<< in Mr Stallman's email
18:41.13Joerg-Neo900http://talk.maemo.org/showthread.php?p=1396903&highlight=stallman#post1396903
18:54.14Joerg-Neo900maybe somebody just needs to send RMS a email telling him to "according to your former email, please say so on FSF site"
19:29.33cc_1they won't speak of an unreleased product on the FSF site
20:08.51sicelodoes FSF know about Neo900?
20:30.49Juestoyes, it looks like?
20:31.06Juestogood question
20:34.05anon-we should draft a letter to the FSF to present the Neo900 as a better alternative to their current phone
20:34.24anon-FSF funding could make this project work
20:34.39Juestowhich phone?
20:35.06anon-"Tehnoetic S2 with Replicant" - see atk's link
20:36.51anon-also they need to understand the significance of their nonfree modem "caveat"
20:37.25Joerg-Neo900S2 prolly has modem separation
20:37.48Joerg-Neo900at least partially, not sure if they have shared RAM
20:53.24anon-that's not enough. the modem needs to be able to be turned off completely
20:55.46anon-I always take notice when I read an article where cell phone tracking was used in an investigation, so it's being used
20:56.00anon-all that is required is that the phone is connected to the network
20:57.11Joerg-Neo900sure thing. We're aware of that
20:58.00Joerg-Neo900but even RYF is not "Respects Your Privacy"
20:58.35Joerg-Neo900Freedom in the definition of FSF is strictly in a FOSS context
20:59.56Joerg-Neo900it doesn't *really* cover neither Security nor Privacy
21:01.34Joerg-Neo900the "fun" part in FSF's "RYF cert": they don't even have a means to certify a mere hardware provided to them without any software at all
21:01.43*** join/#neo900 wicket64 (~wicket@dynamic-186-29-252-175.dynamic.etb.net.co)
21:02.17Joerg-Neo900the whole RYF thing is sw-focused. A product consisting of hardware only doesn't exist for them
21:02.25anon-but even the software isn't free if they have the baseband processor in there
21:03.34anon-I don't think that technoethical is good either
21:03.56anon-they charge extreme prices for reflashing ebay hardware
21:04.14Joerg-Neo900let's send them a Samsung S2 and a Neo900, both without any software I.E erased storage, the ask for their assertion which is more appropriate to receive a RYF certification or any other approval
21:04.57Joerg-Neo900anon-: *nod* that is what I understood they do
21:30.10*** join/#neo900 pkircher_ (~pkircher@unaffiliated/pkircher)
21:43.47*** join/#neo900 pkircher_ (~pkircher@unaffiliated/pkircher)
22:01.30*** join/#neo900 wicket64 (~wicket@dynamic-186-29-108-231.dynamic.etb.net.co)
23:02.12*** join/#neo900 luke-jr (~luke-jr@unaffiliated/luke-jr)
23:53.29*** join/#neo900 _Chris_ (~Chris@p4FCA0BC3.dip0.t-ipconnect.de)

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