Most TV programs are broadcast in HD format. Especially sports. That was the main reason we got rid of our last CRT. The scoreboards were getting cut off at the edges. That, and the fact that the bottom right corner of the display had permanently faded to black.

Sounds like the issue is getting to the server, not the LLM server itself. If so, may want to look into running a reverse proxy, or if you want to access it remotely, tunnels: https://github.com/anderspitman/awesome-tunneling

A long time ago I helped set it up so an elderly relative’s HOA dues were auto-withdrawn from their checking account. Someone stole one of their checks, washed it, wrote in a different name and amount, and cashed it. Bank anti-fraud caught it, refunded the money, and closed the account. I sent the HOA a message explaining the situation and asking what the procedure was to change account numbers.

They emailed over an attached PDF form. Had space for fullname, phone, address, bank routing and account number, and her real signature. Pretty much a PII nightmare. The instructions were to have it filled out and emailed back to them. 🤦🏻‍♂️

Told the relative to print it out and send it back by post.

AWS S3 lets you upload all content to a bucket, then mark it as a website. If usage is not too heavy, it can stay under the free tier.

But a favorite free one is Cloudflare pages: https://www.geeksforgeeks.org/techtips/deploying-static-website-to-cloudflare-pages/

You can keep your content on github, connect it to a CF page, and have it auto-update on push to github.

Palm 😔

Windows MICE: https://en.wikipedia.org/wiki/Windows_Metafile_vulnerability

Any CEO who says AI would replace staff is pandering to short-term investors. They’re not a long-term visionary.

That, and wiping off the caked dust.

Wonder if the 5% that actually made money included companies that sell enterprise AI services, like AWS, Microsoft, and Google?

I remember being at a conference when a guy walked up to a group of us chatting. wearing a Google Glass. Everyone stopped talking, turned around, and just scattered. A while later he walked into the men’s room and someone reported him to security. That afternoon, the glass was gone.

Guess nobody learned that lesson.

Shades of dotcom days. Everyone hopped on the bandwagon. Most lured by the high salaries and gold-rush mentality. Nowadays, just having a CS degree isn’t enough. You want portfolio pieces to set you apart. Start by having a damn portfolio. You can set one up for free on GH Pages or CloudFlare. Or pay a few bucks and set one up on Wordpress. If you can’t figure out how, that CS degree was wasted.

You want stories that show you bring value. Show that you can build things beyond school projects. Even if you do school projects, document them and push them out. Show why they’re cool and what you can do. Throw up screenshots, diagrams, or animations. No walls of text.

Also, learn to sell yourself. Not in the oily LinkedIn way. Just be out there. Contribute back. Educate others and have a voice. Blog, newsletter, social media, book, or video channel. They’re dead-easy to set up and free so there’s no gatekeepers to go through, other than your ideas.

If in a big city, go to Meetups or demo days. Meet people and ASK WHAT THEY DO. Help connect them to others. Anyone just sitting there cranking out resumes is going to get filtered by the LLM screener. Might as well pin up your resume above the urinal at the pub.

Finally: everyone can low-code or vibecode. Those are table stakes now. You want to do better.

They’re worried he does well and more people like him show up on their home turf.

Also, Streisand Effect.

I promise you they’re not.

Grafana: https://tomerklein.dev/visualizing-traefik-metrics-with-grafana-and-prometheus-step-by-step-a6a1e9b5fb2c

It’s a gimmick to get publicity. But if it happens, the company has to generate revenue to pay it off.

Guess how browser makers make money off a ‘free’ product?

Ran the 20B on a Mac under LMStudio. Pretty zippy and did OK on basic coding tasks.

By all means, run MCPs that give full access to your desktop. Nothing can go wrong.

A few suggestions:

• Some of those components may end up costing a lot to operate. You said you’re doing it as a portfolio piece. May want to create a spreadsheet with all the services, then run a cost simulation. You can use the AWS Cost calculator, but it won’t be as flexible doing ‘what if’ scenarios. Any prospective employer will appreciate that you’ve given some thought to runtime pricing.

• You may want to bifurcate static media out and put them in S3 buckets, plus put a CloudFront CDN in front for regional scaling (and cost). Static media coming out of local server uses up processing power, bandwidth, storage, and memory. S3/CloudFront is designed for just this and is a lot cheaper. All fonts, js scripts, images, CSS stylesheets, videos, etc. can be moved out.

• Definitely expire your CloudWatch log records (maybe no more than a week), otherwise they’ll pile up and end up costing a lot.

• Consider where backups and logs may go. Backups should also account for Disaster Recovery (DR). Is the purpose of multiple AZs for scaling or DR? If for DR, you should think about different recovery strategies and how much down-time is acceptable.

• Using Pulumi is good if the goal is to go multi-cloud. But if you’ve hardcoded Aurora or ALBs into the stack, you’re stuck with AWS. If that’s the case, maybe consider going with AWS CDK in a language you like. It would get you farther and let you do more native DevOps.

• Consider how updates and revisions might work, especially once rolled out. What scripts will you need to run to upgrade the NextCloud stack. What are the implications if only one AZ is updated, but not the other. Etc.

• If this is meant for business or multiple users, consider where user accounts would go? What about OAuth or 2FA? If it’s a business, they may already have an Identity Provider (IDP) and now you need to tie into it.

• If tire-kicking, may want to also script switching to plain old RDS/Postgres so you can stay under the free tier.

• To make this all reusable, you want to take whatever is generated (i.e. Aurora endpoints, and save everything to a JSON or .env file. This way, the whole thing can be zapped and re-created and should work without having to manually do much in the console or CLI.

• Any step that uses the console or CLI adds friction and risk. Either automate them, or document the crap out of them as a favor to your future self.

• All secrets could go in .env files (which should be in .gitignore). Aurora/RDS Database passwords could also be auto-generated and kept in SecretsManager and periodically rotated. Hardcoded DB passwords are a risk.

• Think about putting WAF in front of everything with web access to prevent DDOS attacks.

This is a great, learning exercise. Hope you don’t find these suggestions overwhelming. They only apply if you want to show it off for future employers. If it’s just for personal use, ignore all the rest I said and just think about operating costs. See if you can find an AWS sales or support person and get some freebie credits.

Best of luck!

There’s more: https://lemmy.world/comment/18699894

• https://lima-vm.io/
• https://tart.run/
• https://github.com/SpaceBlocks/lume-mac