• 1 Post
  • 51 Comments
Joined 3 years ago
cake
Cake day: June 7th, 2023

help-circle

  • I ditched cable TV over a decade ago for a simple antenna (and wrote a notable Reddit post on the antenna while I was at it). That was done because I was tired of my wallet being raped each month, because I had to buy a higher bundle to get the channels I wanted. I was stuck with cable internet for a number of years afterwards, as it was the only option in my area. Then T-Mobile offered up 5G based internet in my area at a low price. That was around 6 years ago and I haven’t looked back.

    The cable companies sat on their laurels while the world moved on. They are now shocked that their terrible offerings for terrible prices are falling to real competition. Sure, I fully expect the new carriers to do everything in their power to enshitify their service offerings. That’s the nature of business/ But, with the market open to competition, there is now a real opportunity for us customers to shop around and get a less shitty experience. Broadband internet is a commodity and is completely fungible. Prices should be falling and it was only rent seeking rules keeping the prices up.


  • This is it exactly. I made a hard cut with Reddit, but I’ll admit to missing the sysadmin subreddit. The place was full of very smart, helpful people and also cranky. The PowerShell subreddit was another great resource. I haven’t been willing to go back, but those sorts of communities only exist when you hit a certain mass of people on a platform.



  • Yes, and you can probably get better performance with different block sizes. This is just what I used to fix drives as it was fast enough and I couldn’t be arsed to do any real testing to find the right speed. Also, my stash of drives was no where near homogeneous, so the right size for one type of drive may not have worked for a different type of drive. I also used the 4MB block size when imaging drives to have an ok-ish speed while not losing too much data if there were read errors.



  • I can think of a couple of reasons off the top of my head.

    You don’t say, but I assume you are working on-site with your work system. So, the first consideration would be a firewall at your work’s network perimeter. A common security practice is to block outbound connections on unusual ports. This usually means anything not 80/tcp or 443/tcp. Other ports will be allowed on an exception basis. For example, developers may be allowed to access 22/tcp outbound, though that may also be limited to only specific remote IP addresses.

    You may also have some sort of proxy and/or Cloud Access Security Broker (CASB) software running on your work system. This setup would be used to inspect the network connections your work system is making and allow/block based on various policy settings. For example, a CASB might be configured to look at a domain reputation service and block connections to any domain whose reputation is consider suspect or malicious. Domains may also be blocked based on things like age, or category. For this type of block, the port used won’t matter. It will just be “domain something.tld looks sketchy, so block all the things”. With “sketchy” being defined by the company in it’s various access policies.

    A last reason could be application control. If the services you are trying to connect to rely on a local program running on your work system, it’s possible that the system is set to prevent unknown applications from running. This setup is less common, but it growing in popularity (it just sucks big old donkey balls to get setup and maintain). The idea being that only known and trusted applications are allowed to run on the system, and everything else is blocked by default. This looks like an application just crashing to the end user (you), but it provides a pretty nice layer of protection for the network defenders.

    Messing with the local pc is of course forbidden.

    Ya, that’s pretty normal. If you have something you really need to use, talk with your network security team. Most of us network defenders are pretty reasonable people who just want to keep the network safe, without impacting the business. That said, I suspect you’re going to run into issues with what you are trying to run. Something like SyncThing or some cloud based storage is really useful for businesses. But, businesses aren’t going to be so keen to have you backing their data up to your home server. Sure, that might not be your intention, but this is now another possible path for data to leave the network which they need to keep an eye on. All because you want to store your personal data on your work system. That’s not going to go over well. Even worse, you’re probably going to be somewhat resistant when they ask you to start feeding your server’s logs into the businesses log repository. Since this is what they would need to prove that you aren’t sending business data to it. It’s just a bad idea all around.

    I’d suspect Paperless is going to run into similar issues. It’s a pretty obvious way for you to steal company data. Sure, this is probably not your intention, but the network defenders have to consider that possibility. Again, they are likely to outright deny it. Though if you and enough folks at your company want to use something like this, talk with your IT teams, it might be possible to get an instance hosted by the business for business use. There is no guarantee, but if it’s a useful productivity package, maybe you will have a really positive project under your belt to talk about.

    FreshRSS you might be able to get going. Instead of segregating services by port, stand up something like NGinx on port 443 and configure it as a reverse proxy. Use host headers to separate services such that you have sync.yourdomain.tld mapped to your SyncThing instance, office.yourdomain.tld mapped to your paperless instance and rss.yourdomain.tld mapped to FreshRSS. This gets you around issues with port blocking and makes managing TLS certificates easier. You can have a single cert sitting in front of all your services, rather than needing to configure TLS for each service individually.



  • I run Pi-Hole in a docker container on my server. I never saw the point in having a dedicated bit of hardware for it.
    That said, I don’t understand how people use the internet without one. The times I have had to travel for work, trying to do anything on the internet reminded me of the bad old days of the '90s with pop-ups and flashing banners enticing me to punch the monkey. It’s just sad to see one of the greatest communications platforms we have ever created reduced to a fire-hose of ads.







  • I started self hosting in the days well before containers (early 2000’s). Having been though that hell, I’m very happy to have containers.
    I like to tinker with new things and with bare metal installs this has a way of adding cruft to servers and slowly causing the system to get into an unstable state. That’s my own fault, but I’m a simple person who likes simple solutions. There are also the classic issues with dependency hell and just flat out incompatible software. While these issues have gotten much better over the years, isolating applications avoids this problem completely. It also makes OS and hardware upgrades less likely to break stuff.

    These days, I run everything in containers. My wife and I play games like Valheim together and I have a Dockerfile template I use to build self-hosted serves in a container. The Dockerfile usually just requires a few tweaks for AppId, exposed ports and mount points for save data. That paired with a docker-compose.yaml (also built off a template) means I usually have a container up and running in fairly short order. The update process could probably be better, I currently just rebuild the image, but it gets the job done.



  • a Bambu Labs compatible heat sink, an E3D V6 ring heater, and a heat break assembly are required
    a fan was sacrificed to mount a Big Tree Tech control board. Most everything ended up connecting to the new board without issue, except for the extruder.
    made a custom mount for the ubiquitous Orbiter extruder.
    The whole project was nicely tied up with a custom-made screen mount.

    So, other than the enclosure and print bed, what’s actually left of the original printer? It seems like the way to get a Bambu printer to run FOSS is to open the box from Bambu Labs, toss everything inside the box in the trash, drop a custom built printer in the box, and then proceed with your unboxing.


  • I have to agree with @paf@jlai.lu on this. I’d much rather have those models as part of the ecosystem than not. I do think part of the 3d printing hobby is learning to look at a model and recognize what can be printed on what type of printer, where supports are needed and where modifications may need to be made. For example, I recently purchased a model through TitanCraft. And the models they create are clearly designed with a resin printer in mind. they have some small features which are difficult or impossible to print on an FDM printer. While I knew that mini-figure models can be challenging on FDM, I went ahead with the purchase anyway. And the resulting min-fig’s staff was so thin my printer just couldn’t print it cleanly. I had to load the STL into Blender and spend an hour or two separating the staff out from the rest of the model and then I thickened it considerably. Sure, the haft of the shaft is a bit thick for the proportions of the model, but not too bad.

    I make a similar evaluation of stuff I see on the various model sharing sites, before I try to print it. Does it need supports? Are some of the details going to be very hard or impossible for my printer to make? Should I split the model? And, while I am pretty crap at Blender, I may consider doing some simple edits to make a model easier to print and/or make changes I want. For example, I liked these ghosts but didn’t care for the spring and just wanted them hollow so I could stuff a UV LED inside them. With glow in the dark PLA, these look neat at night. So, I beat my head against Blender until I had them how I wanted them.

    So, I wouldn’t want to stifle other peoples’ creativity. Let them create and enjoy the fact that people are willing to create and release this stuff for you to print. If it doesn’t work out, fix it and re-release it.