Hey everyone! Since it was brought up in this thread I've created a Minecraft server.

Details:

• Version: 1.20 (Join from Bedrock)
• Host: tildes.nore.gg
• Plugins: Basics for server administration and rapid leaf decay

I know there was some push back on running v1.20. I am operating under the assumption that the majority of Minecraft players here aren't opposed to the newest version.

Currently the server is un-whitelisted.

I used to run moderately large Minecraft servers years ago. I'd love for us to have a healthy player base so that we can have periodic events (in game lore, UHC, etc.)! I play more of a game master role - so don't be surprised if you see me just floating around in creative mode!

Edit:

Updates:

• Set sleep threshold to 50% of online players in beds
• Disabled chat verification enforcement server-side. You need to install a mod to disable it client side if you're afraid of the chat reporting system.
• Disabled mob griefing
• Installed a fast leaf decay plugin
• Upped from 20 to 32 player slots (we hit 20/20 today!)
• Created a site to get build access (You can use /nonick in game to revert this - and /realname to reveal the Minecraft account name for another player with a nickname)

Hello everyone! A few days ago I mentioned I was working on a new WebExtension for Tildes.

Since the tidal wave of users has flooded the Spectrian plains of Tildes, I came up with this idea for having interactive guided tours of the interface to explain how Tildes works and why certain things are the way they are. Well, a basic version with two (count 'em, two!) tours is here! An introduction tour as an example of what to expect and some extra info. And a homepage tour going over everything you can find there.

Firefox users, you can install Tildes Shepherd today! Chromium-based browser users, you will have to wait a while or switch to Firefox, sorry. ;)

As you will see in the introduction tour after installing the extension, if you have any questions or feedback, you can message @Community or comment in this topic. It's very likely I made some mistakes in what's already there so even if it's just a typo, let me know!

As far as other tours goes, I have some planned and am open to anyone creating their own. Even if you have no programming knowledge whatsoever, if you can come up with a tour by taking screenshots and drawing over it in your favorite image editor I'd be more than happy to turn that into code for you. The most time-consuming part of creating tours so far has been finding out all the information and then condensing it into something readable, the coding aspect has been pretty easy.

If you're new to Tildes and like what you see, please consider donating! A fundraiser was started by @talklittle and a number of goals have already been reached, with 2 more goals remaining at 500 donors. So if you want that to happen, donate! Thank you! <3

Make sure to back up your save files if you're on the experimental branch!

Edit: The path to the save file in Linux isn't correct:

/home/[LocalUserName]/.steam/steam/steamapps/compatdata/526870/pfx/drive_c/users/steamuser/AppData/Local/FactoryGame/Saved/SaveGames/76561198144444658 [#this number might be different.]

Should see the save file with the title of your save there, just copy it to somewhere else.

This is where I found it on Ubuntu 20.04, with proton.

After 11 years of life, Google Authenticator has added cloud backups for OTP keys in version 6.0.

Google Security Blog: Google Authenticator now supports Google Account synchronization

This is surprising news to me, because historically Authenticator had no way to backup keys by design. Here's a 2017 quote from a Google engineer who maintains Authenticator:

There is by design NO account backups in any of the apps. ^[source]

This design choice always made sense to me, as the point of 2FA is that you've got (1) something you know, and (2) something you have. The second factor should be tied to a physical device. If you lose the physical device, the second factor should be gone, and you'll need to use one of those 10-ish backup codes that we all definitely keep somewhere safe. I'm quite befuddled that Google is reversing this design choice and walking back their previously strong, security-centric design for the sake of user convenience in the case of a lost phone. I used to advise my friends and family to choose Google Authenticator over Authy for this specific reason.

If you want further reading, here's a PCWorld article with an altogether different tone than Google's announcement: Google Authenticator’s long-awaited cloud 2FA feature carries hidden risk