| 01:17.02 | *** join/#neo900 ashneo76 (~ashneo76@c-24-1-252-39.hsd1.il.comcast.net) |
| 01:29.16 | *** join/#neo900 merlin1991 (~merlin@Maemo/community/cssu/merlin1991) |
| 01:40.17 | *** join/#neo900 Humpelstilzchen (erik@f054183233.adsl.alicedsl.de) |
| 05:40.39 | *** join/#neo900 R0b0t1 (~realname@unaffiliated/r0b0t1) |
| 06:52.06 | R0b0t1 | DocScrutinizer05: nice @ sys-boot settings |
| 07:33.19 | *** join/#neo900 gr8 (~gr8@unaffiliated/gr8) |
| 07:33.28 | *** join/#neo900 paulk-aldrin (~paulk@armstrong.paulk.fr) |
| 07:34.10 | gr8 | hi, the Neo900 sounds awesome and it claims to care about my privacy. But what about radio triangulation? See https://en.wikipedia.org/wiki/Mobile_phone_tracking This is a major concern for me, in fact I don't use mobile phones for this reason. I guess the very same problem applies to the Neo900? Is it possible to disable the phone antenna and LTE and just use Wifi? |
| 07:34.53 | paulk-aldrin | gr8, I would say yes and yes |
| 07:57.30 | *** join/#neo900 ShadowJK (~jk@212.7.198.194) |
| 08:03.13 | enyc | gr8: yes, they very much make the point that the gsm/3g/lte modem is isolated and can't access cpu memory... |
| 08:06.31 | *** join/#neo900 PeperPots___ (sid1218@gateway/web/irccloud.com/x-ovlnbfegxowdpgji) |
| 08:14.08 | gr8 | enyc: uhm, what does that have to do with my question? Sorry I don't understand what you mean :) |
| 08:15.50 | *** join/#neo900 XDS2010 (sid1218@gateway/web/irccloud.com/x-ckclghxcrueddmlm) |
| 08:40.52 | gr8 | paulk-aldrin: how certain are you about that? |
| 08:41.52 | paulk-aldrin | gr8, enyc's answer is not particularely about triangulation, but is related |
| 08:42.14 | paulk-aldrin | gr8, you might want to read http://www.replicant.us/freedom-privacy-security-issues.php for an overview |
| 08:42.31 | paulk-aldrin | gr8, neo900 will be subject to triangulation |
| 08:42.53 | paulk-aldrin | but you should be able to disconnect the modem and antenna reliably |
| 08:42.54 | paulk-aldrin | by design |
| 08:43.05 | bencoh | (as any other gsm device) |
| 08:43.40 | bencoh | but it's still possible to poweroff the modem |
| 08:44.36 | *** join/#neo900 sparetire (~sparetire@unaffiliated/sparetire) |
| 08:44.36 | bencoh | and afaik they should implement some way to "monitor" it ("is it really off ?") |
| 08:49.00 | gr8 | brb |
| 08:49.01 | *** part/#neo900 gr8 (~gr8@unaffiliated/gr8) |
| 08:52.02 | *** join/#neo900 gr8 (~gr8@unaffiliated/gr8) |
| 09:30.04 | R0b0t1 | gr8: You can triangulate any radio. |
| 09:30.37 | R0b0t1 | gr8: On most phones, the modem is running software you do not control and is at a higher privilege level than the application processor. |
| 09:30.58 | paulk-aldrin | R0b0t1, it's not *always* at a higher privilege level |
| 09:31.01 | R0b0t1 | gr8: On the neo900, you can be certain that the radio is off when you turn it off and that it is not tampering with application memory. |
| 09:31.03 | paulk-aldrin | it's actually less common than we think |
| 09:31.16 | paulk-aldrin | it's the case on Qualcomm platforms, that are found on most Android phones, yes |
| 09:31.26 | paulk-aldrin | take any Samsung Exynos device, it's not the case |
| 09:31.38 | R0b0t1 | then how is it laid out? |
| 09:31.40 | paulk-aldrin | and those are pretty popular, too |
| 09:31.51 | paulk-aldrin | R0b0t1, see http://www.replicant.us/freedom-privacy-security-issues.php |
| 09:31.57 | paulk-aldrin | R0b0t1, modem is simply a peripheral |
| 09:32.07 | paulk-aldrin | often linked to the AP via USB-ish link, period |
| 09:32.15 | R0b0t1 | yeah I know how it works |
| 09:32.16 | R0b0t1 | oh okay |
| 09:32.41 | paulk-aldrin | it's usually the case when modem and AP are two different chips |
| 09:33.10 | paulk-aldrin | but the case where "modem boots the AP" is specific to Qualcomm and friends |
| 09:33.26 | paulk-aldrin | on Samsung galaxy devices, the AP has to send the modem its system image, for instance |
| 09:33.34 | paulk-aldrin | because the modem cannot access the storage itself |
| 09:33.59 | paulk-aldrin | R0b0t1, also, perhaps you heard about the Samsung Galaxy backdoor |
| 09:34.04 | paulk-aldrin | it's exactly a consequence of that |
| 09:34.43 | gr8 | paulk-aldrin: thanks for the link, it explains things well. I still have two questions: 1) which parts of the Neo900 are proprietary hardware or software? 2) "afaik they should implement some way to "monitor" it": what do you mean by "should" here, is that planned, and who is "they" btw? |
| 09:35.08 | paulk-aldrin | thanks! I wrote that hoping it would be useful :) |
| 09:35.10 | bencoh | the guys who work on the neo900 hw |
| 09:35.21 | paulk-aldrin | gr8, "they" would be DocScrutinizer05 |
| 09:35.35 | paulk-aldrin | he made a presentation about this |
| 09:35.59 | gr8 | is that presentation online? |
| 09:36.04 | paulk-aldrin | https://www.youtube.com/watch?v=ahPFCFooBv0 |
| 09:36.10 | paulk-aldrin | https://www.youtube.com/watch?v=VWPmXxq1MdQ |
| 09:36.17 | paulk-aldrin | and there is a talk about it at CCCamp next month |
| 09:36.37 | paulk-aldrin | gr8, 1) I expect that the board design will be free |
| 09:36.43 | paulk-aldrin | it sure will be documented |
| 09:36.50 | paulk-aldrin | then all the chips hardware design is non-free anyways |
| 09:37.14 | paulk-aldrin | as for software, there is a read-only proprietary bootrom |
| 09:37.17 | paulk-aldrin | that cannot be replaced |
| 09:37.21 | paulk-aldrin | inside the SoC |
| 09:37.33 | paulk-aldrin | then all the rest on the CPU should be free |
| 09:37.41 | paulk-aldrin | modem system will be non-free |
| 09:37.57 | bencoh | ( http://processors.wiki.ti.com/index.php/Boot_Sequence ) |
| 09:38.09 | paulk-aldrin | (regarding the system: the GPU doesn't work with free software, but we can do without it) |
| 09:38.13 | paulk-aldrin | then there are firmwares |
| 09:38.22 | paulk-aldrin | Wi-Fi will probably require a loaded firmware |
| 09:38.27 | paulk-aldrin | DSP too |
| 09:38.31 | R0b0t1 | It will also likely be possible to have a secure-boot type setup where you can be sure that the initially loaded OS is not compromised. |
| 09:38.37 | gr8 | maybe you could make this summary of proprietary parts avaliable somewhere? |
| 09:38.39 | paulk-aldrin | but it's not that useful since the CPU is more effective anyway |
| 09:38.50 | paulk-aldrin | gr8, I will, on the Replicant wiki, when the device is available :) |
| 09:38.59 | gr8 | awesome :) |
| 09:39.41 | paulk-aldrin | also, we can expect some non-loaded firmwares on other chips, but it depends |
| 09:39.55 | paulk-aldrin | at this point, it's more or less similar to hardware since you're not expected to change that software anyways |
| 09:40.13 | paulk-aldrin | so if you make an exception on freedom for the (non-free) hardware, you might as well do for those kinds of firmwares |
| 09:41.12 | gr8 | hehe I'm still struggling between "want to use as few non-free stuff as possible" and "support projects that go into the right direction" |
| 09:41.46 | paulk-aldrin | I see |
| 09:41.58 | paulk-aldrin | either way, producing hardware *is* the right solution and it requires a lot of support |
| 09:49.33 | gr8 | but it depends on what kind of hardware, maybe it would be more effective to start with the cores (OpenRISC etc.) and start producing free hardware network chips etc.? |
| 09:50.56 | R0b0t1 | that's been thought of |
| 09:51.13 | R0b0t1 | a large hurdle is the layout software is not open source |
| 09:51.28 | R0b0t1 | so you write a hardware specification in VHDL and then must turn it into a circuit you can fabricate |
| 09:51.33 | R0b0t1 | that step is nonfree as well |
| 09:52.37 | gr8 | yeah I know, I have used Xilinx tools, they are awful. Funny that this is a software problem again, though |
| 09:52.42 | edwin | as long as all the components that require non-free firmware are properly isolated I don't have a problem with running non-free firmware. It is a lot better than the Intel ME on modern laptops (https://en.wikipedia.org/wiki/Intel_Active_Management_Technology#Known_vulnerabilities_and_exploits) that has access to the host memory and runs proprietary, exploitable firmware code. |
| 09:53.10 | gr8 | ^ +1 |
| 09:53.35 | R0b0t1 | yeah |
| 09:54.19 | gr8 | good point actually, you can isolation to divide the problem of non-free parts into sub-problems |
| 09:54.28 | gr8 | *use isolation |
| 09:54.31 | Wizzup | which is what the neo900 people are doing |
| 09:55.49 | paulk-aldrin | edwin, "as long as all the components that require non-free firmware are properly isolated I don't have a problem with running non-free firmwar" |
| 09:56.02 | paulk-aldrin | looks like your concern is on privacy/security only! |
| 09:56.05 | paulk-aldrin | I still believe in free software |
| 09:56.12 | paulk-aldrin | regardless of privacy/security |
| 09:56.25 | paulk-aldrin | I don't think it's fair that all that stuff is non-free, even if it's harmless |
| 09:57.09 | paulk-aldrin | gr8, and by the way, there are free FPGA synthethis tools now! |
| 09:57.21 | paulk-aldrin | http://hackaday.com/2015/05/29/an-open-source-toolchain-for-ice40-fpgas/ |
| 09:58.36 | edwin | of course that having a system where everything is free software, including firmware and hardware design would be nice, but I'm happy when there are projects that try to take some practical steps to improving the status quo, even if they don't fully reach that goal |
| 09:59.45 | gr8 | paulk-aldrin: wow! that is good news |
| 09:59.48 | edwin | there is also http://www.lowrisc.org/ that is interesting to follow on the hardware side |
| 10:00.04 | paulk-aldrin | edwin, right |
| 10:00.28 | paulk-aldrin | I agree with the approach, but let's not forget that freeing those chips is desirable, even if we can somewhat isolate them |
| 10:03.22 | edwin | I think that it is important that such projects are honest about what is isolated, what is free software, what requires blobs, and Neo900 certainly does a good job for that (considering its not even a finished device). Contrast that with the controversial "Purism" laptop https://news.ycombinator.com/item?id=9912034 that doesn't really improve much on the status quo |
| 10:08.20 | edwin | maybe a future generation of Neo900 can use chips which require less firmware blobs, but unless you build/design the chips yourselves like lowrisc I don't see how that would be possible. Manufacturers don't seem to care much about releasing the source code for their firmwares :( |
| 10:08.48 | R0b0t1 | you can reverse the blobs with some effort |
| 10:08.50 | R0b0t1 | it's just |
| 10:08.50 | R0b0t1 | eh |
| 10:09.07 | R0b0t1 | the major hurdle I would think for custom hardware is it just sucks so much |
| 10:09.10 | R0b0t1 | who would use it? |
| 10:09.15 | R0b0t1 | who would help develop it? |
| 10:09.15 | R0b0t1 | :\ |
| 10:31.57 | paulk-aldrin | R0b0t1, freeing firmwares is painful, but maybe not as painful as designing our own chips, indeed |
| 10:32.27 | paulk-aldrin | anyways, free hardware desn't exist for chips, so there isn't so much to do anyways |
| 10:32.40 | paulk-aldrin | lowrisc would probably be a "documented" SoC for most people |
| 10:32.53 | paulk-aldrin | because creating silicon chips out of the design is out of reach |
| 10:33.03 | paulk-aldrin | which contrasts with building software, which is dead easy |
| 10:33.13 | paulk-aldrin | (well, not really, but smart people made it dead easy for us) |
| 10:40.16 | *** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae) |
| 10:47.23 | R0b0t1 | if you could make 10k at a time once the cost would be reasonable |
| 10:47.31 | R0b0t1 | or even slightly smaller if the buyers didn't mind a slight premium |
| 10:47.36 | R0b0t1 | like 1k |
| 10:51.29 | *** join/#neo900 antiatom (~ilse@91.214.169.69) |
| 11:23.11 | DocScrutinizer05 | it's really making me feel hapy to see this amount of expertise in this channel :-) thanks folks! |
| 11:23.36 | DocScrutinizer05 | actually there's noting I need to add or clarify |
| 11:25.10 | *** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae) |
| 11:28.15 | DocScrutinizer05 | just about "document which are blobs": http://neo900.org/faq#floss ff |
| 11:33.44 | DocScrutinizer05 | and about "radio triangulation" see U-TDOA which applies to *all* transmitters, so there's nothing Neo900 can do, except disable transmitters. You can do this reliably |
| 11:34.12 | DocScrutinizer05 | ~u-tdoa |
| 11:34.13 | infobot | somebody said u-tdoa was http://en.wikipedia.org/wiki/U-TDOA |
| 11:44.31 | gr8 | maybe you could build a Neo900 without any telephone chip at all? :D That would be awesome. I would be like a mini computer or PDA then. I miss the days when there were pure PDAs |
| 11:44.41 | gr8 | *it |
| 11:45.17 | gr8 | "privacy version" :P |
| 11:49.33 | gr8 | it would be a mobile without the phone then ;) |
| 11:50.48 | DocScrutinizer05 | of course we *could* buold such thing, alas we can't *sell* it |
| 11:50.52 | edwin | isn't that what a wifi-only tablet is? |
| 11:51.06 | edwin | (pure PDA) |
| 11:51.14 | DocScrutinizer05 | yep |
| 11:52.47 | gr8 | but a tablet is too big to fit in my pocket -,- I already have such a thing |
| 11:52.47 | DocScrutinizer05 | but Neo900 is such wifi-only device with an *optional* phone |
| 11:53.06 | paulk-aldrin | gr8, I think there is a Letux device like that |
| 11:54.20 | DocScrutinizer05 | yep, that too. And how about Pandorabox for example, or Pyra. OK again quite a bit larger than Neo900 |
| 11:55.03 | DocScrutinizer05 | anyway see dragonbox, recommended |
| 11:56.12 | DocScrutinizer05 | a pointer into roughly right direction: http://dragonbox-pyra.org/blog.html |
| 11:58.30 | gr8 | DocScrutinizer05: I can't find anything about "Pandorabox" |
| 11:58.50 | gr8 | I guess you mean OpenPandora? |
| 11:58.53 | *** join/#neo900 mvaenskae (~mvaenskae@unaffiliated/mvaenskae) |
| 11:59.13 | DocScrutinizer05 | https://www.dragonbox.de/de/ |
| 12:03.37 | gr8 | omg that's awesome xD |
| 12:10.59 | gr8 | but it is extremely ugly :D |
| 12:11.21 | gr8 | not sure I would like to carry that with me every day... |
| 12:11.40 | DocScrutinizer51 | yep |
| 12:12.31 | DocScrutinizer51 | paericilarly since pandora is same screen size like N810 |
| 12:14.56 | DocScrutinizer05 | particularly* |
| 12:15.30 | DocScrutinizer05 | that's what results in typing when eyes are half closed yet ;-) |
| 12:24.41 | R0b0t1 | so the n900 dts got mainlined, and there is no defconfig? |
| 12:28.34 | DocScrutinizer05 | afaik there used to be a rx51 defconfig |
| 12:28.53 | R0b0t1 | hmmm |
| 12:28.59 | R0b0t1 | yes I see mention of that |
| 12:29.01 | R0b0t1 | must've been removed |
| 12:29.06 | DocScrutinizer05 | dts is mainlined afaik, though unclear if it's really 100% functional already |
| 12:30.31 | DocScrutinizer05 | and whether it's really equivalent regarding device management incl power saving is yet to be confirmed |
| 13:10.21 | *** join/#neo900 jonsger (~Thunderbi@x5f73b352.dyn.telefonica.de) |
| 13:28.01 | *** join/#neo900 ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 13:34.48 | *** join/#neo900 cybiko123 (~cybiko123@c-73-210-142-29.hsd1.il.comcast.net) |
| 13:34.51 | *** join/#neo900 cybiko123 (~cybiko123@unaffiliated/cybiko123) |
| 13:59.48 | *** join/#neo900 jonsger (~Thunderbi@x5f73b352.dyn.telefonica.de) |
| 14:52.28 | *** join/#neo900 infobot (ibot@69-58-76-73.ut.vivintwireless.net) |
| 14:52.28 | *** topic/#neo900 is http://neo900.org | conversations are logged to http://infobot.rikers.org/%23neo900/ and http://irclog.whitequark.org/neo900 |
| 14:52.28 | *** mode/#neo900 [+v infobot] by ChanServ |
| 15:06.36 | *** join/#neo900 gr8 (~gr8@dslb-188-107-038-062.188.107.pools.vodafone-ip.de) |
| 15:11.57 | *** join/#neo900 gr8 (~gr8@dslb-188-107-038-062.188.107.pools.vodafone-ip.de) |
| 15:12.20 | *** join/#neo900 gr8 (~gr8@unaffiliated/gr8) |
| 15:37.10 | *** join/#neo900 Pali (~pali@Maemo/community/contributor/Pali) |
| 16:02.58 | *** join/#neo900 xes (~xes@unaffiliated/xes) |
| 16:50.14 | *** join/#neo900 ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 17:05.05 | *** join/#neo900 cybiko123 (~cybiko123@c-73-210-142-29.hsd1.il.comcast.net) |
| 17:05.05 | *** join/#neo900 cybiko123 (~cybiko123@unaffiliated/cybiko123) |
| 17:45.38 | DocScrutinizer05 | fun LED: http://www.adafruit.com/datasheets/WS2812B.pdf |
| 17:47.01 | *** join/#neo900 paulk-collins (~paulk@gagarine.paulk.fr) |
| 18:06.56 | wpwrak | DocScrutinizer05: it lacks wifi ;-) |
| 18:07.31 | DocScrutinizer05 | yeah, and a mpeg2 player |
| 18:08.00 | wpwrak | naw. but you need wifi to connect to the cloud, where the led settings are stored |
| 18:08.32 | wpwrak | i wonder how to display ads with just one LED, though |
| 18:08.54 | DocScrutinizer05 | it's a 'pixel', see datasheet ;-) |
| 18:09.06 | DocScrutinizer05 | they even claim 30fps |
| 18:09.27 | DocScrutinizer05 | actually pretty smart |
| 18:09.47 | DocScrutinizer05 | if it works like it should |
| 18:10.32 | wpwrak | it's cute ... but also quite expensive |
| 18:10.37 | DocScrutinizer05 | building huge video walls becomes incredibly easy, at least regarding wiring |
| 18:10.55 | DocScrutinizer05 | thought as much, so I didn't even check. How much? |
| 18:11.15 | wpwrak | http://www.digikey.com/product-search/en/optoelectronics/led-indication-discrete/524729?k=WS2812B |
| 18:11.28 | DocScrutinizer05 | OUUUCH! |
| 18:11.31 | wpwrak | probably with some hefty adafruit margin, though |
| 18:11.47 | DocScrutinizer05 | yeah, adafruit is evil |
| 18:12.35 | DocScrutinizer05 | for a 4.50 bucks I could build them myself ;-) |
| 18:12.50 | wpwrak | ah, and that's where it's really used: http://www.aliexpress.com/store/product/4m-DC5V-WS2812B-led-pixel-srip-non-waterproof-60pcs-WS2812B-M-with-60pixels-white-PCB-only/701799_935613197.html |
| 18:13.25 | DocScrutinizer05 | now that looks much better, eh? |
| 18:13.42 | wpwrak | yeah. it suddenly makes sense :) |
| 18:15.40 | DocScrutinizer05 | 30 * 30 px $420 |
| 18:17.42 | DocScrutinizer05 | hmm, 40*10 makes for a nice digital clock, I guess |
| 18:19.13 | wpwrak | naw, 3 * 60. seconds, minutes, hours, weekday, month, and a few LEDs for RAID-5 |
| 18:19.50 | DocScrutinizer05 | 120 bit ? |
| 18:21.03 | wpwrak | 3 * 60 = 60 seconds + 60 minutes + 24 hours + 7 days + 12 month + 21 spare |
| 18:21.15 | DocScrutinizer05 | ugh |
| 18:21.32 | DocScrutinizer05 | aaah you think analog |
| 18:21.35 | wpwrak | or drop the month and have day of the week plus day of the month |
| 18:23.22 | wpwrak | by the way, is https://neo900.org/stuff/joerg/spacerframe/sketch.pdf still accurate ? especially the 2.8 mm ? |
| 18:23.44 | DocScrutinizer05 | err yep, why not? |
| 18:23.58 | wpwrak | just checking |
| 18:24.06 | DocScrutinizer05 | we should recheck the height though |
| 18:25.04 | DocScrutinizer05 | maybe we can check the actual height of the B2Bs |
| 18:25.23 | DocScrutinizer05 | then add the PCB thickness of UPPER |
| 18:26.50 | DocScrutinizer05 | the 2.8 were based on assumed height of modem module plus PCB thickness. |
| 18:27.57 | *** join/#neo900 jonsger (~Thunderbi@x5f73b352.dyn.telefonica.de) |
| 18:28.28 | wpwrak | the DF40C-60DS-0.4V is 1.5 mm |
| 18:28.40 | DocScrutinizer05 | possibly the B2B Nik picked are a tiny bit higher |
| 18:29.19 | wpwrak | the DF40C series goes from 1.5 to 4.0 mm, in 0.5 mm increments |
| 18:29.27 | DocScrutinizer05 | hmm, that's effecive height on mating? |
| 18:29.33 | wpwrak | yup |
| 18:30.02 | DocScrutinizer05 | we need to check what Nik picked |
| 18:31.01 | wpwrak | see above :) |
| 18:31.24 | DocScrutinizer05 | he hardly has picked 1.5mm, that wouldn't fit |
| 18:31.43 | DocScrutinizer05 | either 2.0 or 2.5 |
| 18:31.50 | wpwrak | i guess he didn't _mean_ to pick an 1.5 mm b2b, yet that's what's in the schematics ... |
| 18:32.02 | DocScrutinizer05 | :-S |
| 18:32.48 | wpwrak | anyway, we can figure that out later. so for now i just use 2.8 mm. |
| 18:32.54 | DocScrutinizer05 | then pragmatic: 2.0 is a tough fir for a 2.2 module, so 2.5 |
| 18:33.05 | wpwrak | -> 3.3 mm ? |
| 18:33.10 | DocScrutinizer05 | yep |
| 18:33.24 | DocScrutinizer05 | or would we gain a 0.2 from soldering? |
| 18:34.03 | DocScrutinizer05 | then 2.0 (+0.2) => 3.0 total |
| 18:34.05 | wpwrak | finally i get to use this picture ;-) https://archive.today/0WJl6/6d76554faa031e805d5274740e9098e458899a24.jpeg |
| 18:34.38 | DocScrutinizer05 | :-) |
| 18:35.15 | *** join/#neo900 norly (~norly@enpas.org) |
| 18:35.19 | DocScrutinizer05 | I guess we could afely assume a 0.2mm gain from "sloppy soldering", eh? |
| 18:36.31 | DocScrutinizer05 | worst gase we mill out a 0.2mm deep pool in UPPER ;-) |
| 18:36.35 | DocScrutinizer05 | case* |
| 18:37.16 | DocScrutinizer05 | nah, go for 3.0 for now |
| 18:38.35 | DocScrutinizer05 | checks module heights |
| 18:39.43 | wpwrak | total height of the bounding box of the spacer frame then becomes 4.9 mm. good. that still fits in a "thin" block of acrylic |
| 18:40.28 | DocScrutinizer05 | PHS8 2.0, PLS8 2.3 |
| 18:41.16 | DocScrutinizer05 | I wonder... |
| 18:41.27 | DocScrutinizer05 | actually 2.5mm B2B? |
| 18:41.45 | wpwrak | i can guess where the 2.8 mm come from ... |
| 18:41.46 | DocScrutinizer05 | wpwrak: what do you think? |
| 18:42.28 | wpwrak | may be unavoidable. lest we make such a cut-out |
| 18:42.29 | DocScrutinizer05 | yeah, for PHS8 the 2.0mm B2B makes sense |
| 18:42.46 | DocScrutinizer05 | but since we also want to offer PLS8... |
| 18:43.00 | DocScrutinizer05 | so it's 2.5 + 0.8 sandwich then |
| 18:43.38 | DocScrutinizer05 | and thus, spacer height |
| 18:44.12 | DocScrutinizer05 | good you asked :-) |
| 18:45.42 | DocScrutinizer05 | when our spacerframe proto doesn't perfectly match our sandwich proto, so what? then we have a 0.5mm 'gap' between kbd mat and kbd frame |
| 18:46.17 | wpwrak | :) let's shrink the last thin bit of wall a little then. that's 0.9 deep but at most 0.7 mm wide. trimming that is likely to actually improve it ... |
| 18:46.18 | DocScrutinizer05 | unless we add a few layers paper under mat |
| 18:46.31 | *** part/#neo900 gr8 (~gr8@unaffiliated/gr8) |
| 18:46.35 | DocScrutinizer05 | go ahead |
| 18:46.41 | DocScrutinizer05 | :-) |
| 18:47.46 | DocScrutinizer05 | how about live streaming webcam showing the mill operate? ;-) |
| 18:48.11 | wpwrak | naw, got no operational webcam |
| 18:48.30 | DocScrutinizer05 | and no really operational uplink I guess :-) |
| 18:49.06 | wpwrak | besides, i just figured out the curved outline shape. a tricky beast |
| 18:49.09 | DocScrutinizer05 | anyway don't forget to make lots of snapshots |
| 18:49.34 | DocScrutinizer05 | yeah, the outline is non-trivial |
| 18:50.20 | wpwrak | it's curved by only about 1 mm on the sides, but still ... |
| 18:51.16 | DocScrutinizer05 | yep |
| 18:51.42 | DocScrutinizer05 | at least the long sides *seem* to be straight |
| 18:51.50 | wpwrak | it's cool how fast the outline reloads in freecad. i've been getting used to > 1 minute processing with anelok :) |
| 18:52.06 | wpwrak | yes, they're straight as far a my scans can tell |
| 18:52.23 | DocScrutinizer05 | your scans are in line with my eyes ;) |
| 18:53.23 | DocScrutinizer05 | would you provide a file format that's also suitable for printing? |
| 18:54.22 | DocScrutinizer05 | I most certainly could get some printed protos too, until camp, then |
| 18:54.23 | wpwrak | STL seems to be pretty universally accepted |
| 18:54.30 | DocScrutinizer05 | \o/ |
| 18:55.48 | wpwrak | most 3D printer will have kittens with that 0.7 mm wall, though ;-) |
| 18:55.57 | DocScrutinizer05 | wpwrak: should we already consider slots for 2nd SIM? |
| 18:56.56 | DocScrutinizer05 | (0.7mm wall) well then I'd print an additional 0.5mm and literally cut the excess away |
| 18:56.57 | wpwrak | once i have the basic model it'll be easy to add rectangular cuts |
| 18:57.15 | DocScrutinizer05 | :nod: |
| 18:58.44 | wpwrak | (print more) that may get tricky, too, since you'd then produce an undercut. that per se isn't a problem, but the whole thing may get fragile enough to come apart when you cut it |
| 18:59.11 | DocScrutinizer05 | s/cut/mill|file|sand/ |
| 18:59.54 | DocScrutinizer05 | we'll see |
| 18:59.58 | wpwrak | maybe with a dremel and a sanding cylinder ... there you also get thermal effects to help you. well, they CAN help you. or get in the way :) |
| 19:00.33 | DocScrutinizer05 | rather the latter - but I have ice spray for that ;) |
| 19:01.13 | wpwrak | i guess one or two extra hands would then come in handy, too ;) |
| 19:01.23 | DocScrutinizer05 | yep, indeed |
| 19:03.03 | wpwrak | i guess most engineers would prefer it if evolution had avoided that upright walk |
| 19:03.58 | DocScrutinizer05 | or use spiders instead of apes as proto |
| 19:05.13 | wpwrak | hmm. sounds like an opportunity for symbiosis - one spider on every finger. for SMT, you don't need a lot of force ... |
| 19:05.23 | DocScrutinizer05 | muses... "if I were a spider, would I be afraid of myself?" |
| 19:05.51 | wpwrak | can a human be afraid of other humans ? |
| 19:05.58 | DocScrutinizer05 | s/afarid/scared/ |
| 19:06.20 | DocScrutinizer05 | sure, but of $self ? |
| 19:07.28 | wpwrak | do spider brains also have two halves ? |
| 19:07.46 | *** join/#neo900 sparetire_ (~sparetire@unaffiliated/sparetire) |
| 19:08.08 | DocScrutinizer05 | definitely not. so you think they are less susceptible to schizophrenia? |
| 19:12.22 | wpwrak | would seem plausible, no ? |
| 19:35.04 | Humpelstilzchen | 21:03:03 <+wpwrak> i guess most engineers would prefer it if evolution had avoided that upright walk <--as people who had to learn to walk multiple times.. |
| 19:46.12 | *** join/#neo900 Oksana (~chatzilla@Maemo/community/council/Wikiwide) |
| 19:56.30 | *** join/#neo900 ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 20:59.23 | DocScrutinizer05 | LOL! https://twitter.com/insideX/status/623180335715631104 |
| 21:02.26 | Pali | :D |
| 21:04.13 | *** join/#neo900 cybiko123 (~cybiko123@c-73-210-142-29.hsd1.il.comcast.net) |
| 21:05.37 | paulk-collins | nice one |
| 21:27.56 | bencoh | :D |
| 21:56.01 | *** join/#neo900 cybiko123 (~cybiko123@c-73-210-142-29.hsd1.il.comcast.net) |
| 21:56.07 | *** join/#neo900 cybiko123 (~cybiko123@unaffiliated/cybiko123) |
| 22:20.06 | *** join/#neo900 cybiko123 (~cybiko123@c-73-210-142-29.hsd1.il.comcast.net) |
| 22:20.08 | *** join/#neo900 cybiko123 (~cybiko123@unaffiliated/cybiko123) |
| 22:59.36 | *** join/#neo900 arossdotme (~zxy@79-69-203-244.dynamic.dsl.as9105.com) |
| 23:15.20 | *** join/#neo900 ccnnjj (~matt@cl-598.bos-01.us.sixxs.net) |
| 23:42.06 | *** join/#neo900 Oksana (~chatzilla@Maemo/community/council/Wikiwide) |
