this post was submitted on 26 Jun 2023
445 points (100.0% liked)

Technology

37747 readers
235 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
alyaza@beehaw.org
TheRtRevKaiser@beehaw.org
gyrfalcon@beehaw.org
rs5th@beehaw.org
Los@beehaw.org
coldredlight@beehaw.org
SemioticStandard@beehaw.org
TheRtRevKaiser@kbin.social
remington@beehaw.org
445
Technology Connections talks about a red fridge from Walmart for an hour (youtu.be)
submitted 1 year ago by Rentlar@beehaw.org to c/technology@beehaw.org
145 comments fedilink hide all child comments
 

In a video by @Techconnectify@mas.to, Alec goes into a deep dive into the simplicity of his particular model, its shortcomings and variety of data logging tests in an attempt to fix them.

TL,DW: Very simple, cheap and ingenious design, with one compressor loop between the fridge and freezer in series. However, its temperature sensor is wonky and so the fridge is more affected by how long the compressor operates than the actual temperature itself. There is a signficant temperature differential between the top and bottom, fans on the exterior or interior could help but with the faulty sensor only made matters worse. With the controller replaced with a proper temp control unit the fridge functioned much better.

you are viewing a single comment's thread
view the rest of the comments
[–] atocci@kbin.social 1 points 10 months ago

I'm probably a bit late to reply, but... He was @ mentioned in the body of the original post, which Mastodon would have notified him of because mas.to is federating. Opening the notification would bring him to this thread on Mastodon, where everything would appear as it normally does when viewing a thread on Mastodon. From there, you can hold a conversation as normal with notifications and all. Unless you were looking at instance URLs, you probably wouldn't even notice the user you're replying to isn't on Mastodon themselves.

Beauty of federation! It (mostly) just works!