text
stringlengths
9
408
[1309.42 --> 1312.02] I'm like, oh, hold on a second here, I'll get you a little zip file with a URL.
[1312.36 --> 1316.32] I did that with a video of my daughter the other day that was, like, 170 meg to a parent,
[1316.48 --> 1317.90] and Telegram was like, nope.
[1318.54 --> 1320.74] So I just used the object storage, and it worked great.
[1321.24 --> 1325.06] Yeah, and the command line client is, like, the pro way to get things up there,
[1325.06 --> 1330.12] because what I do, because I'm such a nerd, is I have a Uake dropdown terminal
[1330.12 --> 1335.24] where it's always, like, in one of the tabs, so it's, like, up, up, change a couple of things, hit enter.
[1335.60 --> 1336.48] It's great.
[1336.86 --> 1340.76] But on top of that, they've got cloud firewalls, they've got VLAN support,
[1340.82 --> 1345.24] they have a really powerful DNS manager, they're beginning to roll out bare metal servers,
[1345.50 --> 1347.52] and they also work with infrastructure management.
[1347.68 --> 1349.78] So if you want to plug in with Kubernetes and Terraform,
[1349.88 --> 1353.48] maybe you want to even just use Linode as part of a multi-cloud strategy.
[1353.48 --> 1354.78] They're great for that, too.
[1354.84 --> 1360.12] In fact, 66% of companies will save money working with a mix of alternative cloud providers
[1360.12 --> 1362.78] instead of just relying on, like, one big hyperscaler.
[1362.86 --> 1364.58] So it's worth just looking into that.
[1365.08 --> 1366.96] Linode could be part of your multi-cloud strategy.
[1367.30 --> 1370.02] And if you ever run into any trouble, you ever need any help,
[1370.08 --> 1372.44] they've got the best customer service in the business.
[1373.14 --> 1376.72] And when your business is running on Linode, it's nice to know that's available.
[1377.22 --> 1379.16] And their support for the community runs deep.
[1379.28 --> 1382.56] They're making it possible for our team to get together in Denver.
[1382.56 --> 1384.48] They're making the whole road trip possible.
[1385.28 --> 1385.98] And that's pretty awesome.
[1386.06 --> 1389.66] And not only that, but they're going to be bringing swag and giveaways like raspberry pies
[1389.66 --> 1392.88] and all kinds of awesome shirts they've made just for the trip.
[1393.00 --> 1396.20] And it's just going to be a whole party made possible by Linode.
[1396.26 --> 1399.12] And they're doing that just to have a chance to connect because, like us,
[1399.50 --> 1400.44] they miss seeing people.
[1400.58 --> 1401.26] It's been a while.
[1401.68 --> 1404.68] And Linode has been so enthusiastic about supporting our reunion.
[1405.78 --> 1407.30] But there's so many things I could go on about.
[1407.34 --> 1408.84] You just got to go check it out for yourself.
[1408.96 --> 1411.00] You got to get your hands on it and see it.
[1411.00 --> 1412.38] So go use that $100.
[1413.30 --> 1414.40] Maybe learn something.
[1415.62 --> 1416.70] And support the show.
[1417.50 --> 1419.70] Linode.com slash SSH.
[1419.70 --> 1428.50] Now, I came across a thread on Reddit a couple of weeks ago that Shaw, who's an ISP in Canada,
[1428.76 --> 1435.12] was blocking Plex because it thought it was suspicious, which tingled my spidey sense a little bit.
[1435.62 --> 1440.04] Because I often tell people that I share my Plex server with that the ISPs don't care.
[1440.16 --> 1442.02] It's all just encrypted traffic.
[1442.18 --> 1444.46] They have no idea what is going on, right?
[1444.46 --> 1446.42] And so I dug into it a little bit.
[1446.48 --> 1451.30] And one of the comments has some really interesting information about how the Plex web app works,
[1451.36 --> 1453.68] which I thought might be interesting to share with you all.
[1454.62 --> 1461.36] Now, Shaw Protected Browsing uses a service called Zvelo, which happens to flag app.plex.tv.
[1461.36 --> 1469.06] And the way that the Plex app works in your web browser is it downloads the code to the browser and then runs it locally.
[1469.36 --> 1477.40] So if you can't access or the web URL is blocked by an ad blocker or some kind of safe browsing plugin,
[1478.48 --> 1481.18] it just can't download the code and you can't run it.
[1482.04 --> 1489.80] And because of this, you know, it could affect things running, you know, a web app on a TV, for example, might suffer the same fate.
[1489.80 --> 1495.38] And I just thought it was really interesting that these apps aren't local.
[1495.66 --> 1501.44] They're not locally rendered, which is why when Plex update their UI, you don't have to download anything.
[1501.68 --> 1503.46] It just automatically happens.
[1504.90 --> 1509.22] Plex clients for Android, Android TV, iOS, tvOS, etc.
[1510.12 --> 1512.84] aren't affected because they are full versions of the app.
[1512.84 --> 1524.06] So if you have a smart TV or a hosted Plex web app.plex.tv, you're probably going to want to find a way to route it around something like Zvelo,
[1524.18 --> 1527.52] which is what Shaw uses to avoid this issue.
[1528.24 --> 1530.20] It's hard to not be skeptical.
[1530.64 --> 1531.60] Safe browsing.
[1531.78 --> 1535.00] This just sounds like they're trying to reduce load on their network, doesn't it?
[1535.02 --> 1538.10] Or perhaps encourage people to sign up for streaming packages.
[1538.10 --> 1551.38] I absolutely find it abhorrent that Verizon or AT&T, they all do it here, have different quality profiles of Netflix videos or YouTube videos.
[1551.52 --> 1557.26] And they lock you into certain quality profiles unless you pay them more money.
[1557.26 --> 1563.52] This is one of the reasons I decided to set up my PepWave with their Fusion Hub VPN solution,
[1563.72 --> 1570.82] because it routes my traffic through a VPN and they can't tell what it is, and so they don't re-encode the video for me.
[1571.28 --> 1575.46] Actually, what AT&T does, each provider does a little bit differently.
[1576.10 --> 1580.04] And AT&T is particularly frustrating because they just sort of brute force it.
[1580.04 --> 1586.98] So that way, the YouTube client and the Netflix client, they just sit there and bang their head against the video streaming service,
[1587.06 --> 1590.24] asking for the best quality, and it keeps failing and failing and failing.
[1590.56 --> 1596.78] And then when the client finally says, okay, fine, I'll go down to the next lower quality, it tries that, that fails.
[1596.86 --> 1599.84] And then when it finally goes down to 480p, then it plays.
[1599.94 --> 1604.74] So you just sit there waiting while your carrier is blocking these connections.
[1604.74 --> 1607.96] You wait with your little spinner on the screen.
[1608.14 --> 1609.10] It's so frustrating.
[1609.34 --> 1613.88] And to see Shaw do this for Plex, it really, it stinks.
[1614.24 --> 1614.98] It stinks.
[1615.10 --> 1618.96] Because the reality is they know what's going on over that Plex port.
[1619.06 --> 1622.70] They know it's not some sort of attack or some sort of weird malware.
[1622.90 --> 1624.26] They know it's video streaming.
[1625.10 --> 1629.82] And my reading of the law is the copyright violation really happens when you download the file.
[1629.82 --> 1636.32] I think, I don't know, I could be wrong if anybody wants to let me know in a clear, explain it to me like I'm a five-year-old way,
[1636.64 --> 1637.92] cell phone.show slash contact.
[1638.04 --> 1641.40] But my understanding is you're not actually violating copyright if you stream it.
[1642.10 --> 1643.10] That can't be right.
[1643.44 --> 1647.50] But either way, I don't know how Plex scoots around that particular issue.
[1647.90 --> 1652.20] But regardless, it's not Shaw's place to enforce copyright law.
[1652.36 --> 1654.44] It's just not, or IP law.
[1654.54 --> 1656.72] It's just, they should just be passing the bits.
[1656.72 --> 1661.38] Yeah, I don't expect my water company to choose which bits of water I get.
[1663.00 --> 1665.56] Yeah, although you do want them to keep the bad stuff out of the water.
[1665.74 --> 1667.34] So that might be a bad analogy.
[1668.74 --> 1673.48] I know, Alex, you are, you are very organized compared to me in your Plex collection.
[1673.48 --> 1675.98] Like you have collections for everything.
[1675.98 --> 1678.42] You've got nice, consistent album art.
[1678.58 --> 1684.42] Like at some point in time, you must have just sat back, had a drink and spent like hours organizing all of your metadata.
[1684.76 --> 1685.70] Well, I am now.
[1685.70 --> 1689.90] This week I've found possibly my new favorite Plex pick of the year.
[1690.50 --> 1691.82] Plex Meta Manager.