Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!



A Coffeeshop's Weekends Without Wi-Fi

c_monster Re:easier solution... (513 comments)

An easier solution would be to just have hourly changing codes

How exactly is that easier than turning off the WiFi router on weekends? Who's going to update the codes? Who's going to print up the six zillion little slips of paper with "this hour's code"? Who's going to set up the router to kick off 'expired' machines without interrupting legitimate users?

Besides, according to TFA "The staff doesn't want to have to enforce the cafe's unspoken policy of making a purchase to use the space (and the Wi-Fi)..."

more than 9 years ago


c_monster hasn't submitted any stories.


c_monster has no journal entries.

Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>