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.
been trying to lower my social presence on services as of late, may go inactive randomly as a result.
it only works as a UPS if you periodically discharge the battery. My first “server” was a compaq laptop, I had used it for years and then reprovisioned it to Ubuntu Server, after 2 or 3 years of 24/7 if you unplugged it at all it just instant died because keeping it 100% charged all the time killed the battery.
I’m not PC but, one benefit of using a central server for syncthing is an always on backup that doesn’t require another client device to be on, it also allows for easier creation of new shares.
For example, with syncthing you can set the “servers” client device to auto approve/accept any shares that are to trusted devices, then when you get a new device, instead of needing to add that device to every device you share on the syncthing network, you only need to add that device to the server and then you can have your other clients connect to the servers share instead of device to device. It’s easier. You can also configure the shares on the server to use encryption by default too, since you don’t really ever need to actually see the files on the server since it’s basically a install and forget style client.
As an example of what I mean:
I have 10 different devices that run syncthing, 9 clients and a “server” client. these clients are not always on at the same time, and as such when I change a file, the files can become desynced and cause issues with conflicts. By having a centralized server, as long as the server is on(it always is) and client itself is online, it’s going to always sync. I don’t need to worry about file conflicts between my clients as the server should always have the newest file.
Then for example say my phone died. Instead of needing to readd every seperate client that the phone needs to share with to the new device, I only need to add the phone as a trusted source on the “server” client via the webui -> click share to that device on every share the phone needs, and then remap the shares to the proper directories on the mobile device. this is vs having to add every device to the phone, and the phone to every device it needs access to ontop of reconfiguring all the shares. It’s simpler, but fair warning does cause a single point of failure if the server goes offline.
yea I have the machine backed up in case this happens. I have noticed that its a mess UI wise. But ipfire doesn’t seem to be stable. every few months it’ll randomly kill itself which will take everything on the network down until i manually restart the machine and then force tell it a new DNS server. It’s something I’ve never managed to resolve on the machine, and I don’t seem to have that issue with my test network with OPNsense.
I’m in the process of switching from ipfire to opnsense myself.
I hate how bloaty opnsense is at first glance but it has so much more control so once I copy my current config I’ll be leaving ipfire in the dust.
I have never thought of doing this. That’s now going on my server.
I’m all some Debian dereritive, whether it’s Q4OS or just Debian,
deleted by creator
I lack the use case for this service but, it looks good on paper. Nice!
If I understand the project right, this would be a great opening for non-profit communities to make a page for the town and add the services, instead of the typical static pages
Basically many domain providers will hold onto domains for a little while after it expires.
Some like namecheap also advertise the domain names to peddle-man companies that will somehow buy temporary access to the domain after your extortion recall window expires.
To continue the namecheap example, when your namecheap domain expires, it gives you a lapse window where you can pay like double the cost of the domain renewal to reclaim it. If you don’t reclaim it during that window they give it to a middleman whom will somehow buy a 2 or 3 months domain lease for it. They will put it on a “site for sale” broker page and will charge you easily 100x what you paid for the domain if you wanted it back.
I would recommend just keep checking on it every few days to see if it gets released.
I believe they are talking about this.
If you have it at all exposed to the internet, you should probally terminate it
As a summery: Multiple endpoints on the software don’t check for authentication and an unauthenticated person can retrieve your complete settings configuration including your API keys and your password and also change your current configuration, Just by sending a simple POST request.
That’s wild to me that that was something that was able to be done.
Yea, which is a fair expectation, but it’s not a safe assumption. Verify it does before prolonged use. Make sure its well ventilated(heat is killer to batteries as well), and that some form of BMS is present on the system, and that it’s enabled because some have the system but have it disabled by default.