Nice. Software developer, gamer, occasionally 3d printing, coffee lover.
My first impression from the adhesion issue (which doesn’t appear to be the main issue of this post) is that you may need to clean your build plate. But considering it was relatively good as it is, I assume you did and the few spots may just be accidental touches to the surface. In either case, their guide is here: https://wiki.bambulab.com/en/filament-acc/acc/pei-plate-clean-guide
As for the extrusion issue - considering the apparent randomness of it my guess would be either an issue with the filament or a partial clog.
Yup, with PIA the port is random but yes, there should be scripts out there to leverage PIAs forwarding with your torrent software. And yeah, if you were to port forward through your router that could lead to accidentally exposing your actual IP.
incompatible with port forwarding with any VPN
I’m not sure if there is a misunderstanding here, but port forwarding through a VPN is generally agnostic of most network setups. It’s a tunnel, doesn’t require your network to have port forwarding setup or even for it to be capable of it.
There are quite a few text equivalents. text-generation-webui looks and feels like Automatic1111, and supports a few backends to run the LLMs. My personal favorite is open-webui for that look and feel, and then there is Silly Tavern for RP stuff.
For generation backends I prefer ollama due to how simple it is, but there are other options.
So far I’ve helped my team of 5 get on them. Some other teams are starting as well. We’ve got Windows, Linux, and Mac OSX that developers are running on their work machine (for now), and the only container specific issue we ever encounter is port conflicts, which are well documented with easy to change environment variables to control.
The only real caveat right now is we have a bunch of micro services, and so their supporting services (redis, mariadb, etc.) end up running multiple times, so their is some performance loss from that. But they’re all designed to be independent, only talking to each other via their API, so the approach works.
If this is your take your exposure has been pretty limited. While I agree some devs take it to the extreme, Docker is not a cop out. It (and similar containerization platforms) are invaluable tools.
Using devcontainers (Docker containers in the IDE, basically) I’m able to get my team developing in a consistent environment in mere minutes, without needing to bother IT.
Using Docker orchestration I’m able to do a lot in prod, such as automatic scaling, continuous deployment with automated testing, and in worst case near instantaneous reverts to a previously good state.
And that’s just how I use it as a dev.
As self hosting enthusiast I can deploy new OSS projects without stepping through a lengthy install guide listing various obscure requirements, and if I did want to skip the container (which I’ve only done a few things) I can simply read the Dockerfile to figure out what I need to do instead of hoping the install guide covers all the bases.
And if I need to migrate to a new host? A few DNS updates and SCP/rsync later and I’m done.
And despite having cloud integrations, if my WAN is offline I can still view my doorbell. I haven’t tested it HA received notifications or anything though, as I just rely on the Unifi Security app.
Are you copying it to a locally mounted ext4 or is it a network share of an ext4 drive, and if so - what type of network share?
Yeah I was surprised. I’m hoping it was a manufacturing defect and assuming they replace it it doesn’t happen again. If they don’t replace it though I have to stick to my convictions.
As an avid dbrand fan, their grip case for the Pixel 9 Pro was disappointing. The plastic around the USB port is super brittle and broke after less than a week. Now the bottom is deformed and I’m waiting on a reply to my support ticket before I find an alternate case and kiss my skin goodbye
Incoming based on the code here:
There are some great mobile games out there. A few of my favorites include Dawncaster and Slice & Dice. Personally when I’m looking for a new game I use https://www.darkpattern.games/ to check if they are exploitive.
60C is when PLA starts to warp, but even lower is when it starts to degrade. 6 years is more than enough for this level of degradation even in a less volatile environment.
Holy shit, 10,000 commits because each change was individual (I’m assuming automated).
I’ve seen it a few times in passing and always assumed it was like, a tech demo or proof of concept.
I’ve had bad tinkering break my system before, but never had an update break it irreversibly. The closest would actually be on Silverblue itself, when an update to the kernel was using different signing keys that cause the system not to boot. Fortunately it was simple, I selected the previous deployment and I was in (on a non versioned OS I would have selected the previous kernel which most are configured to retain the last few). A quick Google revealed Ublue had a whole kerfuffle and after verifying it was legit, I enrolled the new certs into my MOK.
Although one time on Arch I had installed an experimental version of Gnome from one of their repos, and was pleasantly surprised when that version finally released and I removed the experiment repo and did an update absolutely nothing at all broke. Nothing.
This consternation is definitely common. It’s hard to apply skills to something with no long term impact of benefit. I’ve improved my skills by finding stuff I can help on in the communities I participate in.
It’s natural to be overwhelmed, so deciding on a project does scope what you can learn, but a hard part is architecting the foundation of that project.
Introducing new features to an existing project is a great way to get your feet wet - it has multiple benefits, for one of you do take a position as a developer in the future, you likely won’t be architecting anything initially, primarily improving on existing projects. So participating in OSS projects is a similar mechanism to that - you have to learn their codebase to a degree, you have to learn their style and requirements, etc.
Even if you don’t ultimately contribute, it’s still a learning experience.
The fundraising was for the development of Pixelfed’s source code. e.g. adding new features, bug fixing, etc. - not for currently hosted servers and their infrastructure. So it went to @dansup.