I just had this notification come up, not sure if it's exclusive to ~~Pixel Watches~~ (appears to be Pixel Watch exclusive currently) and Pixel phones - but seems to be a more "intelligent" version of Trusted Devices since supposedly the range is shorter, and it requires your watch to be unlocked.

Seems nice. If your phone is unlocked by the watch, a screen on the watch will appear for a few seconds that lets you relock the phone (and I suspect prevents it from unlocking again until the PIN is entered).

Obligatory "trust your surroundings" disclaimer if you enable this. I haven't had the opportunity to test the range yet, but I'll certainly enjoy it at home at the very least.

Google has a support document on this feature here - provided by @[email protected]

It seems like the communities list that comes up has less entries than I would expect it to, is there a max amount of communities that can show up, or a different type of filter? For example, I'm subscribed to the Summit community, but it only shows if I do a search for it.

Additionally, is there a way to change the sorting for it to alphabetical order, instead of by MAUs?

Hopefully I haven't missed something obvious, or I'll feel quite silly!

Back in the Android Wear says, this used to be a feature on my Moto 360, but then in WearOS' next generation/rebranding the feature was lost. Under the idea of separating the watch and phone they somehow just couldn't even include the setting to opt into this.

Just like setting off a timer or alarm on the phone would go off on the watch... Alarms are back (bidirectional too!) but not the timers sadly.

I guess we finally have the technology to sync the two devices again without an external app being installed on both.

Hello!

In about four hours from now, we're going to be under maintenance briefly to perform an upgrade to Lemmy 0.19.1 which was released yesterday. There are a few fixes in this release, but primarily the push for getting this update applied quickly is a fix to outgoing federation activities (these are the messages that get passed between servers to indicate an action that you've performed).

I've not seen any signs of federation breaking, but I'd rather go ahead and get that fix applied now before it does end up becoming an issue. The update process shouldn't take too long, I am not even sure if there are any database migrations that need to be ran for this one (which is usually where most of the processing time comes from).

As always, during the maintenance window you'll be able to follow any updates regarding it over on The BitForged Network's status page.

Let us know if you have any questions, or run into any issues!

- The BitForged Team

Hello everyone!

The 0.19.0 update for Lemmy has just been released, we'll be going ahead with updating the instance at 8PM EST, which is about 9 hours and 30 minutes from the time of this post.

0.19.0 includes some pretty nice features, such as account data (profile settings/details, subscriptions, block lists, not posts/comments) importing/exporting which is great for migrating to and from other instances, or just keeping an occasional backup of your own settings, as well as user-based instance blocking (blocks communities from a specific instance on a user level, does not block comments/posts from users on said instances), and the new "Scaled" sort type (which is like "Hot" but accounts for smaller communities and gives them a boost).

Do note, that 0.19.0 has a few breaking API changes from the previous releases which can impact third-party clients. Most applications / alternative front-ends have already been updated to account for this, but there are probably still some around that do not.

The database migrations contained in the update appear to be on the lighter side, so the update process is expected to take less than 30 minutes, but we'll have a message on our status page indicating the progress along with any updates should things go south.

Thanks!

- The BitForged Team

Edit: Update has completed, and finished smoothly!