EDIT: As one user pointed out, this is not about Apple Music the streaming platform, this is about basically itunes but itunes no longer technically exists as an application.

So a little background: my father just died and a big part of his life was listening to music, for most of his life he's been building themed compilations of songs he liked using whatever medium was available, magnetic reel tapes in the '60s and '70s, then cassette tapes, then CDs, and of course playlists for the last 20 or so years. Now my mother and I would like to back up and save a lot of that work as those compilations have a lot of sentimental value and are pretty unique. There's lots of old obscure rhythm and blues and soul songs that you aren't really going to come across anywhere else. However, it's pretty much all locked into Apple Music, which isn't really a problem in the here and now, because we all have tended to use macs since my mother adopted them in the '80s or '90s. However, we don't really want that data just locked into a private ecosystem that has been getting more and more restricted and where we have less and less control.

So I'm looking for a way to keep those playlists intact and export them out of Apple Music in a playable format and into a less locked in system to then back them up. Most of the music should be DRM free as a lot of it would have been taken off of CDs probably as MP3 files, though a lot of that would've happened 15+ years ago.

Does anyone have any ideas about the best way to do that? I seem to be able to manually export each one into a .txt file but of course it's not really playable sound files. My tech skills are pretty limited, I have about an average amount of knowledge or even slightly more for someone my age (30s) who grew up around computers and the internet but I grew up after it necessary to have basic coding skills to use computers so my experience doing even basic coding or running scripts is pretty much nil. Any ideas would be appreciated.

Edit: it’s version 1.0.6.10

Overview

If you want to see just the final result, check out my TiMaSoMo showcase post. This post does minimal amount of showcase of the final project, although it does include some pictures. If you want to see a showcase of the software, the original author has made a great video showcasing it that is worth checking out: YouTube videoBlogpost for those who prefer reading. Instead, this post is more a discussion of my experience developing a device.

Initial Planning

The goal of this project was to create a dedicated audio player, to separate that capability from my phone. The main source of audio will be streaming Spotify, not local files. Although unfamiliar with them, I felt that a Raspberry Pi was a good baseline device. For audio, I had an old USB DAC/amp that I wanted to repurpose. Using this DAC/amp would allow for some of my harder to drive headphones to work, as well as just getting cleaner audio. Then, I was planning on just using an eInk touchscreen. The rationale for eInk was so that it would feel different than my phone, and just feel like it was intended for music instead of scrolling. The logic was if I put a regular LCD screen on, it would not differ from a smartphone, and therefore I might as well just connect my DAC to my phone and use that. For software, the plan was to just use either Android or some lightweight linux distro. The initial plan for batteries was to just use rechargeable AA batteries, so that I can easily swap them out. One major reason I wanted to go with the DIY route was for repairability, especially with batteries. If I got an existing Digital Audio Player (DAP) on the market, I knew that the Li-Ion battery would eventually go bad, and existing devices on the market may not be easily repairable.

Hardware Sourcing

My hardware approach was to buy one component at a time. That way, if I ran into an issue with the feasibility of the approach, I could pivot without having wasted money on all the components ahead of time. This approach did slow down development as I was frequently waiting on hardware, but was more fiscally responsible. In January I got a Raspberry Pi 3a+, and played around briefly with some different operating systems. The next part that was needed was to source the screen.

Initial Plan for eInk

The original goal was to try and get a touch eInk screen, roughly 5” for a reasonable price. I spent a few weeks trying different places to try and find one, but could not find one. Since I could not find one I started thinking about pivoting to an LCD screen. With this pivot, I started defining goals of the project more. If I were to just use an LCD touchscreen potentially running Android, what makes it different from using my phone? I spent a few weeks trying to define the goals of the project, and was not able to come up with satisfactory answers if I went with an LCD screen.

Clickwheel design pivot

In the process of trying to figure out my approach, I stumbled across this YouTube video. I felt like this would be a good starting point. It seemed to solve the issue of it not being another Android device, which was my main problem I was trying to solve. However there were a few parts of the implementation that I did not like:

• It relied on using old used Apple hardware. This works for now, but over time it would become harder to source replacement parts.
• I did not already have the hardware, so I would have to buy an old used iPod and strip it for parts
• It was a bluetooth implementation, so I would have to figure out how to fit my DAC into an old iPod, which seemed unrealistic
• The battery while replaceable, was a non-descript battery so getting a new replacement with the same form factor would be harder.

Luckily, for the clickwheel, someone on the weekly programming project on Tildes pointed out this new clickwheel. Since that seemed to be a reasonable approach I ordered one and also got a small LCD screen from Amazon. Unfortunately, the screen used up all the GPIO pins and had non-existent documentation or drivers. I was unable to get the screen to work, so I returned it and ordered a Waveshare 2” LCD. I was intentional on finding one that could be a regular display without using too many GPIO pins. The Waveshare screen had significantly better documentation, and with a bit of work I was able to get it working. With that solved, I started wiring in the clickwheel, and creating basic code to detect basic inputs, which I then used to modify the original code for the Spotify player to handle my clickwheel (see below for comments on code modification). Once I had the screen and clickwheel, I could also develop the software while waiting for parts. Image showing the early iteration of the device

The last main part I had to solve was batteries. Another helpful comment on the weekly programming thread on Tildes told me about 14500 and 18650 batteries. I sourced a 14500 charger and some 14500 cells from Amazon. I had some issues with the first charger I got, and since they were shipping directly from China, it meant the second one would take another few weeks. Picture of using the 14500 battery. The cells I sourced said they were 2500 mAh. I tried one out, and had playtime of about 30mins, not enough to even listen to a full album on a single charge, which is inadequate. I used a portable battery bank rated at 10000 mAh to set a benchmark, and that lasted significantly longer (I was probably around 50% after about five hours or so of playback). This indicated that the 14500 cell was falsely claiming capacity, which is apparently a common issue on Amazon. It also seemed like 14500s rarely have capacity above 700mAh, so I realized that a 14500 would not work. So I decided to upgrade to an 18650 cell, which I could source the actual battery locally from a reputable vendor, with a capacity of 3400mAh. Since I realized that small hobbyist electronics like this on Amazon were shipping directly from China, I started ordering from AliExpress for the charger, which saved me some money for the same part (and even picked up a spare just in case). Picture of me using the 18650 to listen to music on my balcony during the summer. Since I did not need the extra power of the RPi 3a+, and the battery was taking more space, I ordered a RPi Zero 2w+. I also ordered some micro USB ends to solder to to make internal cabling, as well as a USB-C port to use for charging. By May I had all the hardware parts I needed, and all that was left for hardware was to design a case to 3D print, which is detailed below.

Software Development

The first thing I tested was installing Raspotify which this project used, and set it up with my DAC. Since that worked, I started to program the clickwheel using GPIO pins. I had never used a RPi before, but found some easy tutorials on programming the buttons of my clickwheel in Python. Once the buttons were programmed, I had to figure out the rotary encoder, but was able to find a Github repo that had a working Python code to process the inputs. I was able to add that, and created a Python class that would handle all the inputs of my clickwheel. Once that was coded, I just had to incorporate that into the code for the Spotify player frontend. I forked the repo, and was greeted with at the top of the main file this comment:

# This code is a mess.
# This is me learning Python as I go.
# This is not how I write code for my day job.”

This was not an encouraging comment to read, as at the start my Python skills were relatively low. I was able to quickly find where the inputs from the clickwheel were being handled. The original code had clickwheel inputs being handled in a separate C program and then communicating to the Spotify frontend via sockets. Since my clickwheel code was handled via a Python class I was able to simplify it, and not require sockets to be used. With that working, I just had to set up all the required steps to get the project working. Unfortunately, the documentation for deployment was extremely lacking. I was able to find a Github issues post that provided instructions so was able to get it all set up. I was able to get to this phase by the end of March.

Once I had it all working, I could start on expanding the software to fit my use case as well as start working on any bugs I encounter. I felt a good starting point in handling this was to start addressing the issue of “this code is a mess.” Cleaning up the code would be a good way to gain familiarity with the code as well as make it easier for me to address any bugs or future enhancements. I started work on creating a class diagram, but it was really tedious to do it from scratch with such a large codebase, so I deserted that plan quickly. I am thinking of creating some sequence diagrams from some features I implemented recently, which would help in general documentation to refer back to in the future. I did find some classes that would make more sense in separate files, so did do that. I also started adding in new features as well. The first was to implement a “hold switch” which turns off the screen and disables the clickwheel input. Before, the screen would be on a 60sec timer to turn off, but I felt that sometimes I would want to have the screen stay on (like if I am just sitting in a chair listening to music). This was a relatively easy feature to implement. One bug that kept on appearing is that the screen would frequently freeze on me, normally about 60sec into a song, but would update once the next song started playing. I spent several weeks tracking down this issue, thinking it was software related, as the screen used to timeout after 60sec. I also thought it might be a configuration of my OS, so did some debugging there as well. Finally, I plugged in my main desktop monitor, and realized when the small 2” screen would freeze, my desktop monitor would not. This lead me down to investigating the driver for my screen. I found an issue with someone having similar issues with the original driver that Waveshare forked. I then realized that there was a setting that the screen would stop updating if less than 5% of the pixels were changing. Once I changed that in the config file, the screen freezing issue stopped. I was able to solve this major issue by late July.

The last major feature I have implemented is to create the ability to add new WiFi networks from the app itself. This was a needed feature if I wanted to bring it anywhere outside of my home, since 3rd Party Spotify apps cannot download music. Luckily, there was a search feature, which gave me a baseline for text input using the clickwheel. I was able to create a basic page that prompts for the input of a SSID and the password, and then adds that to /etc/wpa_supplicant/wpa_supplicant.conf and then restarts the wireless interface. I added this feature into the overall settings page I added, which also included other useful dev options, like doing a git pull for me to avoid having to SSH into the Rpi to do it. The settings page features were a part of my project for TiMaSoMo.

Case Design

I started work on the case in late May roughly. The plan was that I was going to design the case and have my friend who owns a 3D printer print out my design for me. To continue with the project goal of repairability, I wanted to avoid using glue for the case. Instead, I wanted to use heated inserts to hold all the components. I had not used any 3D modeling or CAD software before, so it was a learning experience. I settled on using FreeCAD, which I was able to learn the basics of what I needed relatively quickly. I started with a basic case design for a prototype, to help plan out how I would lay things out. On my computer screen, having the device be 40mm thick sounded fine, but after receiving the prototype I realized I would need to be aggressive in thinning out the design. However, this protoype in early June was very helpful in getting a better understanding of how I needed to design it. Case prototype pictures.

The first iteration I was able to get down to 27mm, which was a significant improvement. I received this iteration in mid July. However, there were parts that did not fit properly. Most of the mounting holes were not aligned properly. However, the bigger issue was that at 27mm the device would not be thick enough to hold the DAC and screen stacked on top of each other. This iteration still had the DAC keep the original metal housing, so that I could easily remove it and use it as originally intended if I did not want to continue using my audio player. First case iteration pictures.

The second iteration I decided to remove the metal housing of the DAC, which freed up a lot of internal space, with the main limiting factor of thickness being the 18650 battery. So I kept the thickness around 27mm, but had more internal space. Removing the metal case of the DAC was relatively straightforward, except figuring out how to secure it to the print. Luckily, there were two roughly 2.5mm holes in the PCB, that I was able to use to secure it. I also started to do a more complex design, since I was getting more experienced with FreeCAD. I also moved the RPi to the top of the case, so that the two parts of the case could easily separate, with only micro USB connectors being used between the parts in the top and bottom part of the case(Picture of third iteration showing this feature). For anyone who has had to repair electronics that did not fully separate due to ribbon cables (laptops are the worst for this it seems), you understand the quality of life improvement of having the two parts easily separate. I got this iteration of the case in early September, and found a few issues of parts conflicting. However, with the use of a dremel, I was able to modify it to get it to roughly fit (although janky in some parts).In this picture you can see the power switch, which I had to modify to sit outside the case. I wanted to fully assemble it, so that I could start using it and figure out where it needs to improve. The biggest issue aside from conflicting parts was that the top of the case was bulging, so I wanted to add another point of connection to prevent it. This bulge was partly caused by the screen cutout causing a weak point in the top of the case. Second case iteration pictures.

The third iteration was part of my TiMaSoMo project. This was a relatively simple minor tweaks, as well as fix some minor pain points of the previous iteration. I reinforced the top significantly to prevent bending, as well as add a fifth point to secure it. I also added a recess to make accessing the switches for power and hold easier to use (although I think I messed up the hold switch one). Overall, this print worked well, and there is currently no plans for a fourth iteration. Fourth iteration pictures.

Here is all four cases compared side by side

What I learned

The first lesson I had to learn was how to define project goals. Not being able to source an eInk screen had caused me to pivot, and in doing so I had to reflect on what truly mattered for my project. I knew that DAPs existed, so why build my own rather than buy one? Most DAPs on the market seem to be Android devices where they removed the phone functionality and added in quality audio components. Part of a dedicated audio device was to not have my phone be the everything device that they are, but a second Android device with an LCD screen and better audio components is not the solution. Luckily, I encountered the clickwheel based approach, which did solve that issue (and probably better than an eInk would have). Also, I wanted the device to be easily repairable. Li-Ion batteries go bad, which was another major concern for me with the current options of DAPs. Repairability was something that mattered to me, but I had to embrace what that meant for the form factor. If I went with a non-descript Li-Ion pillow battery, I could probably significantly reduce the size. Understanding that I wanted to avoid just being another Android device and have repairability and replaceable parts as the defining features were useful to keep in mind. That approach did result in compromise though, primarily in physical size at the end.

The second big thing I learned was just the process of sourcing parts for a project like this. The closest project to this that I have done in the past is create a DIY cable tester. That simply just involved some switches, resistors, LEDs, and some AA batteries that I could all source locally. So having to buy more complex electronics where the documentation mattered was a learning curve for me. Luckily, early on I was ordering from Amazon, where returns were relatively easy. The problem with Amazon though was false advertising for batteries and some components were shipping directly from China. So, switching to AliExpress saved me money without adding any additional in shipping.

Learning 3D modelling and getting stuff 3D printed was also a huge learning curve for me. I am glad that I got a very rough prototype printed early on in the process. In designing the prototype, I just was not concerned about saving space. However, once the prototype was printed and off my screen and into my hand, I realized how aggressive I needed to be in compacting things. The other thing with using FreeCAD is I learned too late in the process about part hierarchies, and I still do not fully understand them. Not using part hierarchies properly led me to have to do a redesign on each iteration, as moving mounting holes over a few mm would shift every part added after it. Luckily, my designs were relatively simple, but having hierarchies handled properly would have helped me iterate quicker. On top of getting prototypes in hand quickly, using imperfect prints and just adjusting the parts that didn’t work with with a dremel was useful. If I didn’t do that with the second iteration, I would not have dealt with the issue that the top of the case would bend out over time. Spending time using the imperfect device helped me figure out the issues to make the next iteration better.

Future Goals

The first goal I will add in future expansion is to add better documentation and create a better development workflow. Right now, my process includes pushing any changes I do (luckily I am using Github branches now), then pulling the updated repo and starting it on my Pi. However, I never test if it compiles properly before pushing, so I end up sometimes doing five pushes in ten minutes, playing whackamole with compilation errors. Being able to run a dev version on my desktop with keyboard emulation for inputs would be beneficial.

Another big issue that I want to solve is that I need to clean up the audio on lower resistance headphones like my IEMs. There appears to be some electrical noise, that only sensitive devices like IEMs detect. The solution I am currently considering is to add in a capacitor on the voltage rail between the Pi and the DAC to hopefully get cleaner power.

Another issue is that I currently have no indicator of battery life. Since it is an 18650 Li-Ion battery, I should be able to just detect the gradual decrease in voltage, and calculate battery percentage. However, GPIO pins appear to be unable to do that natively, so I may have to add in a small controller board to do it. I have not looked too much into this.

There are a few UI/UX decisions that do not match my preferred way of listening to music. So over time I plan on gradually tweaking the UI/UX to match what I want it to be. A prime example of this would be that when I select an artist, I want it to present a list of their albums, instead of playing their most popular songs.

I want to be able to use Spotify Lossless, since that has rolled out near the end of this project. Unfortunately, it seems that currently it will not be supported. Seems like Librespot (which is the basis for Raspotify) does not currently have a solution that does not involve working around Spotify’s DRM.

Conclusion

Overall, I am really glad I took on this project. It took a long time for me to get it to a finished state. However, the experience has been really fun, and I have learned some new skills. Also, having a dedicated device that all it does is stream Spotify is really nice. I always found myself whenever I was listening to music ending up scrolling on my phone for a bit more stimulation, and then realized I have not been paying attention for the past couple of songs. Having a device where all I do is just listen to music and leave my phone behind has been nice. Also, modifying the code to fit my preferred use case has been nice. There are points where I realize I do not like how something is laid out, but then I have agency to change the layout. Here are some pictures of the final device.

If you want to build the device yourself, I will warn you that it has some rough edges. Also, the DAC/amp is discontinued, so sourcing that to fit inside the case would be tricky. However, my Github repo has all hardware listed, the code needed, and easy to follow software deployment instructions.

I use a Mac for work, Linux for my personal machine, and the same mouse between the two. I’m accustomed to the dpi/acceleration on Mac, so when I switch to my PC at the end of the day there are slight inaccuracies with the pointer. My wrist compensates to cover the gaps and I develop wrist strain after short periods of use.

Does anyone know how to make the Linux mouse dpi/acceleration as close to identical as possible with my Mac?

chimera linux w/ gnome btw

She currently has apple everything, but is open to getting something like a Garmin watch.

Rough requirements are:

• Batter life of at least a few days with normal use, ideally up to a week
• Physical activity tracking for swimming. She isn't a runner and doesn't need running-specific features.
• Heart rate / sleep tracking
• Receive and view emails / texts / notifications from her iphone

Some watches she is most interested in are:

• Enduro 3 even though she's not doing multiple day expeditions, she loves the idea of the battery lasting that long, but it is a bit heavy / bulky and has a lot of features that she won't use for the price
• Another apple watch, but even the upgrade is only a day and a half of battery
• Garmin forerunner, we were taking a look at this comparison chart and if she doesn't care about all the running features, would the cheapest version like https://www.garmin.com/en-US/p/1611937/pn/010-02863-33/ to just act as a budget apple watch with better battery as long as she still gets all the notifications and it works with her iphone?

Also taking suggestions from other brands, I'm just mostly familiar with Garmin and have an instinct solar 2 for 4 years that I really enjoy.

hey everyone — i finished my music/sound project back on halloween but forgot to post it here!

it is drone/noise/ambient/experimental music so if that’s not your thing, i completely understand!

listen and download for free on bandcamp

or listen on other streaming platforms:

• spotify
• apple music*
• youtube
• deezer (cannot find link at the moment)
• amazon music
• 100+ more, just search “mabry amalgam” and I hope you’ll find it.

(*) for some reason the distributor created a new artist with the exact same name as my correct account just for this EP. If you want to hear my other stuff as well, here’s the correct profile

this was a music/sound project with contributions from some fellow tildes users. some of you may remember my post from several months ago asking if anyone wanted to collaborate. a number of you kind folks did and I used 5 users contributions throughout the project.

i’m very happy with how things evolved (and don’t have the overwhelming urge to pull it down and tweak it into oblivion per normal) and am very grateful for everyone who participated. it was a unique experience for me and i enjoyed 99% of it! the 1% I didn’t enjoy was dealing with a new music distribution service, but that’s a different topic.

seriously, thank you

i was in a creative rut for months and having the pieces submitted by other people really helped.

i don’t know if the folks want to be credited directly in this post but those who agreed to being credited in general have been with the final releases.

i tried my best with the tags but i’m still not 100% on how to tag properly :)

Now that it is finally fall weather in the Midwest, I have been back to making stews/soups.

My current go-to’s are Zuppa Toscona, Pozole Rojo, and I just made some Kartoffelsuppe (German Potato Soup with Sausage), but I’m looking for more! Any stew-like meal that’s hearty and warm - I like to make a big batch Monday night & eat it for lunches throughout the week, so preferably ones that reheat OK.

I love the Dapanji I’ve had from a local place with hand-pulled noodles, but that seems a bit out of my skill level or comfort-zone to try to make.

What are some of your favorite stews (preferably with recipes)?

Recipes

A prototypical example of what I am looking for would be fruit juice. Where I am at the only options for something that isn't orange or apple are overpriced lemonades with about thirty to fifty percent fruit content and truly expensive 100% ones.

Usually I simply buy the expensive ones and add 1-2 parts water ending up with better tasting juice at same or less cost.

Another step would be squeezing fresh fruit yourself but that adds time, space, complexity and money costs.

What things can be done in a typical kitchen without buying additional single purpose appliances? Sufficiently multipurpose ones or small tools are fine. Basically I want to reduce the number of steps in which the food is industrially processed.

I heavily utilize ChatGPT to generate .ics files to populate my Apple Calendar with various events, but I have been wanting to upgrade my time management and also use the Reminders app.

I recently used ChatGPT to help me populate a Trello board with tasks associated with a project I am working on, but I was getting annoyed with having my workflow split across Apple Calendar and Trello. I exported my Trello board as a CSV and was trying to have ChatGPT turn it into a file I could import into Reminders, but as it turns out, this is not easy.

.ics files do contain syntax for reminders tasks with due dates that populate the Apple Calendar, but generating an .ics file with only reminders tasks and importing into Calendar doesn’t actually work. Calendar recognizes that the .ics contains Reminders tasks and opens Reminders to import the tasks, but Reminders returns an error because it doesn’t support import, it only supports export to Calendar.

I found that Reminders has a Reminders.scpt dictionary file within the .app package that details .applescript commands that can create new tasks, so I fell into the world of AppleScript. The issue with AppleScript is that it was created in the 80s and hasn’t been updated since 2013. It has no native CSV support and is pretty clunky.

AppleScript does have text file support, so I was able to have ChatGPT convert my CSV into a .txt that I could parse with AppleScript. This allowed me to automate the creation of tasks in the Reminders app from my Trello CSV, but it was annoying and I still feel like there must be a better way.

Does anyone here use AppleScript regularly and know its full capabilities?

Also, are there any good resources out there for learning more about AppleScript? The Apple documentation is very out of date and it seems like more of a legacy language than something Apple regularly maintains.

Quick background: wife inherited an iPhone 8 plus from a recently deceased relative. Said relative used to have AT&T, wife and I do not. I was hoping to possibly use this phone on an upcoming international trip but it would need to be unlocked from the carrier first so I can put a new sim card in it. (Just to be clear, I don't mean getting into the actual phone, we've already saved the few photos and messages that were on there and reset the phone to factory settings). Tried doing the automated process on the AT&T website and it was denied immediately, no explanation given. Tried calling them and the automated system straight up hangs up on me because I don't have an account with them. So lastly we tried taking it directly to an AT&T store where they directed us to either call the number that keeps hanging up on us, or to "take it to one of those places at the mall that can unlock it for you". Useless.

I've done some research on this and seen various solutions online. Most of those solutions I have already tried (like calling the number or trying the online portal thing) or their situations don't apply to my case (like having purchased a new phone or having an account already with AT&T). One thing I've seen mentioned multiple times that seems to get results is to file a complaint with the FCC, so I went to do that and welp... government is shut down. FCC not accepting any complaints at the moment.

Another thing that I thought of was jailbreaking the phone, but I haven't done that to a phone in many years and am not even sure if that would resolve the issue of it being carrier-locked. But surely if 'those places at the mall' can unlock them without going through AT&T, then I might be able to as well. Hence I came here asking for help.

Anyone have any experience with this sort of thing?

tl;dr: disconnect from your VPN (or allow LAN connections)

I recently got an iPhone 17 and was being driven mad because, at first, CarPlay worked flawlessly on my 2019 Honda Fit (EX). However, next time I plugged in CarPlay refused to open. The phone was charging, the icon on the infotainment showed CarPlay, but it would hang for ~10s and close with a "no devices found, check cable, etc.". Android Auto worked for years without hiccups.

Nothing changed after a factory reset, reboot, etc. of the infotainment as many recommended.

I saw an offhand comment with how a VPN can cause problems. I'm connected to one 24/7 and I'm sure it worked earlier when I didn't set it up yet. I disconnected from the VPN and CarPlay immediately worked. The VPN I use has a "Allow LAN connections" setting which made disconnecting from the VPN unnecessary.

Wanted to throw this out there for people troubleshooting in the future. Not sure if this is specific to Honda or Apple, but my money is on how Apple devices do networking.

Haven't been following the macOS updates closely but a big feature I'm looking forward to in macOS 26 is Apple's container solution as an alternative to Docker.

The "container" command line tool: https://github.com/apple/container

The underlying Containerization package: https://github.com/apple/containerization

The main improvement over Docker on Mac is that it uses separate lightweight VMs per container, instead of one shared Linux VM hosting all containers. This means the RAM allocation can be dynamic instead of the user having to decide how many total GB to allocate for the Docker VM. So if I'm running a lot of containers I expect it to work without manually changing settings, and if I'm running only a single container then I expect it won't waste resources with allocated-but-unused RAM.

Currently these repos are on version 0.4.1 and 0.8.1 respectively, which tells me they're not ready yet. Hoping they're ready around the time macOS 26 releases to GA.

I have recently found myself wanting to learn to draw. I have very minimal visual arts skills, and feel much more comfortable with a musical instrument than a sketchbook. I would like to change that, not to become some exceptional artist or anything, but because I like the idea of being able to just sketch and draw and doodle in my spare time.

I have an iPad, Apple Pencil, and ProCreate, but I don't really know where to begin. I would be most likely learning to use ProCreate at the same time as learning to draw, although I don't know if that's a bad idea or not.

Are there books, online courses, YouTube videos that you would recommend for a complete beginner?

Introduction

July, 1914. Paris.

Tensions are high all around the European continent. A long-growing discontent has reached a sharp peak not even a full month earlier with the assassination of Archduke Franz Ferdinand. In the midst of these ever-uneasy days, a young American doctor by the name of Robert Cath gets a sudden invitation from his best friend, urging him to join him on the now-legendary Orient Express.

As he boards the train, he cannot predict the chaos that will follow. Luxurious as the train may be, this will not be an idyllic trip, but the scene of a murder. Blood will be shed, conspiracies will unfold, secrets will be revealed and romance will have a chance to blossom. With the official beginning of the Great War only a matter of days away, he may be the last passenger to step aboard what will be...

The Last Express

Welcome everyone to the first month of the Colossal Game Adventure! I am sure most people reading this will know the details already given the activity on the setup threads. Just to reiterate though, the Colossal Gaming Adventure is a monthly event where we will be playing through older games together. While @kfwyre organized the voting and nomination phases, each month will have a different host. We have seven months' worth of games already scheduled through March 2026, and I have the honor of being the conductor for the inaugural round!

As you saw above, our first leg of this grand journey will have us board The Last Express, a 1997 adventure game about a mystery on the Orient Express. I myself have not played it yet and will be experiencing it for the first time with most people here, because this game seems to be the poster child for hidden gems. A game that received critical acclaim and praise from critics and players alike, and clearly a work with serious passion and effort, but according to Wikipedia it sold only 100,000 copies on its initial release.

Luckily for us, one of those 100,000 copies belongs to kfwyre, who brought it to my attention with this passionate recommendation back in May. That link has some mild spoilers for the very beginning of the game, so you may not want to read it, but here's the key takeaway that made this game so interesting: this game plays out in real time. As you explore the train, characters will go about their set routines and events will unfold off screen regardless of you being present to witness them. These events can set up unknown domino effects that will impact you, and your own choices can also have unforeseen consequences that won't come into play until much later.

To that end, don't be discouraged by failure. Many adventure games of this era rely on trial and error but in this game failure is particularly integrated into the gameplay. Someone might somehow get the luckiest run ever and manage to complete the game on their very first playthrough without ever encountering a fail state, but ultimately, this game will call for a bit of patience. And maybe guides if you have the original version or the hints don't help. Which I personally think is pretty neat. Doesn't get much more classic/retro than looking up walkthroughs on GameFAQs!

So all aboard The Last Express, and enjoy the ride.

Game Information

Versions: Original Release and DotEmu/Gold Edition. The DotEmu version is a re-release which has additional features such as hints and tutorials, which may make it easier.

Platforms: Windows, MacOS, MS-DOS, iOS, Android

Genre(s): Adventure, Mystery, Point-and-Click

Links: Mobygames, Wikipedia

Stores:

• GOG, Original: The original 1997 release, in all its 1990’s glory for purists. (Also may come with some extras like a soundtrack and "making of" from a 2011 Collector’s Edition published by DotEmu, but which is now wiped from the internet...?)
• Steam, Gold Edition: The remake/remaster released by DotEmu with added hints and tutorials, as well as interface tweaks. (Note: while it lists macOS, the game is 32-bit, which is unsupported by any macOS versions beyond 10.14 Mojave.) This version is on sale for only 11 more hours at the time of this topic being posted!! An extreme time crunch for sure, so if you see this message, now's the time to buy it!!
• iOS (Apple App Store) and Android (Google Play Store). These ports are also by DotEmu and predate the Gold Edition.

Game Setup

The main purpose of this topic is to get people up and running with the game. As such, it's recommended that you:

• Share which version of the game you're playing
• Share what hardware you're playing it on
• Share if there are any tools/mods that you recommend
• Share anything you think is important for people to know before they start the game
• Ask questions if you need help

Another purpose of this topic is to revisit the game and its time period:

• Do you have any memories or associations with this game itself?
• What about its system or era?
• What aspects of retro gaming were common at the time?
• What other games from the same time period are you familiar with?
• What are you expecting from this game in particular?

Finally, this topic is the beginning discussion for people starting to play it:

• Post updates sharing your thoughts as you play.
• Ask for help if you get stuck.
• Offer help to others.

It is recommended that you reply to your own posts if you are making consecutive updates so that they are in the same thread.

IMPORTANT: Any links to the game should be legal distributions of the game only. Please do NOT link to any unauthorized copies.

IMPORTANT: Put any spoilers in a dropdown block. Copy/paste the block below if needed.

<details>
<summary>Spoilers</summary>

Spoiler text goes here.
</details>

FAQ

With all the pleasantries out of the way...

> PRESS START

(Credit to @Boojum for the splash screen. It's too awesome not to include!)

IMPORTANT

We now have a splash screen. (Thanks @Boojum!)

ALSO IMPORTANT

Please read all directions for submitting a proper ballot.

Any improper ballots will NOT be counted, but you will get a polite message from me before the count asking you to fix them. XD

• All ballots must be top-level comments.
• All top-level comments should be ballots ONLY.

I will be using the Collapse Replies button to tally votes, so any ballots not in top-level comments will not be counted.

After you submit your ballot, you can respond to your own post in a new comment to lobby for your choices (which is optional but highly recommended). It's completely fine to have conversations downthread from the ballots, but please make sure that the top-level remains clean.

Submitting Your Ballot

• Each person has 20 votes to distribute among games they see fit.

• Each person can allocate a maximum of 5 points per Single Game/Arcade Special.

• Arcade Specials count as one block (do not vote for each game in them individually).

• Votes should be listed as NAME (VOTES) -- e.g. Pong (3)

• Voting closes 48 hours from the posting of this topic.

Please ensure your titles match mine exactly (copy/paste highly recommended). I will be using CTRL+F to tally votes u/Spore_Prince has written a program to tally the votes, so any different spellings will not being counted. See examples below, as well as my actual ballot in the topic.

Big Rigs: Over the Road Racing (5)
Portal 3 (5)
Half-Life 3 (3)
Team Fortress 3 (2)
Night Trap (2)
Xexyz (1)
Zelda: The Wand of Gamelon (1)
Left 4 Dead 3 (1)

Big Rigs: Over the Road Racing (10)
Protal 3 (7)
Wand of Gamelon (5)

Voting Outcomes

• The top 6 games/Arcade Specials will become the next 6 months of CGA.
• Of the remaining games, the bottom 50% will be cut from the list.
• The remaining 50% will stay on the list and will enter the next voting round starting at their current point totals instead of 0.
• The next round of nominations will happen in 6 months, and participants will be limited to nominating 1 new game OR 1 new Arcade Special.

Nominees

Arcade Specials

This is always weighing on my mind and is coming after this comment I wrote.

The tech sector, especially the hyper-online portion of it, is full of devs who were doing some random shit before and shifted to AI the past few years. Don't get me wrong, I'm one of those: In much the same way, very shortly after the release of ChatGPT, I completely changed my own business as well (and now lead an AI R&D lab). Sure I had plenty of ML/AI experience before, but the sector was completely different and that experience has practically no impact aside from some fundamentals today.

The thing is, LLMs are all in all very new, few people have an active interest into "how it all works", and most of the sector's interest is in the prompting and chaining layers. Imagine network engineering and website design being bagged into the same category of "Internet Worker". Not really useful.

Some reflexions on the state of the business world right now...

In most SMEs, complete ignorance of what is possible beyond a budding interest in AI. Of course, they use ChatGPT and they see their social media posts are easier to write, so they fire some marketing consultants. Some find some of the more involved tools that automate this-and-that, and it usually stops there.

In many large companies: Complete and utter panic. Leaders shoving AI left and right as if it's a binary yes-ai/no-ai to toggle in their product or internal tools, and hitting the yes-ai switch will ensure they survive. Most of these companies are fuuuuuucked. They survive on entropy, and the world has gotten a LOT faster. Survival is going to get much harder for them unless they have a crazy moat. (Bullish on hardware and deeply-embedded knowledge; Bearish on SaaS and blind-spend; Would short Palantir today if I could)

In labs just like mine: I see plenty of knowledgeable people with no idea of how far-reaching the impact of the work is. Super technical AI people get biased by their own knowledge of the flaws and limitations so as to be blind to what is possible.

And in tech entrepreneurship, I see a gap forming between techies who have no respect for "vibe coders" on the grounds that they're not real programmers, and who don't end up using AI and fall massively behind since execution (not code quality) is everything. And at the same time I see vibe coders with zero technical prowess get oversold on the packaging, and who end up building dead shells and are unable to move past the MVP stage of whatever they're building.

And the more capable the tool you're using is, the more the experience can be SO WILDLY DIFFERENT depending on usage and configuration. I've seen Claude Code causing productivity LOSSES as well as creating productivity gains of up to 1000x -- and no, this isn't hearsay, these numbers are coming from my own experience on both ends of the spectrum, with different projects and configurations.
With such massively different experiences possible, and incredibly broad labels, of course the discussion on "AI" is all over the place. Idiocy gets funded on FOMO, products built and shut down within weeks, regulators freaking out and rushing meaningless laws that have no positive impact, it's just an unending mess.

Because it's such a mess I see naysayers who can only see those negatives and who are convinced AI is a bubble just like that "internet fad of the 90s". Or worse, that it has zero positive impact on humanity. I know there's some of those on Tildes - if that's you, hello, you're provably already wrong and I'd be happy to have that discussion.

Oh and meanwhile, Siri still has the braindead cognition of a POTUS sedated with horse tranquilizer. This, not ChatGPT, is the most-immediately-accessible AI in a quarter of the western world's pocket. Apple will probably give up, buy Perplexity, and continue its slow decline. Wonder who'll replace them.

This is the first time in my career that a Mac is the preferred machine for an organization. I've been using Windows for 30 years. This is a big change for me but I want to learn some useful tips and tricks on Mac os.

This could be "what are some changes you made on the Mac settings to make your Mac experience feel more comfortable?" Or "what tool on Mac can you not live without?"

There aren't any rules really, I want this to be a fun conversation, thanks everyone!

Can be viewed here

Is this just the usual pointless Apple fanfare?

I'm not very techy so I'm just wondering why this is a big deal. It seems to me it's just a different theme of sorts? But in this video MKBHD is making it out to be a really big deal. Is it like technologically super impressive? What's the big deal?

I would like to upgrade my aged 8 years old laptop and I'm completely undecided about which laptop to buy right now.

I considered Apple Intel laptops terrible, bad thermals, overpriced, unreliable, touch bar (uggg), I hated every second working on it, when the company I work for upgraded me with a M1, it was such a huge improvement from any laptop I have ever tried, absolutely no noise, incredibly performant and the longest battery life of any laptop by a lot.

I still don't like the Apple ecosystem, and I would prefer to use Linux as my main OS, but I can't find anything that comes even closer for the price of a Mac Air, If I go with Framework I'll get a less performant machine with a way worse battery, I honestly don't think the premium on repairability is worth for me when I don't have any issues repairing more challenging laptops, at the end repairability will be how easy is to get new parts.

ThinkPads have good reputation and repairability, but for what I see, the quality has gone down the drain in their latest models, and if I go with their premium models I get similar performance to Apple with worse battery, Dell has similar issues.

Gaming laptops are not an option, I don't do any PC gaming and the size and aesthetics are a dealbreaker for me.

The main issue seems to be that until ARM processors become better competitors to Apple, the battery life will be always the bottleneck, and I don't know how good the new Snapdragon X Elite compares right now.

Besides web development, photography edition and video editing (4k), I don't do many demanding tasks, I'm more than fine with the performance of a M1 as the baseline.

As an alternative, I'm thinking about getting a powerful desktop for the demanding tasks and a less powerful laptop with a good battery and screen, but ideally I would prefer a single machine.

Haven't seen anyone mention that project in a few years, but now I'm in the unique position to talk about it. I live somewhere where I can't get any proper internet service - mobile broadband is slow, DSL or fibre lines are not brought out to where I live, and the only other option is cable internet access, which I've 1. had bad experiences with in the past and 2. where I live is operated by a company with laughably bad reviews at exorbitant prices for what they offer. We are talking about 60 USD (eq) a month for 100 megabit service.

So I shopped around to see what other options there are, and Starlink made me an offer. Free equipment, which is usually 400 bucks, delivered to my house, and then an unlimited data plan at whatever speeds I can get where I live for 50 a month, with a one month free trial. I said yes, paid with Apple Pay (seriously, did not have to fill out a single form or sign anything) and the dish arrived the next day.

Now, I know, Starlink is run by Musk, who is somewhere around the top 10 of my nightmare blunt rotation and also pretty likely to be an actual neo-Nazi, but I say whatever. It's not like the alternatives are much better, and at least SpaceX has some actual value for humanity, if you ask me. I might put a "I bought this before Elon went crazy" on my router, though.

I got the dish delivered and set it up on my roof. The app - which is excellent - tells you to orient it north if you're on the northern hemisphere, and to roughly point it up. I built my own mounting solution - a wooden board with mounting holes that snaps in place on my roof - and set everything up, not expecting much.

I was absolutely blown away. The app, once more, is stellar and incredibly easy to use, and a joy to play around with. I got a satellite connection in minutes, and did a speed test. I got 200 down and 50 up in the Starlink app, but independent speed tests as well as my own experience routinely hit 400 down and around 80 up. Genuinely impressive. Ping around 30, by the way. Consistent as well.

The next few days were a similar experience, although I did notice a drop in speeds if there was heavy rain. The speeds dropped however to around 150 over 30, which is still more than usable, and latency was not impacted at all as far as I can tell.

Honestly, it's a super compelling package. Setup was so simple my grandma could have done it, the hardware is beautifully made and very robust, and the designers really did think of a lot here. The cables are just weatherproofed Ethernet and you can bring your own (although they don't recommend it), the router is Wifi 6 and looks damn snazzy, the dish can even heat itself up to melt snow in winter.

If you're looking for reliable internet service, I really can't recommend Starlink enough. If where you're planning on running it is within the service area and you're fine with the 50 dollar a month price point (no speed or data caps, by the way) I'd say go for it.

Now, there are people who will say that it's a good option for remote places, but not that great for densely populated areas in buildings that could get for example cable service, and you shouldn't rely on it. But, well, I haven't been completely honest here:

The real sting in the tale is that I live in one a large European city with plenty of access to other internet methods (just unlucky in terms of my specific building, which is getting fibre next year), and mounted the dish on top of my townhouse in one of the most dense districts in town. It works flawlessly, and it's been the fastest internet service I've ever had, period.

Course, it can't compete with a fibre line, sure, but many people don't have those - and then, service or hardware might still add large costs on top of that. And with Starlink, I can just take it with me whenever I move, and don't need to ever worry about ISPs again.

I don't have many sufficiently nerdy friends to talk about this with, so if you're curious or have any questions, I'll do my best to answer them. If you have Starlink too and feel like I missed something, feel free to contribute to the conversation.