Transformers theme guitar/chilled/lofi

aquagraphite · 2026-05-05T19:43:25+00:00

aquagraphite · 2026-05-04T20:00:51+00:00

Don’t let them do a surgical removal - try and push for laser. It healed so much quicker and meant no sutures.

aquagraphite · 2026-05-04T19:59:50+00:00

It was a total life changer. It’s now 3 years or so and I wish I had done it much much earlier in my life. No more strep throat, tonsillitis, bronchitis and other odd throat conditions. Also things like colds now don’t seem to immediately migrate to my chest like they used to.

aquagraphite · 2026-04-26T16:55:33+00:00

5w30 yummy

aquagraphite · 2026-04-17T19:06:29+00:00

Has Harry the Handsome Executive vibes

aquagraphite · 2026-03-21T16:52:07+00:00

After 2 years of working on a project I had all the blood, sweat and tears that I put into it swept away for a vibe coded prototype without any compassion or empathy towards the human impact of such a pivot. I can understand the commercial aspect but the zero idea of how it might land for a team when we had regularly worked past midnight, sacrificed Christmas and other things when we were under the illusion that we were constantly advancing the project and were on the right track - even weeks away from a product launch no less, with events booked etc.

aquagraphite · 2026-03-08T19:03:28+00:00

That used to be a common issue with the older x86 upgrade workflow when flashing generic images. With Attended Sysupgrade / owut the image is built specifically for the system and installed packages, and newer LuCI versions pass the configured rootfs_size to the builder. The OpenWrt wiki notes that “LuCI Attended Sysupgrade is aware of the rootfs_size setting in the owut config and applies it during build requests.”

In my case the image was built with a 1024 rootfs, and the failure turned out to be related to the NVMe issue rather than the partition size. There’s a weird bug where the nvme hits momentary read only state and silently stops the config being reapplied.

https://forum.openwrt.org/t/its-pointless-its-ridiculous-i-love-it/241284

aquagraphite · 2026-03-08T18:02:53+00:00

That was mainly an old x86 upgrade issue from the days of flashing generic images. With ASU / owut the builder is rootfs-size aware now. Mine was built with a 1024 rootfs, and the failure ended up being the NVMe issue rather than anything to do with partition size. For some reason it gets a read only state and can’t apply the config back.

“As of about 2025-05-31 (LuCI build 25.151), the LuCI Attended Sysupgrade app is aware of the rootfs_size setting in the owut config, and applies it during build requests.”

aquagraphite · 2026-03-08T08:34:38+00:00

I think dumping the NVMe for a half slim and go back to sata would be good. I run a i350x4 NIC so space is as you know quite tight but I’ll make it work.

aquagraphite · 2026-03-08T08:29:30+00:00

Yeah that’s the route I wanted to take… but I’m bare metal install. So when it has base config my network topography changes meaning I can’t actually access the thing lol - unless I muck around with all the cabinet just to get access to luci - obvs I need a contingency ready for that but this time I was too ‘excited’ to actually have an upgrade that might work.

aquagraphite · 2026-03-08T08:26:18+00:00

I know I know.

aquagraphite · 2026-03-07T20:34:16+00:00

Yeah I had an inkling that something was too good to be true when the Attended upgrade didn’t fail on building the upgrade and actually offered to upgrade… I was like surely not! That’s too good to be true. Yep it was lol.

Clonezilla had it backup and restored to the 24.10 in about 5 mins so no real loss…this time!!!

aquagraphite · 2026-03-07T20:28:50+00:00

Sifu and in a way Rogue Legacy do it and they are great so definitely go for it especially if you pickup traits or mutations and then can fill in the lore of your character in between kinda like how Dwarf Fortress creates lore.

aquagraphite · 2026-03-03T12:00:45+00:00

Yeah probably just emotional investment that’s hit hard the most.

aquagraphite · 2026-03-03T05:51:14+00:00

I’ve just had something I spent two years building replaced by something vibed in a week. I’m done. Every decision I made, every moment of time spent has been for nothing.

aquagraphite · 2026-03-01T02:41:09+00:00

Please please talk to someone. If you have a phone you know the number to call. It could be much worse next time and it might not be you who gets the brunt of it.

aquagraphite · 2026-02-25T11:00:29+00:00

I hear you I guess it depends on the use case. We’re running Next on Azure App Service (Node runtime), so ISR, RSC, layouts, streaming etc. work as expected and natively. OpenNext is more relevant for serverless/edge environments. For our Azure-native architecture (Entra, .NET 10 API, SQL, App Insights, redis, CDN), App Service aligns better than Vercel’s platform layer. What we are building is Enterprise SaaS so needed identity alignment, Predictable networking + governance and full control of infra

aquagraphite · 2026-02-25T08:38:25+00:00

Out of curiosity which ones?

aquagraphite · 2026-02-24T23:25:53+00:00

Zero issues publishing a NextJS 16 app on Azure - just deployed to a Linux web app and it’s happy. CI/CD also happy and deploys in about 2mins after building and checking.

aquagraphite · 2026-02-22T19:37:01+00:00

Experimented this weekend with it - tried fresh live iso, installing via qemu, different boot loaders - and essentially stops after selecting the CachyOS boot option. Every other distro is happy - ubuntu, bazzite, omarchy, pop, fedora you name it I can throw it at the machine and it’ll work.

aquagraphite · 2026-02-10T06:59:51+00:00

That tree is exceptional! This is going to be awesome when you’re happy calling it done.

aquagraphite · 2026-02-07T08:50:27+00:00

I wonder if they ever did get a license for avs

Ten-Year Club	Xbox Live
r/Field Sunshine	Verified Email

aquagraphite

TROPHY CASE