[Noisebridge-discuss] DEAD AIR

[ryan rawson]

It's a weird compliment. If twitter was unimportant then who cares. But because of its importance, people will demand more than platitudes. For now it's informal and leading edge thinkers like here on noisebridge. But as carrier iq found, things can go south very rapidly. Turns out they don't collect SMS and keystrokes but the damage is done. (nb: most carriers retain SMS content for at least 1-3 days)

Sent from your iPhone

On Dec 6, 2011, at 11:20 AM, John Adams <jna at retina.net> wrote:

> Honestly, our search just sucks.
> 
> There is lots of bitching (internally) about fixing search and we just haven't done it.  Messages drop off after a day or so because the search system is separate from the main tweet storage db. That's why you see posts disappear after 24 hours or so. 
> 
> Instead of:
> 
> https://twitter.com/#!/search/realtime/from%3Arabite 
> 
> Go to 
> 
> https://twitter.com/rabite
> 
> ... and all the messages are there.
> 
> Big brother is not here and not censoring. Chill.
> 
> -j
> 
> 
> On Mon, Dec 5, 2011 at 5:31 PM, John Morgan <dr1ce315 at gmail.com> wrote:
> I certainly can't say for sure that twitter was censoring, and it certainly could have been a bug.  One of the biggest things i've personally noticed with twitter is I would see a bunch of retweets come through, and then they would disappear the next day.  Only a few cases of tweets not coming out at all.  The problem is not with twitter or their hard working staff; it's with big brother that is going to come in and do whatever they feel like with the cloud, including censoring twitter.  The necessity for decentralized text messages is crucial if not today, in the near future..
> 
> 
> Good thing I live in a Faraday cage, that tin foil hat sure gets annoying...
> 
> On Sun, Dec 4, 2011 at 11:10 PM, Danny O'Brien <danny at spesh.com> wrote:
> On Sun, Dec 4, 2011 at 9:10 PM, John Adams <jna at retina.net> wrote:
> On Sun, Dec 4, 2011 at 1:26 AM, Ryan Rawson <ryanobjc at gmail.com> wrote:
> 
> However, this situation may be actually the case. The patriot act
> gives the US Government wide ranging powers. One of the major powers
> is the NSL and accompanying gag order.  Why a subpoena was used in the
> case you are describing is not clear, but almost certainly NSLs have
> been delivered to twitter and they have executed on it.  What else is
> in the bag of tricks?  Remember, the NSL gag orders threads are
> personal.  That means if the sysadmin who is requested to pull data
> blabs, then the federal government will put that person in jail.  Your
> legal department wont be able to do anything about it.
> 
> I understand how NSLs work. I (may have) had to respond to some of them (at some company) but I wouldn't be able to tell you if I (did or did not.)
> 
> Warrants are used for account contacts and Subpoenas for information to identify user accounts. The PATRIOT act allows for these requests but to order a company to censor? 
> 
> I have never seen one with that sort of a request before, ever. 
> 
> Yeah, I'd be very interested to hear about that. NSLs are used to obtain data, not block stuff. 
> 
> Still, the fact that https://twitter.com/#!/search/realtime/from%3Arabite returns nothing *is* kind of weird -- an indicator of a bug, if nothing else. 
> 
> I don't pretend to understand how the current terms of Weev's bail might intersect with all of this.
> 
> d.
> 
>  
> 
> -j
> 
> 
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
> 
> 
> 
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
> 
> 
> 
> _______________________________________________
> Noisebridge-discuss mailing list
> Noisebridge-discuss at lists.noisebridge.net
> https://www.noisebridge.net/mailman/listinfo/noisebridge-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.noisebridge.net/pipermail/noisebridge-discuss/attachments/20111206/f18abf98/attachment-0003.html>