solofroto

joined 1 year ago
[–] solofroto@lemmy.ml 5 points 1 year ago (1 children)

You're my fucking hero.

[–] solofroto@lemmy.ml 0 points 1 year ago

Okay I need a bit more information. Are you dual booting Linux with Windows? Tell me more about how this is setup, including what drives you're talking about

[–] solofroto@lemmy.ml 2 points 1 year ago

Just marry me already.

[–] solofroto@lemmy.ml 0 points 1 year ago (1 children)

Reolink My RLC-520A's can be configured through a web interface. No app required. I can just navigate to the camera's IP address through a web browser to configure it.

I -do- use the app, however, for live streaming and configuration because it's more intuitive for me. However, the app isn't necessary for these specific cameras. I can't speak for other models, though.

[–] solofroto@lemmy.ml 1 points 1 year ago

You're most certainly welcome.

[–] solofroto@lemmy.ml 1 points 1 year ago

Hehe you're welcome!

[–] solofroto@lemmy.ml 2 points 1 year ago

FOKIN WOT M8?!

[–] solofroto@lemmy.ml 0 points 1 year ago (2 children)

If I'm not mistaken, when you mount whatever you're mounting, you need to specify the read/write permissions with the mount parameters. Trying to change the permissions after it's already been mounted won't work, afaik.

[–] solofroto@lemmy.ml 1 points 1 year ago (3 children)

Of course. Maybe someone will find it useful :D

[–] solofroto@lemmy.ml 0 points 1 year ago (4 children)

Did you get this fixed?

[–] solofroto@lemmy.ml 0 points 1 year ago (2 children)

I edited the original post to include the script.

[–] solofroto@lemmy.ml 1 points 1 year ago (1 children)

Yeahhh I know about that, it still sucks to have to do that, but it's great that it's an option, at least. I'm just old now and it's very hard for me to find a game that I enjoy. But 9 times out of 10, when I do, I go ahead and buy it.

 

Edit: Everyone is asking for the code, so here it is. Keep in mind, this code assumes a few things:

  1. You'd need to specify the virtual environment path for Python.
  2. You'd need to specify the directory for which the games are located.
  3. You'd have to put a "game_info" file in each game's root directory.
  4. You'd need to have steamcmd installed.
  5. The format of the game_info file is like this (I use CS.RIN.RU):
build: 17601020
steamid: 548430
csrinru: https://cs.rin.ru/forum/viewtopic.php?f=10&t=81377

Hope I'm not breaking any rules. This is my first post on Lemmy. I tried to post on garbage-ass Reddit but apparently being a new user means you can't do fuck-all. So, I'm gonna try to make Lemmy a home.

Anyway, I pirate games. Mostly because I'm broke, and somewhat because I hate spending money on a game and then hating it 15 minutes into it. But anyway..that's neither here nor there.

The entire purpose of this post is just to share this neat little thing I created. I'm not promoting it -- it isn't released. I just wanna share nerdy shit with other people.

The issue that I was having is that I figured, over time, my pirated game collection will get quite big. It will become increasingly more time-intensive to check back to the piracy forums for updated pirated versions of the game.

So I came up with a solution. Whenever I download a new pirated game, I will create a file called "game_info" in the directory which will include three little bits of data.

  1. The build number of the pirated game
  2. The Steam App ID
  3. The link to the forum topic about that game from the piracy site I go to.

I wrote a script that will scan my games directory for each game_info file. It will then use steamcmd to check SteamDB for the latest patches released and compare that to the current build number in the game_info file. Obviously if they don't match -- there's an update. And it will inform me. This way I can quickly check if there are any updates available for a game, then I can go to the piracy forum and check to see if anyone has released the updated version yet.

I thought it was cool. Anyway, just thought I'd share some nerdy shit.

Feel free to degrade me.

view more: next ›