Just your normal everyday casual software dev. Nothing to see here.

People can share differing opinions without immediately being on the reverse side. Avoid looking at things as black and white. You can like both waffles and pancakes, just like you can hate both waffles and pancakes.

  • 0 Posts
  • 369 Comments
Joined 2 years ago
cake
Cake day: August 15th, 2023

help-circle

  • I believe they are replying to the article you posted in regards to the download from legit sites comment, not the fact that the sites have shit web practices (which while correct is a different thing).

    To the people who didn’t read the article posted in the comment prior, basically the software installed wasn’t the legitimate software, it was a modified software that was a trojan that was forwarding passwords stored in the keepass database to a home server.

    That’s not something that the sites are going wrong, nor is it the password managers fault. That’s fully the users fault for downloading a trojan.


  • Keepass does a pretty decent job. I have keepassXC on my Windows, Debian and Android devices. On Android it’s integrated into the phone(and the autofill service if actual 2fa isn’t supported on the app) so it works on every application. With IOS though I know they can be a stickler on anything remotely technical so I’m not sure if something similar exists with it. I also use syncthing as the service to make sure the same copy of the database is on each device to prevent having to use a password manager that requires a subscription for a cloud service, this also minimizes my risk factor of a cloud service being compromised.


  • I have Proxmox Backup Server backing up to an external drive nightly, and then about every 2 or 3 weeks also backup to a cold storage which I store offsite. (this is bad practice I know but I have enough redundancies in place of personal data that I’m ok with it).

    For critical info like my personal data I have a sync-thing that is syncing to 3 devices, so for personal info I have roughly 4 copies(across different devices) + the PBS + potentially dated offsite.






  • However, Google can still take a service fee on transactions completed with alternative payment methods. For in-app and linked purchases in games, Google can charge a fee of up to 20% for purchases that “impact game outcomes, gameplay progress rate, or player power,” as well as for purchases with “random outcomes” (i.e., loot boxes).

    What the hell even was the point then for Epic fighting this. “Oh yea you can use an alternate store and use an alternate payment system, FYI we are still charging you the google service fee”

    Like sure 20% is less than 30% but like, google isn’t involved the number should be 0%

    Also the fact that google required a time-frame(3 years) on how long it has to be before they are allowed to pay other stores to not put their store on the device… I feel like Epic’s entire fight was just a way to piss money away, only thing it really accomplished was a fake image of software freedom and a control to add even more restrictions in place.







  • the implication of that is weird to me. I’m not saying that the horse is wrong, but thats such a non-standard solution. That’s implementing a CGNAT restriction without the benefits of CGNAT. They would need to only allow internal to external connections unless the connection was already established. How does standard communication still function if it was that way, I know that would break protocols like basic UDP, since that uses a fire and forget without internal prompting.




  • I haven’t used a guide aside from the official getting started with syncthing page.

    It should be similar to these steps though, I’ll use your desktop as the origin device.

    1. install syncthing on all devices you want to be syncing with
    2. on your desktop syncthing page, click “add remote device” and add the device ID of your phone(found on your phones syncthing app), you can also add any other device you want to have communications with (you will need to approve this action on the phone as well so be on the lookout for a notification)
    3. make a backup of your current keepass file just in case these steps shouldn’t cause files to change but, since the end goal is syncing two devices that you have mentioned have differences with files with the same name better safe than sorry
    4. create a keepass share on one of the devices (the folder path of this file should be wherever your keepass file is stored on your device. If this file is in a folder with a bunch of other files, you may want to move the file to it’s own subfolder or you will end up sharing all of the files in that path)
    5. under file versioning chose what type of file version control you want. I prefer staggered since it when a remote device changes the file it moves the old file to a folder, and then deletes them according to the settings
    6. at this point you should double check the name of your mobile devices keepass file name, if its the same as the name of the db on the desktop, you should rename it prior to continuing. Keepass should be able to detect a file conflict and rename it on it’s own but, better safe than sorry.
    7. share the folder with the device you want to sync it(your phone in this case)
    8. Your phone should get a notification that a device wants to share something with it. Approve it, be careful not to clear it because it’s a pain in the butt to get that notification back if you accidentally deny or swipe it away, the mobile app isn’t /amazing/ with it’s UI (but it has gotten better)
    9. once approved configure it to where you wanted the file to be on your mobile device.
    10. You should be done at this point. Syncthing should be automatically syncing the keepass files between the two

    Some things you may want to keep into consideration. Syncthing only operates when there are two devices or more that are online. I would recommend if you are getting into self hosting a server, having the server be the middle man. If you end up going that route these steps stay more or less the same, it’s just instead of sharing with the phone, its sharing with the server, and then moving to the server syncthing page and sharing with the mobile. This makes it so both devices use the server instead of trying to connect to each other. Additionally, if you do go that route, I recommend setting your remote devices on the server’s syncthing instance to “auto approve” this makes it so when you share a folder to the server from one of your devices, it automatically approves and makes a share using the name of the folder shared in the syncthing’s data directory. (ex. if your folder was named documents and you shared it to the server, it would create a share named “documents” in where-ever you have it configured to store data). You would still need to login to the server instance in the case of sharing said files to /another/ device, but if your intent was to only create a backup of a folder to the server, then it removes a step.

    Another benefit that using the server middleman approach is that if you ever have to change a device later on down the road, you are only having to add 1 remote device to the server instance, instead of having to add your new device onto every syncthing that needs access to that device.

    Additionally, if you already have the built in structure but it isn’t seeming like it is working, some standard troubleshooting steps I’ve found helpful:

    • if trying to share between devices, make sure that there is at least two devices that are connected as remote devices active in order to sync
    • If above is true, make sure the folder ID’s are the same between both devices. that is how syncthing detects folders that should be sync’d
    • If also true, make sure the devices are being seen as online in remote devices. If it isn’t showing as online, the connection is being blocked somewhere, verify you don’t have a firewall or router blocking it somewhere.