OminousOrange

joined 1 year ago
sorted by: new top controversial old
Nearly 80% Of New EVs Are Leased: Dealer Data in c/[email protected]
[–] [email protected] 4 points 16 hours ago

It really made the most sense for me. Essentially long term rent a car and when the term is up, either technology has progressed to where the features of a new model are vastly superior, so give it back to the dealership, or there is still limited supply (I'm in a small EV market in Canada) and tech is more or less the same, then I buy it out.

Seemed like a fairly significant reduction of risk in getting an EV and a win win either way.

Looking for zigbee smart plugs with monitoring in c/[email protected]
[–] [email protected] 9 points 2 days ago (1 children)

I'm not sure if they're available with UK plugs, but I've got a pack of Thirdreality Zigbee plugs that monitor energy use and have a button on them to toggle power.

I've got them connected to Home Assistant. Two do a bit of climate control in a coldroom, the others are for occupancy lighting.

Does each language have "lefty loosey righty tighty"? in c/[email protected]
Las Vegas staff say MrBeast should be blacklisted, cite OSHA, setting medics for failure in c/[email protected]
[–] [email protected] 3 points 3 weeks ago

I would like to see a minority of the house representation of elected people from individual regions with term limits, with a majority of the house being regular people randomly selected to serve for a defined amount of time.

The Two Big Insurers Still Betting on Fossil Fuels [State Farm & Berkshire Hathaway] | Most companies have cut back on oil, gas and coal investments after big climate-related losses in c/[email protected]
[–] [email protected] 1 points 3 weeks ago

It's easy, collect premiums and reject any claims as being "acts of God".

Rant: I can't believe I miss Shaw in c/[email protected]
[–] [email protected] 7 points 3 weeks ago (1 children)

You could check at the Canada Post office if you can charge their provided boxes to that account number.

Unfortunately Rogers is now the largest professional sports holding company in the world now too, with buying out Bell's stake in MLSE. Nothing like promoting competition by allowing megacorps to keep acquiring.

Pastas Assembled in c/[email protected]
[–] [email protected] 2 points 3 weeks ago

Oh yes, I'm not saying don't season your water. Just that seasoning the water on its own is not a way to prevent pasta sticking.

Pastas Assembled in c/[email protected]
[–] [email protected] 4 points 3 weeks ago

Yep, I really like how he applies the scientific method to cooking. Some of my favourites are how he's found the perfect way to boil an egg, cook steaks and roasts (dry brine, reverse sear), and make chocolate chip cookies (he made over 1500 cookies testing how changing each variable changed the final cookie).

Pastas Assembled in c/[email protected]
[–] [email protected] 47 points 3 weeks ago* (last edited 3 weeks ago) (4 children)

It's not salting your water, nor the water volume to pasta ratio, nor if the water is boiling or not, nor oil in the water, but stirring early in the cooking process that will prevent sticking.

From the great Kenji Lopez-Alt:

Pasta is made up of flour, water, and sometimes eggs. Essentially, it's composed of starch and protein, and not much else. Now starch molecules come aggregated into large granules that resemble little water balloons. As they get heated in a moist environment, they absorb more and more water until they finally burst, releasing the starch molecules into the water. That's why pasta always seems to stick together at the beginning of cooking—it's the starch molecules coming out and acting as a sort of glue, binding the pieces to each other, and to the pot.

...

The problem is that first stage of cooking—the one in which starch molecules first burst and release their starch. With such a high concentration of starch right on the surface of the pasta, sticking is inevitable. However, once the starch gets rinsed away in the water, the problem is completely gone.

So the key is to stir the pasta a few times during the critical first minute or two. After that, whether the pasta is swimming in a hot tub of water or just barely covered as it is here, absolutely no sticking occurs. I was able to clean this pot with a simple rinse.

Research in c/[email protected]
[–] [email protected] 9 points 1 month ago

Here's one local to me. Slightly old but quite relevant.

The thermodynamics of electric vs. internal combustion cars in c/[email protected]
[–] [email protected] 1 points 1 month ago

Occasionally, but I work from home and my wife's commute is fairly short, so we can often time the roughly once a week charging so it's during the day.

‘Right to Repair for Your Body’: The Rise of DIY, Pirated Medicine in c/[email protected]
[–] [email protected] 6 points 1 month ago

Oh yes, your pay-to-win government duopoly isn't helping anything, but don't call it impossible. The Affordable Care Act was a start, and I don't doubt the right people could make universal healthcare access a real thing in the US.

14
Network loss after 24hrs on Docker LXC (lemmy.ca)
submitted 6 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]
18 comments fedilink
 

Fine folks of c/selfhosted, I've got a Docker LXC (Debian) running in Proxmox that loses its local network connection 24 hours after boot. It's remedied with a LXC restart. I am still able to access the console through Proxmox when this happens, but all running services (docker ps still says they're running) are inaccessible on the network. Any recommendations for an inexperienced selfhoster like myself to keep this thing up for more than 24 hours?

Tried:

  • Pruning everything from Docker in case it was a remnant of an old container or something.
  • Confirming network config on the router wasn't breaking anything.
  • Checked there were no cron tasks doing funky things.

I did have a Watchtower container running on it recently, but have since removed it. It being a 24 hr thing got me thinking that was the only thing that would really cause an event at the 24 hr post start mark, and it started about that same time I removed Watchtower (intending to do manual updates because immich).

...and of course, any fix needs 24 hours to confirm it actually worked.

A forum post I found asked for the output of ip a and ip r, ~~see below.~~ Notable difference on ip r missing the link to the gateway after disconnecting.

Update: started going through journalctl and found the below abnormal entries when it loses connection, now investigating to see if I can find out why...

Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] Nameserver 1.1.1.1:53 has failed: request timed out.
Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] Nameserver 192.168.1.5:53 has failed: request timed out.
Apr 16 14:09:16 docker 922abd47b5c5[376]: [msg] All nameservers have failed

Update 2: I found using systemctl status networking.service that networking.service was in a failed state (Active: failed (Result: exit-code)). I also compared to a separate stable Docker LXC which showed networking.service was active, so, did some searching to remedy that.

x networking.service - Raise network interfaces
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-04-16 17:17:41 CST; 8min ago
       Docs: man:interfaces(5)
    Process: 20892 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
    Process: 21124 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug (code=exited, status=0/SUCCESS)
   Main PID: 20892 (code=exited, status=1/FAILURE)
        CPU: 297ms

Apr 16 17:17:34 docker dhclient[20901]: DHCPACK of 192.168.1.104 from 192.168.1.1
Apr 16 17:17:34 docker ifup[20901]: DHCPACK of 192.168.1.104 from 192.168.1.1
Apr 16 17:17:34 docker ifup[20910]: RTNETLINK answers: File exists
Apr 16 17:17:34 docker dhclient[20901]: bound to 192.168.1.104 -- renewal in 37359 seconds.
Apr 16 17:17:34 docker ifup[20901]: bound to 192.168.1.104 -- renewal in 37359 seconds.
Apr 16 17:17:41 docker ifup[20966]: Could not get a link-local address
Apr 16 17:17:41 docker ifup[20892]: ifup: failed to bring up eth0
Apr 16 17:17:41 docker systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Apr 16 17:17:41 docker systemd[1]: networking.service: Failed with result 'exit-code'.
Apr 16 17:17:41 docker systemd[1]: Failed to start networking.service - Raise network interfaces.

A reinstall of net-tools and ifupdown seems to have brought networking.service back up. apt-get install --reinstall net-tools ifupdown

Looking at the systemctl status return, I bet everything was fine until dhclient/ifup requested renewal about 24 hours after initial connection (boot), found that networking.service was down, and couldn't renew, killing the network connection.

We'll see if it's actually fixed in 24 hours or so, but hopefully this little endeavour can help someone else plagued with this issue in the future. I'm still not sure exactly what caused it. I'll confirm tomorrow...

Update 3 - Looks like that was the culprit. Container is still connected 24+ hrs since reboot, network.service is still active, and dhclient was able to renew.

Update 4 - All was well and good until I started playing with setting up Traefik. Not sure if this brought it to the surface or if it just happened coincidentally, but networking.service failed again. Tried restarting the service, but it failed. Took a look in /etc/networking/interfaces and found there was an entry for iface eth0 inet6 dhcp and I don't use ipv6. Removed that line and networking.service restarted successfully. Perhaps that was the issue the whole time.

0
Proton Drive Camera Backup has Arrived! (proton.me)
 

This has been one of the key features I've been waiting for to finally be able to move away from Google Photos and OneDrive for mobile photos backup.

0
Proton Drive Camera Backup has Arrived! (proton.me)
 

This has been one of the key features I've been waiting for to finally be able to move away from Google Photos and OneDrive.

1
Another patio sectional, fresh out of the shop. (lemmy.ca)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
6 comments fedilink
 

Just made this sectional following the plans from Ana White.

Roughly $900 CAD in materials, $750 of that being the cushions. I used Duvholmen cushions with Jarpon covers from Ikea, accent pillows I found at Home Sense. All 2x4 lumber and I used pocket holes where screws would be visible. Finished with Ready Seal natural cedar.

Quite happy with it overall. It's really comfortable and will last far longer than (and was cheaper than) those plastic weave ones from big box stores.

view more: next ›