Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Engineering Library- R857.O6B54 2016

Location: Sciences Library Library- RC78.7.D53B56 2012

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Action Packed Media, a boutique media services firm based in Modiin, is looking to hire customer service reps for telecommuting shift work on a freelance basis.

Our firm has been subcontracted by an international brand to turn around customer service email query responses via a web-based dashboard.

Applicants must be able to work from home using their own high-speed internet connections and must be able to filter user queries according to category and according to urgency. Most of the queries can be responded to via provided templates, while others necessitate more attention.

The exact shift structure is still in the process of being worked out, but it looks like shifts will consist of three to four hours of activity in the evening hours - we'll know more in the coming days. Because the exact shift structure is still somewhat unknown, applicants must be willing to work late at night. Basic web and computer skills are a must, and experience with web-based query management systems is a plus.

This job pays 30 NIS per hour plus a benefits package which includes pension and havra'ah. Alternatively, freelancers who have tikim with mas hachnasa and can issue invoices will be paid according to 35 NIS plus VAT per hour.

Please submit resumes to moderationjob@gmail.com with the subject line "feb11 opening."

Dynamic and fun start up in Sharon area looking for Customer Service Representatives.

This is a daytime job (09.00-18.00), salary NIS 7000.

MOTHER TONGUE ENGLISH

The job involves:

• Responding to customer issues relating to the product.
• Researching, analyzing and trouble-shooting customer issues.
• Providing feedback from customer communications to Marketing, Sales and R&D.

Department Secretary for international company in Tel Aviv

Job Description

• Daily administration duties
• Managing diaries
• Coordinating meetings
• Setting up conference calls
• Maintaining databases
• Handling travel arrangements
• Arranging conferences

• Experience from similar role.
• Fluent Hebrew and English

Responsibilities

• Provide client support and technical issue resolution via E-Mail, phone and other electronic medium.
• Moderating the company's customer support forum
• Updating self-help documents so customers/employees can try to fix problems themselves
• Logging and keeping records of customer/employee queries
• Identify and correct or advise, on operational issues in client website or company systems.
• Working with customers/partners to identify service problems and advising on the solution
• Analyzing service information to spot common trends and underlying problems

• 3 years as a technical customer support representative/engineer
• Ability to build a web 2.0 support practice from the ground up (self help capabilities, forums etc.)
• Experience with website hosting/security/performance and DNS management
• Excellent communication (oral and written), interpersonal, organizational, and presentation skills.
• Fluent spoken and written English
• Self motivated, detail-oriented and organized.

• Experience working at a SaaS company preferably a B2C or B2B (SMB – small customers)
• Provided "Web2.0 technical support" (over mail, chat, phone with automated and advanced customer support tools)
• The ability to write very good documentation in English(FAQ, How to's, technical notes)
• Experience with a 24*7 lean support operations (using external answering services or off-shored resources)

Position Purpose: Responsible for performing all the administrative activities for members of Executive Management.

Position Responsibilities:

-Responsible for performing all the administrative activities for members of management.
-Attend staff meetings and maintain minutes.
-Arranges conference calls as required.
-Manages the senior manager's calendar and independently schedules appointments.
-Prepares expense reports and purchase requisitions as required.
-Arranges travel plans and itineraries, compiles documents for travel-related meetings. Maintains weekly and monthly Travel Dashboard for Executive review.
-Conducts moderately complex research as required and compiles and produces statistical reports.
-Proposal writing
-Some bookkeeping

Knowledge/Skills/Experience: Prior experience working in an administrative capacity is required, preferably high tech. Strong experience in Microsoft Office, Excel, PowerPoint, CRM and search engines is required.

Send cover letter and CV to mayer@RankAbove.com

"It's too early for us to be realistic," David Weinberger says in closing is2k7. Where reality is binary, forcing us to categorize each piece of information, digital networked storage lets us add metadata along multiple axes. We shouldn't rush to cram it all back into real boxes. Instead, we can build new structures, sometimes adding metadata to digital contents, sometimes using the "contents" as metadata with regard to another question we're asking.

That lack of hierarchy sounds threatening to some, perhaps including universities, who are accustomed to being the authorities. Online, we find new sources of authority, though we also have to learn and re-learn when not to trust both online and offline sources. The university's challenge, and all of ours, is to engage with these new sources of information and meta-information. The answer to "too much information" is likely not to shut off the spigot but to hand out better filters and filter-building toolkits (aggregators, search engines, databases, social network tools, and mashups).

I'm headed to Everything Is Miscellaneous for more.

My OII colleague Tobias Escher reports on a German decision on website operator liability for user-posted content. A professor unhappy with his reviews on Meinprof.de, such as comments calling him a "psychopath," sued. The site had removed the comments on his complaint, but he nonetheless demanded that the site pay a fine and be enjoined from allowing similar comments to be re-posted. The appeals court sensibly rejected that injunction. According to Tobias:

The court has decided that a general “cease and desist” for unacceptable comments is against the law. As a professor one has to face public criticism that cannot be prohibited ex ante.
...
In general this is a positive outcome for web sites that leverage the wisdom of the crowds as it offers some protection for the often not-for-profit operators of these sites. However, this does not justify defamatory comments on those sites and the court has emphasized the operators’ duty to remove those entries as soon as they are recognized. Last but not least, the subject under public scrutiny does matters as professors might well be made to face personal criticism in their role as public figures while teachers and nurses might have to be treated differently.

German law lacks a CDA Section 230, which immunizes U.S. service providers from defamation liability for user-contributed comments. So RateMyTeachers.com can ignore claims of defamation, leaving U.S. teachers to fight back with words, leaving their own comments or questioning the reliability of the site.

German sites, by contrast, can be held liable for their users' false assertions. If such liability were automatic, triggered immediately upon the posting of a defamatory comment, sites that permitted users to post content might as well paint lawsuit targets on their homepages: anyone could claim to have been defamed there; anyone unhappy with postings could get a heckler's veto against not just individual posts but the site itself. Sensibly, then, the MeinProf.de court limits the potentially unbounded liability in a manner similar to the U.S. caution against prior restraints of speech. The site can't be held liable until it has been given an opportunity to defend or remove the post; those who want to make libel claims against hosts should start by giving the host notice.

My U.S.-centric view is still that posters and their subjects should battle over online defamation between themselves, leaving their online hosts out of the picture. As we all depend on intermediaries to speak online, our speech gets less free with each new burden and risk-sensitivity we put on the intermediaries. Those who feel victimized have access to the same speech technologies to respond -- putting them on a more level playing field than arises when one calls in the law and an intermediary is chilled. In the German context and legal tradition, however, this decision seems to get close.

After blogging about ICANN's new gTLD policy or lack thereof, I've had several people ask me why I care so much about ICANN and new top-level domains. Domain names barely matter in a world of search and hyperlinks, I'm told, and new domains would amount to little more than a cash transfer to new registries from those trying to protect their names and brands. While I agree that type-in site-location is less and less relevant, and we haven't yet seen much end-user focused innovation in the use of domain names, I'm not ready to throw in the towel. I think ICANN is still in a position to do affirmative harm to Internet innovation.

You see, I don't concede that we know all the things the Internet will be used for, or all the things that could be done on top of and through its domain name system. I certainly don't claim that I do, and I don't believe that the intelligence gathered in ICANN would make that claim either.

Yet that's what it's doing by bureaucratizing the addition of new domain names: Asserting that no further experiments are possible; that the "show me the code" mode that built the Internet can no longer build enhancements to it. ICANN is unnecessarily ossifying the Internet's DNS at version 1.0, setting in stone a cumbersome model of registries and registrars, a pay-per-database-listing, semantic attachments to character strings, and limited competition for the lot. This structure is fixed in place by the GNSO constituency listing: Those who have interests in the existing setup are unlikely to welcome a new set of competitors bearing disruptions to their established business models. The "PDP" in the headline, ICANN's over-complex "Policy Development Process" (not the early DEC computer), gives too easy a holdout veto.

Meanwhile, we lose the chance to see what else could be done: whether it's making domain names so abundant that every blogger could have a meaningful set on a business card and every school child one for each different face of youthful experimentation, using the DNS hierarchy to store simple data or different kinds of pointers, spawning new services with new naming conventions, or something else entirely.

I don't know if any of these individually will "add value." Historically, however, we leave that question to the market where there's someone willing to give it a shot. Amazingly, after years of delay, there are still plenty of people waiting in ICANN queues to give new gTLDs a try. The collective value in letting them experiment and new services develop is indisputably greater than that constrained by the top-down imaginings of the few on the ICANN board and councils, as by their inability to pronounce .iii.

"How do you get an answer from the web?" the joke goes: "Put your guess into Wikipedia, then wait for the edits." While Wikipedians might prefer you at least source your guess, the joke isn't far from the mark. The lesson of Web 2.0 has been one of user-driven innovation, of launching services in beta and improving them by public experimentation. When your users know more than you or the regulators, the best you can do is often to give them a platform and support their efforts. Plan for the first try to break, and be ready to learn from the experience.

To trust the market, ICANN must be willing to let new TLDs fail. Instead of insisting that every new business have a 100-year plan, we should prepare the businesses and their stakeholders for contingency. Ensuring the "stable and secure operation of the Internet's unique identifier systems" should mean developing predictable responses to failure, not demanding impracticable guarantees of perpetual success. Escrow, clear consumer information, streamlined processes, and flexible responses to the expected unanticipated, can all protect the end-users better than the dubious foresight of ICANN's central regulators. These same regulators, bear in mind, didn't foresee that a five-day add-grace period would swell the ranks of domains with "tasters" gaming the loophole with ad-based parking pages.

At ten years old, we don't think of our mistakes as precedent, but as experience. Kids learn by doing; the ten-year-old ICANN needs to do the same. Instead of believing it can stabilize the Internet against change, ICANN needs to streamline for unpredictability. Expect the unexpected and be able to act quickly in response. Prepare to get some things wrong, at first, and so be ready to acknowledge mistakes and change course.

I anticipate the counter-argument here that I'm focused on the wrong level, that stasis in the core DNS enhances innovative development on top, but I don't think I'm suggesting anything that would destabilize established resources. Verisign is contractually bound to keep .com open for registrations and resolving as it has in the past, even if .foo comes along with a different model. But until Verisign has real competition for .com, stability on its terms thwarts rather than fosters development. I think we can still accommodate change on both levels.

The Internet is too young to be turned into a utility, settled against further innovation. Even for mature layers, ICANN doesn't have the regulatory competence to protect the end-user in the absence of market competition, while preventing change locks out potential competitive models. Instead, we should focus on protecting principles such as interoperability that have already proved their worth, to enhance user-focused innovation at all levels. A thin ICANN should merely coordinate, not regulate.

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Main Library- HV6250.4.W65N78 2011

Location: Main Media Collection - Video record 42363 DVD

Location: Main Media Collection - Video record 42350 DVD

Location: Main Media Collection - Video record 42310 DVD

Location: Main Media Collection - Video record 42430 DVD

Location: Main Media Collection - Video record 42314 DVD

Location: Main Media Collection - Video record 42304 DVD

Location: Main Media Collection - Video record 42294 DVD

Location: Main Media Collection - Video record 42303 DVD

Location: Main Media Collection - Video record 42423 DVD

Location: Main Media Collection - Video record 42410 DVD

Location: Main Media Collection - Video record 42439 DVD

Location: Government Information - J 16.1:929-30/SUPP.

Location: Main Library- HV5840.M3B57 2004

Location: Law Library- KF301.S8653 2015

Location: Main Library- HA19.B447 2016

Location: Electronic Resource- 

Location: Government Information Storage- HV6793.I8S7 198417-P712SA 2:C929 1976-82

Location: Electronic Resource- Am 1901 U.S. Dept Lab 78320.O

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource-