Datasets:
willtheorangeguy
/
2021-SelfHosted-Transcripts

Dataset card Data Studio Files
xet
 Community
text
stringlengths
9
408
[1725.82 --> 1726.62] Try it all out.
[1726.62 --> 1729.30] And take advantage of their machine learning alerting.
[1729.86 --> 1733.96] Datadog enables you to pinpoint the root cause of an issue faster than ever.
[1733.96 --> 1740.56] So try their products out for free for 14 days by visiting datadog.com slash selfhosted.
[1740.66 --> 1745.56] For a limited time, if you start a trial and create one dashboard, you'll get some free swag.
[1745.68 --> 1746.56] A Datadog t-shirt.
[1747.06 --> 1748.40] And I miss swag.
[1748.68 --> 1750.06] I miss event swag.
[1750.42 --> 1751.26] I miss t-shirts.
[1751.78 --> 1752.44] So go get one.
[1752.52 --> 1754.16] Datadog.com slash selfhosted.
[1754.20 --> 1754.62] Great account.
[1754.62 --> 1755.90] Get that trial going.
[1755.98 --> 1756.54] Get a t-shirt.
[1757.12 --> 1760.70] And then begin visualizing your entire infrastructure.
[1761.04 --> 1763.14] Datadog.com slash selfhosted.
[1765.10 --> 1766.52] Listener Chris writes in,
[1766.64 --> 1770.14] I run a number of services from my home server that are internet facing.
[1770.50 --> 1774.66] I understand that the smart best practice is to minimize that as much as possible.
[1774.66 --> 1777.66] But some of these things I want to access whilst I'm away from the house.
[1778.16 --> 1780.24] Some of them are also used by family members.
[1780.32 --> 1782.68] And so it's unavoidable on some levels.
[1782.94 --> 1784.08] My question is this.
[1784.08 --> 1789.82] How do I know if a service is hardened enough to raw dog it out on the open internet?
[1790.28 --> 1790.60] Wow.
[1791.80 --> 1793.96] We're just going to let's let that sit for a second.
[1795.16 --> 1795.96] How do you know?
[1796.10 --> 1797.44] How do you know if you can raw dog it?
[1798.06 --> 1798.40] Yeah.
[1798.50 --> 1802.14] I mean, I feel this one, you know, Plex is one, you know, Plex you kind of feel safe about.
[1802.22 --> 1806.04] But how do you know about some of the lesser used ones like subsonic or something?
[1806.12 --> 1806.32] Right.
[1806.32 --> 1810.20] I think it's safe to assume that everything is porous.
[1811.20 --> 1811.56] Everything.
[1812.06 --> 1812.34] Yeah.
[1812.34 --> 1815.30] I hate, though, that the answer always is put it behind a VPN.
[1815.76 --> 1815.98] Why?
[1816.16 --> 1820.22] I mean, with WireGuard these days, it's really the barrier to entry.
[1820.34 --> 1822.32] As long as you don't screw up your subnets like I did.
[1823.22 --> 1824.62] The barrier is pretty low.
[1824.78 --> 1828.92] But you have friends and family that are using your Plex server without connecting to WireGuard.
[1829.26 --> 1830.72] You know, like Plex is such a great example.
[1830.72 --> 1834.36] Or Jellyfin because you do often want to share with others.
[1834.62 --> 1834.98] That's true.
[1835.18 --> 1838.50] And I could see that being true with others as well.
[1838.90 --> 1840.48] Nextcloud he mentions in here.
[1840.66 --> 1843.66] But BabyBuddy, I'm not so sure about that.
[1843.78 --> 1845.44] You know, that starts to get a little more niche.
[1846.36 --> 1850.20] And I hate to be the guy that just says, well, if it's big, you can use it publicly.
[1850.30 --> 1851.76] And if it's small, you should hide it.
[1851.84 --> 1855.28] But that's kind of a general rule of thumb that I follow.
[1855.88 --> 1857.62] You know, you try to figure how many eyes have been on it.
[1857.62 --> 1861.02] You know, another angle to consider is security by obscurity.
[1861.72 --> 1867.38] Now, if you think that, you know, you just have a random URL that you're using to access this service.
[1867.58 --> 1869.14] And you've put it behind a reverse proxy.
[1869.58 --> 1873.60] And probably these days you're using Let's Encrypt to generate a certificate for it.
[1873.64 --> 1875.30] So that you know that things are secure.
[1876.12 --> 1877.48] Well, I've got bad news for you, I'm afraid.
[1877.54 --> 1881.96] If you go to crt.sh and type in your domain name.
[1881.96 --> 1889.48] You'll see every single certificate that's ever been issued by Let's Encrypt for your domain name.
[1890.10 --> 1899.26] And so you think to yourself, okay, well now my super secret string that I came up with to hide this service is now out in the public domain.
[1899.38 --> 1901.82] So really, it's not secret at all.
[1901.82 --> 1906.14] One thing you could do to kind of work around that is use a wildcard certificate.
[1907.02 --> 1908.98] That would kind of sort of help.
[1909.52 --> 1912.48] Because it wouldn't, you know, publish the actual string.
[1913.40 --> 1919.92] But it just goes to show to me that, you know, security through obscurity is really not, it's an illusion.
[1919.92 --> 1929.96] Yeah, and I was going to suggest throwing it out on like a VPS like Linode and run your software there for a bit on the public internet and monitor the logs.
[1930.10 --> 1933.20] But you could run something for six months and nobody nibbles at it.
[1933.28 --> 1938.14] And then on, you know, day one of seven months, somebody nibbles on it.
[1938.56 --> 1939.78] It's tricky that way.
[1939.78 --> 1949.38] And so it really, the only way to have full peace of mind, and that's what I've opted to do here in Lady Joops, is just to have absolutely zero outside inbound.
[1949.92 --> 1954.02] It's the only way I've found to be completely comfortable with it.
[1954.12 --> 1963.50] I don't necessarily always follow that rule myself because some services like mail servers, web servers, media streaming servers, they have to be public by their very nature.
[1963.78 --> 1969.42] So you have to hope that those just have more eyes and that they get a little more attention and that they've been a little more audited.
[1969.76 --> 1972.18] But remember, logging is your friend.
[1972.40 --> 1975.94] So if you ever suspect something weird is happening, go check your logs.
[1976.00 --> 1977.12] See if you have weird logins.
[1977.12 --> 1979.30] See if you have somebody hitting your website all the time.
[1979.30 --> 1980.36] Use Datadog.
[1980.68 --> 1980.94] Yeah.
[1981.26 --> 1981.58] Yeah.
[1981.62 --> 1983.60] Use something that will go through there and alert you.
[1983.72 --> 1985.22] That absolutely could be a good way to go.
[1985.72 --> 1989.78] It's a good question, though, listener Chris, because I'm sure it's one that people struggle with.
[1989.82 --> 1991.48] So let us know what you out there would do.
[1991.96 --> 1993.68] Self-hosted.show slash contact.
[1993.68 --> 1996.36] Now, we have Joseph who writes in.
[1996.42 --> 2001.28] He says, I have a bunch of those Tekken smart switches flashed with Tasmoto and they work great.
[2001.66 --> 2005.04] I have a need for smart switches to replace my wall switches, though.
[2005.40 --> 2010.22] You know, for example, like my kids' closet lights, which are always left on.
[2010.22 --> 2021.38] I would also love to replace the controllers on our ceiling fans with smart devices, something that would toggle the light on and off and also set the fan to high, medium or low or even off completely.
[2021.60 --> 2026.76] My preference would be for something I can self-host, non-cloud connected, open source software.
[2026.76 --> 2032.02] Are there any devices which would actually fill this need or similar to the way the Tekken smart plugs do?
[2032.32 --> 2032.88] What are your thoughts?
[2033.36 --> 2034.46] Well, this is an easy question.
[2035.00 --> 2038.62] The Shelly devices are exactly what you're looking for.
[2038.70 --> 2040.50] And I think we've talked about them on a previous episode.
[2040.76 --> 2047.32] But just to recap, they're about the size of an Oreo cookie and they go inside the light box behind the switch.
[2047.46 --> 2049.06] So you don't change the switch itself.
[2049.52 --> 2054.42] But this little cookie size box has a relay inside it.