Wander

Even if it's just an archived version, someone somewhere will find utility in IT or coding advice posted over a century ago.

This new version introduced a system so that your instance stops sending out content to other instances that are supposedly dead / offline.

Unfortunately for some reason there's false positives. When I checked comparing the results from a curl request vs the information in our Lemmy database I found over 350+ false positives.

In the DB there is a table called "instance" which has a column called "updated". If the date on that column is older than 3 days, your server will stop sending any content to those instances.

For some reason I had entries that were dated as last being alive in July, while actually they were always up. If an entry is incorrect, you can fix it by manually using an update statement and adding today's date. If your instance is not too large you can safely update all entries to today's date and check if everything works as expected from then on any new content created on your instances.

The dead instances won't have an impact unless your instance is larger and generates more content, thus it might be easier to simply update all entries and have Lemmy believe they're all alive if you start noticing wonky behavior and don't want to check one by one.

If you don't know how to access the database run this command where domaincom is your instance domain without the dot.

1. docker exec -it domaincom_postgres_1 busybox /bin/sh

2. psql -U

(The default user is 'lemmy') You could technically do this is one single step, but it's good to know the command to get shell access to the container itself if you didn't know how to.

This should give you access to a postgres CLI interface. Use \c to connect, \dt to list tables and \d+ tablename to list table definition. You can also run SQL queries from there.

Try with this query: SELECT * from instance to list all instances and their updated date.

You can use other SQL queries to get better results or correct false positives. Just be careful with what you execute since there's no undo.

I want to allow certain trusted users the ability to take down my lemmy instance or reboot it or x, y, z actions in case things go wrong or there is a security incident.

Ideally I would want to have some sort of admin interface that's secure and tested and allow these users to have some sort of login and from there have the ability to execute certain actions that could correspond to a "break glass in case of emergency" scenario.

I've been pointed at https://www.portainer.io/ but they seem to have a steep price for the limited use-case that I would be giving it.

I know about some admin interfaces like webmin, but I don't know which one allow you to create very restricted users or just give users the ability to execute some limited pre-defined commands.

Thank you <3

I'm trying to understand how an app would even get that info in the first place, how that's classified and why a mobile operating system even has a way to provide that data.

Am I correct in assuming that if an app is used without play store / play store framework that it would not be able to get access to that data?

Thanks!

Hello!

Years ago I found that nomachine was really good to set up remote desktops that felt nearly native.

However, nomachine is proprietary and I was wondering if there were any solutions in 2023 that were more recommended for running a remote desktop on a cloud vm / VPS / proxmox vm.

Unfortunately it seems that Sunshine requires a GPU, otherwise I would be using it together with moonlight.

Yikes.

I just had to do this myself and found this handy guide on reddit created about a year ago. So I don't claim credit, but I wouldn't want such useful content to be available only on reddit, so I'll share it over here:

Credit goes to /u/walllable.

Original POST:

Title's pretty self explanatory I think! This will be using VirtualHere, a program that connects one computer's USB devices to another computer via Wi-Fi, and will also let you access this functionality via Game Mode, so you don't have to go into the desktop in order to do this. This might use less battery power than controlling your PC via Steam Link as well since the Deck doesn't have to decode a video/audio stream and all that. This involves installing the program on both your Deck, and on your PC. I'll be providing instructions for both.

Skip step 1 if you've already set the desktop deck account's password. If you don't know if you have or not, go ahead and follow it.

1. Go into desktop mode (Open the Steam Menu, go to Power, select "Switch to Desktop,") open System Settings, and go to the Users section, then click "Change Password." Set it to whatever you'd like, though ideally something easy to type with the On-Screen Keyboard, since you'll be typing it every time you want to use the Deck as a controller.

2. Open the file browser, and make a folder in the Documents folder named "virtualhere" (all lowercase, no quotes)

3. Download the VirtualHere Linux Server. The specific one you'll want is "VirtualHere USB Server for Linux (x86_64)," under "Generic VirtualHere USB Server Builds"

4. Save the file you're downloading to the virtualhere folder you made in your documents earlier.

5. In the file browser, right click on the "vhusbdx86_64" file that you downloaded, and click on "Properties." In the window that opens, go to the "Permissions" tab and tick the "Is executable" checkbox.

6. Open Steam on your desktop, and click "Add a Game" on the bottom left corner, then click "Add Non-Steam Game." (You can add pretty much whatever application you want for this step, it doesn't matter much since we'll be changing all of its settings later anyway.)

7. Find the application you just added in your list of games, right-click it, then click "Properties"

8. Replace whatever text is in "Target" with env, whatever's in "Start in" with "./" (with quotes,) and "Launch options" with -u LD_PRELOAD konsole --fullscreen --notransparency --hold -e sudo /home/deck/Documents/virtualhere/vhusbdx86_64 You can also change the name of the application and set an icon, if you'd like (I set mine to "PC Controller.) The end result should look like this.

9. Close the Properties window, and go ahead and launch it from Steam, then enter the password that you set earlier (The terminal not showing any changes as you type is normal.) If you see text that says VirtualHere USB Server is running...press CTRL-C to stop then you're all set on the Deck side of things!

You can now exit Desktop Mode, and go back into Game Mode on your deck, we're pretty much done here.

Now let's get the PC side of things set up, this won't take as many steps as getting it set up on the Deck.

1. Download the VirtualHere Client for your respective platform. In my case I'm on Windows, but the process should be pretty similar for other platforms? I'm not sure about Linux, but assume if you're using Linux you probably know what to do.

2. Open the file that you just downloaded, you should see a window like this pop up.

3. Open the application you added on your Deck, and enter your password with the On-Screen Keyboard (Old down the Steam button, and press the X button to bring it up.)

4. Once you've done that, the window on your desktop should have its list populated like this. If not, try double-clicking on the "USB Hubs" text in the window. That seems to help it appear faster for me, I think?

5. Double-click on the "Steam Controller" entry, and you should hear a noise indicating a USB device got connected, and a popup similar to this from Steam in the bottom-right corner.

And you should be all set! Your Deck will now behave like a Steam Controller does, including being able to do stuff on the desktop, per-game bindings (that use your custom bindings from your Deck if you've got any set up!) and gyro functionality.

To disconnect the Deck from your PC, show the VirtualHere window from the status section thing on your taskbar, and just double-click on the Steam Controller entry again. You should hear Windows' "USB Disconnect" sound, and regain control on the Deck itself so you can exit the application.

Some notes that I think can be handy:

1. If you don't regain control on your Deck after exiting VirtualHere, don't worry, this isn't permanent! Just hold down the power button on the top, and select "Restart." Once the Deck's back up and running, you should be all good.

2. If you're having problems with latency or the connection dropping out, try connecting your Deck to the 5ghz band of your router (Or the 2.4ghz band if 5 ghz is screwing you over!)

3. Lowering the screen brightness on your Deck before you connect it to your PC will help your battery last longer, if you plan on using it for an extended period of time.

Hopefully Valve adds this as native functionality someday, but until then I've really been liking this, since I don't really have any other controllers to use other than a Steam Controller, and I figured "Well, I paid $400 for this thing with a good controller in it, I might as well use it for my PC." Hope this guide came in handy!

From when it was still cool and niche to be a redditor and you needed to identify each other in public, you could use that sentence.

Lemmy / Kbin is getting to the point where it's cool and niche. Want it or not, you're one of the cool counter-mainstream kids now.

So, what's our secret code phrase?

Something with big colorful tiles I believe. Was recommended as the way forward for self hosting in general, but I can't find it now.

Thank you <3

EDIT: It was Yunohost! Thank you everyone. This helped me out a lot.