text:
Network Working Group M. Thomas Request for Comments: 5016 Cisco Systems Category: Informational October 2007 Requirements for a DomainKeys Identified Mail (DKIM) Signing Practices Protocol Status of This Memo This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract DomainKeys Identified Mail (DKIM) provides a cryptographic mechanism for domains to assert responsibility for the messages they handle. A related mechanism will allow an administrator to publish various statements about their DKIM signing practices. This document defines requirements for this mechanism, distinguishing between those that must be satisfied (MUST), and those that are highly desirable (SHOULD). Thomas Informational [Page 1]
RFC 5016 DKIM-SSP-REQ October 2007 Table of Contents 1. Introduction ....................................................2 2. Definitions and Requirements Language ...........................3 3. SSP Problem Scenarios ...........................................4 3.1. Problem Scenario 1: Is All Mail Signed with DKIM? ..........4 3.2. Problem Scenario 2: Illegitimate Domain Name Use ...........5 4. SSP Deployment Considerations ...................................6 4.1. Deployment Consideration 1: Outsourced Signing .............6 4.2. Deployment Consideration 2: Subdomain Coverage .............6 4.3. Deployment Consideration 3: Resent Original Mail ...........7 4.4. Deployment Consideration 4: Incremental Deployment of Signing .................................................7 4.5. Deployment Consideration 5: Performance and Caching ........8 4.6. Deployment Consideration 6: Human Legibility of Practices ..8 4.7. Deployment Consideration 7: Extensibility ..................8 4.8. Deployment Consideration 8: Security .......................8 5. Requirements ....................................................9 5.1. Discovery Requirements .....................................9 5.2. SSP Transport Requirements ................................10 5.3. Practice and Expectation Requirements .....................10 5.4. Extensibility and Forward Compatibility Requirements ......13 6. Requirements for SSP Security ..................................13 7. Security Considerations ........................................13 8. Acknowledgments ................................................13 9. References .....................................................14 9.1. Normative References ......................................14 1. Introduction DomainKeys Identified Mail [RFC4871] defines a message level signing and verification mechanism for email. While a DKIM signed message speaks for itself, there is ambiguity if a message doesn't have a valid first party signature (i.e., on behalf of the [RFC2822].From address): is this to be expected or not? For email, this is an especially difficult problem since there is no expectation of a priori knowledge of a sending domain's practices. This ambiguity can be used to mount a bid down attack that is inherent with systems like email that allow optional authentication: if a receiver doesn't know otherwise, it should not assume that the lack of a valid signature is exceptional without other information. Thus, an attacker can take advantage of the ambiguity and simply not sign messages. If a protocol could be developed for a domain to publish its DKIM signing practices, a message verifier could take that into account when it receives an unsigned piece of email. Thomas Informational [Page 2]
RFC 5016 DKIM-SSP-REQ October 2007 This document defines the requirements for a mechanism that permits the publication of Sender Signing Practices (SSP). The document is organized into two main sections: first, a Problem and Deployment Scenario section that describes the problems that SSP is intended to address as well as the deployment issues surrounding the base problems, and the second section is the Requirements that arise because of those scenarios. 2. Definitions and Requirements Language o Domain Holder: the entity that controls the contents of the DNS subtree starting at the domain, either directly or by delegation via NS records it controls. o First Party Address: for DKIM, a first party address is defined to be the [RFC2822].From address in the message header; a first party address is also known as an Author address. o First Party Signature: a first party signature is a valid signature where the signing identity (the d= tag or the more specific identity i= tag) matches the first party address. "Matches" in this context is defined in [RFC4871]. o Third Party Signature: a third party signature is a valid signature that does not qualify as a first party signature. Note that a DKIM third party signature is not required to correspond to a header field address such as the contents of Sender or List-Id, etc. o Practice: a statement according to the [RFC2822].From domain holder of externally verifiable behavior in the email messages it sends. o Expectation: an expectation combines with a practice to convey what the domain holder considers the likely survivability of the practice for a receiver, in particular receivers that may be more than one SMTP hop away. o DKIM Signing Complete: a practice where the domain holder asserts that all legitimate mail will be sent with a valid first party signature. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119]. Thomas Informational [Page 3]
RFC 5016 DKIM-SSP-REQ October 2007 3. SSP Problem Scenarios The email world is a diverse place with many deployment considerations. This section outlines expected usage scenarios where DKIM signing/verifying will take place, and how a new protocol might help to clarify the relevance of DKIM-signed mail. 3.1. Problem Scenario 1: Is All Mail Signed with DKIM? After auditing their outgoing mail and deploying DKIM signing for all of their legitimate outgoing mail, a domain could be said to be DKIM signing complete. That is, the domain has, to the best of its ability, ensured that all legitimate mail purporting to have come from that domain contains a valid DKIM signature. A receiver in the general case doesn't know what the practices are for a given domain. Thus, the receiver is at a disadvantage in not knowing whether or not it should expect all mail to be signed from a given domain. This knowledge gap leads to a trivially exploitable bid-down attack where the attacker merely sends unsigned mail; since the receiver doesn't know the practices of the signing domain, it cannot treat the message any more harshly for lack of a valid signature. An information service that allows a receiver to query for the practices and expectations of the first party domain when no valid first party signature is found could be useful in closing this gap. A receiver could use this information to treat such questionable mail with varying degrees of prejudice. Note that, for the foreseeable future, unrestricted use patterns of mail (e.g., where users may be members of mailing lists, etc.) will likely suffer occasional, non-malicious signature failure in transit. While probably not a large percentage of total traffic, this kind of breakage may be a significant concern for those usage patterns. This scenario defines where the sender cannot set any expectation as to whether an individual message will arrive intact. Even without that expectation, a receiver may be able to take advantage of the knowledge that the domain's practice is to sign all mail and bias its filters against unsigned or damaged in transit mail. This information should not be expected to be used in a binary yes/no fashion, but instead as a data point among others in a filtering system. Thomas Informational [Page 4]
RFC 5016 DKIM-SSP-REQ October 2007 The following exchange illustrates problem scenario 1. 1. Mail with a [RFC2822].From domain Alice is sent to domain Bob with a missing or broken DKIM first party signature from Alice. 2. Domain Bob would like to know whether that is an expected state of affairs. 3. Domain Alice provides information that it signs all outgoing mail, but places no expectation on whether it will arrive with an intact first party signature. 4. Domain Bob could use this information to bias its filters to examine the message with some suspicion. 3.2. Problem Scenario 2: Illegitimate Domain Name Use A class of mail typified by transactional mail from high-value domains is currently the target of phishing attacks. In particular, many phishing scams forge the [RFC2822].From address in addition to spoofing much of the content to trick unsuspecting users into revealing sensitive information. Domain holders sending this mail would like the ability to give an enhanced guarantee that mail sent with their domain name should always arrive with the proof that the domain holder consented to its transmission. That is, the message should contain a valid first party signature as defined above. From a receiver's standpoint, knowing that a domain not only signs all of its mail, but places a very high value on the receipt of a valid first party signature from that domain is helpful. Hence, a receiver knows that the sending domain signs all its mail, and that the sending domain considers mail from this domain particularly sensitive in some sense, and is asking the receiver to be more suspicious than it otherwise might be of a broken or missing first- party signature. A receiver with the knowledge of the sender's expectations in hand might choose to process messages not conforming to the published practices in a special manner. Note that the ability to state an enhanced guarantee of a valid signature means that senders should expect mail that traverses modifying intermediaries (e.g., mailing lists, etc.) will likely be quarantined or deleted; thus, this scenario is more narrow than problem scenario 1. Informative Note: a receiving filter may choose to treat scenario 2 much more harshly than scenario 1; where scenario 1 looks odd, scenario 2 looks like something is very wrong. Thomas Informational [Page 5]
RFC 5016 DKIM-SSP-REQ October 2007 1. Mail with a [RFC2822].From domain Alice is sent to domain Bob with a missing or broken first party DKIM signature from domain Alice. 2. Domain Bob would like to know whether that is an expected state of affairs. 3. Domain Alice provides information that it signs all outgoing mail, and furthermore places an expectation that it should arrive with an intact first party signature, and that the receiver should be much more wary if it does not. 4. Domain Bob could use this information to bias its filters such that it examines the message with great suspicion. 4. SSP Deployment Considerations Given the problems enumerated above for which we'd like SSP to provide information to recipients, there are a number of scenarios that are not related to the problems that are to be solved, per se, but the actual mechanics of implementing/deploying the information service that SSP would provide. 4.1. Deployment Consideration 1: Outsourced Signing Many domains do not run their own mail infrastructure, or may outsource parts of it to third parties. It is desirable for a domain holder to have the ability to delegate to other entities the ability to sign for the domain holder. One obvious use scenario is a domain holder from a small domain that needs to have the ability for their outgoing ISP to sign all of their mail on behalf of the domain holder. Other use scenarios include outsourced bulk mail for marketing campaigns, as well as outsourcing various business functions, such as insurance benefits, etc. 4.2. Deployment Consideration 2: Subdomain Coverage An SSP client will perform lookups on incoming mail streams to provide the information as proposed in the problem scenarios. The domain part of the first address of the [RFC2822].From will form the basis to fetch the published information. A trivial attack to circumvent finding the published information can be mounted by simply using a subdomain of the parent domain that doesn't have published information. This attack is called the subdomain attack: that is, a domain wants to not only publish a policy for a given DNS label it controls, but it would also like to protect all subdomains of that label as well. If this characteristic is not met, an attacker would need only create a possibly fictitious subdomain that was not covered Thomas Informational [Page 6]
RFC 5016 DKIM-SSP-REQ October 2007 by the SSP's information service. Thus, it would be advantageous for SSP to not only cover a given domain, but all subdomains of that domain as well. 4.3. Deployment Consideration 3: Resent Original Mail Resent mail is a common occurrence in many scenarios in the email world of today. For example, domain Alice sends a DKIM-signed message with a published practice of signing all messages to domain Bob's mailing list. Bob, being a good net citizen, wants to be able to take his part of the responsibility of the message in question, so he DKIM signs the message, perhaps corresponding to the Sender address. Note that this scenario is completely orthogonal to whether Alice's signature survived Bob's mailing list: Bob merely wants to assert his part in the chain of accountability for the benefit of the ultimate receivers. It would be useful for this practice to be encouraged as it gives a more accurate view of who handled the message. It also has the side benefit that remailers that break DKIM first party signatures can be potentially assessed by the receiver based on the receiver's opinion of the signing domains that actually survived. 4.4. Deployment Consideration 4: Incremental Deployment of Signing As a practical matter, it may be difficult for a domain to roll out DKIM signing such that they can publish the DKIM Signing Complete practice given the complexities of the user population, the outsourced vendors sending on its behalf, etc. This leaves open an exploit that high-value mail, such as in Problem Scenario 2, must be classified to the least common denominator of the published practices. It would be desirable to allow a domain holder to publish a list of exceptions that would have a more restrictive practices statement. NB: this consideration has been deemed met by the mechanisms provided by the base DKIM signing mechanism; it is merely documented here as having been an issue. For example, bigbank.example.com might be ready to say that firstname.lastname@example.com is always signed, but the rest of the domain, say, is not. Another situation is that the practices of some address local parts in a given domain are not the same as practices of other local parts. Using the same example of email@example.com being a transactional kind of email that would like to publish very strong practices, mixed in with the rest of the user population local parts, which may go through mailing lists, etc., for which a less strong statement is appropriate. Thomas Informational [Page 7]
RFC 5016 DKIM-SSP-REQ October 2007 It should be said that DKIM, through the use of subdomains, can already support this kind of differentiation. That is, in order to publish a strong practice, one only has to segregate those cases into different subdomains. For example: accounts.bigbank.example.com would publish constrained practices, while corporateusers.bigbank.example.com might publish more permissive practices. 4.5. Deployment Consideration 5: Performance and Caching Email service provides an any-any mesh of potential connections: all that is required is the publication of an MX record and an SMTP listener to receive mail. Thus, the use of SSP is likely to fall into two main scenarios, the first of which are large, well-known domains that are in constant contact with one another. In this case, caching of records is essential for performance, including the caching of the non-existence of records (i.e., negative caching). The second main scenario is when a domain exchanges mail with a much smaller volume domain. This scenario can be both perfectly normal as with the case of vanity domains, and unfortunately, a vector for those sending mail for anti-social reasons. In this case, we'd like the message exchange burden to SSP querier to be low, since many of the lookups will not provide a useful answer. Likewise, it would be advantageous to have upstream caching here as well so that, say, a mailing list exploder on a small domain does not result in an explosion of queries back at the root and authoritative server for the small domain. 4.6. Deployment Consideration 6: Human Legibility of Practices While SSP records are likely to be primarily consumed by an automaton, for the foreseeable future they are also likely to be inspected by hand. It would be nice to have the practices stated in a fashion that is also intuitive to the human inspectors. 4.7. Deployment Consideration 7: Extensibility While this document pertains only to requirements surrounding DKIM signing practices, it would be beneficial for the protocol to be able to extend to other protocols. 4.8. Deployment Consideration 8: Security SSP must be able to withstand life in a hostile, open-Internet environment. These include DoS attacks, and especially DoS attacks that leverage themselves through amplification inherent in the protocol. In addition, while a useful protocol may be built without Thomas Informational [Page 8]
RFC 5016 DKIM-SSP-REQ October 2007 strong source authentication provided by the information service, a path to strong source authentication should be provided by the protocol, or underlying protocols. 5. Requirements This section defines the requirements for SSP. As with most requirements documents, these requirements define the MINIMUM requirements that a candidate protocol must provide. It should also be noted that SSP must fulfill all of the requirements. 5.1. Discovery Requirements Receivers need a means of obtaining information about a sender's DKIM practices. This requires a means of discovering where the information is and what it contains. 1. The author is the first-party sender of a message, as specified in the [RFC2822].From field. SSP's information is associated with the author's domain name, and is published subordinate to that domain name. 2. In order to limit the cost of its use, any query service supplying SSP's information MUST provide a definitive response within a small, deterministic number of message exchanges under normal operational conditions. Informative Note: this, for all intents and purposes is a prohibition on anything that might produce loops or result in extended delays and overhead; also though "deterministic" doesn't specify how many exchanges, the expectation is "few". Refs: Deployment Considerations, Sections 4.2 and 4.5. 3. SSP's publishing mechanism MUST be defined such that it does not lead to multiple resource records of the same type for different protocols residing at the same location. Informative note: an example is multiple resource record of the same type within a common DNS leaf. Hence, uniquely defined leaf names or uniquely defined resource record types will ensure unambiguous referencing. Refs: Deployment Consideration, Section 4.2. Thomas Informational [Page 9]
RFC 5016 DKIM-SSP-REQ October 2007 4. SSP retrieval SHOULD provide coverage for not only a given domain but all of its subdomains as well. It is recognized that there is some reasonable doubt about the feasibility of a widely accepted solution to this requirement. If the working group does not achieve rough consensus on a solution, it MUST document the relevant security considerations in the protocol specification. Refs: Deployment Considerations, Sections 4.2 and 4.5. 5.2. SSP Transport Requirements The publication and query mechanism will operate as an internet-based message exchange. There are multiple requirements for this lower- layer service: 1. The exchange SHOULD have existing widespread deployment of the transport layer, especially if riding on top of a true transport layer (e.g., TCP, UDP). Refs: Deployment Considerations, Sections 4.5 and 4.7. 2. The query/response in terms of latency time and the number of messages involved MUST be low (less than three message exchanges not counting retransmissions or other exceptional conditions). Refs: Deployment Consideration, Section 4.5. 3. If the infrastructure doesn't provide caching (a la DNS), the records retrieved MUST provide initiators the ability to maintain their own cache. The existing caching infrastructure is, however, highly desirable. Refs: Deployment Consideration, Section 4.5. 4. Multiple geographically and topologically diverse servers MUST be supported for high availability. Refs: Deployment Considerations, Sections 4.5 and 4.7. 5.3. Practice and Expectation Requirements As stated in the definitions section, a practice is a statement according to the [RFC2822].From domain holder of externally verifiable behavior in the email messages it sends. As an example, a practice might be defined such that all email messages will contain a DKIM signature corresponding to the [RFC2822].From address. Since there is a possibility of alteration between what a sender sends and a receiver examines, an expectation combines with a practice to Thomas Informational [Page 10]
RFC 5016 DKIM-SSP-REQ October 2007 convey what the [RFC2822].From domain considers the likely outcome of the survivability of the practice at a receiver. For example, a practice that a valid DKIM for the [RFC2822].From address is present when it is sent from the domain, and an expectation that it will remain present and valid for all receivers whether topologically adjacent or not. 1. SSP MUST be able to make practices and expectation assertions about the domain part of a [RFC2822].From address in the context of DKIM. SSP will not make assertions about other addresses for DKIM at this time. Refs: Problem Scenarios 1 and 2, Sections 3.1 and 3.2. 2. SSP MUST provide a concise linkage between the [RFC2822].From and the identity in the DKIM i= tag, or its default if it is missing in the signature. That is, SSP MUST precisely define the semantics of what qualifies as a first party signature. Refs: Problem Scenarios 1 and 2, Sections 3.1 and 3.2. 3. SSP MUST be able to publish a practice that the domain's signing behavior is "DKIM Signing Complete". That is, all messages were transmitted with a valid first party signature. Refs: Problem Scenario 1, Section 3.1. 4. SSP MUST be able to publish an expectation that a verifiable first party DKIM signature should be expected on receipt of a message. Refs: Problem Scenario 2, Section 3.2. 5. Practices and expectations MUST be presented in SSP syntax using as intuitive a descriptor as possible. For example, p=? would be better represented as p=unknown. Refs: Deployment Consideration, Section 4.6. 6. Because DKIM uses DNS to store selectors, there is always the ability for a domain holder to delegate all or parts of the _domainkey subdomain to an affiliated party of the domain holder's choosing. That is, the domain holder may set an NS record for _domainkey.example.com to delegate to an email provider who manages the entire namespace. There is also the ability for the domain holder to partition its namespace into subdomains to further constrain third parties. For example, a domain holder could delegate only _domainkey.benefits.example.com Thomas Informational [Page 11]
RFC 5016 DKIM-SSP-REQ October 2007 to a third party to constrain the third party to only be able to produce valid signatures in the benefits.example.com subdomain. Last, a domain holder can even use CNAME's to delegate individual leaf nodes. Given the above considerations, SSP need not invent a different means of allowing affiliated parties to sign on a domain's behalf at this time. Refs: Deployment Consideration, Section 4.4. 7. Practices and expectations MUST be presented as an information service from the signing domain to be consumed as an added factor to the receiver's local policy. In particular, a practice or expectation MUST NOT mandate any disposition stance on the receiver. Refs: Problem Scenarios 1 and 2, Sections 3.1 and 3.2. 8. There is no requirement that SSP publish practices of any/all third parties that MUST NOT sign on the domain holder's behalf. This should be considered out of scope. INFORMATIVE NOTE: this is essentially saying that the protocol doesn't have to concern itself with being a blacklist repository. Refs: Problem Scenarios 1 and 2, Sections 3.1 and 3.2. 9. SSP MUST NOT be required to be invoked if a valid first party signature is found. Refs: Deployment Consideration, Section 4.2. 10. SSP MUST NOT provide a mechanism that impugns the existence of non-first party signatures in a message. A corollary of this requirement is that the protocol MUST NOT link practices of first party signers with the practices of third party signers. INFORMATIVE NOTE: the main thrust of this requirement is that practices should only be published for that which the publisher has control, and should not meddle in what is ultimately the local policy of the receiver. Refs: Deployment Consideration, Section 4.3. Thomas Informational [Page 12]
RFC 5016 DKIM-SSP-REQ October 2007 5.4. Extensibility and Forward Compatibility Requirements 1. SSP MUST NOT extend to any protocol other than DKIM for email at this time. SSP SHOULD be extensible for protocols other than DKIM. Refs: Deployment Consideration, Section 4.7. 2. SSP MUST be able to add new practices and expectations within the existing discovery/transport/practices in a backward compatible fashion. Refs: Deployment Consideration, Section 4.7. 6. Requirements for SSP Security 1. SSP for a high-value domain is potentially a high-value DoS target, especially since the unavailability of SSP's record could make unsigned messages less suspicious. 2. SSP MUST NOT make highly leveraged amplification or make-work attacks possible. In particular, the work and message exchanges involved MUST be order of a constant. Refs: Deployment Consideration, Section 4.8. 3. SSP MUST have the ability for a domain holder to provide SSP's data such that a receiver can determine that it is authentically from the domain holder with a large degree of certainty. SSP may provide means that provide less certainty in trade off for ease of deployment. Refs: Deployment Consideration, Section 4.8. 7. Security Considerations This document defines requirements for a new protocol and the security related requirements are defined above. Since it is expected that the new protocol will use the DNS as a basis for the published SSP information, most if not all of the threats described in [RFC4686] will be applicable. 8. Acknowledgments Dave Crocker and Jim Fenton provided substantial review of this document. Thanks also to Vijay Gurbani and David Harrington for their helpful last call reviews. Thomas Informational [Page 13]
RFC 5016 DKIM-SSP-REQ October 2007 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2822] Resnick, P., Ed., "Internet Message Format", RFC 2822, April 2001. [RFC4686] Fenton, J., "Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)", RFC 4686, September 2006. [RFC4871] Allman, E., Callas, J., Delany, M., Libbey, M., Fenton, J., and M. Thomas, "DomainKeys Identified Mail (DKIM) Signatures", RFC 4871, May 2007. Author's Address Michael Thomas Cisco Systems 606 Sanchez St San Francisco, California 94114 USA Phone: +1-408-525-5386 Fax: +1-408-525-5386 EMail: firstname.lastname@example.com Thomas Informational [Page 14]
RFC 5016 DKIM-SSP-REQ October 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
Thomas Informational [Page 15]


text:
Andreas Tomalla (born 13 March 1963), better known by his stage name Talla 2XLC, is an electronic music producer and DJ whose work has spanned from industrial music to trance music.
In 1980, Talla 2XLC began DJing with the sounds of Kraftwerk, YMO, and Depeche Mode.
In 1984, Talla 2XLC started a small nightclub event called Technoclub, the first such club in Frankfurt to focus on electronic dance music. Initially, Technoclub was a Friday-night event held in the smaller, 350-person capacity room of the Dorian Gray discothèque inside the Frankfurt International Airport. In 1986, Technoclub moved to the 600-capacity Roxannes, where it remained through 1988. In 1989, it briefly moved to the 800- or 900-capacity Omen venue, then in September 1989 to the Dorian Gray's 2000-capacity main room, where it remained until the Dorian Gray closed in 2000. Technoclub may have been the world's first major "super-club".
In the mid-1980s, he was involved with a band called Moskwa TV. In 1987 he co-founded the group Robotiko Rejekto and was associated with the fledgling record label Techno Drome International, an imprint of ZYX Records. Robotiko Rejekto's track "Rejekto" was one of the label's first releases. In 1988, he started a new project called Bigod 20, which would go on to be one of Europe's most successful EBM acts of the early 1990s.

subset: commoncrawl


text:
633 35 55 33 firstname.lastname@example.com
No products
Check out
4,13 €
Condition: New product
-1 Item Items
Warning: Last items in stock!
Availability date:
The minimum purchase order quantity for the product is 1
Quanty: - +
Add to cart
Mascarilla Comic Black
Recipient :
Name of your friend * :
E-mail address of your friend * :
* Required fields
Send or Cancel
Tweet Share Google+ Pinterest
No customer reviews for the moment.
30 products in category:
has been added to compare.
has been removed from compare.


text:
Have fewer, more productive meetings
Is your calendar filled with too many meetings?
Give your team an online meeting tool that lets them work side-by-side in real time—or skip the meeting and catch up async
Less talking, more doing
Traditional video conferencing platforms are great for talking about work, but not so much for doing it. One-sided screen sharing makes it hard to keep people engaged and contributing.
Switchboard lets you get more work done during conference calls by making everything multiplayer, so you can work together on anything. Persistent rooms that save your work mean that, when it's time to gather as a team, you can simply head to the room knowing everything is there. No more meeting prep and no more digging through multiple tabs to find what you need. Or cancel the meeting and get everything you need async.
Key features:
- Live voice and video calls
- Meeting recording
- A huge canvas to visually organize apps, documents, and files in one view
- Dedicated, persistent project and meeting rooms that save your work
- Interactive, multiplayer browsers for web-based files, documents, and applications
- Built-in whiteboard for brainstorming, ideation, and creative collaboration
- In-room sticky notes, chat, polls, and surveys
- No integrations needed: All browser-based apps work in Switchboard
- Free accounts get Pro features for 14 days
Get more done during meetings–and in between them
Switchboard's always-open rooms let you work together as a team during and between meetings.
- Collaborate on support strategies
- Improve support ticket resolution
- Resolve customer issues in collaboration with other team members
Switchboard solves all these challenges with host-free rooms that save your work, so you can pick up where you left off next time. Or you can skip the meeting and review work async because it's all right there.
Your online meeting room is always ready
Get a huge canvas to visually organize all the apps, documents, and files you need in one view, so you can see who's doing what.
All browser-based apps work in Switchboard—with no fiddly integrations. Just create your meeting room, add what you need with a simple copy-paste, and get to work. No need to set the room up or share materials ever again: everything is right where you need it.
Make meetings actually collaborative
In Switchboard, every browser-based document, website, app, or file is multiplayer. This means everyone can contribute and work together in real time or async—and always in context. No more waiting your turn to share your screen, raise a hand, or find out what document your team's talking about.
Just open up your whiteboards, sticky notes, browsers, or apps and work on the same content side-by-side.
Continue working, even between meetings
Dedicated, persistent rooms save your work, so work doesn't stop once the meeting's over.
Check on dashboards, project tracking tools, or quickly grab a document in your dedicated meeting room, whenever you need to. Can't attend a meeting? Want a quick way to share a new finding? Record sessions and add them to your room to keep everyone up to date, no matter when they're online.
Cancel more meetings and collaborate async
Who says you should always default to having a meeting? Switchboard rooms let you quickly check in on a project without needing to schedule a status update. When everything is in one place, you have an always-on bird's-eye view of what's happening.
Move work forward faster, communicate in context, and make everything multiplayer.
Project rooms
Give your team permanent access to your dedicated, persistent project room with everything they need in one place. Work together side-by-side or async on anything—and never send a meeting link or invite again.
Connect with your team and stay on the same page throughout the week with collaborative 1:1 rooms. Make async check-ins between meetings a breeze, ensure projects are moving forward, and stay aligned without endless DMs.
All-hands meetings
Rally your company with immersive All Hands that reflect your company's collaborative culture. Create a dynamic place where people can add content—apps, files, documents, web browsers, videos—to easily share and learn from one another.
Share more than just your screen
Switchboard lets you share and work on anything in real time or async.
You can use the free version of Switchboard for:
- Free web conferencing and file sharing
- Creative brainstorming sessions
- Catching up async and canceling more meetings
- In-room messaging with team members via live chat, polls, and surveys
- Dedicated rooms for design reviews, 1:1s, and sprint planning, among others
- A single source of truth to manage workflows, projects, and cross-functional, hybrid, or remote work
- A unified workspace for highly collaborative small teams or small businesses
Switchboard is a collaboration platform that lets you host video meetings with its free video conferencing and audio conferencing functionality. However, Switchboard's free plan goes beyond traditional web conferencing tools like Skype, Zoom, and Google Meet: Rather than just talking about work, you can work side-by-side with in-person, hybrid, or remote team members during your video conference. With persistent rooms that save your work, Switchboard makes it easy to work async and cancel more meetings without sacrificing teamwork.
Yes, meeting participants can record team meetings using Switchboard's online meeting platform. This means anyone who missed the meeting can catch up async. What also makes Switchboard stand out from other video conferencing solutions is the ability for all team members to explore the meeting room and make contributions without changing other people's views. This way, you can check out recordings and work on browser-based apps, documents, and files without distracting anyone during your video chat.


text:
Spring break has come and gone in Austin, which means that we're recovering from another amazing SXSW Interactive festival. This year for me was a year of narrative story technologies and Community. For the last several years I've been going to SXSW with my wife, Irma, and this year she had her own session. That meant she spent a lot of time in the women in tech tracks, and we didn't see each other as much as usual. It'll be interesting to read her write up, when she gets to it.
Friday – Al, Tim, BBQ, Old Friends, & 3D Printed Clothes
Friday started off with Life in the OASIS: Emulating the 1980's in-Browser, a panel from Ready Player One author Ernest Cline (who has a new novel coming out, Armada, which I just pre-ordered), and Jason Scott, rogue librarian at the Internet Archive, talking about 80's video games an in-browser emulators. Unfortunately due to our bus driver getting lost (transportation was a recurring pain-point at SXSW this year) I wasn't able to make the session, but Jason, being a free-range archivist, put up the audio for all of us to enjoy.
While we didn't have time to get to the Life in the OASIS session, we had some time to burn till the session after, so Irma and I headed to Exhibit Hall 5, which is big and always has a lot of room to plop down and get your stuff sorted. SXSW is the kind of conference where you can be just looking for a place to get your bearings and end up listening to Al Gore talk about climate change, the Pope, and his newfound optimism, which is exactly what happened.
After Al we moved up front for a presentation from perennial SXSW personality Tim Ferriss, who had a 30 minute How To Rock SXSW in 4 Hours talk, followed by QA. It's always weird for me to see Tim at SXSW. I was on the first row of his first SXSW talk on the tiny Day Stage promoting the about to be released 4 Hour Work Week, way back in 2007. To say our paths diverged would be an interesting understatement. The main points of Tim's talk were: Don't be a jerk and treat everyone like they could make your career (because they probably can),. He had some hangover cure suggestions (eat avocados before you go party), and reminded all the introverts to take the time to breathe.
One anecdote he told on the treating everyone well point was from one of his early CESes. He spent most of his time in the bloggers lounge (a good place to meet people), and while everyone was trying to get the attention of Robert Scoble, he chatted up the lady checking people in. Eventually he made a comment about Robert, and she said, "Oh, you should totally talk to him. He's my husband, let me give you a ring back in San Francisco and we'll have lunch." So yea, you never know who people are. I was standing in line at a session later in the conference and started talking to the lady next to me, who turned out to be the head of innovation at Intuit.
After Tim it was time for lunch, and we ended up at Ironworks BBQ. They have a $16.45 3 meat sampler plate (beef rib, sausage, and brisket), and well… a picture's worth a thousand words…
Our buddy Matt Sanders (formerly a Polycot, then an HPer, and now at Librato) was in town from San Francisco for the conference, and joined us to indulge in smoked meat. We ended up eating at Ironworks at least 3 more times, which was kind of expensive, but fast and good.
After lunch Matt and I headed over to the new JW Marriott to a panel from Dutch fashion designer Pauline van Dongen titled Ready to Wear? Body Informed 3D Printed Fashion. This session was a perfect example of what makes SXSW such a unique conference: It's a subject that I'm curious about, but one I'd never go to a conference specifically to see. Pauline was wearing some of her tech-enabled fashions (a shirt with solar cells embedded in it), and talked about how fashion meets technology and how often in technology we design for the static (interlocking shapes), not the organic. She profiled two of her projects, one a sleeve that morphs based on the wearer's movement, and the other a neck ruff that uses electrically contracting wire to 'breathe' while worn. The challenges she faced (48 hour print cycles, unpredictability of material behavior) and insights discovered were really interesting, and it was one of the panels I kept thinking about most over the next few days.
After this panel I wandered through the job fair for a bit, which has expanded significantly in the last year. It was interesting to see Target and Apple looking for candidates at SXSW.
Saturday – Storytelling Machines, Future Crime, New Parents in Tech
First thing Saturday morning was my session with Jon Lebkowsky: Machines That Tell Stories. We had a great turnout, and there are notes from the discussion at the link. Looking over the schedule, storytelling and storytelling systems were a very hot topic. I was talking to Deus Ex Machina (an interactive theater project) producer Robert Matney later that it felt like the story zeitgeist erupted out of nowhere, and the flood of sessions made for a very interesting conference. The discussion was really interesting, and it was gratifying to hear that there was a lot of cross-pollination between attendees. I even heard that people were still connecting at the airport on their way home.
Chris Hurd, one of my friends and the guy behind DVinfo.net, gave me a tip one time from his years working big trade shows like NAB: The best way to keep a spring in your step at a long conference is to change your socks in the middle of the day. So after leading our session, and stopping into the 3M booth, we went back to the car, dumped our stuff, and I changed my socks. We had a long day ahead of us, and it was definitely worth it.
Next I went to a session titled Future Crimes From the Digital Underworld by Marc Goodman. It's always interesting to see the people who've given a talk a lot of times versus people who are presenting the material for the first time. Marc's obviously really practiced at this talk, complete with jokes, audience-call-outs, and what have you. It's a fun talk, but the net-net is that everything in security is terrible, and it's just going to get worse with trillions of IoT devices. I didn't need Marc to tell me that. I have Taylor Swift.
After that was Irma's meetup: New Parents in Tech. She had an interesting turnout, with only one other woman (there was a lot of competition for the women technologist this year, with a strong moms in tech panel opposite), but a lot of dads. Two product guys from Fisher Price showed up, too, and I had an interesting discussion with them about Baby's Musical Hands (Clara's first app) and iPad cases (they don't sell many anymore, possibly due to the kid market saturating with hand-me-downs). After a good discussion, it was on to…
Saturday/Sunday – Community
Community! And Harmontown! And Dan Harmon!
Ok, I'll admit it. Community is my biggest takeaway from SXSW. It's my favorite TV show, the only thing I watch obsessively. I've seen every episode, most of them a half dozen times. I follow the actors (even the lesser-known ones) on twitter. Fanboy = Me.
Yahoo! Screen picked up Community last year after NBC didn't renew it. The switch from broadcast to streaming distribution made it perfect SXSW fodder, especially after the Harmontown documentary premiered at SXSW Film last year. Yahoo! pulled out the big guns, though, and beyond just having Dan show up to talk about the switch, they brought the whole cast, and premiered the 1st episode of the new season a few days early for the fans. It was epic.
We had great seats for Harmontown, and were next to the stage when they brought out the cast and showed the season premier. When they showed the episode everybody sat down on the floor, and in one of the most amazing things I've ever been in the middle of, we all sang along kumbaya style to the theme song.
The episode was great, and we had a wonderful time.
The next morning, after a panel I'll talk about in a second, was a SXSW panel with the Community cast. Everyone was there again, and there was a great discussion about the show. For my money, it was even more interesting than Community's previous Paleyfest discussions, probably due to the fact that there wasn't a real moderator, just Dan Harmon asking the cast questions. We had front row seats for that one, too.
Some notes for Community fans:
- In the QA someone mentioned Conspiracy Theories and Interior Design as their favorite (it's my favorite too, I was the weirdo in the audience who applauded at that), and Dan told a story about how they essentially threw out the last 1/3rd of the episode (the original ending involved the teachers creating the conspiracy) while they were shooting. The final scene didn't get scripted until they were in the study room blocking it off. They had NBC Standards and Practices on the phone, because there's a lot of gunplay, and they were describing it, and finally the person from Standards and Practices said 'Is there any way you can make it about gun safety?' And if you've seen the episode, that's how the ending happened. Lots of Community episodes come together at the last minute.
- The speech Ben Chang gives in Analysis of Cork-Based Networking (about the character being a real person, but just being portrayed as crazier and crazier) was lifted nearly verbatim from an email Ken Jeong wrote to Dan Harmon about the character. When Ken was performing it, he teared up (those are real tears) because he was so touched.
- Alison Brie's contract is up this season, we'll see if she's back if they make a movie or Season 7.
- In discussing the longer episodes now that they aren't constrained by NBC commercial breaks, Joel McHale noted that The Dick Van Dyke Show episodes were 29 minutes, which made me think that there's an interesting comparison between The Dick Van Dyke Show as Community and I Love Lucy as The Big Bang Theory.
Ok, so that's Community. It was great. Watch it on Yahoo! Screen.
Sunday – Transmedia Storytelling, Bot Authors, & Makers
Before the morning Community panel was a session titled Worlds Without Boundaries: Books, Games, Films, with James Frey (author and media maker) and Jon Hanke (architect behind Google's Ingress game). It was a fascinating discussion about media that crosses boundaries. James mentioned he was heavily inspired as a kid by the book Masquerade, which included puzzles and a treasure hunt in the real world. In his series, Endgame, there's a puzzle pointing to keys that unlock a chest in the Caesars Palace casino in Las Vegas holding $.5, $1, and $1.5 million dollars in gold (per book, respectively). They're doing an app with Niantic Labs (Google), and they're planning films. It's an interesting product development scheme: Have a stable of creatives come up with a world. Sell some of the rights (film, TV), partner to do some products (games), and do others in house (books, novellas).
After the Community panel I spent some time in the SXSW trade show. General themes this year were lots of Japanese hardware startups (on Kickstarter, natch), lots of countries, and almost no hosting or cloud booths (save for Softlayer). A lot more music, and a little ergonomic furniture. Overall a less interactive-heavy trade show than years gone by. I'm not entirely sure why that was, but there you go. Wordpress didn't come with their great t-shirts this year, so I guess I'll have to actually go to the store to buy my clothes. I did manage to pick up a new Olloclip, though, and even got to see it built in front of me.
In the afternoon I made it over to Automated Insights panel When Robots Write The News, What Will Humans Do?, moderated by James Kotecki, Automated Insights' PR guy. This was an great discussion between Robbie Allen, the CEO of Automated Insights, and Lou Ferrara, a VP from Associated Press. Automated Insights' software produces AP stories in sports and stock reporting from raw data, and it was interesting to hear their discussion about what will be automated and where human value really lies. Automated Insights thing is producing one billion pieces of content for one person each, which I think everyone can agree is where a large part of the content we consume is headed.
After the Automated Insights panel I headed over to SXSW Create, the free maker area of the conference. While I was there I got to try out Lumo, a new interactive projector for kids that's about to hit Indiegogo. More on that later.
The Gaming Expo next door to Create was as crazy as ever, and really starting to outgrow the space they have for it. The only larger space downtown is the Convention Center, though, which puts them in kind of a bind. VR headsets were everywhere (almost always accompanied by lines of people waiting to use them), and it was good to see indie games like That Dragon, Cancer represented.
Monday – API Fails, Narrative Systems, Non-Linear Story Environments, Enchanted Objects, Home Projector Installations, & BBQ Science
The next day I tried to get into Wynn Netherland's talk Secrets to Powerful APIs, but I was late, so Matt and I couldn't fulfill our tweet-promise.
Instead, Matt and I went to the MedTech expo, and saw an interesting startup doing a small wireless body temp monitor for babies (slap a bandage over it, battery's good for a month), some interesting sleep trackers (lot of quantified self folks at SXSW) and of course Withings with their smart watch whose batteries work for 8 months.
After that I headed to Technology, Story, and the Art of Performance by Elena Parker (who came to our Machines That Tell Stories session and had some of the best insights) and Michael Monello from Campfire, a division of Sapient Nitro that specializes in unique interactive experiences.
Elena and Michael's presentation was one of the most meaty of the sessions I attended, full of helpful, hard-won insights into interactive projects. Slides are available here, and audio is here.. They showcased three: Deja View, a project for Infinity where actors you see on screen talk to you through the phone (dynamic video branching and voice recognition), Hunted, an ARG-like that used some clever magic tricks to make users think they were being controlled, and a project for the From Dusk Till Dawn TV series, where players could call in and talk to the character Santanico Pandemonium and she would try to recruit them for her cult (branching narrative, voice recognition).
Some of my major takeaways from the presentation:
- MaxMax: Elena talked about how while in games you program for MinMax (system constantly minimizes the players chances while maximizes the games chances, by attacking the player, moving enemies toward them, etc), in interactive story experiences you want to optimize for MaxMax, where you give the users as much of a chance of progressing as you can. They're likely only going to experience it once (replay value not being high, except for people who want to understand how the system works), so work as hard as you can to make sure they succeed.
- Embrace Genre: When you're giving people a new and unfamiliar experience, ground them in tropes and genre conventions they already understand. That way they have something to hold on to.
- 3 Act Structure: Use the standard exposition, rising action, climax story structure. Everybody understands it, it works, if you're re-inventing all the other wheels, don't re-invent that one.
- Magic!: There's an interesting cross-over with the magic community. They worked with a magician to design some of their interactive tricks (powered, in the end, by people sitting in a call center). Fooling the brain is what they do, and is what delights our users.
- Don't Branch: Traditional Choose Your Own Adventure stories use a branching structure, which leads to some short experiences and some long ones. That's a negative for experiences you want users to fully enjoy, so instead of branches, create a looping structure where each act breaks into sections, but they all come back at the end. Something like this: -=-=-=-
- Test: When you're testing an interactive narrative, write out only the main 80% line first, and test it on 5 people. This will validate your assumptions about how most people will view it, and won't waste your time creating alternate paths if your base assumptions are broken. Once you've passed 5, write out the rest and test on 50 people (I think this was how it went, they should post the slides soon) to validate your overall script. Then run a production beta test on as many people as you can to get data for all the subtle things you wouldn't expect.
After this panel I kept with the story theme and went to the Stories Asunder: Tales for the Internet of Things panel, with Lisa Woods from the Austin Interactive Installation meetup, and her team that produced Live at the Dead Horse Drum, an iBeacon powered non-linear location-based story experience on the east side of Austin. Also joining them was Klasien van de Zandschulp from Lava Lab, who's created some really fascinating geo-fence/iBeacon based non-linear story experiences in the Netherlands, including one under development where inhabitants of museum paintings create a social network the user can browse (think HogwartsPaintingBook). They had some really interesting examples, and I hope to experience some of their work soon.
On the way to my next panel I walked by the SXSW bookstore, and noticed that David Rose whose book Enchanted Objects I'd done a double-take on a few days before was going to be signing it just about then. So I bought a copy and a few minutes later David showed up, and we had a great 10 minute long conversation about projection mapped interactive art objects. David teaches at the MIT media lab, in addition to a lot of other stuff, and his book has moved straight to the top of my to-read stack. It sounds exactly like a subject I've posted about here before, and something that feels like it's moving from Bruce Sterling design fiction to real world product very quickly.
After talking to David I headed to the Storytelling Engines for Smart Environments panel, which had Meghan Athavale (aka Meg Rabbit) from Lumo Play on it. Meg's been doing interactive projection installations in Museums for many years, and has had the question 'Can I get this in my house?' posed more than a few times. Recently component prices have been dropping, so she's designed the Lumo Interactive Projector, a projector based toy for kids, and is about to run an Indiegogo for it. Meg's the kind of entrepreneur you can't help but root for. She came to SXSW by herself, set up a booth in Create, and is trying to drum up as much excitement as she can. I really hope her Indiegogo is a big hit.
After Storytelling Engines I headed over to the GE BBQ Research Center with Matt and Irma for some free BBQ. It was good, but Irma didn't care for it. Research accomplished!
Tuesday – AR/VR, Moonshots, New Assets, Space Cleaners, & Happy Bruce
Tuesday morning I hit the Mixed Reality Habitats: The New Wired Frontier panel presented by IEEE. My biggest 'wow' takeaway, aside from the fact that nobody seems to know what Microsoft's up to with Hololens or those Magic Leap guys (light fields?) with their headset, was from Todd Richmond, Director at USC's Institute for Creative Technologies, who said his group felt that most people would be wearing headsets (Google Glass-like or Hololens AR like, or Oculus Rift VR like) 8 hours a day for work in 5-10 years. When someone says something like that, I think it's time to take notice. Consider the headsets of today as the original iPhone. Think about how far we've come in the 6 years since that was released.
After that I watched Astro Teller speak about Moonshots at Google [x]. His main point was that they always strive to fail quickly and get real-life feedback as fast as possible. He talked about a bunch of wild projects they're working on like delivery drones, internet by high-altitude self-driving balloons, kite-based wind power, the self-driving car, and others. With each he emphasized how failure early lead to faster learning.
I hit a session entitled How to Rob a Bank: Vulnerabilities of New Money, with some fairly impressive speakers. Their main point seemed to be that your personal information is an emerging asset class that you should be concerned about. That just like your dollars in a bank, your purchase history and address and Facebook posts have value, and we don't really know how to protect that yet.
On our way back through the trade show Irma and I ran into Astroscale, a company from Singapore started by some Japanese ex-finance guys (follow me, here). They've hired engineering resources to design a satellite that will de-orbit space debris. Imagine that your $150 million dollar satellite is going to be impacted by a bit of out-of-control space junk. You pay these guys $10 million, and then go find that space junk, attach their micro-satellite to it, and de-orbit it before it can crash into you. And they're running a promotional time capsule project with Pocari Sweat and National Geographic to collect well wishes from kids and send them via a SpaceX launch to the moon. So yea, 30 years after Reagan's Star Wars and Brilliant Pebbles, and here's what we've got. I'm surprised it isn't on Kickstarter.
The end of SXSW is always Bruce Sterling's talk, and this year was no different. Bruce was kind of happy this year, and was almost channeling Temple Grandin in appearance, but happy Bruce isn't always most interesting Bruce. If you'd like to give his talk a listen, it's up on SoundCloud. Hopefully next year he'll have some tales from Casa Jasmina to share.
So that was it, SXSW Interactive 2015. 5 days of old friends, new friends, stories, the future, BBQ, and space junk. I can't wait to see you next year!


text:
Category Archives: Uncategorized
We place a high value on transparency and trust. We believe it's important to be clear and concise when it comes to your business and money.
A simple and quick application process with a fast turnaround so that you can focus on what you do best, running your business.
You'll work with a dedicated consultant who has a proven track record of success. We encourage our team to establish long-term relationships with our clients.
We offer a diverse platform of lending options and marketing solutions to assist your business in achieving its goals.
What our clients are saying:
Hear from our actual clients on how their business has been affected after becoming a P4P Partner.
I'm a salon owner now on my third opening. I've been working with Statzer from the beginning, for many years and highly recommend!
Thank you for helping my store this month. Every year after the holidays sales decline and thanks to you I was able to get the summer inventory in stock that we needed. You've all been very helpful.
I appreciate the all the work you put into helping the business. I didn't really think there were going to be many options until we had our initial conversation, and there's a great stress off my shoulders now that we've made headway. Looking forward to working together from now on.


text:
Wikibooks:Wikibooks for Wikimedians
While this is not a listing of rules or policies, it contains information about an important Wikibooks process, custom etc. This page should be helpful to our users; please let us know if it is not. | This page contains useful information about the Wikibooks project.
Wikibooks is one of many Wikimedia Foundation projects. Wikibooks is different from many of the other projects in that Wikibooks focuses on writing books rather than single pages. Wikipedia, Wikiquote, and Wiktionary can each be thought of as hosting a single book for instance. Keeping this in mind should help you to understand many of Wikibooks' differences. This page is intended to help answer some frequently asked questions that people familiar with other Wikimedia projects ask and to help you become more familiar with Wikibooks' policies, guidelines and culture in the hopes that you might become a Wikibookian as well.
Wikibooks is closely related to Wikipedia, but it's not part of Wikipedia
editThe most striking differences between Wikipedia and Wikibooks have to do with the nature of the projects. Encyclopedia articles and textbooks simply aren't the same things.
Textbooks vs. articles
edit- Wikibooks are supposed to be Textbooks, meaning that they are intended to facilitate teaching an area of knowledge.
- Textbooks are self-contained, meaning that the chapters link to each other internally, but not to other wikibooks.
- Textbooks have chapters, subchapters, and pages. A textbook should have navigation between its pages, a Table of Contents, and other book-like resources (glossary, appendices, etc).
- Textbooks are not supposed to be collections of individual articles, but are supposed to have a unifying theme and narrative.
- Textbooks shouldn't just include facts. A book needs to present those facts in a way that will be understandable by its target audience.
Wikibooks uses wikilinks conservatively
edit- As a general rule, Wikibooks pages don't contain as many links as Wikipedia articles. This is because a book is supposed to be a self-contained resource with a contiguous narrative. Links to all sorts of outside places can, furthermore, serve as a distraction. Links to other resources should usually be placed in a separate resources or bibliography section at the end of the book or page.
- Avoid making red-link references on Wikibooks. While it may sometimes be useful on Wikipedia to make red-links to articles that aren't written yet but would make a useful reference, on Wikibooks they should only be made to pages that fit in with the overall structure of that book.
- External linking should also be exercised sparsely. If technical terms are used which may be unfamiliar to the book's target audience, you may link to an external source about the term. Note, however, that Wikibooks are not created only for use on this medium, but may be published in other forms (such as off-line or printed) where these links will not work. Please also be careful when doing this, as a link to a non-existent or misspelled Wikipedia article will not come up red on Wikibooks. Make sure to follow the link, see that it works properly, doesn't lead to a disambiguation page, etc.
- To link to a Wikipedia article, use the form
[[:w:Article title|text you want]]
, where "w:
" is the prefix for Wikipedia. (There are other prefixes for other Wikimedia projects). Do not use the external link form ([https://en.wikipedia.org/w...
). Any text after the pipe will render as linked text. The previous example renders as "text you want".- If the text you want to display is the same as the linked article title, then you can use the pipe trick. Type
[[:w:Article title|]]
. When there is a link to an article, but no text after the pipe, the name of the page will be displayed (without the:w:
prefix). The previous example renders as "Article title". - The templates {{Wikipedia}} and {{Wikipedia-inline}} are also helpful. For more information on interwiki linking, see Help:Interwiki linking.
- If the text you want to display is the same as the linked article title, then you can use the pipe trick. Type
Wikibookians take a different approach to many things
edit- Where is the village pump?
- See the reading room.
- Where are the WikiProjects?
- Some can be found at Wikibooks:WikiProject. For ones that do not exist, a place to start a discussion on creating one would be the projects reading room.
- Why do my pages need to be "de-wikified"?
- [[Any]] [[old]] [[word]] is unlikely to point to anything because Wikibooks' naming conventions differ from Wikipedia's. Also, books tend to collect most external links and resources together into a centralized bibliography. See Wikibooks:Dewikify for details.
- What are the naming conventions?
- The main page of a book is generally named "Book Name", while subpages are generally named "Book Name/Sub Page", or "Book Name/Chapter/Sub Page". Wikibooks does not use the Wikipedia-style disambiguation convention of "Book Name (Page Name)"
- Where are the disambiguation pages?
- Disambiguation pages are only used in a limited way in the Cookbook. Organizational pages (such as shelves) are used to list similar books.
- What are Wikibooks' policies? How do policies differ from Wikipedia's?
- There are many differences, some big, some small. If you are interested in policy, see The complete list of current Wikibooks policies. Wikibooks tends to be more minimalist than Wikipedia is, so the number of policies that we have is far smaller than Wikipedia.
- What is the recommended style for making and editing books?
- There is no single style, but we do have some recommendations that we suggest for new Wikibookians. Look them over, but remember, these are just guidelines. As an author or an editor, you are given many freedoms in designing your books. Where authors disagree, you must work towards consensus. Some of our books have individual style guides (local manuals of style) to try to keep things consistent within one book.
- Who decides the format/layout/audience/style/navigation/etc of a new book? Is there a single "right way?"
- Who makes the decisions about a book? You do! Authors are given a broad range of freedoms and liberties when it comes to writing books. We ask that all the pages in a single book are formatted the same, in order to give the book unity and continuity. Different books have different target audience, and the style of each book should be adapted for its particular target audience, so different books adopt different styles.
- What is the policy on importing articles from Wikipedia to Wikibooks for use as textbook chapters?
- Request the article be imported, then follow the instructions that will be added to the imported page.
- How do I cite sources or include references?
- Most books, if they cite sources at all, gather all citation references in a single biographical type page, similar to what is commonly done in dead-tree books. See Wikibooks:Manual_of_Style#Footnotes_and_references.
- Why do some books look a lot like Wikipedia articles?
- Some pages have been imported from Wikipedia, but not yet rewritten into proper books. You can help!
How you can help
edit- What kinds of cleanup tasks are there to do here on Wikibooks?
- Wikibooks has many of the same tasks as Wikipedia does. Pages can be categorized, pages can be improved (edited, corrected, expanded), vandalism can be reverted, double-redirects can be removed... and the list goes on and on. For a listing of tasks that you can do, see Wikibooks Maintenance.
- How can I get involved?
- There are many ways to get involved at Wikibooks. Most discussions about policy and structure can be found in the Reading Room where people can ask and answer questions. There are always good books to look through in Featured Books, where the community gets together and focuses on what books should be considered good models for other books to follow. Most of our debates about acceptable content on Wikibooks take place on the requests for deletion page.


text:
Next: Integration with Version Control Systems, Previous: Caveat: gettextize
and autopoint
users, Up: Invoking gnulib-tool [Contents][Index]
Gnulib provides some functions that emit translatable messages using GNU
. The 'gnulib' domain at the
Translation Project collects
translations of these messages, which you should incorporate into your
own programs.
There are two basic ways to achieve this. The first, and older, method is to list all the source files you use from Gnulib in your own po/POTFILES.in file. This will cause all the relevant translatable strings to be included in your POT file. When you send this POT file to the Translation Project, translators will normally fill in the translations of the Gnulib strings from their "translation memory", and send you back updated PO files.
However, this process is error-prone: you might forget to list some source files, or the translator might not be using a translation memory and provide a different translation than another translator, or the translation might not be kept in sync between Gnulib and your package. It is also slow and causes substantial extra work, because a human translator must be in the loop for each language and you will need to incorporate their work on request.
For these reasons, a new method was designed and is now recommended. If
you pass the --po-base=directory
and --po-domain=domain
options to gnulib-tool
, then gnulib-tool
will create a
separate directory with its own POTFILES.in, and fetch current
translations directly from the Translation Project (using
or wget
, whichever is available).
The POT file in this directory will be called
domain-gnulib.pot, depending on the domain you gave to the
option (typically the same as the package name).
This causes these translations to reside in a separate message domain,
so that they do not clash either with the translations for the main part
of your package nor with those of other packages on the system that use
possibly different versions of Gnulib.
When you use these options, the functions in Gnulib are built
in such a way that they will always use this domain regardless of the
default domain set by textdomain
In order to use this method, you must—in each program that might use Gnulib code—add an extra line to the part of the program that initializes locale-dependent behavior. Where you would normally write something like:
setlocale (LC_ALL, ""); bindtextdomain (PACKAGE, LOCALEDIR); textdomain (PACKAGE);
you should add an additional bindtextdomain
call to inform
gettext of where the MO files for the extra message domain may be found:
bindtextdomain (PACKAGE "-gnulib", LOCALEDIR);
(This example assumes that the domain that you specified
to gnulib-tool
is the same as the value of the PACKAGE
preprocessor macro.)
Since you do not change the textdomain
call, the default message
domain for your program remains the same and your own use of gettext
functions will not be affected.
Next: Integration with Version Control Systems, Previous: Caveat: gettextize
and autopoint
users, Up: Invoking gnulib-tool [Contents][Index]


text:
Created with Sketch.
Previous Lesson
Complete and Continue
Created with Sketch.
Million Dollar Instructor
Created with Sketch.
Million Dollar Instructor
Welcome! (7:31)
How to pick your topic (30:55)
How to be an expert (7:31)
Why teaching is so awesome (7:31)
Additional Materials
Created with Sketch.
Section 1 - Doing your course research
Pick an aggressive launch date (7:31)
Create your rough outline (7:31)
Understand the different forms of content (7:31)
Creating quality content (30:55)
Created with Sketch.
Section 2 - Choose your course content mix
Screencasting (7:31)
Video production background (30:55)
Audio over slides (7:31)
Alternative content (30:55)
Created with Sketch.
Section 3 - Put out a pre-release and start testing demand
Pre-sell to test demand (7:31)
Pre-release pricing strategy (7:31)
How to promote your course (7:31)
Get your course on BetaList (7:31)
Why your promo video matters (7:31)
Create a Promo video (30:55)
Prelaunch Case Study: Million Dollar Instructor (30:55)
Using ConvertKit to message your first signups (7:31)
Implementing your pre-launch landing page (10:42)
Created with Sketch.
Section 4 - Defining your teaching style
Your teaching mindset: Yoda I am not (7:31)
Learning from Khan Academy (7:31)
Developing your own teaching style (7:31)
How to divide up material (7:31)
Deliver on your promises (30:55)
Create mini challenges (30:55)
Create in-depth assignments (7:31)
Some assignment examples (7:31)
Create time for review (7:31)
Created with Sketch.
Section 5 - Content is king
Plan out your content ahead of time (3:25)
How to create a script (7:31)
How to create great slides (7:31)
Including other useful tools and resources (7:31)
Created with Sketch.
Section 6 - Content production
Screencasting Materials (7:31)
Screenflow Download and Install (2:19)
Screenflow Updating Preferences and Activation (7:31)
Screenflow How to make Screencasts (30:55)
Screenflow Splicing Video Stopping and Starting (7:31)
Screenflow Adding Media (7:31)
Screenflow Audio Features (30:55)
Screenflow Video Features (3:49)
Screenflow ScreenRecording Features (7:31)
Screenflow Call Out Features (30:55)
Screenflow Annotation Features (30:55)
Screenflow Text Features (7:31)
Exporting Screenflow ScreenCasts (7:31)
Video Production: Getting started (7:31)
Video production: $50 Studio (5:16)
Video production: The Million Dollar Instructor set-up (7:31)
Video production: Full studio set-up (7:31)
Created with Sketch.
Section 7 - Get your first loyal students
Where to network to gain first loyal students (7:31)
Interacting with students (3:55)
Turn your early adopters into evangelists (7:31)
Created with Sketch.
Section 8 - Launching Your Course
Define your value proposition (7:31)
Communicate Your Value Proposition (30:55)
Use your story to stand out (7:31)
Case Study: Get your course live (7:31)
Created with Sketch.
Section 9 - How to grow your audience
Knowing when you're ready for growth (7:31)
Growth Principle #1 - Give something valuable away for free (7:31)
Growth Principle #2 - Build your email list (7:31)
Build your email list exercise (7:31)
Growth Principle #3 - Create a minimum viable course (7:31)
Case Study: User Growth Bootcamp (7:31)
Case study: Bitfountain - From initial growth to 100K potential customers (30:55)
Case Study: Bitfountain - Converting potential customers into paid customers (30:55)
Finding growth (7:31)
Offline Events
Blog and email
Your network
Social Media
Discount Forums
Ebook (Guest Lecture)
Deal Websites
Created with Sketch.
Section 10 - How to price your courses and make money
Why you should reexamine your pricing (7:31)
Price discrimination (30:55)
Pricing strategy (7:31)
Subscriptions (7:31)
Discounting (6:22)
Multiple products (7:31)
Pricing hack to make more money #1 (1:06)
Pricing hack to make more money #2 (7:31)
Pricing hack to make more money #3 (7:31)
Pricing hack to make more money #4 (30:55)
Pricing hack to make more money #5 (7:31)
Created with Sketch.
Section 11 - Scaling your course with new products, messaging, and analytics
Scaling your course #1 (7:31)
Scaling your course #2 (7:31)
Analyzing student behavior and advanced messaging (7:31)
Created with Sketch.
Section 12 - Expert Interviews
Interview with Justin Mitchel (7:31)
Interview with Josh Payne (30:55)
Interview with Caleb Wojcik (7:31)
Interview with Mattan Griffel (30:55)
Interview with Mark Lassoff (30:55)
Interview with David Kadavy (7:31)
Interview with Scott Britton (7:31)
Interview with Paul Solt (7:31)
Interview with Nathan Barry (7:31)
Communicate Your Value Proposition
Lesson content locked
If you're already enrolled,
you'll need to login
Enroll in Course to Unlock


text:
Claudia Dei, cow back more than ever faced with six birds that want to break anywhere. Good life, sun, sea and beautiful pussies, who would not want such a life?
Duration: 1 ore e 21 minuti
All models appearing on this website are 18 years or older. Click here for records required pursuant to 18 U.S.C. 2257 Record Keeping Requirements Compliance Statement. By entering this site you swear that you are of legal age in your area to view adult material and that you wish to view such material.
In tutti i contenuti pubblicati in questo sito, Ogni riferimento a persone esistenti o a fatti realmente accaduti od a luoghi ed istituzioni è puramente casuale e frutto di fantasia degli attori e sceneggiatori.
All rights reserved. Please visit Epoch our authorized sales agents. Billing Support
Copyright information
18 U.S.C. 2257 Record-Keeping Requirements Compliance Statement
Pornliving.com Honest Reviews | Porn Reviews | Porn Reviews | Sir Rodney's Porn Reviews


text:
June 27, 2013
Mark Weisbrot
The Guardian Unlimited, June 27, 2013
Em Português
See article on original website
If Edward Snowden can make it to Ecuador, it will be a good choice for him and the world. The government, including President Rafael Correa and foreign minister Ricardo Patiño, proved their courage and steadfastness in the face of threats and abuse last year when they granted asylum to Wikileaks' founder Julian Assange. The media took advantage of the fact that most of the world knows nothing about Ecuador to misinform their audience that this government "represses the media." The same efforts are already underway in the Snowden case. Without defending everything that exists in Ecuador, including criminal libel laws and some vague language in a new communications law, anyone who has been to the country knows that the international media has presented a gross caricature of the state of press freedom there. The Ecuadorean private media is more oppositional than ours in the United States, trashing the government every day.
Unfortunately groups like Americas Watch (of Human Rights Watch) and the Committee to Protect Journalists, which do good work in some countries, have joined Washington's campaign against Ecuador, publishing gross exaggerations. These groups should be a bit more worried about the chilling effect that the Obama administration's unprecedented prosecution of whistle-blowers, and other abuses, have had on investigative journalism in the United States.
The great irony is not that Snowden should enlist help from Ecuador, or even Russia and China for that matter, in escaping political persecution. Has any journalist or human rights advocate criticized the thousands of Salvadoran refugees who escaped U.S.-sponsored murder and repression in the late 1970s and 80s by fleeing to the United States, "the world's greatest purveyor of violence," as Martin Luther King, Jr. once described it? Political refugees do not choose their host countries according to whether they agree with government policy. The great irony in this case is that Ecuador gets dragged through the mud for considering asylum for a whistle-blower who has been charged under the Espionage Act. Who — yes, ironically – probably could not even get a fair trial in the U.S. because the media here has already convicted him.
Washington would almost certainly retaliate against Ecuador for granting asylum to Snowden. In addition to commercial sanctions, there are possible covert actions. In 2010 there was a coup attempt against Correa; although there is no direct evidence of U.S. involvement, the police who led the uprising had a long relationship with U.S. officials, including funding. Many in Ecuador's government believe that Washington was involved, and if it wasn't, this would be the first coup attempt in at least 60 years against a left government in Latin America that Washington had nothing to do with.
The Obama administration has led a successful media campaign to reframe the Snowden case in cold war terms, and much of the media has gone along for the ride, portraying Ecuador as wanting to "poke its finger in Washington's eye." Correa must be doing this for some political gain at home too, they say. It's the exact same menu that was served up when Ecuador granted asylum to Assange, with the added primitive view that these "anti-American" troublemakers down south must have a new "ringleader" to replace Hugo Chavez. But any of the newly independent left-of-center governments in South America would have granted asylum to Assange. Brazil's then-president Lula da Silva was one of Assange's first (before Correa) and strongest defenders, and Brazil would likely approve an asylum request from Snowden too. Snowden, like Assange, has a well-founded fear of political persecution – especially after being charged with espionage, a crime he clearly did not commit. So as a matter of international law and of principle – including the principle of self-determination – none of these governments would participate in what Wikileaks is correctly calling a "rendition" of Snowden to the U.S.
If Washington is ultimately forced to respect international law in this case, it will be because many countries, most strikingly in South America, no longer fear U.S. retaliation. Since Snowden did a huge public service by revealing government wrongdoing, this is another example of how U.S. citizens — contrary to what our media tells us every day — actually benefit from the development of a more multi-polar world.


text:
The HIGHQUEST Discipleship Series is a discipleship training platform and pathway that integrates personal reflection on the Scripture and a small group experience.
This gender specific series equips men and women to walk with God for a lifetime by developing the concepts and personal practices that are foundational to living a Christ-centered life. The major themes (tracks) of the HIGHQUEST Series are:
These three themes represent the essential life long pursuits of a follower of Christ. They represent our vertical relationship with God, our inner relationship with ourselves, and our outward relationship with those both inside and outside the Kingdom. Discipleship is a direction rather than a destination. These three pursuits establish the direction for a lifetime of following Christ. |
Sign up for our HighQuest Newsletter


text: The Career Fire Fighter Paramedics Association of Ocean City, IAFF Local 4269 and the Red Knights Motorcycle Club Md. Chapter 3 are co-sponsoring Bishopville native Ashley Tartufo, who will be running on the IAFF Burn Foundation Fire Fighter Marathon Team. Tartufo, a Career Fire Fighter/Paramedic with Howard County Fire Rescue, was inspired to join the fire service by her neighbor Tom Kane, a 32-year veteran, who recently retired from the Ocean City Fire Department. Pictured, from left, are Michael Maykrantz, Vice President IAFF Local 4269 Ocean City, and his son, Connor; Tartufo; and Father John Tortufo, treasurer Red Knights Motorcycle Club Md, Chapter 3.


text:
Product Description
Polished Brass Pieces 6.5 Creedmoore
*Includes extra pieces to ensure usable quantity
*We sell quality, polished brass and nickel casings for the purpose of reloading. We carry the most popular calibers like 9mm, .223, 308 and 45, as well as hard to find casings such as 458 Socom, 50 Beo, 450 Bushmaster and others. Most of our bulk quantities include extra pieces of brass or nickel to ensure a usable quantity.
*We offer free shipping- no matter the caliber or size of order. Our customer service wonÕt be outdone. We work hard for your satisfaction and should a problem ever arise, weÕll work with you to make it right.


text:
Share this page with your social networks:
Copyright © 2024 Ultimate Workout and Recovery All rights reserved.
Ultimate Workout and Recovery strongly recommends that you consult with your physician before beginning any exercise program or the use of any of our products. Additionally, we strongly recommend that the product is assembled using construction gloves while the product is lying down and by someone that specializing in assembling products. It is also suggested to use WD40 lubricating oil for adjusting of the system. Please seek advice from a trusted professional therapist or personal trainer on the workouts and fitness routines. This product is intended for adults and for children 10 years of older, under adult supervision, and the gym should never be left unattended around small children 5 years old or under. The Ultimate Workout and Recovery System MUST be installed correctly using the thresholds as its base goes directly under the legs of a chair or bed for stationary function and security AT ALL TIMES. The gym can be drilled into the ground using concrete screws of Tapcon® screws; once the unit is anchored into the ground, it can be used while standing up, and only then can it be used while standing up. The warranty on the steel/aluminum structure/gym is good for 5 years. Please contact us regarding the warranty on accessories. Structure/Gym manufactured in the USA. Please allow 7-10 weeks for delivery.


text:
Exciting Media Sponsorships with WPFW!
"WPFW programming will make the concept of community radio real by providing the local majority population with important and relevant education, information, and entertainment. Through its programming, the station will act as a networking agent for the community-at-large."(Excerpt from WPFW Mission Statement)
Pacifica is a non-commercial radio broadcasting foundation committed to the principles of peace and social justice. In addition, WPFW is also based in the jazz aesthetic and, on occasion, may choose to partner with non-profit institutions and organizations on events and performances where such natural affinities exist through our Media Sponsorship program.


text:
Murdered: Soul Suspect gets teaser site, web game cracked
Murdered: Soul Suspect has just been named and revealed by Square-Enix. it's coming to PC, PS3 and Xbox 360. We received a very cryptic email for the project along with some very odd images. The link in the email points to a teaser site and Twitter account.
We received three images along with the message 'What is the hardest case to solve?' Here they are cobbled together (thanks gingeas)
Square-Enix just sent VG247 an email to confirm the name of the game. Here's what they said:
"Murdered: Soul Suspect is an exciting new game from Square Enix which challenges players to solve possibly the hardest case of all"
Now a web game for the title has gone live. the password is Ronan. (Thanks dex3108)
When entered, you can download the below image and message:
O'Connor, male, mid- 30s, 170lbs, 5' 11"
Detectives aren't supposed to get bloody knuckles, but I've done a lot of things I wasn't supposed to do. I lived through it all, the beat-downs, the back-stabbing, disrespect most people wouldn't see in ten lifetimes and I never lost a fight… until now.
Steph has noticed that the area code on the palm reading sign in the background reads '725'. That's the new area code that Nevada is getting in 2014. This could be a release date or setting tease?
Also notice the tree bark in the photo. Looks like it belongs to a white birch tree, and you can see the pointy-end of the leaf in the top corner. The only issue is that it would put the game outside of Nevada, as the tree is not indigenous to that area. Could be Aspen bark, but the leaf pattern doesn't match - Aspen leaved are more round. We'll find out soon enough.
Also, is this the new Crystal Dynamics IP they teased last year?. Superannuation seems to think its a mystery-horror title in the works from Airtight Games which he wrote about back in January.
Here's the website image:
There's also a Twitter account @Murdered.


text:
Yellow Topaz
Availability: In stock
Weight In Caret | 4.1800 |
Weight In Ratti | 4.5900 |
Weight in grm | 0.8300 |
COLOUR | Yellow |
ORIGIN | No |
Benefits | Improvement for Business and Marriage |
Quality | Excellent |
Shape | Oval |
Mantra | "ॐ ग्रां ग्रीं ग्रौं सः गुरुवे नमः (Om Graam Greem Graum Sah Guruve Namaha)" |
SIZE | No |
CERTIFICATION | Free Lab Certificate |
TREATMENT | Unheated And Untreated |
Yellow topaz Crystals are the variety of quartz and are closely related to Amethyst. The meaning Yellow topaz gemstone, comes from the Greek word meaning 'citron'. Yellow topaz is a joyful stone which bright energy which lights up many aspects of your lives.
It is helpful to clear unwanted energies from the environment, family issues caused by negative energies can also be cleared. This is a stone for the month of November.
The colour of this stone is yellow of the lemon, yellow/gold quartz.
How to Wear :It impress to God Brahaspati. Wearer should wear YELLOW TOPAZ in the Index Finger of hand on Thursday morning. Before Wearing YELLOW TOPAZ, dip it into Cow milk or Ganga jal. While wear this stone chant "om graam greem graum sah guruve namaha" mantra. It improves the business and merriage life. It is available in different shape and size.
Benefits :- It will help you to be decisive about what you will bring into your life.
- It brings energy to all of the lower three chakras.
- This may bring mental clarity and may precipitate an increase in spiritual vision.
- It is particularly used to promote success in business.


text:
Alas, reality has long since abandoned those who are waging a war on the American educational system. Beck's interlocutor actually compared the "indoctrination" one finds in a typical American college to what one would find at the University of Peking in communist China. Are they for real? Mr. Beck said that liberal professors want a free flow of ideas, so long as the topic is pornography or abortion. I don't think I ever have had an assignment pertaining to abortion, and the only time I've read on pornography was in Feminist Theory, where we examined Catherine MacKinnon's claim that it was a civil rights violation against women. Damn those liberals, corrupting American culture with their strident opposition to pornography! I'm sorry, but if a Zionist hawk who wrote his final paper urging feminist theorists to support more American military interventions abroad can get an "A" from a professor with a UCLA Ph.D specializing in women's roles in Arab liberation movements (and if this same professor offered to give me advice in trying to get one of my other papers published), then I'm not too worried about bias effecting my learning experience.
Beck offered (I assume half-satirically) a "pledge" that college age students could make to their parents. It consists of three parts (I'm paraphrasing from memory):
1) I will be a barrier between liberal ideals and truth.
2) If I am tempted to "the dark side" I will discuss things for at least an hour with my parents.
3) If after an hour I still disagree with my parents, then I will proudly assert my independence with the understanding that they will no longer pay for my tuition.
Gosh, what a contrast! I mean, I'm sure seeing a commitment to free inquiry and open minds present in that pledge that's missing from contemporary academia. Disagree with your parents, get your tuition cut off! That's the way to foster that independent spirit!
I've urged that Carleton attempt to provide more balance in its political alignment, if only to make debates more interesting. And there will always be horror stories that make the news. But folks like Beck are simply talking non-sense in how they portray the general contemporary college climate. Things aren't nearly as bad as they make them out to be. And I honestly think that nearly anyone who actually is present in a mainstream college or university will attest to that.