[HN Gopher] Rabbit data breach: all r1 responses ever given can ...
       ___________________________________________________________________
        
       Rabbit data breach: all r1 responses ever given can be downloaded
        
       Author : dcchambers
       Score  : 72 points
       Date   : 2024-06-25 19:39 UTC (3 hours ago)
        
 (HTM) web link (rabbitu.de)
 (TXT) w3m dump (rabbitu.de)
        
       | yazzku wrote:
       | It was obvious from their "key note" in day one that this project
       | was a scam. The best thing that can happen to it at this point is
       | for it to be sued and shut down.
       | 
       | Anybody can string a couple of API calls together and write an
       | "app". That is not programming, and this project is a massive
       | undertaking for somebody of their skill. It should have never
       | gone to market to begin with, regulations should have stopped it
       | on its feet. The fact that they put more effort into their "key
       | note" than the actual product was already a red flag. It's like
       | some marketing guys got together and decided that they were going
       | to "take the world by storm with AI".
       | 
       | > we have internal confirmation that the rabbit team is aware of
       | this leaking of api keys and have chosen to ignore it. the api
       | keys continue to be valid as of writing.
       | 
       | Yeah.
        
         | llamaimperative wrote:
         | I mean that is definitely programming. The real distinction
         | you're looking for is the gap between programming and building
         | a production-ready product.
        
           | RIMR wrote:
           | I see no benefit in being pedantic. Obviously writing code
           | that performs simple API interactions is "programming". The
           | definition of programming is extremely broad.
           | 
           | It is rather clear to me that yazzku is saying that the
           | programming required to pull of what the R1 does falls well
           | below what Rabbit promised their customers. That this is such
           | a bullshit design that we can infer that the entire product
           | is a scam, because if they were serious it wouldn't be so
           | obvious that no work into actually making a useful product.
        
             | llamaimperative wrote:
             | You can build perfectly fine products without programming
             | anything at all. The problem isn't the
             | lack/scale/type/complexity of programming. The problem is
             | that the product is bad, and this is not a pedantic point
             | at all.
        
               | sandwitches wrote:
               | Please don't cheapen professional expertise in this way.
               | The product is bad, yes, but why? Because the programming
               | is bad, and the programmers are negligent.
        
               | llamaimperative wrote:
               | > Anybody can string a couple of API calls together and
               | write an "app". That is not programming
               | 
               | Yes it is. Simple as.
               | 
               | Please don't gatekeep something as casual as writing
               | code. Good lord.
        
         | sandwitches wrote:
         | I have bad news about most SaaS products.
        
       | devonsolomon wrote:
       | Move slower and break less things.
        
         | AdamJacobMuller wrote:
         | "move fast and break things" is an excuse for how this could
         | have happened (not that i'm defending it) but the last bits of
         | the article...
         | 
         | > the rabbit team is aware of this leaking of api keys and have
         | chosen to ignore it. the api keys continue to be valid as of
         | writing
         | 
         | That's just damning. Making the mistake is one thing, but,
         | having it pointed out to you and refusing to fix it is
         | unconscionable.
        
       | Havoc wrote:
       | > rabbit team is aware of this leaking of api keys and have
       | chosen to ignore it. the api keys continue to be valid as of
       | writing
       | 
       | Remind me how many billions was this supposedly worth?
        
         | Hamuko wrote:
         | Reportedly only some hundreds of millions. The makers of that
         | stupid AI Pin that you strap onto your chest and that catches
         | on fire was trying to sell itself to Hewlett-Packard for $1
         | billion.
        
       | drodgers wrote:
       | For a company who's product requires trusting them with login
       | tokens for all your favourite online services, this is
       | ludicrously short-sighted.
        
       | chad1n wrote:
       | Apparently after this was made public, they finally revoked the
       | key which obviously broke the R1s because they didn't update the
       | key on their server.
       | 
       | So this is the IT literacy of AI startups...
        
         | kotaKat wrote:
         | As jesse himself said on the Rabbit Discord:
         | 
         | "please don't under estimate the effort and IQ level of our eng
         | - its much more complicated than that."
         | 
         | I present no other commentary.
        
       | olliej wrote:
       | This provides useful context for the other story about revoking a
       | key breaking all their services.
       | 
       | I wish there was a mechanism on HN to link related (but
       | different) stories - beyond people in the comments I mean. I
       | think it would be especially useful over time (eg I could relate
       | these today because they're both on front page at the same time,
       | but if someone came across this in the future the relationship
       | may have been lost)
        
         | Retr0id wrote:
         | https://news.ycombinator.com/item?id=40793192
        
       ___________________________________________________________________
       (page generated 2024-06-25 23:01 UTC)