Atop is pretty sweet for logging performance metrics over time and including data on what would have caused it with autosorting by effect of process included. Interface isn’t pretty and seems a little complicated on the surface but there are colors to help. That is if synology has repos to install it.

Not trying to be combative here but the tests you linked further support what I was saying. A small chamfer and I really mean small will have a similar effect once rendered in gcode to a fillet. If you have access to software to generate a fillet easily that is good too. That being said I would only do it for the outer rim.

Either way the print looks like it is warping on the lowest layers and has elephants foot which is what I suspect is the biggest issue here.

The steps I proposed are

1. Wash the plate to help with adhesion
2. raise z offset just a tiny bit
3. if possible add a chamfer
4. if adhesion is still a issue add a brim

Hey OP, just so you do not waste time. I mis-spoke and told you the opposite of what you should do in the program. No bevel, I meant chamfer!

I know it doesn’t make a lot of sense to make the surface area touching the build plate smaller but it is worth it since it provides relief from the layers above pulling when it is shrinking.

3 things.

1. Wash your build plate with soap and hot water. It helps more with adhesion than you think. Do not use glue stick or any adhesives on the plate. People report that it works but I always found significantly better results with just soap and hot water on pei with materials that adhere to pei well such as pla. Masking tape with adhesives might make a difference for materials that do not stick to pei.
2. If you are designing the part or have any time with cad then put a tiny bevel chamfer on the surface that touches the build plate. Doesn’t meet to be large. Just something. It helps with cooling shrinkage and retraction of pla on the first layers.
3. enclosure or still air will help but are not strictly needed for pla.

Last thing I would do is maybe adjust your z-offset. It looks like it might be experiencing some elephants foot at the bottom. I would try raising the head just by about .10. Really though that is going to be fully determined by your first layer of course.

Buy a 3d printer pen. Believe it or not they are pretty great at filling the spaces as long as the spaces are not too complicated or wide.

deleted by creator

That is a wild take imo.

This is the way. They have a image generator too

The head might be too close to the bed. You could potentially compensate with either additional top layers in the slicer or just give it some more room to lay down layer one. Another possible cause is potentially too much heat. I am going by the slight elephants foot at the bottom of the cube and the slight droop at the top of the X and Y.

If you ask me it should have been the cob. Not the kernel.

Just wanna add here that it is not just hurt in terms of time, money or loss of data(those are a given). It could even land you in legal trouble that you can not explain your way out of in some extreme circumstances.

This.

Also containerization in general. Not just docker. This includes podman and LXC (which is probably your best bet if you want a full system in a container)

If you are starting with nothing then maybe a lithophane conversion on the photo

https://3dp.rocks/lithophane/ https://itslitho.com/ https://github.com/muldjord/lithomaker

Just some options. 3dp.rocks works well from my experience. That would at least give you a starting point. I’d see if there is some way you can scale it on the z axis of the features are point straight up to get more depth on what the lithophane provides.

Link Yes it was very real and it was very much Canada lol

Agreed. Just point them to the repository. Cloning the repo and running the script is the barrier to entry here. If they can’t do that then reading it would do them no good either which means they have some learning to do.

Can confirm. Worked for a few years for authorized retail and they leaned pretty hard into it.

Filecoin showed promise as a nearly free option. I used to be a storage provider. Met a lot of other storage providers at conventions. The people involved were pretty alright. I haven’t interacted with the community in a few years though. Biggest problem I saw back then was a lack of a user friendly means of storing and retrieval. That might have changed now.

Whatever option you pick please make sure you encrypt your data before you send it off.

What ISP are you referring to? I have genuinely never heard of an isp that takes 24 hours to rotate your IP. Also utilizing dynamicdns is not going to incur more dns traffic? Dynamic DNS updates your dns provider from a system on your local network that your pub ip has changed then your provider will start sending traffic to the new ip. Propagation used to take a while but I haven’t experienced propagation wait times of over 10 minutes in years. This all being said dynamic DNS isn’t exactly the most elegant solution. It is just one of the simplest that I mentioned. There are significantly better options overall that completely take the requirement of a static pubip completely out of the equation and can be built using all free open source tools relatively easily.

I mean I’ll be real. Sure in some circumstances that could be an annoyance for 15 seconds for some software that might rely on a session whenever your ip changes like once a month if that. A rotating ip is probably one of the easiest things to work around amongst the plethora of challenges that ISPs present for those who want to self host.

I mean just take a look at what is involved if you are in a situation where cg-nat is implemented. You legitimately have no control over the root of your network at that point. I have that issue in particular with what is essentially a mobile hotspot as my failover for when my fiber fails. That being said I had to architect it in a way that took that took cg-nat into consideration. If I hadn’t then when fiber fails it would take down my services as a whole anyway.

My point is that those challenges have workarounds, you can solve those issues relatively easily and they even present a level of security. Where it is actively malicious is with restrictions to capacity such as upload limits in which they to a degree lie about their speeds and capacity. The terms of service stuff is just flat out awful too.

If you have control over at least the root of your network you can totally get away with hosting in a dynamic pub ip. You just need to set up dynamicdns. There are other ways of handling this specific issue too. You can always go to a colocation and set up a server there if you want. You could also create your own reverse proxy tunnel in a place that is public then forward it. There are lots of work arounds really. Yeah, it sucks that American ISPs generally don’t support ipv6 but there are totally ways to work around it all.

What really gets me up in arms is when they advertise gigabit connections or 500mb speeds only to limit upload to 20mb/s. That is where they are actively inhibiting self hosting communities.