Heavybell

joined 1 year ago
[–] [email protected] 1 points 3 days ago

Ahhh, how logical :P

thanks

[–] [email protected] 10 points 3 days ago (7 children)

The fucker is a chaser?

[–] [email protected] 3 points 1 month ago

I personally prefer like/dislike over a star rating system. Maybe, MAYBE having a middle "meh" rating would be helpful but at the end of the day you either recommend something or you don't. If you ask a friend "should I play this?" and they say "idk man" that's basically a recommendation to not play it.

[–] [email protected] 5 points 1 month ago

No, you`re right.

[–] [email protected] 43 points 1 month ago* (last edited 1 month ago) (2 children)

This looks like a python programmer that is mad they have to write ~~C#~~ Java…

[–] [email protected] 11 points 1 month ago (1 children)

I don't believe there was any specific API in use here, for virus scanning or not. I suppose maybe the device driver API? I am not a kernel developer so I don't know if that's the right term for it.

Crowdstrike's driver was loaded at boot and caused a null pointer dereference error, inside the kernel. In userspace, when this happens, the kernel is there to catch it so only the application that caused it crashes. In kernelspace, you get a BSOD because there's really nothing else to do.

https://youtube.com/watch?v=wAzEJxOo1ts

[–] [email protected] 3 points 2 months ago

/usr/bin/joe mama

[–] [email protected] 0 points 2 months ago

I would like to use IPv6 but google and MS are having a dick waving contest with competing implementations, as I understand it. So fuck it.

[–] [email protected] 21 points 2 months ago (1 children)

Google search is still better than bing, somehow. Gmail is good for signing up to stuff I don't want mailing my protonmail. Google maps is still genuinely useful. Youtube is, for now, still better than any alternative I know about. I don't see what's wrong with Pixel phones.

Don't get me wrong, google is evil now and I don't like it. But I don't know any better alternatives for those things. Mm, except gmail, I could replace that I guess but it's such a pain.

[–] [email protected] 16 points 3 months ago

I program professionally in C# and I gotta say, it really isn't for that. You can do services in it, but that's as low level as I'd suggest. It's definitely a high level language for rapid dev of web and desktop stuff.

[–] [email protected] 10 points 3 months ago (1 children)

If the only tool you have is a hammer, everything looks like a nail.

That's the only thing I can think to answer your question. There are some problems that are best solved with other tools, like text parsing for example you might want to call out to some code written in a functional language.

[–] [email protected] 5 points 3 months ago (1 children)

The ATO's myTax system is pretty great, I hope with this you guys finally get something as nice.

111
submitted 4 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]
 

cross-posted from: https://lemmy.world/post/15565311

It was a long running project, but I finally did it. I built what I'm calling a smart mailbox that communicates the presence of mail locally with Home Assistant via ESPHome.

Parts:

Tools:

  • Soldering iron
  • Router for cutting grooves in wood
  • Drill and hole saw bits
  • Various files and sandpaper

For a start, I followed this guide to get me started on the power delivery portion, but I ended up using much higher valued resistors since I found that I was losing more battery charge through the voltage divider than I was from the ESP32 or proximity sensors.

Once I'd tested the concept with the parts just laying in a jumble on the table, it was time to get to work.

I started by cutting a plank of pine to fit my mailbox, chamfering the ends to make space for the metal joins. I routed out some spaces for the tops of the bolts that hold the mailbox down.

Measured out where the sensors should go, along with a surrounding space to screw down some little perspex windows to cover them. The idea I wanted was for the mail to be able to slide over the sensors without getting caught on them, as well as to protect them from dust.

Routed out the dents and cleaned them up with a chisel and sandpaper. Cut the perspex to shape for a test fit.

On the other side, I routed out a notch for the cable to access the sensors.

I had originally planned to just solder wires into the sensors, but then I realised JST connectors would fit perfectly into the sensors. This meant I had to widen the holes somewhat, which I did with a small chisel and file.

I got a bit lazy with making screw holes to hold down the perspex, so they're not in as neat a place as I'd like. If I did this again I'd measure properly for their placement. Still, with countersinking they hold down the perspex well and nothing sticks up for mail to get caught on.

I also got started on making a housing for the solar panels. I used the router to carve out a 1-2mm area for them to sit in, and a much deeper ditch linking the two terminals, which you'll see in a later picture. For now, here's how they look sitting in it.

Wiring up the prototype board was next. Again, see the article I linked above for how this works. I used pin headers to allow the ESP32 dev board to be slotted in and out, just in case I ever needed to take it out for replacement or reprogramming. Also the JSTs on the prototype board are for connecting the battery (top left), connecting the solar panels (bottom left), providing power to the sensors (bottom right) and clock and data lines for the sensors (top right). Since the sensors are both using the same I2C bus address and cannot be configured otherwise, I had to run two clock and data lines, but if I'd found sensors that could have different addresses I could have just used one of each. I didn't take a photo of the board at this stage, but I later added another header to connect a button to reset the ESP32 from the outside.

I also made the data and power cable for the sensor board.

The solar panel housing and 'sensor plate' were both painted and treated with polyurethane spray to protect them from rain and humidity.

I drilled holes in the weatherproof box to fix the cable glands and the weatherproof button. In the case of the solar panel wire, I had opted to buy speaker wire since I figured it would be easier to run in the channel between the two solar panels, being flat. But that also made it not really fit the cable glands that great. I ended up stripping some of the outer sheath off some 2 wire power cable I had, and wrapping that around the part of the speaker wire that gets clamped in the glands, just to make a reasonable seal. These all were on the side I decided I would mount at the bottom, so water wouldn't be able to easily fall into the box.

Final test fit. I later used epoxy glue to glue down the nylon headers and the battery holder inside the box.

The mailbox itself also needed a hole in the bottom for the sensor cable to come out. After drilling a hole and filing it into a square shape, I cut some rubber grommet strip to size and fitted it around the hole, with some marine silicone adhesive to protect the sharp metal edges from water and to hold the grommet strip in place.

I'd drilled some holes in the brick wall my mailbox sits upon for masonry anchors, and this piece of treated pine got the last of my polyurethane spray, just in case.

Using a two pieces of the leftover perspex glued together, I made an internal mount for the antenna, figuring it would be best to not have the thing either floating around freely inside the box or sticking out the side where people could potentially break it off.

Finally, after weeks of off and on work, it was ready to install.

The ESPHome coding used my VCNL4010 component, and if anyone is interested I can share it but it's kinda a large file.

8
submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]
 

cross-posted from: https://lemmy.world/post/12979137

I made an ESPHome external component for the VCNL4010 proximity sensor.

Hopefully it's of use to someone.

view more: next ›