| ▲ | apparent 3 hours ago | |||||||||||||||||||||||||||||||
I think the key question is whether the automated actions resulted in information being retained by Pebble. If it was just going through a motion and pulling some data (or pulling all data but only keeping some of it), then that would be consistent with Eric's story and not be the kind of scraping that Rebble is worried about. They're worried about the content being archived somewhere else, and they seem to think that happened. But did it? | ||||||||||||||||||||||||||||||||
| ▲ | fphhotchips 3 hours ago | parent | next [-] | |||||||||||||||||||||||||||||||
One thing I'm confused about in this whole thing is what makes Rebble think they have a right to the data in the first place? They scraped it! "We don't like you scraping the data we scraped" doesn't hold water for me, whether Eric retained it or not. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||
| ▲ | AlotOfReading 3 hours ago | parent | prev | next [-] | |||||||||||||||||||||||||||||||
It might not be the kind of scraping rebble is worried about, but a bunch of requests to extract data into another form is very plainly scraping and the contract doesn't differentiate based on intent or whether the process is entirely automated. The entire contract is similarly loose and informal, which contributes to these sorts of misunderstandings. The most reasonable solution would have been for Eric to send an email first, but few contract disputes start with everyone doing the most reasonable thing. | ||||||||||||||||||||||||||||||||
| ▲ | 3 hours ago | parent | prev [-] | |||||||||||||||||||||||||||||||
| [deleted] | ||||||||||||||||||||||||||||||||