IsoKiero

@IsoKiero@sopuli.xyz

• ⁨Comment⁩ on ⁨New nickel-iron battery charges in seconds, survives 12,000 cycles⁩ ⁨⁨3⁩ ⁨days⁩ ago⁩:

  Team expects, may be useful, could be used, prototype, are currently investigating and so on. Cool piece of technolgy, but no even mention when they’d expect that to be commercially available, if it’s even possible to manufacture in commercial scale. Like many other new battery chemistries and technologies, it shows promise and makes a good headline, but at this point that’s pretty much it.

• ⁨Comment⁩ on ⁨Is the Raspberry Pi Still an Affordable SBC? I Don't Think So⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Armbian works on most, if not all, raspberry pi compatible boards. I meant that support from vendor is often a lot shorter than from raspberry and it can cause problems/bugs with bootloaders and drivers unless vendor is actively working with armbian/kernel development for their chipset.

• ⁨Comment⁩ on ⁨Is the Raspberry Pi Still an Affordable SBC? I Don't Think So⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  Orangepi and other “clones” often use rockchip on their boards which isn’t as well supported as Raspberry equivalent so it’s not direct replacement. Also their supported lifespan is often much less than rpi.

• ⁨Comment⁩ on ⁨Tor calls for more Snowflake proxies!⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  It is, but the sad reality is that while you contribute your capacity for good cause it’ll be abused by bad actors as well. Obviously with snowflake node you don’t get to see what’s excactly going trough, but some time ago I had exit node running and I got several calls from my ISP that there’s malicious traffic coming from my IP address. ISP managed it pretty well when I explained what’s going on but eventually they got so many complaints from other peers on the network that they took ‘hard route’ and told that they’ll take my connection down unless I shut down the node. No hard feelings for the ISP, they took all the abuse mails and other annoyance for me and I absolutely understand their decision. But it’s good to at least acknowledge that tor isn’t just to get around oppressive policies.

• ⁨Comment⁩ on ⁨AI Didn't Break Copyright Law, It Just Exposed How Broken It Already Was⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:

  I wouldn’t compare Swartz with the AI scrapers. Aaron pulled mostly public domain documents from JSTOR and caused minor issues with the servers which is “a bit” different than pulling everything from the internet to a database over a practically global DDOS-attack. But when companies do it it’s apparently somehow different and Swartz was pretty much publicly lynched and eventually bullied to suicide.

• ⁨Comment⁩ on ⁨Finland's Ministry of Justice is considering halting its plans to start using US-hosted cloud services⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  It’s a government thing. I’m not sure when they’ve started to consider alternatives, but that renewal process (as old systems are on EOL) has most likely been on the table for years.

• ⁨Comment⁩ on ⁨Frigate NVR Critical RCE Vulnerability⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

  That’s my use case. But my frigate-box is strictly behind firewall and I access it over wireguard when I’m away.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Get a VERY good on-site support deal for your hardware. You also may need to adjust TTL values on your network stack.

• ⁨Comment⁩ on ⁨Upgrading storage to usb drives⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  You’re not worrying for nothing. Losing wall power will shut down the drives and as usb-cradle is generally slower than “proper” drive bus it’s more likely that some write operation is going on when power is lost and that’ll potentially cause data corruption. Obviously not every power outage will cause issues, but I’d say it’s a higher risk with USB-drives than with drives on a SATA/m.2 bus.

  But no matter what your setup is, raid is not a backup. All kinds of things can happen which cause loss of data and you should plan accordingly. If all you have is two drives on usb-cradles I might choose to use one of them as a offline backup disk and one for ‘live’ data so that it’s more likely that at least one of the drives is functional even after power issues or whatever, but that approach has it’s own problems too.

• ⁨Comment⁩ on ⁨What are your technology mispredictions?⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  I had a two (or maybe a bit less) bitcoins on my wallet back in the day. I sold them for ~20€.

• ⁨Comment⁩ on ⁨What are your technology mispredictions?⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Well, the touchscreen part and maybe a bit more, had the same reaction on many directors at Nokia at the time. I don’t know if they feel like an idiot, but at least you’re not alone.

• ⁨Comment⁩ on ⁨'Worst in Show' CES products include AI refrigerators, AI companions and AI doorbells⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  Cameras don’t stop anyone, but I still have few recording my yard. It’s more of a hobby and I’m planning to integrate person detection on those to home automation but for me it’s also a small piece of peace on my mind. Should someone steal my car trailer (or a car) I’d have some footage for the police and insurance. Also a while ago we had a decent storm around and we weren’t at home so it was nice that I could check for possible damages remotely.

  But absolute majority of time I don’t even think about them. I don’t have any notifications enabled, I’m not interested about neighbors cat running across our yard or getting interruptions every time someone on the family comes or goes. And while Frigate has some AI things built in, the whole thing runs locally. There’s no way I’d install nest or some other camera which sends/stores data to anywhere which isn’t 100% in my control.

• ⁨Comment⁩ on ⁨LVM question⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  I haven’t tested lvm on arm-based systems, but if it doesn’t automatically locate them you could try pvscan/vgscan/lvscan.

• ⁨Comment⁩ on ⁨'Microslop' is heading for Edge – major browser redesign is inspired by Copilot, and it's already seriously unpopular⁩ ⁨⁨5⁩ ⁨weeks⁩ ago⁩:

  We still have handful of those around at work. 2000, XP and maybe some embedded variant of 98 too still somewhere. They are controlling some non-critical but still useful industrial stuff with stupidly large price tag to replace.

  Specially XP is still going to be around for quite a while in industrial settings where the production line is controlled via single computer and replacing it would mean replacing the whole line with price tag potentially in millions. And those aren’t even that old machines, their planning and manufacturing just takes “a while” due to certifications and everything.

• ⁨Comment⁩ on ⁨LVM question⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  If you’re talking about just moving the physical volumes (as in the actual hard drives) as is to another computer they’re automatically scanned and ready to go in majority of modern distributions. No need to export/import anything. This is obviously assuming your boot drive isn’t a part of volume group and you have healthy drives at your hands. You can test this with any live-distribution, just boot from USB into a new operating system and verify your physical volumes/volume groups from that.

  If you want to move the volume group to a new set of disks simplest way would be to add physical drive(s) to volume group and then removing the old drive(s) from it after data has been copied. Search for pvmove and vgreduce. This obviously requires a working system, if your data drive has already failed it’s a whole another circus.

• ⁨Comment⁩ on ⁨Windows 11’s 2025 problems are getting impossible to ignore⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Microsoft deserves all the crap they’ve ordered, but skipping 9 on versioning was pretty smart move on their part. There’s still a ton of older software which just checks if windows version matches ‘windows 9’ to include both 95 and 98 (and all their variants). If 8.1 was released as 9 it would’ve broken a lot of compatibility which at least then was a big deal for Windows. And it still is, but now it seems that they’ll happily break everything from their most known product.

• ⁨Comment⁩ on ⁨Contract for self-hosting help⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Even if your router acts as an DNS proxy it shouldn’t overload any pihole installation unless you have a crapload of devices doing millions of queries per hour. My pihole manages all my devices (20-30 individual things) without any problems and even if I hit some rate limit it’s going to be a change to default configuration, not a immovable object on your way. Based on quick glance over that reddit thread a new router might be a good option, but that’s another easy-ish task to accomplish. I use mikrotik device and I’m pretty happy with it but there’s a ton of good options.

  For hiring someone to coach you I can see quite a few of potential issues. People who claim to know what they’re talking about but don’t really have the knowledge, straight up scammers obviously, mismatch in personal chemistry which will make learning unnecessarily difficult or even impossible, some people just aren’t good at teaching even if they do know their stuff and so on. By all means, use your money however you like, but I personally strongly advice against it unless you can get some courses on (preferably local) reputable vendor. You can look for online courses too, cisco has a ton of courses on networking, redhat has plenty of linux courses and other big players have their own training and even certificates if you want to go that far.

• ⁨Comment⁩ on ⁨Contract for self-hosting help⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  For pihole you don’t need support from router. It’s convenient if you can adjust dhcp-server settings so that pihole will automatically cover your whole network, but it’s not a requirement, you can just manually set each device to use pihole as DNS server. All you need is a static IP address outside your DHCP -pool. For spesific router configurations, you can ask those too, just include spesific model and possibly screenshots from your router interface.

  That iMac of yours is more than enough to get you going. If you plan to run multiple things on it it might be good idea to look for hypervisors like proxmox or ovirt, but basic qemu+libvirt -setup on pretty much any linux-installation will work just fine too.

  For the 3rd part, your concerns are mostly about networking and setting up pihole/other servers on your local network will gain you knowledge on how to manage that as well. Also, you can set up nextcloud/immich/whatever locally at first, get familiar with them and then allow access from the internet either via bitwarden or other tunneling or directly over public network. Latter has obviously way bigger threat models than using VPN and accessing stuff that way, but gladly the networking side of things is somewhat it’s own beast from the servers so you can build everything local only at first and then figure out what’s the best approach for you with remote access.

• ⁨Comment⁩ on ⁨Contract for self-hosting help⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  However right now I’m simply feeling overwhelmed and blocked.

  I could explain to you in pretty decent detail how to build a setup which could cover pretty much every imaginable scenario for a home gamer, but that would also be suitable to serve a mid-sized company who’ll have multiple people on duty to manage the servers, storages, security, networking and other stuff. Also it’d cost roughly as much as a decent house. That’s close to the ‘big picture’ you’re looking for and equally overwhelming than your current situation. I’ve been earning my living with this stuff for quite a while now and there’s still a ton of things I’m at a very much beginner level. Maybe the difference now vs starting this is that I actually have some idea on things which I don’t know and thus I know when to learn more/ask from more experienced team members.

  Just like eating an elephant, this field requires that you take it piece by piece. You’ll learn new things to build both your setup and your knowledge further, but if you try to eat it all at once it just doesn’t happen. First you need to decide a simple goal on what you want to get out of self hosting. DNS-based ad-blocking on your network is pretty neat and setting up pihole will get you started. Also with that you don’t need to allow any external connections to your network. Plus if something goes wrong you can easily just return to where you started from and try again. Setting your own router with DHCP, caching DNS and other stuff is pretty neat too and it’s also pretty simple to isolate from the rest of the network so you’ll have your ‘normal’ stuff still working while you learn for new things. Whatever it is, set up a relatively simple goal to work for. Then you can start to ask questions like ‘is raspberry pi 4 suitable for this’ or ‘what subnet I should use for my homelab’ or even ‘how to install debian on a old laptop to run pihole’.

  Or if you really insist on going to the deep end, go to library and pick up TCP/IP Network Administration from O’reilly (altough that might be a bit outdated by now) or something similar and dig in. The o’reilly one has a bit over 700 pages to go trough. There’s equally in-depth books for linux administration, firewalls, network security and so on. Annas archive will most likely have some decent books too if you don’t care about legal issues and want to go trough brick-sized books as pdfs.

• ⁨Comment⁩ on ⁨Contract for self-hosting help⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Some random thoughts about your points:

  1. It’s a pretty damn big picture you’re looking at. Networking, backups, hypervisors, storage solutions, security and a lot of other topics are each big enough that you can make a career out of any of those alone. Obviously you don’t need to know everything about everything but as you learn more you’ll find more and more stuff to learn so I’d say there’s no practical way to learn ‘big picture’ just over a few hours of ‘lessons’. Also there’s a ton of variations on what one might consider as ‘self hosting’. Some will have setup comparable to decent sized company, others will have a single raspberry pi on top of their router.

  2. Same goes here, it’s a pretty big field to go trough. The best setup for me is most likely very different from the best setup for you. Also with real world constraints (money, bandwidth, space available, electricity price…) the best setup is practically quaranteed to be some kind of compromise. Also, at least in my opinion, it makes sense to start with what you already have or can cheaply get, so that you’ll get something out of the system with as little investment as possible even if the first iteration might be a bit janky. Also your needs will likely change over time so the ‘optimal’ configuration for today might be wildly different from the configuration tomorrow.

  3. This goes hand-in-hand with first point. You need to understand some basic networking, backup scenarios and proper threat mitigation against security threats, hardware failures, power outages and so on. Also there’s no ‘initial setup’ after which the system is complete as, again, your needs will change over time.

  4. That’s why we’re here. Just describe your problems in a reasonably sized chunks. Don’t ask how to build a homelab but instead ask for something more spesific which doesn’t have a crapload of variables to figure out before getting to the actual problem.

  For the money part, I’ve done stuff like this for companies (getting suitable hardware for their needs, setting it up, offering support…) as a freelancer and at least in here that’ll cost you 80-150€/h commercially. Even as a hobbyist I personally wouldn’t take that kind of contract as I heavily doubt that you’re willing to throw thousands of euros on the table (as properly going trough your list will take quite some time). However, if you can narrow things down and ask for something spesific I’ll happily reply to you around here for free if I happen to have time and/or knowledge about the matter.

  So, figure out what you want from the system right now, what’s the first thing you want to build. It might be a hypervisor so you can keep experimenting with virtual machines, it might be a pihole for your network or something else, but you’ll need a pretty spesific goal. Then you can come back and ask more spesific questions and get deeper into the rabbit hole. Also, specially if you’re starting from scratch, there’s no such thing as a perfect setup. I’m working on a decent sized company with offices around the globe and even with those resources there’s still compromises with pretty much everything as cooling capacity, bandwidth, financial, man hours and other things aren’t infinite.

• ⁨Comment⁩ on ⁨Librarians Are Tired of Being Accused of Hiding Secret Books That Were Made Up by AI⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Just a few days ago I tried to feed my home automation logs to copilot in hopes that it might find a reason why my controller jams randomly multiple times per hour. It confidently claimed that as my noise level reported by controller is -100dB (so basically there’s absolutely nothing else on that frequency around, pretty much as good as it can get) it’s the problem and I should physically move the controller to less noisy area. A decent advice in itself, it might actually help on a lot of cases, but in my scenario it’s a completely wrong rabbit hole to dig in. I might still move the thing around to get better reception on some devices but it doesn’t explain why the whole controller freezes for several minutes on random intervals.

• ⁨Comment⁩ on ⁨Holiday Upgrade Disasters⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  If it tries to start but doesn’t do anything it’s pretty much a lost cause then as the drive gets power but fails to initialize. In theory a simple broken solder joint somewhere might cause that and that might be fixable, but that requires at least somewhat decent soldering station and some experience. Or maybe you could get a donor board and swap out memory chips from the old one, but that’s even more tricky. Hopefully it’s not too expensive lesson.

• ⁨Comment⁩ on ⁨Holiday Upgrade Disasters⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  I’ve had some luck with portable drives by removing the drive from enclosure and attaching it directly to sata-bus instead of USB. Also, as a general rule for anyone who might stumble on this, whenever attempting recovery at first create an image (I use ddrescue) and work with that. That way you’ll minimize risk of causing even more damage.

  A while ago we “fixed” couple of hard drives with my brother. All of them had a single faulty diode, apparently it was a known failure point on those drives and brother found instructions online how to bypass that diode. Obviously that doesn’t really fix the drives, but a small piece of wire and some soldering was enough to get drives spinning again long enough that he could copy data over to new drives.

• ⁨Comment⁩ on ⁨Dell and Lenovo may limit mid-range laptops to 8GB DDR5 RAM in response to rising memory prices⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  With cloud computing you get someone (or at least some entity) to blame when things go wrong which apparently has some value too. Also, if you don’t need a lot of resources cloud can be cheaper than setting up whole infrastructure by yourself, but that has a ton of variables. Plus with cloud there’s often option for colocation/high availability/ddos protection and other stuff around which can be pretty expensive to build yourself.

  Obviously if you try to shoehorn your current modrate sized esx/hyper-v/whatever environment to the cloud as is, that’s going to be expensive.

• ⁨Comment⁩ on ⁨Backing up Spotify⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  You can get refurbished hard drives for around 300$/20TB (quickly searched estimation). So, 15 drives plus maybe another 5 for raid reundancy takes you back 6k$. Server to hold those drives 1-2k$ (used), UPS, internet connection and other bits’n’bobs and your total is very roughly around 8k$ (or €, as I threw the estimations on a pretty big ballpark).

• ⁨Comment⁩ on ⁨UK to “encourage” Apple and Google to put nudity-blocking systems on phones⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Damn right. I paid for the device, it’s mine and I can use it solely to take pictures of my bare ass should I choose so. There’s of course, and for a reason, limitations on how I can use those pictures, but those apply to any device capable of taking a photo of anything. But I can still use pictures of my ass as a wallpaper in my own home if I want to.

• ⁨Comment⁩ on ⁨What's the security situation when opening a jellyfin server up for casting?⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Not spesifically helpful with your cgnat-situation, but my jellyfin runs on a isolated network and it’s just directly exposed to the internet via named reverse proxy in order to share the library with family and friends. Should someone get access to that they can obviously use the VM for nefarious purposes, but it’s a known risk for me and the attacker would need to breach trough either my VLAN isolation or out of the virtual environment to my proxmox host if they wanted to access my actually valuable data.

  Sure, there’s bots trying every imaginable password combination and such, but in my scenario even if they could breach either the jellyfin server or reverse proxy it’s not that big of a deal. Obviously I keep the setup updated and do my best to keep bad actors out. but as I mentioned, breach for that one server would not be the end of the world.

  With cgnat there’s not much else to do than to run a VPN where server is somewhere publicly accessible and route traffic via that tunnel (obviously running a VPN-client on jellyfin-server or otherwise routing traffic to it via VPN). Any common VPN-server should do the trick.

• ⁨Comment⁩ on ⁨Decreasing Certificate Lifetimes to 45 Days⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  It’s pretty simple to set up. Generate CA, keep key and other private stuff stored securely, distribute public part of CA to whoever you want and sign all the things you wish with your very own CA. There’s loads of howtos and tools around to accomplish that. The tricky part is that manual work is needed to add that CA to every device you want to trust your certificates.

• ⁨Comment⁩ on ⁨⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  And given how “fast” IPv6 adoption has been, switch to something non-IP based is not going to happen any time soon.

  Also, while I kind of get the idea author is talking about, pulling random addresses out of thin air and managing routing for that, even on a small scale, is going to have a crapload problems. Without subnet hierarchy with routes, gateways and stuff would mean something like globally broadcasted ARP packets and absolutely massive routing tables on endpoints. Plus with that approach the reslience of IP-networks would be lost (or routing tables would need to grow even more).

  Also there’s some pretty big issues with malicious actors on the network, incompatibility with every router on planet and a ton more. What that kind of approach working globally would need is some scifi-level networking without latency or bandwidth limitations.

• ⁨Comment⁩ on ⁨Lawmakers Want to Ban VPNs—And They Have No Idea What They're Doing⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  RTT is just ‘a bit’ slower than via usual transfer channels.