OK a bit of self-promotion but this is what we help people all the time. You can either run a hotspot with external antennas or put in a booster. https://www.waveform.com
Happy to help if you want to email me.
28,688 karma · joined April 7, 2011
CEO at Waveform.com, Technology Fellow at EFF, co-founder/advisor OpenSignal.com, Repair.org board member
sina dot khanifar at gmail dot com.
http://twitter.com/sinak
Happy to help if you want to email me.
I couldn't recommend doing so more. Text is so much easier, even if you have voicemail transcription.
A few questions:
- Do you support MMS (photos and videos)?
- Do you support creating auto-reminders to follow up with specific customers?
- Can you set up an autoresponder that responds when users sends a specific key message? Eg if the customer sends "Start" then can you autoreply with a canned message?
From the article:
> From an early age, Asimov was drawn to the communal aspects of fan culture, but he made it more difficult for women to experience that sense of community. Women have long occupied an ambiguous place in science fiction, where they have been alternately welcomed, dismissed, and harassed. Asimov took advantage of what he called the rising percentage of “shrill young girls” at conventions in the 1960s, and his unique position at such events—he was invariably the center of attention—made his example especially insidious. His admirers looked to him as a model of how to behave, and fandom was complicit for years in his serial misconduct in ways that have never been fully acknowledged.
> Asimov has always meant a lot to me, and the best qualities of his work—his rationality, curiosity, and imagination—changed thousands of lives for the better. Yet the visible edifice of his hundreds of books needs to be balanced against the unseen wall that he built around the heart of science fiction. His actions had a negative impact on an untold number of women [...]
10 mw/cm2 for critical tissue doesn't happen. The power levels by the time the signal reaches important body tissue are much, much lower than that.
From the Wilson Sonsini Press Release:
> In a big win for critics of Section 1201, the court held that Green and Huang satisfy the injury-in-fact requirement for Article III standing, meaning they have standing to challenge the statute on First Amendment grounds moving forward. In another big win, the court affirmed that "code is speech"—and thus protected by the First Amendment—and that using code to circumvent technical protection measures "arguably implicates" First Amendment rights as well. In so doing, the court dismissed the government's assertion that Green and Huang's desired acts of circumvention are not protected speech. Finally, although the court dismissed Green and Huang's facial challenges to the DMCA as an unlawful prior restraint, it concluded their "as-applied" First Amendment challenges can move forward, denying the government's motion to dismiss that claim.
https://www.wsgr.com/wsgr/Display.aspx?SectionName=publicati...
I'm guessing they haven't bought licenses from the FCC, so my bet is that they're using the 900 MHz ISM band.
There's only 26 MHz of spectrum in that band, which isn't much, particularly for a mesh setup that won't be particularly spectrally efficient.
Even with a high 30 dB signal to noise ratio, the Shannon channel capacity in a 26 MHz band is 50 Mbps. MIMO helps a bit, but even in ideal real-world conditions you'll likely have at most 50 Mbps to share between all the users connected to a node. Spread that across a few users/mesh hops, throw in some packet retransmissions and noise, and it's not nearly enough to compete with LTE networks at any meaningful user density.
Incentivizing users to create as many nodes as possible is a good idea, as that allows lower power transmissions and better frequency reuse. It's still a huge struggle to get anywhere near commercial wireless speeds, particularly in areas where there are fewer nodes and a higher density of users.
> Evidence indicates that these workers experienced no significant decline in their likelihood of being employed and a modest reduction in their hours worked over the six quarters following the first and second wage increases.
* Legal: Taking on precedent-setting cases (e.g. establishing code as a form of speech, overturning Betamax Doctrine, challenging censorship laws). Full list is here: https://www.eff.org/victories
* Technology: Helping launch projects like LetsEncrypt (now its own org), Privacy Badger, Certbot, Panopticlick, Democracy.io, HTTPS Everywhere.
* Advocacy/activism: Pushing state & federal legislatures in the US and around the world to pass laws that protect user's rights, and not to pass laws that would harm them. Also to push regulatory bodies (e.g. FCC) similarly.
(I'm a Tech Fellow at EFF but not speaking for the org in any capacity)
O'Keefe is a conservative activist has a storied history of "severely editing" videos to mislead: https://en.wikipedia.org/wiki/James_O'Keefe
Just click "New Filing" or "New Express" depending on what kind of comment you want to leave.
We just submitted comments here in case you need ideas: https://ecfsapi.fcc.gov/file/DOC-56ec3d08ba000000-A.pdf
Also of note, YC, TechStars and Engine Advocacy released their "Startups for Net Neutrality" letter to Pai this morning: http://www.engine.is/startups-for-net-neutrality
[1] http://mason.gmu.edu/~rhanson/futarchy.html
[2] https://blog.ethereum.org/2014/08/21/introduction-futarchy/
https://imageoptim.com/mozjpeg
It has sensible defaults and is super-easy to use.
The EFF fights for an Internet free of surveillance and censorship.
EFF is looking for a Software Engineer with:
* Strong programming skills with one of our server-side languages: Python, PHP, JavaScript, or Ruby.
* Familiarity with HTML, CSS, and client-side JavaScript.
* A love of free and open-source software. Experience with a CMS like WordPress or Drupal is a plus.
This is a full-time position based in EFF's San Francisco office. Because our team benefits from close communication with the attorneys, technologists, and activists at EFF, working remotely is not an option.
EFF is an amazing place to work. You'll join a team of developers and designers to lead high-impact campaigns that protect civil liberties online.
Apply here: https://www.eff.org/opportunities/jobs/software-engineer
(Dear recruiters/outsourcing agencies: Please don't contact us as we're not interested at this time.)
(Obvious plug: If you happen to have a few desks or a small office spare, please email me.)
But rather than this being a problem with federation itself, perhaps it's an issue with existing implementations. Things like XMPP give protocols so much flexibility with extensions that upgrades become costly and difficult to implement. Others, like HTTP, SMTP, and IRC are updated very slowly.
It seems like it should be possible to implement federated protocols that are focussed on fast iterations. For example, a protocol could specify that each version has a fixed lifetime of just one month, and require all clients and servers update to the new release in the last week of that month. Such a fast-paced protocol would have some disadvantages over slower ones (e.g. longevity), but it seems better suited to the pace of modern software and service development.
But I've never developed a protocol, let alone a federated one. I'd love to hear some potential problems or examples of failed protocols that have taken this kind of approach.