Inventor looks like a certifiable scam artist

https://m.primal.net/HXPS.jpg


Interesting! Yet gives off strong dystopian vibes.


Muy bueno, no es para todos pero a muchos les puede servir


Cool surveillance tech; looking forward to everything everywhere being fed to a single corporation for analysis. Can’t see how that goes wrong!


good grief


We will never learn.

"Let's record everything we and the people we are talking to and upload it into a central location" so we can replace God with AI.....

Is In-Q-Tel involved in this at all??


what is this gay shit?


Apart from the headline, this is like: “Why putting spying devices all around you or hacking them when we can make you were one?!”. One thing is for sure, AI ain’t funny.


i assume you have privacy concerns


And they're buying a stairway to heaven


Do we need that for our improvements? I'm not sure 🎩⚡💜🧡


Totally not dystopian


We went from,  "How dare Facebook suggest things I talk about!" to "Oh cool! Something that will tell me how to think about the stuff I talk about!" Real fast.


dystopian as it can be


Head kicked by donkey 🫏.


This is getting too obvious. It’s insulting. I live in what some may define as the “hood” and there’s a government program giving out tablets with free wifi but nothings being done about the illegal evictions happening to people. Are we supposed to believe the government sudden generosity?🥷s are paranoid so no one’s buying it too many efforts to put devices in peoples home that record and watch everything.


But is it a luxury watch everyone can be afforded to spend their time on?


“Tab is a small puck that hangs around your neck and listens to everything you (and the people around you) say. “

Just what we need!


"superpowered tamagochi" does not equal "replace God" LOL.  gfyai


Maybe it's time certain groups of people stopped being so industrious


Seems dystopian as fuck no ?

Is there any way to have privacy when using chatGPT like cloud based AI services ? Like an encrypted dedicated instance in the servers of the company, in order to use AI tools in a private manner ?

The product you shared yesterday was more privacy preserving IMO, I like it much more:
note1fmw3vq7mpxhpfhhkz7saedm5nr07ck6k7yxst9gxd0q3dcl5mahscrj678

https://primal.net/e/note1fmw3vq7mpxhpfhhkz7saedm5nr07ck6k7yxst9gxd0q3dcl5mahscrj678


Yep


Webby award from the gremlin himself huh


What do you think about these wearable ai products? I don't see why a phone wouldn't just be a better version of it


What could possibly go wrong🤔🙄


“You should have no expectation of privacy…”


What a terrible concept.


Reads exactly like a 2021 SBF glorifying piece... 🫣😅


Will it die if I don’t take care of it?


IMHO these "growth opportunities" are mostly cash grabs riding the AI hype train. They hope to attract capital and be first to market with some product, but even if they do, they won't have a real moat or competitive advantage. In the majority of cases it will be good for the founders getting payed for a few years and making a name for themselves, but a waste of the investors capital.

Maybe I'm pessimistic and one of these will turn into the next standard form factor, but I don't like gambling and have the feeling that the real innovation will come out of the open source and maker communities.


i want to get rid of that so called trending notes and i want a normal scroll bar - its impossible to scroll with this one on a pc


Your post is getting a lot of likes and reposts.
Added to the https://nostraco.in/hot feed


For those that don't wish to think anymore or never did in the first place


Another Harvard drop-out. Is that the key to success?


For a moment I thought I was reading Orwell. Though there's something appealing in the whole personal trainer/therapist idea (and I wouldn't discard the whole thing), it also reminds me of the telescreen in your face  24/7 from 1984.
https://image.nostr.build/efae1925d8766b586dfcca4f546e3747bcda7b27fd171b2e6e6c5c859de01e99.jpg#m=image%2Fjpeg&dim=720x1440&blurhash=%5D17d%3A%3D%7Eq9Et8D%25-oofWYM%7CWA-%3DD%25ozkDRj-%3Bn%7DafayRj00kEs%3AMwaz4%3Ax%5D-%3BWAxt%3FFf5kDWAITngtRxvayM%7B.99Fjst8Rk&x=48a12e0feab5ee7f9a01c2bceb243d906a5f5003a6a3581adc65b616cfa0fe58


you are an exceptionally alert lady, now you point it out i remember and damn if i need to have a hard copy to read again

that book was pivotal in my educational career... the english teacher refused to let me, the only interested student in the class, to suggest we do a book report on it

said english teacher proceeded to fuck with me in ways that orwell would have predicted... and made me arc up like i was carrying 2000V of electricity

i didn't get my degree in CS because of this, pretty much, but it was worth it, i was already half qualified AT THAT POINT (and now i'm phd material)


YOU CANNOT WIN AGAINTS US, JACK WE RE THE ELITE OF THIS SYSTEM WE WILL COME FOR THE DESTROY


i think that programmability is the main thing and that takes a really radical and radically sane philosophy of computer systems design, i don't think AI really helps that much if you don't have good fundamentals in the system design

this is partly why i'm a @golang maxi - to me, it is like the kind of language that we should be using to make the entire system with, with clear and clean and well structured code a lot things get a lot simpler to do, like adding and changing features without blowing  everything else up


Cool


Sounds like a person with a mission. If this were a team of founders with great achievements, the masses would automatically put them on a pedestal.
I actually feel if it’s one guy with a mission, he is likely going to change the world. We need to celebrate such people!


I Agree very much. Knowing how bug prone most of our C/C++/Java bases are and adding AI on top of these Swiss cheese fundamentals is in my nightmares. This is why I would never give AI control access to my environment. LLMs are just too prone to instruction injection.

I love golang so much. The only reason I wouldn't call myself a golang maxi is because if I had to do embedded devices and things that must hook into C, i would reach for odin. But odin is essentially a go-like with lower level control of memory. Check it out if curious.

- https://odin-lang.org/


You’re cool


you have my attention


yeeah just to make a more nuanced comment

i think it was an error in Go's design to not make memory management more explicit

i tend to think of every var statement as an allocation instruction, but i don't think that's how it works actually

the trickiest thing is what to do when you produce values that you need to send outside of a function scope, and specifically when they are pointers, pointers make such a mess, but are neccessary, and at the same time extremely troublesome because it's nearly impossible to deduce until you actually execute it in every possible condition what actually happens to the memory

odin looks interesting but i'm too committed to Go tbh

it's just annoying the piss out of me new quirks in the modules system causing me a headache

i honestly wish there was an opt out for modules, i miss the old days, oh, there was problems with mangled gopaths if you worked on more than one unrelated project in the same gopath but tha could have been fixed so much more simply than modules, i still hate modules, took me a year to finally bend to them and i still regret it


Interesting. Probably would not be as effective for those whose dialogue is primarily internal.  Decent thing to do would be to inform third parties they’re being recorded. That could get old in a hurry.


kinda a lot muchness.


> pointers make such a mess, but are neccessary

ikr! I've shot myself with pointers and nil interfaces countless times. I try to write in a more pure functional style to be more aware of pointers and mutability but Go is really designed with interfaces in mind. So it's always easier to put state inside a struct and attach methods to it. Makes extending and refactoring very easy, but it also leads to more pointer receivers and heap allocs. Oh yeah the heap! Wish it was easier to deduce if a var will escape to the heap. Just read a good article about it, but it's never straight forward:

https://medium.com/eureka-engineering/understanding-allocations-in-go-stack-heap-memory-9a2631b5035d

The modules are very powerful if you're the downstream and upstream follows strict SemVer. I understand the need. The things I have headaches around is the change in behavior  from v0 to v1 and the change in import path with every major version bump.

But I have very few grumps about Go as a whole and continue to love using it day to day.

> odin looks interesting but i'm too committed to Go tbh

That's why it caught my eye. I've been programming in Go almost exclusively for almost a decade. Odin has taken a lot of the good ideas and lessons of Go and has some really nice ergonomics like the explicit context, or_return operator and really the best error handling I've seen so far. Even the package names they use are sometimes the same as in go's stdlib, so it's very easy for a gopher to read odin once you know the small syntax changes. Look at the hello world:

```odin
package main

import "core:fmt"

main :: proc() {
    fmt.println("Hellope!")
}
```


there was a nice language called V but to be honest it was a bit too close to Rust in it's base principles and syntax

i actually proposed an extension of the return syntax to allow it to be used  to directly break out in error condition but i forget reasons ian lance taylor said nein

i personally have very few problems with managing state and pointers anymore for the type of thing you describe - it just takes a little experience to know - most of the time you want to use a mutex, sometimes an atomic is better when it's just a single value

the issue of values escaping to the heap is a pretty pesty one, but only really matters in so much as if your code might suffer from the STW GC pause that happens when it has to be reorganised or allocated in the first place

for sure, if at all possible you try to accurately allocate slice capacities when you make new slices, and for those situations when you have a lot of memory being rewritten, new data stored and old data quickly forgotten about

yeah, this is the one annoying thing, you really have to do freelists sometimes and you really need to be careful about allocating memory for things in go, it's too easy to just forget and wind up blowing the stack and bloating the heap and having GC pauses and that's just not ok if you are trying to keep latency down

honestly, all things considered these are small inconveniences  compared to the memory hell of C or the OOP hell and compile time of C++ or the fucking smarmy attitude of "wustatshins" god i hate rust god i hate mozilla *breathe*


ah yeah, also, don't do pure functional... pass by value is ok for small things but it quickly blows out into a data copy problem and when the data contains pointers as well, then you have knotty puzzles for the GC to deal with as well

there's a reason why the two languages that are most notorious for blowing up your memory and dying due to OOM are C++ and Haskell, one is nasty OOP/template/variant syntax disambiguation, and haskell is constantly copying memory instead of allowing it to be mutated

neither approach are optimal for the hardware, you'll get better at knowing what approach to use with problems as you solve more problems :D don't worry! and do always keep reading those good texts about internals like memory management, that's really important shit, i probably need to do more of this kind of study but i did a lot over the years already


Just need to be careful we do not slide into full cyborgs.