Announcing: Slashdot Deals - Explore geek apps, games, gadgets and more. (what is this?)

Thank you!

We are sorry to see you leave - Beta is different and we value the time you took to try it out. Before you decide to go, please take a look at some value-adds for Beta and learn more about it. Thank you for reading Slashdot, and for making the site better!



Hack AT&T Voicemail With Android

macguys Re:passwords.. (242 comments)

He's got a point. Why can't voice mail run over some data connection authenticated by the phone's unique ID or something similar? They certainly do billing that way. It is 2010, and voice mail still works by having the phone call out to a magic number- how antiquated!

Doesn't that defeat the whole "GSM; move your SIM from one phone to another" thing?

more than 4 years ago

Web Radio Negotiations Carry Poison Pill

macguys just say "no thank you" to the riaa etc. (243 comments)

Visit garageband.com, cdbaby, myspace, podsafe music network, etc. to find some great music that is being distributed by songwriters who are not part of the commercial music world. It's time to say "no thank you" and move on.

more than 7 years ago



How do you include open source options in a software RFP?

macguys macguys writes  |  more than 2 years ago

macguys (472025) writes "I work for a government agency that is about to put out an RFP for software to support the business of the agency. There are several commercial products which would probably meet the needs of the agency. There are also several open source options. I'd like to consider open source, but don't have a clue on how I can include them. While the commercial vendors have staff to respond to an RFP, for open source software, there is no one to package a response. Ideas?"

Mobile zoo for Q/A?

macguys macguys writes  |  more than 4 years ago

macguys (472025) writes "I work for an organization that supplies automation to a large group of libraries. While we have a robust Q/A process for our sites, it's all done on desktop machines using Firefox, IE, Safari, Chrome, etc. As more and more of our end users are accessing our assets via mobile devices, it seems to me that we should have a formal process for doing Q/A on those devices. I'm working on a proposal that includes buying (and regularly refreshing) a "petting zoo" of mobile devices for developer testing and q/a of our web assets. While my management agrees that this is a good idea, there is concern that we will end up having lots of cell phone contracts for devices that are only used a few times a year.

I'd appreciate knowing how other organizations handle mobile device q/a. How do you decide which devices to test on, and how do you handle having to buy a 1 or 2 year service contract for each device purchased for testing?"


macguys has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?