Interesting. Yes, that's basically what I've been going for but none of my prompts ever gave a satisfactory response. Plus I noticed you just copy/pasted from my initial comment and it worked. Weird.
After my last post I was eventually able to get it to work by uploading an example image of Santa pulling the sleigh and telling it to use the image as an example, but I couldn't get it by text prompt alone. I guess I need to work on my prompt skills!
Hmm, lived there for a long time and walked by Boston City Hall almost every day. I'm not quite sure how to differentiate objective beauty and subjective beauty, but at least subjectively, in my opinion, it's an eyesore.
Agreed on all fronts that City Hall Plaza is a disaster, though. I thought there were plans to revamp it with the Government Center station green line revamp a few years ago, but not sure if that improved anything.
You're right that there was a plaza renovation project. It has helped massively, (though I think it didn't go far enough), and it was only completed at the end of 2022 so most people grousing about the building have never seen it.
Yeah, I didn't understand the purpose of this device when it came out and still don't. It's an interesting system but seems like worst of both worlds because the coral TPU and M7 aren’t low power enough for battery applications, and it's unclear whether the full 4 TOPS of the Coral is achievable given the MCU’s memory bus bandwidth. So to me it looks like a computationally underpowered system that you have to keep plugged into the wall.
Going with the Cortex A Coral Dev Board or another SBC with the PCIe or USB standalone Coral TPU seems like a better bet. You'd get a better camera (eg via USB), more processing power and memory, and more full featured software (both Linux and TFLite instead of baremetal or embedded OS and TFLite Micro). Price point would be higher for this option, but you'd certainly make that up in saved time very quickly not having to deal with baremetal programming or an embedded OS.
One thing that springs to mind is a monitor for predator (pest animal) traps in remote bush regions. The system spends most of its time asleep, and is woken and starts consuming power only when a PIR sensor is triggered from a visiting animal's body heat.
Then the battery-sapping stuff happens to analyse video and differentiate between target and non-target species and finally trigger the trap or go back to sleep.
A system like this would be an ecological game changer in my country.
Jetson Nano is a lot more expensive. But at the same price point as Coral you can buy Orange Pi 5 with 4 gigs of ram, 6 tops NPU(not supported as good as Coral though, but is generally more open and has support of much more frameworks) and have a full-blown OS there. SBC is $66, and camera is another $15. And you can buy it right now, not "pre-order" something "coming soon". Coral supply history is a very sad tale. The hardware was impressive 4 years ago, when it first came out. But now we have no second generation in sight, no supply and no communication from Google that they are still interested in this project.
I've been writing gstreamer-based inference pipelines for a couple years on Jetsons and in my experience there is never a "just" with any of the these, sadly. It is such a painful platform to deal with at a software level... I wish NVidia had more competition.
Without RidgeRun wiki's working pipelines I'd have suspected gstreamer on Jetson never worked at all. It's beautiful when everything comes together but absolutely chock-full of gotchas.
Plus Nvidia seems to think that an acceptable time frame to support a Jetson model is like 2 years, which makes them effectively abandonware soon after launch. They get one LTS OS distro and that's it.
Compare that to ~15 years of ongoing support that the Pi foundation does for the average Pi.
I concur. I've been in that ecosystem for a few years and I finally had to give up on my Jetson Nano in "favor" the new Jetson Nano Orin. Which did solve a lot of my issues with software, and I paid for it, too. Just say no to Nvidia sbc lol but it's extremely powerful when the software is aligned with your goals.
Vendoring means to bundle dependencies into a project directly (often this means copying source code and using/maintaining the copy) rather than from some other source (other packages, OS, package repo, etc). Here's an article from LWN that talks about it with a real world example: https://lwn.net/Articles/842319/
That's right, origin and destination are still visible. Even if you use encrypted DNS to hide hostname to IP lookups, your actual traffic has to be routed somehow by someone. Whether that's your ISP or a VPN provider + their ISP.
Posted this on another thread about VPNs a few weeks ago. Reposting here since I think it applies.
I've recently been describing what a commercial VPN provides to non-technical friends and family as a type of "global virtual Internet cafe" subscription - the pros and cons of using a physical Internet cafe mostly apply. An Internet cafe isn't inherently (i.e. due to technical benefits of underlying technology) any more or less secure than connecting to your home or work wifi/network, and the Internet cafe knows who you are and what websites you're visiting, but your ISP/employer doesn't (since you're "at" the Internet cafe, not on your home/work network).
Of course, your ISP/employer does know that you're visiting the Internet cafe, and in the case of work (and some ISPs) can stop you from doing so.
If you visit a website from an Internet cafe, the website may still be able to figure out who you are, just like they can when you bounce between different networks normally. And of course, if you login to your account on a website or put your shipping address or something in when buying something, you're self identifying (unless you have throwaway accounts or forwarding addresses or whatever).
And finally, if someone really wants to figure out who you are to a high degree of confidence, they will.
I find this lands pretty well and is close enough to being technically correct without getting into the details that non-technical people would start glazing over if I got into.
I've recently been describing what a commercial VPN provides to non-technical friends and family as a type of "global virtual Internet cafe" subscription. It's not inherently (i.e. due to technical benefits of underlying technology) any more or less secure than connecting to your home or work wifi/network, and the Internet cafe knows who you are and what websites you're visiting, but your ISP/employer doesn't (since you're "at" the Internet cafe, not on your home/work network).
Of course, your ISP/employer does know that you're visiting the Internet cafe, and in the case of work (and some ISPs) can stop you from doing so.
If you visit a website from an Internet cafe, the website may still be able to figure out who you are, just like they can when you bounce between different networks normally. And of course, if you login to your account on a website or put your shipping address or something in when buying something, you're self identifying (unless you have throwaway accounts or forwarding addresses or whatever). And finally, if someone really wants to figure out who you are to a high degree of confidence, they will.
I find this lands pretty well and is close enough to being technically correct without getting into the details that non-technical people would start glazing over if I got into.
