• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle


  • Modeling: YouTube is helpful here search for AutoCAD (computer aided design), mid journey actually has an unreal render I hope to export soon and ai is getting better and better at generation.

    Buying a printer: 2 main categories plastic and resin. Plastic is easier, larger scale, generally printed in pla petg or abs each with their own qualities. Resin is generally smaller and more precise(read jewelery minis), and requires requires UV treatment/chemicals to cure.

    Early recommended printers: (plastic) ender or prusa. Ender will be more maintenance and give you better tuning/control, prusa will be more expensive and work a bit better out of the box.

    Material: highly recommend just starting with pla and when you figure out the basics, you can change materials. The other ones will last longer and survive longer, but 3d printing has a learning curve. PLA is a good introduction

    First print: download the STL or model of a benchy, it may be tempting to print something cool first, but this is a tool that needs calibration. Benchies have specific dimensions to print angles, rings, platforms, bridges ect). Go download software of choice, 3 years ago that was Cura. Load the STL file and you can click around, but I don’t recommend changing much. PLA prints well around 200*, I liked to add 2-4 extra layers of “shell” for durability, hollow support TREES are fantastic for overhanging ledges - NO COLUMNS!!, 20% infill means it will be mostly hollow but print quick and have some structure. Cura would default to the most geometrically sound pattern (honeycomb). A raft will put a grid down first to stabilize, it helped day 1, but got in the way later. infill.

    Follow a youtube guide on leveling your specific printer, when the print fails, lookup what went wrong here: https://www.simplify3d.com/resources/print-quality-troubleshooting/

    3d printing is a lot of work, plastic deteriorates over time, but you can do a ton of cool stuff. I recommend finger surfboards, organization kits to start and the replica jet engine is a right of passage.


  • First off, it’s important to understand Responsive Design responsive design and why you shouldn’t be writing your own css these days as a newbie. Bootstrap is a public css doc with a lot of those problems pre-solved, so you might want to look up some of their tooling.

    As far as a website: you’ll need a domain name, you can get some for free, but they usually have short renewals otherwise this is unavoidable.

    You can pay for “shared hosting” at any of the major vendors like blue host or GoDaddy and get apache or aspx file hosting for like you said $X0/year.

    You can use an s3 static website for ~free. Creating a DNS hosted zone is $.50. but you can create an s3 bucket (think flash drive in the cloud) store a threshold of free documents, and publish them as a website all within the free tier of AWS. This has some technical background and AWS can get expensive of you make mistakes (although this shouldn’t scale much unless you upload a thousands ton of files repeatedly)

    Alternatively you can use GitHub pages . Git is a tool used by developers to share and edit code, they let you publish free HTML as well, but requires learning git or figuring out a tool with a UI like source tree. I don’t think you can use custom domains with this though.

    Although if you have any interest in tech, you can also create a free nginx docker container through a lot of services like ecs, but you can also self host in a “sandbox”. Docker creates a mini virtual machine with all of the code required to run self contained. Nginx let’s you create HTML docker containers by mounting a directory. ~ docker start nginx /website/directory And it just runs self contained.









  • I’m sorry but how? We have appliances with dockerfiles, micro containers for remote controls, extensive botnets of virtual machines, centuries in the future when we have expanded into the solar system and trillions of humans all having millions of unique applications with addresses, it’s inevitable to hit a finite number. When every square meter of smart road has an routable address; we will likely be rewriting networking anyways. The only players pushing IPv6 transition are networking companies because a new standard requires new hardware.



  • Cisco as a client tried to force ipv6 for their managed service and after an entire quarter of attempting to resolve it, we actually disabled it for their virtual address per their request. IPv4 has issues and IPv6 promises solutions, but it’s not a stable platform yet. This appears ignorant but is based on truth. IPv6 is also eventually going to hit exhaustion with the frequency we spin up virtual machines, it’s okay to skip a bad generation.