| 00:20.43 | *** join/#utah infobot (ibot@rikers.org) |
| 00:20.43 | *** topic/#utah is Utah-related discussion including user groups | logs @ http://infobot.rikers.org/%23utah/ | See also ##lds | To combat spam, you must register with NickServ if you wish to speak. This may or may not be temporary. |
| 00:20.44 | *** mode/#utah [+o infobot] by ChanServ |
| 04:59.54 | *** join/#utah bubbalumpy (bubbalumpy@gateway/vpn/privateinternetaccess/bubbalumpy) |
| 05:44.18 | *** join/#utah infobot (ibot@rikers.org) |
| 05:44.18 | *** topic/#utah is Utah-related discussion including user groups | logs @ http://infobot.rikers.org/%23utah/ | See also ##lds | To combat spam, you must register with NickServ if you wish to speak. This may or may not be temporary. |
| 05:44.19 | *** mode/#utah [+o infobot] by ChanServ |
| 12:28.36 | *** join/#utah emcnabb (~emcnabb@hs-nc-1fff767f54-29977-1.tingfiber.com) |
| 14:20.59 | *** join/#utah legreathambino (~braxtron@216.160.248.178) |
| 14:29.21 | *** join/#utah aeryndunham (~quassel@170.250.131.39) |
| 15:29.45 | *** join/#utah josephscott (~josephsco@c-174-52-11-31.hsd1.ut.comcast.net) |
| 15:46.06 | *** join/#utah BLZbubba (~mark@knm.org) |
| 16:37.05 | *** join/#utah tristanbob_h (~Tristan@2001:1948:212:face::8) |
| 16:40.33 | Migs | Has anyone ever set up a solar panel? Thinking of making a backyard theater. Just enough to power a projector, a screen, and a Pi or maybe a Roku. |
| 16:41.52 | Migs | Not sure it's worth it, though |
| 16:42.58 | *** join/#utah jab416171 (~jab416171@c-174-52-63-79.hsd1.ut.comcast.net) |
| 16:45.12 | *** join/#utah tiwula (~lane@70.89.246.241-Busname-UT.hfc.comcastbusiness.net) |
| 16:57.50 | *** join/#utah HexaKhan (~HexaKhan_@unaffiliated/dschinghis-khan/x-8103911) |
| 17:03.28 | RyanE | obvs. without a battery, it's not going to work well, as you want it to be dark when you watch movies... :) |
| 17:10.05 | Migs | I assumed I'd run it off the battery. I think I'm more interested in how you weatherproof all this. |
| 17:11.01 | Migs | and what kind of wattage I'd need if I wanted to, say, watch one 2-hour movie out there per night in the summer. |
| 17:33.22 | RyanE | I assume this would mostly be constrained by how much power your projector uses. I can't imagine the Pi would be more than a rounding error of the power used by the projector. |
| 17:36.52 | *** join/#utah frostyfrog (~frostyfro@unaffiliated/frostyfrog) |
| 17:36.52 | frostyfrog | You'd have to do a bit of reading up on the specs of your devices, do the math with those specs to figure out wattage per hour... youtah has some experience with Solar and radios. |
| 17:37.11 | frostyfrog | hopes that message got through. |
| 19:10.17 | jfindlay | Migs: what most people don't know is that the most important unit in your power circuitry is neither the battery nor the solar array. It is called the charge controller |
| 19:10.47 | jfindlay | it connects the power generating array to the power storage array and the load |
| 19:13.01 | jfindlay | even without a load, you can't just wire up a solar panel and a battery without destroying the battery |
| 19:13.14 | Migs | frostyfrog: It did. |
| 19:13.23 | Migs | Unless there was another one I didn't see, in which case it didn't. |
| 19:14.12 | Migs | I'm really new at this, and still just exploring options. Maybe I could start with a cheap DIY kit. |
| 19:14.14 | frostyfrog | The one talking about specs and math? |
| 19:14.19 | Migs | frostyfrog: Yes. |
| 19:14.24 | frostyfrog | That's the one |
| 19:14.39 | Migs | mess around with something that can power a lamp first |
| 19:14.54 | Migs | then invest in something bigger |
| 19:21.16 | *** join/#utah tristanbob_WSU (~Tristan@65-130-177-248.slkc.qwest.net) |
| 19:26.39 | *** join/#utah Bloodythorn (~Bloodytho@c-76-27-46-75.hsd1.ut.comcast.net) |
| 19:34.48 | youtah | https://www.hamradio.com/detail.cfm?pid=H0-011217 |
| 19:35.08 | youtah | lol, oops, that link was meant for you jsmith |
| 19:35.13 | youtah | cSmith, can check it out too |
| 19:39.14 | *** join/#utah infobot (ibot@rikers.org) |
| 19:39.14 | *** topic/#utah is Utah-related discussion including user groups | logs @ http://infobot.rikers.org/%23utah/ | See also ##lds | To combat spam, you must register with NickServ if you wish to speak. This may or may not be temporary. |
| 19:39.15 | *** mode/#utah [+o infobot] by ChanServ |
| 19:43.27 | frostyfrog | details, details |
| 19:44.22 | jsmith | youtah: You using a standard half-wave dipole or a folder dipole? |
| 19:44.27 | jsmith | folded, that is |
| 19:44.43 | frostyfrog | likes this new idea of a dipole made out of folders. |
| 19:46.06 | jfindlay | what about a tripole? |
| 19:46.48 | jfindlay | ~napoleon |
| 19:46.48 | infobot | It's a liger, bred for its skills in magic. |
| 19:46.52 | frostyfrog | too conductive ;p |
| 19:47.15 | frostyfrog | saw a youtube video of a guy with either a 40m or a 20m dipole made out of paperclips. |
| 20:00.08 | youtah | jsmith, standard quarter wave dipole |
| 20:00.53 | youtah | errr |
| 20:00.58 | youtah | half wave, quarter wave on each side |
| 20:01.04 | youtah | you get what I mean |
| 20:01.15 | youtah | ~33'8" |
| 20:09.26 | frostyfrog | I agree, it's a tad confusing sometimes. |
| 20:13.47 | frostyfrog | Tee hee |
| 20:13.50 | frostyfrog | Silly Docker. |
| 20:14.23 | frostyfrog | You'd think they'd know that Nano CPUs aren't a real thing in a normal CPU ;p |
| 20:26.45 | *** join/#utah goozbach (~goozbach@fedora/goozbach) |
| 20:26.45 | *** mode/#utah [+v goozbach] by ChanServ |
| 20:26.50 | goozbach | phew, that was a slog through the backlog |
| 20:27.03 | goozbach | guess this channel is back among the living |
| 20:27.08 | frostyfrog | Yer welcome! xD |
| 20:30.36 | jima | goozbach: it's irc, so who knows how it'll hold up :-P |
| 20:49.36 | youtah | lol goozbach |
| 20:50.11 | youtah | contrary to what Jayce^ and neybar erroneously say... IRC #utah is alive and well |
| 20:57.42 | jima | do they say that in here? |
| 21:01.54 | jfindlay | I don't think youtah is alive |
| 21:02.24 | frostyfrog | Luckily, he wasn't talking about himself *phew* |
| 21:02.33 | frostyfrog | https://xkcd.com/1782/ |
| 21:05.08 | jima | frostyfrog: it me |
| 21:08.25 | frostyfrog | and me :3 |
| 21:14.44 | jfindlay | slack was great for what it offered when it came out against hipchat et al, but went way too google way to quickly |
| 21:16.35 | jfindlay | for some reason, apps based on chrome are resourceophiles, and insist on always-on, desktop-notification, gps-crosshairs level awareness |
| 21:16.58 | jfindlay | at this point slack is like the skype for chatrooms |
| 21:34.04 | eightyeight | slack is a much better UX than IRC though |
| 21:34.16 | eightyeight | just as Signal is a much better UX than GPG |
| 21:39.26 | youtah | https://imgur.com/gallery/VXifhfy |
| 21:43.57 | joshh | afaict the only advantage to slack over irc is that it's easy for corps to control and it's better looking than most irc gui clients |
| 21:44.18 | joshh | and has a bunch of bots that already work, etc |
| 21:44.29 | jfindlay | eightyeight: I don't think it's fair to compare slack to IRC when talking about UX, but you could compare slack to weechat |
| 21:44.32 | joshh | but i still prefer irc |
| 21:45.06 | eightyeight | slack is more than a frontend |
| 21:46.34 | jfindlay | how many ends does it have? |
| 21:47.01 | joshh | i don't have issues with slack though, other than that it's another thing to keep open in addition to irc |
| 21:47.28 | joshh | and it doesn't suck on phones |
| 21:47.39 | eightyeight | doesn't suck on desktops either |
| 21:47.57 | joshh | ya, even the linux client isn't bad compared to its competition |
| 21:48.55 | jfindlay | my standard for a client is weechat, so pretty much everything sucks in comparison :) |
| 21:49.38 | jfindlay | mainly, I don't want to have to portion out a fistful of resources just to run a chat client |
| 21:53.01 | joshh | right |
| 21:53.04 | eightyeight | weechat relay and weechatAndroid is sexy |
| 21:53.34 | eightyeight | and the slack desktop client is seriously a massive resource hog, no doubt. irritates me to no end |
| 21:53.40 | eightyeight | but then so are chomium/firefox |
| 21:53.46 | joshh | honestly though, millenials really don't seem to even want to care about irc |
| 21:53.51 | joshh | so it's gonna dwindle |
| 21:54.48 | spangborn | I should try IRCCloud's new slack bridge |
| 21:55.16 | joshh | didn't slack just announce they were killing off the irc gateway? |
| 21:55.43 | spangborn | Yes |
| 21:55.48 | eightyeight | it's ded. |
| 21:55.50 | spangborn | this is a new API-based gateway that IRCCloud added |
| 21:55.57 | jfindlay | irc and xmpp |
| 21:55.57 | joshh | ah ok |
| 21:55.57 | eightyeight | also, i'm not sure irc is dying quite yet |
| 21:55.59 | jfindlay | https://get.slack.help/hc/en-us/articles/201727913-Connect-to-Slack-over-IRC-and-XMPP |
| 21:56.51 | eightyeight | freenode has been holding steady with ~ 90k users connected for the past few years, with no immediate signs of dropping |
| 21:56.53 | joshh | eightyeight: it will only be old people and 4chan type kids though, we can't get any of the 20ish fresh-grad type people at work to like it at all |
| 21:56.57 | eightyeight | http://irc.netsplit.de/networks/statistics.php?net=freenode |
| 21:57.01 | eightyeight | i dunno |
| 21:57.12 | eightyeight | free software has a strong IRC heritage |
| 21:57.38 | joshh | the systems type stuff yes, but a lot of the higher level crap these days is using slack |
| 21:57.50 | joshh | like new web frameworks and whatnot |
| 21:57.53 | eightyeight | sure. but corporate messaging has been all over the place |
| 21:58.30 | eightyeight | IRC never caught on with the general public. it's always been highly focused |
| 21:58.58 | eightyeight | but in those tight niche groups, it's been holding strong, like free software, software piracy, and gaming networks |
| 21:59.04 | jfindlay | google could have prevented this if they hadn't courageously migrated away from xmpp to formulate their own 16 different chat systems |
| 21:59.11 | eightyeight | my wife isn't going to use irc though. and neither will her employer. |
| 21:59.55 | eightyeight | irc has what? i total of maybe 200k active users? |
| 22:00.00 | eightyeight | whatsapp has 2 billion. :) |
| 22:00.10 | eightyeight | s/i total/a total/ |
| 22:01.32 | unum | a group I'm part of just moved from whatsapp to slack for privacy reasons. which sounded backwards to me. |
| 22:01.44 | *** join/#utah tristanbob_h (~Tristan@2001:1948:212:face::f) |
| 22:02.17 | eightyeight | very backwards |
| 22:03.11 | eightyeight | 1. Signal. 2. WhatsApp, Wire. 3. Slack, Twitter DM. 4. * |
| 22:03.21 | eightyeight | <- more secure ... less secure -> |
| 22:03.47 | unum | the belief was based off of ownership of whatsapp |
| 22:03.55 | jfindlay | :) |
| 22:03.58 | unum | rather than any knowledge of the technical implementation |
| 22:04.06 | jfindlay | lol facebook |
| 22:04.19 | eightyeight | whatsapp is E2EE via the signal protocol |
| 22:04.39 | eightyeight | sure, facebook owns it. that doesn't mean they can necessarily read your messages. |
| 22:05.32 | jfindlay | dude fb will haxor ur whatsmsgs unto russoanalytic |
| 22:05.45 | eightyeight | gets aluminum foil for hat making |
| 22:15.09 | HexaKhan | I don't use whatsapp nor do I really intend to, but during Zuckerbergs congressional hearing, he said that it's end to end encrypted and they have no way to read or have ads based off the messages for that reason. Might take that with a grain of salt, but he could get in trouble if that's proven to be false. |
| 22:17.57 | eightyeight | he can't read it |
| 22:18.20 | eightyeight | there are two valid concerns with whatsapp, that every user should be aware of |
| 22:18.41 | eightyeight | 1) you have 30 days after initial install and setup to opt-out of sharing metadata with facebook |
| 22:20.06 | eightyeight | 2) you should enable notifications of when key changes happen. whatsapp disables this by default. |
| 22:20.27 | eightyeight | in every case, you can verify that your messages are E2EE for each contact |
| 22:21.09 | eightyeight | enable Settings -> Security -> Show security notifications |
| 22:21.37 | eightyeight | "Turn on this setting to receive notifications when a contact's security code has changed." |
| 22:25.36 | HexaKhan | So might be a dumb question, but couldn't they just be storing the encryption keys on their end? Obviously the app would have to have access to them so I don't understand why they couldn't be holding them also (my tinfoil hat talking). |
| 22:26.11 | HexaKhan | I don't know if/how the keys are generated or stored for whatsapp |
| 22:26.31 | eightyeight | the keys are generated and stored on the phone |
| 22:26.49 | eightyeight | sure, the compiled binary _could_ send the private key to whatsapp/facebook without your knowledge |
| 22:27.24 | eightyeight | but there are a _lot_ of security researchers doing vulnerability discovery on whatsapp. if that was discovered, it would be a huge blow |
| 22:27.48 | eightyeight | and, from the service provider's perspective, there is good reason to not know what the data is users are sending to each other |
| 22:28.22 | eightyeight | if the No Such Agency asks for a data dump on a customer, if facebook doesn't have the keys, the data they hand over is worthless |
| 22:28.39 | eightyeight | but yes, it always comes down to trust, and signal is no different |
| 22:28.50 | eightyeight | do you trust the service provider to be doing what they claim? |
| 22:28.52 | eightyeight | if not, don't use it |
| 22:29.43 | eightyeight | i don't trust telegram to have the faintest clue how to do a cryptographically secure protocol, let alone have my data |
| 22:29.46 | eightyeight | as such, i don't use telegram |
| 22:31.07 | *** join/#utah bryceml (bryceml@2600:3c00::f03c:91ff:fec6:dda1) |
| 22:32.00 | HexaKhan | Yup, exactly. As much as I despise facebook, I actually don't think they are holding the keys for the reasons you said (and would have to be lying about it). But I'm still paranoid mostly because even if they're not now holding keys, they could suddenly change their mind with a simple update. |
| 22:32.30 | HexaKhan | And we'd have to rely on independent research to try to figure out if and what the apps are doing. |
| 22:32.39 | eightyeight | i believe it's in facebook's best interest to remain honest with whatsapp, and not become a MITM |
| 22:32.46 | eightyeight | i believe they know it too |
| 22:33.45 | eightyeight | and that's why i don't think it's "as secure" as signal, because there is facebook as a player, and there are at least 2 things users need to worry about, that they don't have to with signal |
| 22:34.00 | eightyeight | but to migrate from whatsapp to slack, because "more secure" is asinine |
| 22:34.08 | eightyeight | slack is not E2EE, and doesn't even pretend to be |
| 22:42.39 | jlp_znc | youtah: you "accidentally" bought a TM-V71A? that's quite an accident. |
| 22:42.47 | youtah | yup |
| 22:42.52 | youtah | I tend to be accident prone |
| 23:01.24 | jlp_znc | you wanted it for the cross-band repeat functionality? |
| 23:02.19 | jlp_znc | does it have the ability to ID on it's output freq? |
| 23:03.57 | jlp_znc | you should look at this: http://www.repeater-builder.com/kenwood/pdfs/tm-v71ae-mods.pdf (scroll down to the section on Repeater Modification) |