This morning, when I launched Voyager, my settings were reset. I suspect the app may have upgraded and something caused the preferences to be lost. This wasn’t the first time it happened, and who knows if the underlying conditions triggering this reset would happen again.

It would be nice if we can export our preferences into a json file (or whatever format serializes easiest), and re-import them next time the preferences gets lost, so we don’t need to manually make all the changes.

SkyTrain’s King George Station is temporarily closed from Saturday, Apr. 27 until mid-June while we complete multiple infrastructure maintenance works, including the replacement of an original component from when the station opened in 1992.

**Who’s affected: **Customers who ride the SkyTrain to and from King George Station.

**What do I need to do: **During this time, the terminus station for the Expo Line in Surrey is at Surrey Central Station instead of King George Station. Customers should plan for an additional 15 minutes of travel time if they use King George.

• Customers who normally arrive by bus at King George Station to connect to the SkyTrain should stay on the bus to continue to Surrey Central Station.

  • The 345 King George Station/White Rock Centre, 394 White Rock/King George Station Express, and 395 Langley Centre/King George Station buses will all stop at King George Station, then continue to Surrey Central Station.
  • When connecting from SkyTrain to bus, customers should board their bus at Surrey Central Station.

• Trains are arriving and departing for Waterfront Station at Surrey Central Station using both platforms, so check the screens for the next train.

• Between 6 a.m. and 9 a.m. on weekdays, a SkyTrain replacement bus is operating every 15 minutes between Bay 2 at King George Station and a temporary stop on City Parkway at Surrey Central Station.

• Know before you go — plan your trip at translink.ca/tripplanner and sign up for Transit Alerts at translink.ca/alerts.

Additional details:

• During the closure, Expo Line service will operate Waterfront to Braid, Waterfront to Production Way–University, Waterfront to Surrey Central Station.
• Customers who currently use the passenger pickup/drop-off zone at King George Station can access parking lots at Surrey Central Station to access SkyTrain service.
• The Bike Parkade at King George Station will remain accessible.
• Currently, there is a HandyDART passenger pickup/drop-off zone at King George Station; this will be closed. For the duration of the station closure, HandyDART service will continue as normal at Surrey Central and other stations.

**What’s happening: **We’re closing the station temporarily to replace a portion of the tracks called the turnout that allows trains to change tracks and direction at King George Station. It has reached the end of its service life. We’re also taking advantage of the closure to complete other work:

• Replacing a section of power rail between King George and Surrey Central station. These rails are what provide power to the SkyTrain cars, allowing trains to move.
• Realigning our guideway intrusion monitoring systems and preparing station platform to receive the longer Mark V trains that will enter service by the end of the year.
• Elevator inspections, fibre optic cable replacement, station deep cleaning, and various asset repair and replacements that can be completed quickly and efficiently while the station is closed.

**Zoom out: **TransLink’s Maintenance and Upgrade Program is making investments in aging infrastructure across the system to keep customers safe, comfortable, and moving across a reliable transit network every day. For more information and to learn more, please visit translink.ca/keepmoving.

Due to the decentralized nature, and multiple communities on same subject exist across multiple instances, it is not uncommon for people to be subscribed to multiple communities of the same subject. It is also not uncommon for people to submit the same thing to multiple communities of the same subject, thereby resulting in multiple posts of the same content appearing in the feed. Cross post or not, the duplicated content clutter the feed, making it more difficult to consume content quickly.

I think it would be helpful to declutter by hiding/collapsing these posts. A possible implementation could be to keep an index of post titles, author, and submission time; then hide/collapse (cross)posts with same title, submitted by the same author, within some time interval (say for example +/- 1hr). That way the feed wouldn’t be as cluttered.

I understand cross referencing each post against other known posts is an exponentially large task, and could be very resources consuming, so even with the time range filter, it would be prudent to make this an option and likely disable by default to prevent performance issues.

It may be nice to inform the user on the post itself that there are other similar discussions, if they’re interested for other comments/interactions, but that’d be a nice to have in the future kind of thing.

I have too many machines floating around, some virtual, some physical, and they're getting added and removed semi-frequently as I play around with different tools/try out ideas. One recurring pain point is I have no easy way to manage SSH keys around them, and it's a pain to deal with adding/removing/cycling keys. I know I can use AuthorizedKeysCommand on sshd_config to make the system fetch a remote key for validation, I know I could theoretically publish my pub key to github or alike, but I'm wondering if there's something more flexible/powerful where I can manage multiple users (essentially roles) such that each machine can be assigned a role and automatically allow access accordingly?

I've seen Keyper before, but the container haven't been updated for years, and the support discord owner actively kicks everyone from the server, even after asking questions.

Is there any other solution out there that would streamline this process a bit?

Figured I’d share my finding here…

I got the notification for iOS 16.5.1(c) rapid security response today. Despite hearing about it breaking some sites forcing Apple to pull the update a couple weeks back from a podcast (I want to say ATP but I can’t find it in the show notes so I can’t link to the episode), I decided to install it anyway. After installing and restarting the phone, I found almost nothing works. My games spins forever, all web browsers never loads any website, but surprisingly, iMessages were flowing through.

I poked around a bit, turning wifi off and on again, using cellular data only, toggle between roaming network, etc. and nothing worked. Then I noticed the little VPN icon that flashes by so I went and disabled AdGuard VPN and things seems to work again.

Originally I uninstalled the rapid security patch, and things worked again, but then I realized I’d rather put up with some ads than deal with whatever security ramifications not having the patch would cause. Bearing in mind: the intent of these rapid security patches is that Apple thinks these patches are of utmost urgency (I.E. security issue that’s actively exploited in the wild) and they don’t want to slow people down with a big iOS upgrade, so they release and apply these patches quickly. I ended up reinstalling the patch, and turned off my AdGuard in the mean time. Hopefully AdGuard catches up and release a fix next version or two.

Anyway figured I’d drop the note here in case if anyone else is searching on their Mac trying to figure out why their iPhone isn’t working after that patch.