text:
An unmanned Russian resupply mission headed towards the International Space Station came plummeting back down to Earth with three tons of equipment, food and fuel shortly after liftoff.
At 325 seconds into its flight, one stage of the Soyuz-U rocket shut down and the Progress M-12M spacecraft fell back to Earth over Russia.
It's a terrible time for a mission failure. The Shuttle is done and private resupply missions by SpaceX aren't up and running yet. Moreover, it might mean that the crew aboard the ISS has to stay up longer than expected if the cause of the rocket failure can't be sussed out before September 22, when a replacement crew was due to go up.
Since Soyuz is the only game in town, the BBC notes that it could mean that the crew aboard the ISS might even have to be reduced. Toilet parts, for example, could be a problem, which makes sense if you've ever seen all the gear needed for an astronaut to go to the can in orbit. [BBC via Steve Silberman Image: NASA]


text:
Take a nutritious break with Forever Fastbreak!
Whether you're living on the go or need something to fuel you through a workout, Forever Fastbreak is a great supplement to your lifestyle. It's also so delicious that it will make you feel like you've gone to weight management heaven!
This chocolate peanut butter bar is packed with 11 grams of protein, vitamins, minerals and 3 grams of fiber to keep you full! There's really nothing else you need to reach for when you're feeling like you need a little energy in a satisfying snack.
Coming soon! Stay tuned to your country retail and FBO site to learn when the new Forever Fastbreak will reach you.

subset: commoncrawl


text:
Page 1
|1 of 2
This page
HASKINS & S E L LS NEW YORK KANSAS CITY CHICAGO CERTIFIED PUBLIC ACCOUNTANTS SEATTLE PHILADELPHIA PORTLAND DETROIT DENVER CLEVELAND BULLETIN ATLANTA SAINT LOUIS DALLAS BOSTON SALT LAKE CITY BALTIMORE TULSA PITTSBURGH WATERTOWN LOS ANGELES SAN FRANCISCO LONDON BUFFALO PARIS CINCINNATI NEW ORLEANS E X E C U T I V E OFFICES HASKINS & SELLS BUILDING 37 WEST 39TH ST., NEW YORK HAVANA SHANGHAI VOL. IV NEW YORK, JUNE 15, 1921 No. 6 Relations with Clients HAVE you ever stopped to think what it is all about, this work which as a professional organization we are doing? Is it a mere matter of putting in so many hours a day, doing so much work, and collecting so much money? If that's the way you see it you have missed the big thing in the field in which you are engaged. If you have the true accounting instinct and are true to yourself and to the ideals of the accountancy profession your interest will be directed at and your thoughts focused on giving satisfaction to clients regardless of everything else. This generalization may mean much or little depending upon the consideration which is given to it. "Satisfaction to clients" may be a glib term in the parlance of modern inspirational literature or it may be something to take seriously to heart in its application to each specific engagement. Generalities are fine at times in formulating thought and pointing the way, but they accomplish little in the way of getting anywhere. What we need to do is to take "satisfaction to clients" as our watchword and think about it all the time in relation to every piece of work which we undertake. Every engagement is prompted by a motive on the part of the client. The client who comes to us for service is in the same relative position as a patient who goes to a physician. Sometimes the patient knows what his trouble is and sometimes he does not. Some patients go to a physician for relief from some illness; others, like the Chinese, in order to keep well. Likewise, some clients know exactly what they want, can and do tell us. There are other clients who want to be "looked over" generally. Then there are the clients who seek our services as a means of relief and those others who want to be "kept well." Every client has his reason for coming to us. The fact of his coming denotes a need for help. But before this help may be rendered the motive must be either expressed by him or discovered by us. If the client makes clear his purpose the problem is simplified. If he does not do so, it is useless to expect that relief or help may be intelligently afforded until the motive has been discovered. It is only under such circumstances that satisfaction to the client may be expected. There is a new type of client, manifesting itself more and more, which believes in co-operation with the accountant. The type is exemplified in a member of a prominent engineering firm who said recently, "It is the prerogative of the executive calling on accountants for work to be done to
Object Description
Relations with clients
Accounting as a profession
Haskins & Sells Bulletin, Vol. 04, no. 06 (1921 June 15), p. 49-50
|Originally published by: Haskins & Sells
|Deloitte Digital Collection
|Digital Publisher
|University of Mississippi Libraries. Accounting Collection
|Date-Digitally Created
|HS Bulletin 4-p49


text:
Gloria Neal out at AM 760, amid format change
Brace for big changes on the local radio scene. Specifically AM 760. Gloria Neal posted on Facebook:
As many of you know I have splitting my time between hosting the Gloria Neal Show on AM760 Radio from 7am -10am and being a part of the 6pm News Team on CBS4, Mon-Fri. As of this morning, The Gloria Neal on AM760 is no more. Clear Channel is completely changing the format. The official announcement has not been made as to what the format will be, but none of current hosts will be on the new station.
"Colorado's Progressive Talk" may be unplugging. The station was previously a sports talk outlet.
The word Thursday morning from Greg Foster, Clear Channel vice president/programming:
"I can confirm that Gloria Neal's show is no longer on KKZN and she is no longer with our company. We will be announcing new programming for KKZN in the near future."


text:
Williams Sonoma IPA Craft Beer Kit
- Only at Williams Sonoma
- Exclusive
Easy, hassle-free returns online and in-store for eligible items.Learn More
Earn 5% Back in rewards4 plus free standard shipping3every day when you shop with your Williams Sonoma credit card at Williams Sonoma.Apply Now Learn More
- Summary
Brew your own India Pale Ale (IPA) at home with our beer-making kit. It includes all the basic equipment, ingredients and instructions you need to craft great-tasting beer from the very first batch. Follow the step-by-step instructions, and in approx. one month, you can enjoy an American-style IPA with a moderate alcohol level, a fresh hoppy aroma and flavor, and a bright golden-red color.
Includes brewing equipment and ingredients to brew IPA, including enough malt, grain, hops and yeast for your first batch.
Instructions provided in the included booklet, A Guide to Craft Brewing.
Additional equipment and ingredients required:
- Large brew pot, fine-mesh strainer, 10 lb. ice and 10 swing-top bottles.
- Ingredients included for 1 gal. (ten 12-oz. bottles).
- Equipment can be reused to brew additional batches.
- Dimensions & More Info
Kit includes:
- 1-gallon glass carboy fermenter
- Funnel
- Food-grade tubing with thumb clamp
- Thermometer
- Rubber stopper
- 3-piece airlock
- Curved racking cane for bottling
- Brew bag
- Ingredients: malt (1 lb. 3 oz.), grains (3.5 oz.), hops (0.6 oz.), yeast (11g).
- Sanitizer
- A Guide to Craft Brewing instruction booklet
- Gallon glass carboy, food-grade tubing with thumb clamp, rubber stopper, malt extract, brewers grains, sanitizer and brew bag are made in USA of American and imported materials.
- Funnel is made in Taiwan.
- Thermometer is made in China.
- Airlock and racking cane are made in Canada.
- Yeast is made in England.
- Use & Care
- Includes complete step-by-step instructions.
- Ingredients
- Malt pilsner DME extract, brewers grains, summit hops, yeast.
- Shipping
Shipping Information
UPS can deliver most in-stock items within 3–5 business days. UPS is unable to deliver to P.O. boxes.
Shipping Rates
The shipping rate varies depending on your order total and shipping destination. View Shipping Options and Charges.
Next Day Delivery
For an additional charge of $26 per address, we can expedite delivery to most destinations. This service is not available for some oversize items, items shipped directly from the supplier (including perishable and custom-manufactured items), out-of-stock items and items to be shipped outside the contiguous 48 states.
Orders received by 9:00 p.m. ET Monday through Thursday will arrive the next business day; orders placed Friday through Sunday will arrive on the following Tuesday.
Return Policy
At Williams Sonoma, we take great pride in the quality and craftsmanship of our products. Attention to design, materials, safety and construction are our priority. Upon receipt, please inspect your purchase and notify us of any damage; we will arrange for a prompt replacement.
If within 30 days, you are dissatisfied for any reason, you may return your purchase for a refund of the merchandise value. An original receipt or gift receipt is required for all returns and exchanges. Returns with a gift receipt will be refunded in the form of a Merchandise Credit for the amount indicated on the gift receipt. Returns with original receipt will be refunded in the original form of payment, cash and check refunds over $100 will be issued as a company check (may take 14 business days from time of request).
For all cutlery returns (knife sets, single knives, cutting boards, knife sharpeners and knife storage), please contact us at 888.922.4108 to initiate the return.
We cannot accept returns on monogrammed, personalized, special-order items, custom upholstery, food, items shipped direct from the vendor or on items damaged through normal wear and tear. Final sale items ending in .97 or .99 cannot be returned.
Made to Order and Final Sale Furniture items are non-returnable and cannot be cancelled once the order is placed.
For returns of items purchased from your Williams Sonoma Gift Registry, we will gladly provide a refund or exchange for the merchandise within 90 days of your event or within 90 days of purchase, whichever date is later. View Full Returns Policy.


text:
Suppose I have a topic or discussion, and a number of "support" and "opposition" points on each side (You can also think of them as "upvotes" and "downvotes") and I want to calculate a score of how "controversial" a topic is. (Let $p$ be the support score, $c$ be the opposition score, and $f(p, c)$ be the function that determines the controversy score.)
It should have the following properties:
- Controversy is maximized when equal support is given to both sides. Given that some property $g(p, c)$ is held constant (such that the slope of the tangent line of the level curve of $g(p, c)$ at any point is never positive), $f(p, c)$ should be maximized when $p = c$.
- More support on both sides means that more people care and therefore there is more controversy. Given that $p/c$ is held constant, a higher value of $p$ or $c$ should result in a higher value of $f(p, c)$.
- The amount of controversy is the same for the same imbalance of support no matter which side the imbalance favours. $f(p, c)$ should equal $f(c, p)$.
- All the support being on one side means there is no controversy. Given that either $p$ or $c$ is equal to zero, $f(p, c)$ should be equal to zero.
Is there any function like this that is already in use? If not, could one be devised?


text:
Kn10 necesitaba un nuevo diseño de logotipo y lanzó un concurso de diseño en 99designs.
Un ganador ha sido elegido entre 71 diseños de 30 diseñadores freelance.
Looking for a logo design for a business called "Aquatrek". They specialise in products for managing water such as house down-pipes. Would like to see some water theme worked into it.
A Journey with Water
Desired Style:
Water themed
Accepted File Formats:
Vector Formats (.eps, .pdf or .ai)
As mentioned in the short summary. The business is called "Aquatrek" and they specialise in water management products like down-pipes on houses.
Their slogan is "A Journey with Water". Perhaps you could show a version of your submitted logo, one with and one without the slogan.
Designs must be Vector based.
At completion of payment the full rights of the logo must be transferred to me, but I don't mind if you use it in your portfolio.
Something that people would be able to recognize it as Aquatrek's logo if they saw it elsewhere.
I am looking for an image and text in the logo. Not just text with a fancy font.
As for colors, since there is no existing designs so you can use whatever colors you want.
I will be watching this thread very carefully and will give feedback as soon as possible (usually within 24 hours).
Descubre cómo funciona un concurso de diseño u obtén más información sobre nuestros servicios de diseño de logo.


text:
Table of contents
8 June 2012
Prerequisite knowledge
Familiarity with ActionScript and building applications on Adobe AIR.
Required products
Adobe AIR
User level
Prior to Adobe AIR 3, only Adobe could add core features to the runtime. Developers requiring new features could only wait. Now developers can extend the runtime themselves. This new capability allows developers to:
- Achieve deeper integration with target devices
- Incorporate legacy native code in their application
- Achieve maximum performance for critical code
In this article, I'll discuss all of the essential aspects of this feature:
- What you can achieve with native extensions for Adobe AIR
- How to use an extension in an application
- How to create your own extensions
This article focuses on the specifics of developing for Android, iOS, OS X, and Windows. Extensions are also supported on other platforms, including BlackBerry Tablet OS. Starting AIR 3.3, extensions are also supported for iOS Simulator
Extensions support three use cases: deep platform integration, legacy code reuse, and maximum performance.
Mobile devices offer an array of unique capabilities. Some are software, such as the sophisticated Android notification mechanism. Others are hardware, like the dual screens in the Sony S2 tablet.
While Adobe does not take a lowest common denominator approach when adding APIs to AIR, we do focus on creating APIs that can be used across multiple devices. Thus, it is unlikely that AIR will support a dual-screen API any time soon, since the API would be inoperable on nearly all devices.
Extensions can be used to add these capabilities to the runtime as needed. Extension authors can provide API mappings for platform-specific features, and can do so with as little, or as much, sophistication as they need.
Development shops with longer histories often have code from past projects that they would like to bring forward into new applications. In many cases, such code is even relatively portable, written in C or C++ and expecting POSIX APIs.
Regardless of the legacy code's origin, the extensions mechanism allows the code to be wrapped up with an ActionScript API, and thus be used within an AIR application.
Extensions can be used to implement computationally intensive code that requires the highest possible level of optimization. Applications that leverage these compute kernels can implement them in extensions, and then invoke them from ActionScript.
Using native code enables several important optimizations. Firstly, and perhaps most obviously, the computation can be coded in C or assembly for maximum performance. Second, native code can take advantage of multiple cores, which can provide a significant performance boost for parallelizable algorithms. Finally, native code may be able to take direct advantage of the GPU for off-loading certain calculations.
The introduction of extensions brings with it not just a new feature but a new way of writing applications.
Prior to extensions, applications have been written entirely in ActionScript. ActionScript is a capable language, well suited to user interface and core application logic. However, no language is well suited to all tasks, and ActionScript is no exception.
With extensions, applications can be written in two tiers: ActionScript on top, coordinating application and presentation logic, and native code below, providing deep integration, legacy code reuse, and performance.
This architecture is nothing new; applications have been written using this approach for decades, and with any number of languages used in combination. By enabling it in AIR, we allow its many benefits to be brought to bear on AIR application development.
An extension mechanism needs a model, that is, a methodology by which new APIs are bound into the runtime. AIR extensions are modeled as ActionScript libraries that contain native code.
This model allows the creation of a native extension to be separated from its consumption. Thus, extensions can be developed independently, published separately, licensed, sold, and so on as can any ActionScript library. Alternatively, they can be created and consumed by the same developer, possibly even for use with a single application.
While an extension necessarily includes native platform code, each extension is nonetheless intended to be useable across multiple platforms. That is, one need not build a separate extension to leverage a legacy library across each targeted platform. Rather, a single extension contains a platform-specific version of that library for each targeted platform.
Developing extensions in this model is a bit more work for the extension developer but enormously easier for the application developer. It allows an application developer to use a single, cross-platform ActionScript API throughout an application, and rely on the extension to provide the necessary platform-specific implementation. This, of course, is how the built-in ActionScript APIs work, and it's this aspect of the extension model that makes them true extensions to the runtime.
Extensions separate creation and consumption of the extension. This separation makes it possible for developers to creative an extension not only for their own use, but also for others to use. This allows a developer to extend the runtime facilities for all other AIR developers. OEMs can also use this capability to extend the runtime in ways specific to their devices.
Before writing your own extension, it's worth checking to see if the functionality you need is already available; perhaps someone else has done some of the work for you. Extensions created by other developers can be published through any of the normal means: code-sharing sites, blogs, and so on.
Note that access to device-specific capabilities implemented by device manufacturers will typically require obtaining the extension from the manufacturer itself. The manufacturer's SDK or other developer information should contain the necessary information.
When acquiring an extension from external sources, think carefully about whether or not you trust that provider. As with externally sourced ActionScript code, the code in the extension becomes part of your application and runs with full application privileges. By incorporating an extension into your application, you take responsibility for any security issues that extension might contain.
Currently, not all development tools have direct support for extensions. Until they do, you can generally make use of them by working with them as ActionScript libraries. For example, in Flash Builder, you can add an extension to your project by following the same steps you use to add a SWC dependency. Just make sure you select the option to use external linkage as extensions are bundled with, not compiled into, the application.
When you add an extension to your application, the linkage from the application to the extension is recorded in the application's descriptor file. It's nothing more than a list of extension IDs:
Note that an extension must be listed here to be used by the application.
When you debug an application that uses one or more extensions on the desktop, the extension must support Windows or Mac OS X, according to the platform on which you're working. If you're building an application for the desktop, this should work as expected: the behavior of the extension during debugging will match that of the installed application.
If you're targeting a mobile or TV device, note that you'll still get the Windows or Mac OS X implementation of the extension when running in the simulator. This happens because the simulator is just that: a simulation of mobile or TV behavior, and not an emulation of the mobile or TV hardware.
The behavior of the extension when run in the simulator is up to the extension itself. It may provide a desktop implementation, or provide for a simulation of mobile and TV behavior when run on the desktop. Or, it may not run on the desktop at all. (If you're authoring an extension, see "Creating Extensions" below for details on how to implement these approaches.)
If your authoring tool doesn't directly support extensions, launch your application instead at the command line, using the adl tool that is packaged with the AIR SDK. Assuming you are launching with a debug SWF, adl will attempt to connect to any waiting debugger.
To launch with adl, simply place unpackaged copies of the extensions you are using in a single directory and pass that location to adl via the
-extdir argument. (A .ane file is a ZIP file, so you can unpackage one using an unzip tool.)
Note that, while unconventional, the name of the extension directory must end in ".ane". For example, suppose you receive the file SampleExtension.ane. To use it with adl, you could unpackage it into a directory with the same name. The relevant portions of the adl command line are then:
adl -extdir extensions app.xml
where "extensions" is a directory containing the unpackaged extension, i.e.:
. . .
Using the unpackaged form of the extension with adl makes it easier to develop an extension and an app at the same time. You can set up your extension projects to build to the .ane directory, and then pass that same directory to adl. (If you are using the extension but not developing it, just unpackage it one time, and you're all set.)
When it comes time to package your application, you can do so at the command line with adt. Like adl, adt accepts an -extdir argument. Unlike adl, adt requires that the extensions in that directory be complete, packaged versions. (The assumption here is that, at packaging time, your extensions are also complete and packaged.) For example:
adt -package -target apk . . . app.apk app.xml -extdir extensions
If you inspect the file set of the resulting application, it's easy to see that a portion of each extension is added, structure intact, in the new META-INF/AIR/extensions directory. For example:
Other packaging transformations are more complex, and vary by platform. Typically you don't need to be concerned with these details, as they are handled by the AIR packaging technology.
Developing an extension requires a number of skills, including API design, assessing implementation trade-offs, familiarity with the runtime extension API, and working with specific tools and properties of each targeted platform.
Developing an extension requires writing both ActionScript code, as every extension has an ActionScript layer, and native code on at least one platform.
ActionScript can be written using the freely available Flex SDK, Flash Builder, or other tools. The ActionScript portion of the extension will need access to the ExtensionContext API, which is part of the AIR AS3 API surface. Its definition is found, as is the rest of the AIR AS3 API, in airglobal.swc in the Flex SDK.
The native portions of an extension are written with the corresponding native development tools, and the form of the native portion is specific to each platform as well:
|Java Archive (.jar) or shared library (.so)
|iOS/iOS Simulator
|Static library (.a)
|Framework (.framework)
|Dynamic Link Library (.dll)
In general it's possible to use platform-specific structures and conventions, such as resource bundles on Mac OS X. Further details are covered in "Packaging extensions" below.
Your extension will be consumed as an ActionScript API, and that's often a great place to start your design work. Ultimately, the functionality you need to expose via this API will dictate what your implementation must or cannot do.
When developing your API, think about how it will operate across multiple platforms. Sometimes this is straightforward; if you're integrating legacy code, for example, it likely runs the same on each platform. However, when adding deeper platform integration, you may find that there's variation in the underlying platform support that can or should be exposed.
Many built-in AIR APIs address similar situations and use API patterns that you can adopt in your extension APIs:
- If your extension includes functionality that is operable on only some of its supported platforms, you can indicate this at runtime via an
supportsXproperties. The existing NativeWindow API, for example, declares both
NativeWindow.isSupported(are native windows supported at all) and
NativeWindow.supportsTransparency(are transparent native windows supported).
- If functionality varies between devices, you can indicate this at runtime via APIs that surface this variation. Applications can use this information to adapt their behavior. For example, the existing
Multitouch.supportedGesturesproperty reports to applications, at runtime, which gestures the underlying platform supports—something that varies between different mobile platforms.
- Make inoperable APIs fail gracefully. For example, the
NativeApplication.startsAtLoginproperty works only on the desktop, but is a no-op when used on a mobile or TV device. Thus applications can simply call it on all platforms, rather than adding the logic required to make the call conditional.
Extension APIs should also adopt ActionScript conventions where possible. For example, ActionScript APIs use events for notification; extension APIs should do the same. In some cases, this may require translating from different conventions used by the underlying platform APIs.
When you define your public API, compile it into a SWC using Flash Builder, compc, or an equivalent tool. You'll use this SWC again later when creating the extension package.
Extensions contain both ActionScript and native code, and the boundary between the two can vary arbitrarily. The boundary can also be different on different platforms. This flexibility can be used to your advantage, as the extension author, by allowing you to choose the most suitable implementation language for each portion of the extension.
Typically, it's advantageous to write as much code as possible in ActionScript as development in ActionScript is relatively fast, safe, and portable. In some cases, it may even be possible to write the implementation for specific platforms entirely in ActionScript, and extensions allow this.
There are reasons to move logic into native code as well, even beyond legacy code integration. Using native threading facilities, native code can be executed on background threads, thus improving application responsiveness. (More on this later.) Native code may also have access to algorithms that, while implementable in ActionScript, may be provided in optimized form by the OS.
When developing your ActionScript layer, compile a separate SWF for each platform that has a unique implementation. (If two or more platforms share the same implementation, you can reuse the same SWF.) Since each SWF defines the public API of the extension for the platform on which its used, it's important to be sure that each platform is defining the exactly the same public API. You may want to use a common interface definition to leverage the compilers assistance in achieving parity.
The platform-specific portion of an extension implementation can arrive on a target device in two ways.
In the first and most common approach, the implementation is bundled with the application. In this application-bundled deployment model, each application that uses the extension gets its own copy of (the relevant portion of) the extension. This approach also creates a tight binding between the version of the application and the version of the extension that are shipped together, thus avoiding compatibility pitfalls that could occur if one were updated independently from the other.
The second approach is device-bundled deployment. As the name implies, a device-deployed extension implementation is bundled with the device itself, and not with the application. This deployment model is necessarily available only to manufacturers, as only manufacturers can arrange to preinstall software on these devices. Extensions that use this model are typically built by manufacturers in order to provide ActionScript APIs for features unique to their devices.
Note platform implementations, not complete extensions, are either application-deployed or device-deployed. A single extension may contain implementations in both categories. There are two common cases:
- All application-bundled. This is the kind of extension created by a typical ActionScript developer, whether for their own or shared use. It contains platform-specific implementations for multiple platforms, and each implementation is bundled with each application that uses it.
- Device-bundled for one platform, with application-bundled default and simulation behavior. This is the kind of extension typically created by a manufacturer. The implementation for their device is bundled with the device. In order to support a better developer workflow, the extension also includes application-deployed platform implementations for Windows and Mac OS X that operate when running on the desktop.
Borrowing from AIR application packages, extensions include an XML-based descriptor file that declares various properties of the extension. When developing an extension, you'll need to create one of these yourself, using your editor of choice.
The descriptor starts with a namespace declaration:
<extension xmlns="http://ns.adobe.com/air/extension/2.5">
AIR 3.1 onwards, descriptor namespace 3.1 can also be used.
It continues with a mandatory ID and version number:
It allows several optional attributes that are also helpful in identifying the extension:
<name>Sample Extension</name>
<description>This is a description.</description>
<text xml:lang="fr_FR">C'est une description.</text>
<copyright>Copyright 2011, Sample Inc.</copyright>
(The description need not be localized, and the name and copyright can also be localized if desired.)
This is followed by an enumeration of each platform supported by the extension and important information relevant to each platform.
A platform implementation that's application-bundled declares the name of the corresponding library, plus an initialization function. (These are covered in more detail later.)
<platform name="Windows-x86">
The declaration for a device-bundled implementation is simpler, as the device already recognizes the relevant libraries and functions:
<platform name="Sample-ARM">
Finally, an extension can contain an implementation for the "default" platform. This implementation must be ActionScript only, since the actual platform isn't known. And it must be deployed with the application, since there's no way to guarantee a default bundled with all devices. It's represented in the descriptor like this:
<platform name="default">
When an application that uses extensions is loaded, ActionScript code is loaded from various sources in a prescribed sequence:
- Definitions for all built-in APIs are loaded. These are all of the APIs in the flash.* packages. Since these are loaded first, both extension and application code can depend on these APIs.
- The code associated with each extension used by the application is loaded. Note that an extension must be used by the application, as specified by a reference to it in the application descriptor file, to be loaded. (Device-bundled extensions, despite always being present on the device, follow this same rule.) Since extensions are loaded before the application, they cannot depend on any code in the application.
- Application code is loaded. Applications can assume that both built-in APIs and any APIs defined by extensions are loaded before the application itself is loaded.
Note that, due to this sequencing, an extension cannot use a framework like Flex unless that framework is embedded in the extension itself. Furthermore, only one extension can load such a framework. Otherwise, conflicts will arise when other extensions or the application try to load the same framework, resulting in multiple definitions for each class.
To avoid these issues, extensions should typically avoid dependencies on frameworks. Instead, think about the relationship between the extension and the framework from the application's point of view: What interfaces should an extension define so that an application can easily bind it into whichever framework the application has selected?
An extension can define its behavior not only when running on the target platform but also when being run in the simulator during development.
The simulator runs on Windows or Mac OS, so an extension can implement simulator support by simply providing an implementation on Windows and Mac OS.
There are a couple of scenarios that may apply here, depending on which platforms your extension supports and what kind of simulator support you wish to implement.
If an extension supports only nondesktop platforms, then any Mac OS X or Windows implementation provided need only work for simulation purposes. This implementation can be written entirely in ActionScript. It can be as simple (no-ops) or as sophisticated (returning recorded values, canned data, or data from alternate inputs) as you'd like.
On the other hand, if an extension also supports Mac OS X and Windows, then you may want to provide alternate simulator behavior in the Mac OS X and Windows platform implementations. Consider having an explicit mode setting to toggle between the real and simulated behavior.
The "default" platform implementation can be used to provide simulation support, since it also runs on Windows and Mac OS X if no specific implementations are provided for those platforms. However, note that the default will also be executed on all other platforms that don't have a platform-specific implementation, whether they are desktop, TV, or mobile. Typically it's more effective to use the default platform to provide a fallback (for example, with
isSupported returning
With a sense of the end-to-end picture of an extension in place, development can turn to coding. Extension coding leverages an ActionScript API, ExtensionContext, via which calls can be made from ActionScript to native code. It also leverages a native API, the runtime extension API, which is used at three distinct times: during extension initialization, during context initialization, and during execution of the extension functionality.
The native API is made available on all platforms in C. On Android, it is also available as a Java API.
Each extension is given an opportunity to perform one-time initialization when it is first used for a given invocation of an application. Note that this may or may not be at the time the application is started, and may not happen at all if the extension is referenced by the application but never used.
The initialization code is provided either as a function (C) or implementation of an interface method (Java). The corresponding name (function or class) is specified in the extension descriptor:
. . .
When using the C API, note that this call is taken to be an exported C symbol. On most platforms, you must explicitly mark it is as such in your compiled code via an extern "C" declaration and, possibly, an attribute such as
declspec(export). If you try to export a C++ function, C++ name mangling conventions will generally cause the exported symbol to be different from the function name, resulting in a mismatch that AIR cannot resolve. (You may be able to address this by specifying the C++ mangled name, but usually it's easier to turn off the name mangling via the extern declaration.)
When using the Java API, the initializer element instead gives the fully qualified name (for example, com.example.MyExtension) of a class implementing the FREExtension interface. The extension is initialized by creating an instance of this class—it must have a constructor that takes no arguments—and then invoking the
initialize() method on it.
Note that the extension doesn't have a mechanism to report errors that occur during initialization. If the initialization code can fail, then that state should be recorded by the extension, checked during a later call, and finally reported back to the application.
After initialization occurs, the ActionScript portion of an extension next creates one or more ExtensionContexts. An ExtensionContext is a binding between ActionScript and native code, consisting of three elements:
- A set of named functions. These are registered by the native code, and can be invoked from ActionScript.
- A reference to an ActionScript object that can be accessed from both ActionScript and native code.
- A reference to a native code structure that can be accessed only from native code.
The ExtensionContext API is designed to scale across several different models for binding between ActionScript and native code. At its simplest, a single instance of a single context is sufficient for an extension that exposes a handful of functions. For example, an extension that exposes calls to retrieve a device identifier and OS version could simply contain two registered calls, each returning one of these elements.
An extension exposing a broader set of functions might use multiple contexts to group related functions. For example, one context could return device information; another, user information. This allows the two groups to have their own initialization, their own set of registered function names, and so on. In this case, there's still no need for more than one instance of each context.
At the other end of the spectrum, an extension can be used to create a one-to-one binding between ActionScript and native objects. For example, an extension for PDF support might allocate a new ExtensionContext for each PDF document in memory. Each context has the same set of functions; the set of registered functions is essentially the set of methods available on the document class. Each instance of the context uses the ActionScript and native reference storage to maintain the link between the two objects. In ActionScript code:
class PDFDocument {
public function PDFDocument() {
_context = new ExtensionContext(
public function load( url:String ):void {
_context.call( "PDFDocumentLoad", url );
And on the native code side, taking the usual liberties with error handling:
FREObject PDFDocumentLoad(
FREContext ctx, void *functionData,
uint32_t argc, FREObject argv[]
) {
uint32_t length = 0;
uint8_t *url = NULL;
FREGetObjectAsUTF8( argv[0], &length, &url );
PDFDocument *pdf = LoadPDFFromURL( url );
FRESetContextNativeData( ctx, (void*)pdf );
. . .
Of course, these patterns can be combined as well: A single extension could use one extension for a block of simple functions, and another on a per-object basis, and so on.
In C, each context is initialized (and finalized) via a function registered in the extension initialization call. The context initializer must return a set of functions registered by name, and can optionally perform additional work. It can determine which set of functions to return by looking at its second parameter (
PDFDocument in the example above.).
In Java, a similar pattern is achieved via the FREContext abstract class. Extensions must create a derived class that implements the
getFunctions() call, and then return an instance of that class from
FREExtension.createContext(). (Note, however, that the derived class can't use other FREContext helper methods until after
createContext() returns and context initialization has been completed.)
With initialization and registration complete, ActionScript code can begin calling native code via
ExtensionContext.call(). ActionScript objects of any type can be passed to such calls. Native code accesses these arguments using a native API exported by the runtime itself.
Access to ActionScript from native code is centered on the FREObject type. (This is an opaque handle in C, and a class in Java.) Given a FREObject, native code can:
- Determine its type, via FREGetObjectType or dynamically casting to a derived class.
- Convert to an integer, floating point, Boolean, or string value.
If the object is not a primitive type like int, then native code can:
- Set and get properties of the object.
- Call methods on the object.
In order to create values for setting properties, arguments for calling methods, and return values from native functions, native code can also:
- Construct new objects from integer, floating point, Boolean, and string values.
- Construct new objects by invoking class constructors.
Taken together, these capabilities allow fairly complete access to ActionScript from native code.
Nonetheless, accessing ActionScript from native code can be tedious due to the need to handle error conditions, explicitly construct argument arrays, and so on. If you have to access a significant amount of ActionScript from native code—accessing properties, invoking methods, and so on—consider creating a helper method in ActionScript, and invoking that from native code instead.
Finally, note that FREObjects have a limited lifetime: They are only valid while a call into the extension, via
ExtensionContext.call(), remains on the stack. They cannot be held in native code across calls; you'll receive an error if you attempt to use them in this way. If you need to store an ActionScript reference across calls, save it in the ActionScriptData parameter on the relevant context. (If you need to store multiple references, put an Object in ActionScriptData, and hang references off of it as properties.)
The runtime API made available to native code is augmented with special-case accessors for ByteArrays, Arrays, Vectors, and BitmapData objects. These specialized APIs are designed to provide the fastest possible performance for types frequently used to manipulate or transfer large amounts of data.
In C, these APIs take the form of functions that require FREObjects of corresponding types. In Java, they're accessed via classes derived from FREObject, which add additional, type-appropriate methods.
The special-case accessors for Arrays and Vectors are the most straightforward, adding four calls to get and set the length, and get and set individual items. These APIs avoid the inconvenience and overhead of, for example, converting each index from integers to FREObjects and back.
The ByteArray and BitmapData APIs are a bit more complex, and in turn allow direct access to the memory backing the array or image. This allows ActionScript code and native code to share access to memory segments and images without requiring intermediate copies.
ByteArray and BitmapData access involves a three-step process:
- Acquire the object. This locks the underlying memory buffer in place, thus permitting access from native code without the risk of the garbage collector releasing or moving the memory.
- Access the object, reading or modifying as desired. During this time, other ActionScript methods cannot be accessed; they're locked out while the memory buffer is locked.
- Release the object. This invalidates references to the memory obtained in Step 1, and re-enables access to the rest of the API.
For BitmapData only, note that you should also use the invalidate call to inform the runtime as to which portion of the image is updated; this in turn is used to correctly refresh that portion of the image when it's next rendered.
In the C API, the acquire methods return structs which contain a raw pointer to the underlying memory, plus associated necessary information, like the width and height of the image. In Java, this information is exposed as object properties, and access to the memory is provided using an instance of java.nio.ByteBuffer.
Note also that these APIs are subject to the same lifetime rules as any other FREObject. Even if a ByteArray or BitmapData object is locked, references to it cannot be successfully held after the outermost call to an extension returns.
Native code is permitted to use any available platform threading facilities. This means that extensions can be used, among other things, to improve application responsiveness by moving long-running tasks off of the ActionScript execution thread. However, access to the runtime extension API is allowed, with one exception, only from the same thread on which the runtime invokes the extension. (Note that the runtime doesn't make any guarantees about which thread it will use to invoke the extension.)
If you do use an extension to move work to a background thread, there's a straightforward pattern you can use to work with this restriction:
- Upon invocation from ActionScript, gather all the data that's needed and save copies in native data structures.
- Spin up or acquire a thread to perform the work, and hand it the copied data.
- Upon completion, store the results to a native data structure, and notify ActionScript (see below).
- When ActionScript receives the completion notification, call into the extension a second time to retrieve the results, which are copied out of the result data structure.
The signaling mentioned in Step 3 is accomplished by calling FREDispatchStatusEventAsync (C) or FREContext.dispatchStatusEventAsync (Java). This call is the one exception mentioned above; it can be called from any thread at any time after the corresponding context is fully initialized.
When this signaling API is called, it causes a StatusEvent, with the specified code and level, to be queued for dispatch in ActionScript at the next opportunity. Typically, this means the event will be dispatched within one frame. The event is dispatched by the corresponding ExtensionContext object. At this point, since execution is by definition back on the ActionScript thread, it's safe (although optional) to call back into native code.
Extensions that allocate resources (memory, threads, file handles, and so on) in native code should take care to release those resources when they're no longer required. The runtime provides a pair of notification APIs that help manage resources associated with the lifetime of the context or the extension itself.
When a context is released from ActionScript, native code is notified by a call to the registered context
finalizer function (C) or the
FREContext.dispose method (Java). In ActionScript, this can be triggered either explicitly from
ExtensionContext.dispose() or implicitly when the ExtensionContext object is garbage-collected. Use of the
dispose() method is recommended, as there can be substantial delays between when an object is available to the garbage collector and when it is ultimately collected.
When an extension itself is shut down, native code is notified by a call to the registered extension
finalizer function (C) or the
FREExtension.dispose method (Java). Note that the runtime doesn't guarantee that these methods are called. On most platforms, the extension remains loaded as along as the application is running, and so the extension itself is never shut down.
The packaging step connects extension development with extension consumption. Everything that makes up an extension—the descriptor, ActionScript code, native code and resources for each platform—is all assembled into a single, ZIP-based archive. That package is then an input to the application packaging step.
Extension packages are created using the adt command line tool available in the Flex and AIR SDKs.
ADT is the same tool used to package AIR applications for deployment, and the options used to package extensions are largely the same. It begins by telling adt which kind of package you want to create, and the name of the output file:
adt -package -target ane MyExtension.ane \
Next comes the path to the extension descriptor, and to the SWC that defines the ActionScript API:
extension-descriptor.xml -swc ExtensionAPI.swc \
After this comes one or more sequences specifying the individual sets of files for each platform. For example, a simple extension supporting iOS and Mac OS might use:
-platform iPhone-ARM library.swf libextension.a \
-platform MacOS-x86 library.swf Extension.framework
Next is the path to platform descriptor(available only for iOS, AIR 3.1 onwards,optional). It specifies any additional linker options one may want to use on iOS.
-platformoptions platform.xml
Here, the library.swf file is the ActionScript layer for the platform; it must use this reserved name. In this example the same implementation is used on both platforms but, as discussed above, different SWF files could be used if desired.
This is a simple example containing only the minimally necessary library.swf and library or framework for the target platforms. (For the "default" platform, only library.swf is required.) Extensions can contain arbitrary additional files for each platform: images, sound, resource bundles, and so on.
The adt command above results in an extension with the following structure. It's straightforward to see how additional platforms are added, and where additional files are placed:
. . .
The root catalog.xml and library.swf are those taken from the specified SWC. If the SWC contains any additional files, they are also added to the package.
When an extension is consumed by an application, portions of the extension package are transformed and embedded in the application package. This all happens automatically during the application packaging step, and generally one needn't be concerned with the details. However, it can be useful to know where files land in the final package should you need to reference them, and there are some platform-specific details you may find informative.
Ignoring those platform-specific details for a moment, the default transformation for the contents of an extension package are simply to copy it, file by file, into the extensions portion of the application package. This section appears inside the META-INF/AIR directory, in order to avoid conflicts with any of the files included by the application itself.
For example, packaging the extension above for iOS would result in the following structure within the application package:
Note that all files outside the selected platform directory are embedded, so that they can be referenced by the extension if necessary. The extension can find this location, both during debugging and for a deployed application, using
Not surprisingly, only the platform directory matching the target is included; all other platform directories are, if present in the extension, ignored. The platform-specific portions of an extension should therefore not contain any references to the portions of the extension specific to other platforms.
Finally, note that in this example, libextension.a does not appear in the final package. It's subject to one of the platform-specific transformations described below, and therefore is not copied over.
On Android, two extension models are supported: Java archives for extensions developed with the Android SDK, and shared libraries for those developed with the Native Development Kit (NDK). Both are appropriate for some set of extensions; simply pick the one that best suits your use case. (One can, of course, use JNI to bridge between Java and native code on Android, should that also be necessary.)
On Android, resources such as images are compiled into each application and accessed via constants in the generated class R. This mechanism doesn't support composition; there is only one instance of R available. Android extensions can include resources but, to work around this limitation, they must be accessed via an API provided by the runtime.
To include resources in your Android extension, first place them in the "res" subdirectory of the Android platform directory, using the same naming conventions and file structure as for a regular Android application. At packaging time, resources from all extensions are merged into the resources directory of the main application. In order to avoid name conflicts, extensions should use a unique prefix for their resources.
These resources will be merged, as will the code in the Java archive, into the compiled dex and resources files of the main application. They can then be accessed via the
FREContext.getResourceId() method, which takes the desired resource ID as an argument. In other words, instead of accessing an image as, for example, R.drawable.background_image, use
getResourceId( "drawable.background_image" ).
Note that this API is available only in Java, as the Android resource mechanism is a Java construct, not expected to be accessed by extensions using native Android development.
The Java FREContext class also provides, on Android only, a
getActivity() method that returns the main application Activity, which in turn is required by a variety of Android APIs.
iOS is a unique platform in that it does not permit applications to be composed of shared libraries. On iOS, extensions instead take the form of static libraries that are linked into the main executable at packaging time. (This has relatively little cost at packaging time, as AIR applications packaged for iOS are already compiled to ARM code and run through the linker.) This is why the static library (.a) that is in the extension package does not appear separately in the resulting application.
On the other hand, it's conventional on iOS to keep resources, such as images, as external files that are separately loaded at runtime. Such resources can be bundled with the extension, at packaging time, will be copied into the standard application resources directory. This permits the regular NSBundle APIs to be used to load these resources, even from within the extension.
Note that the iOS implementation effectively flattens the namespaces used in both the executable (symbols in the static library) and in the file system (filenames of resources). As a result, extensions must take extra care to choose unique names in order to avoid conflicts. A prefix unique to the extension is typically sufficient. In particular, developers should take care not to use the default name Localizable.strings, as it would certainly conflict with the default Localizable.strings file used by the main application.
Starting AIR 3.3, support for extensions for iOS Simulator is also available. The process for creating extensions for the Simulator is similar to that for creating extensions for Device, except that the static library(.a) is compiled for iOS Simulator and the target platform used is iPhone-x86.
On Windows, the DLL and any associated files are simply placed, intact, in the Windows-x86 directory.
On Mac OS X, extensions take the form of a Framework bundle. This bundle is placed, intact, in the Frameworks subdirectory of the Application bundle. In contrast to the mobile platforms, this mechanism does support composition, and so features like resource bundles work without further changes or the risk of additional name collisions.
When compiling Mac OS X frameworks for use as an extension, developers should set the following options to support correct resolution of the dependency on the AIR framework in all scenarios:
- Add
@executable_path/../Frameworks, and
/Library/Frameworksto LD_RUNPATH_SEARCH_PATHS.
- Use weak framework linking and the flat namespace option.
Together, these options settings allow the application to load the correct copy of the AIR framework first, and then for the extension to rely on the already loaded copy.
Extensions enable a wide variety of new use cases, but like any technology it has its limits. When determining whether or not extensions are appropriate for your application, keep in mind:
- Extensions cannot directly alter the behavior of built-in ActionScript classes. For example, an extension can't modify how the Socket API works, or add support for a new codec for the Video object.
- Extensions cannot directly integrate interactive objects, such as native UI controls, with the display list. (Other items, such as native dialog boxes, may work, depending on the platform.)
If you run into limitations you'd like to see addressed in a future release, let us know on the web at ideas.adobe.com
AIR 3 release candidate provides a comprehensive extension mechanism. With it, developers can build two-tier applications. They can use ActionScript for core UI and logic. They can use extensions and native code for deep platform integration, legacy code reuse, and to achieve maximum performance.
Using an extension is similar to using any ActionScript library. Application developers can easily leverage extensions developed by others. Developing an extension requires knowledge of the targeted platforms and their associated development tools. The extension mechanism provides a flexible model, allowing the application developer to find an optimal balance and binding between ActionScript and native code. Extensions can make use of native facilities, including bundled resources, and a comprehensive extension API provided by the runtime for access to ActionScript.
Prior to extensions, developers had no choice but to wait for Adobe to introduce whatever capability they required of the runtime. Now, these limits have been removed.
Also be sure to check out the Native extensions for Adobe AIR page in the Adobe AIR Developer Center.


text:
List of Audio Applications
From Openmoko
Audio applications, music players (hamradio, midi, mixer, sequencer, tuner, audio-video editing, audio player, recorder, musical software).
|Openmoko Mediaplayer 2
Media player originally written for Om 2007.2.
|Qtopia Mediaplayer
Plays music.
Openmokast is a digital broadcasting application that can use a USB DAB/DMB device to receive mobile multimedia services.
Pythm is a media player frontend, designed to control mplayer or mpd with one GUI on the FreeRunner. As of writing, you need to download python-mokoui separately.
See also
Most of the video players also play audio:


text: This Week at State: March 24, 2017 By DipNote Bloggers on March 24, 2017 1 minutes read time Did you miss any key foreign policy developments this week? We've got you covered. Each week, DipNote will recap the latest U.S. Department of State highlights covering a wide range of global issues, events,… more


text:
The Digichord is Vestal's thinnest and most lightweight watch. The 41mm wide polycarbonate case is only 5.5 millimeters at its thickest point. That's not much thicker than a couple compact discs. The 24mm wide polyurethane strap with locking keeper holds the ultra-thin watch to your wrist. It's so lightweight that if you didn't get so many compliments while wearing it then you'd forget you had it on.
CASE: 41mm Wide ABS Plastic
BAND: 24mm Wide Polyurethane with Locking Keeper
BUCKLE: Stainless Steel
CRYSTAL: PMMA Plastic
MOVEMENT: 12 Hour Premium Digital with Date. Made in Japan
WATER RESISTANCE: 3 ATM / Suitable for Light Splash
WRIST: Medium


text:
NARAL Pro-Choice New York released a statement Thursday crediting the governor and the...
NARAL Pro-Choice New York released a statement Thursday crediting the governor and the new Legislature with making women's rights a priority.
The group also calls for the passage of the Reproductive Health Act, which would codify a woman's right to have an abortion and allows a woman to elect for one if the pregnancy endangers her health, regardless of how late in the pregnancy the health issue arises.
"The November election showed that women's reproductive rights were an issue that influenced the electorate, turned out voters, and ultimately shaped the election. We are heartened to see that key leaders in Albany seem to have gotten that message loud and clear," Andrea Miller, NARAL president, said in a statement.
"In recent statements, leaders across party lines have recognized the need to protect and advance women's reproductive rights," she continued.
"The Governor listed a woman's right to choose as one of his litmus test issues in supporting the coalition government. Senator Michael Gianaris, Chair of Democratic Senate Campaign Committee, credited women's issues such as reproductive rights as spurring victory for pro-choice Democratic candidates. Senator Tom Libous, Chair of Senate Republican Campaign Committee, also acknowledged that it's time for his conference to develop a 'pro-woman agenda.' And Senator Jeff Klein, head of the Independent Democratic Conference, has repeatedly said he believes that a coalition government can and should pass crucial reproductive rights legislation.
"The voters have spoken. If leaders in Albany have truly heard that call, they should act as soon as possible to pass the Reproductive Health Act."


text:
One of my favorite routes in Bay Area Bike Rides is the 102-mile Mt. Hamilton ride. This is my 30th year of doing this route; I've done it three times in 2010, probably 40-50 times in all.
Yesterday I did something I had never done before – and do not recommend – and that's ride the route clockwise. It doesn't take a Roads Scholar to know why it's something I've avoided doing.
The backside of Mt. Hamilton is steep, unlike the San Jose side. It has a section of 4.4 miles that varies between 11-15 percent. I counted my blessings as I reached the summit and reminded myself that while I had done it, it would probably be my last.
That's too bad because I otherwise enjoyed this direction more than the route in my book.
Of course, I put that route in not because I expect everyone to do the ride, but because it covers some great bike riding. You can pick a section that interests you and ride that part. Many riders go to the summit from San Jose and return.
One change to my route I recommend is to avoid Livermore streets entirely by taking the Arroyo Mocho Recreation Path. It goes from Murrieta Blvd. at Stanley Blvd. to S. Livermore Ave. The path offers a riparian habitat next to the Arroyo Mocho Creek, fed by Del Valle Reservoir.


text:
ELIZABETHTON – Building on the superior cardiovascular care it has delivered to patients in Carter and Johnson counties, the Wellmont CVA Heart Institute has opened an office in Elizabethton.
The heart institute is now seeing patients in the Elizabethton Medical Care facility at 1500 W. Elk Ave., Suite 102. Drs. Harold Alison and Joseph Bailey, who are board-certified cardiologists, are providing consults and follow-up care in a convenient setting for patients in these two communities.
"We have been privileged to have so many residents of Carter and Johnson counties entrust us with their cardiovascular care," said Dr. Jerry Blackwell, the heart institute's president. "We are pleased to accommodate them by taking care of their needs close to home with this new office. It demonstrates our commitment to provide high-quality care at the lowest possible cost with the greatest access."
The Elizabethton office is the 15th for the heart institute, which is the region's premier and largest cardiovascular practice. The heart institute has nearby offices in Johnson City and Erwin.
Earlier this week, the heart institute opened an office in Wytheville, Va., showing the commitment to improve the lives of patients throughout Northeast Tennessee and Southwest Virginia.
The heart institute, which also oversees the cardiovascular programs at Wellmont Health System hospitals, recently was named among the top 10 percent in the nation for cardiac care in 2013 by CareChex, a national ratings agency. Delivering the innovative care that has generated such a sterling reputation are 46 physicians, who practice in various aspects of care.
Two of the cardiologists who make a positive difference in patients' lives are Drs. Alison and Bailey, who bring extensive experience to the Elizabethton office.
Dr. Alison graduated from medical school at Columbia University and served his residency at the University of Tennessee and his fellowship at the University of Alabama. Dr. Bailey graduated from the James H. Quillen College of Medicine at East Tennessee State University, completed his residency at the University of Alabama-Birmingham School of Medicine and performed his fellowship at the Cleveland Clinic Foundation.
"Dr. Bailey and I look forward to assisting our patients with compassionate cardiac care that will enable them to live healthier and more productively," Dr. Alison said. "We are proud to be their caregivers, excited to be part of their community and grateful for the opportunity to see them in such a nice facility."
Tim Attebery, Wellmont's vice president of cardiovascular services, said the heart institute will be empowered to offer additional diagnostic services in Elizabethton because of its professional relationship with the Hopland family, which constructed the Medical Care building, He said the heart institute will be able to access other providers in the building that offer nuclear imaging and echocardiograms.
Should patients need advanced care, the Elizabethton office provides seamless access to Holston Valley Medical Center and Bristol Regional Medical Center, which have consistently earned state and national accolades for their expert, highly skilled care.
"Our combined resources reinforce that patients are in superb hands when they choose the Wellmont CVA Heart Institute," Attebery said. "We have consistently proven ourselves as the go-to organization for the best cardiovascular care in the region.
"We're delighted with this reputation but are constantly looking for ways to bolster our services for the benefit of our valued patients. This new office in Elizabethton meshes nicely with that plan of action."
To schedule an appointment with the heart institute's Elizabethton office, please call 423-282-5054. For more information about the heart institute, please visit www.wellmont.org.


text:
We can provide and optimise our services with the help of cookies. By continuing to use the site, you agree to the use of cookies.
Find out more
Okay, thanks
Für den Inhalt dieser Seite ist eine neuere Version von Adobe Flash Player erforderlich.
At this point, we like to give you some background information about us, the people behind Iono Music and about our plans and intentions for our label. But first of all we like to thank our loved wives and children for tolerating our follies. We also thank our label partners and friends for supporting and helping us with our work day by day. And we thank you, the Iono audience for sharing our music taste and supporting our artists by buying their stuff. Why we love what we do When we started our label work we have fixed our labels maxim: We will never release any track of music we do not really love - also when it goes into a more trendy or popular direction than that we obviously prefer. So, you may call our music progressive, psychedelic, full -on, electro, ambient, techno, house, old or new school - we simply call it high quality electronic music. We dont mind about styles and names, the music only has to express deep passion, individual qualitative power and strong musical skills of its producer. On those basics this music began to exist many years ago.Positive, more or less innovative trends, influences and movements will come and go like they always used to do. Of course we know that trance music can not re-invent itself anymore and some people say that in this music genre any story has been told already. But isnt that a fact which also applies to every kind of music style? Classic, Jazz, Pop, each music direction has been following its own pattern for years, decades and centuries - and has still its magic. Our label and all artists are working hard to keep the magic in this music alive for anyone who feels the same pleasure like we do. Iono Music was founded in 2005 by Matthias Sperlich. He was born in 1977 and resident in Berlin, Germany. He works as a professional vfx-artist for cinema and tv as a freelancer.
CREATIONPOOL - Agentur für Internet und Webdesign in Berlin - CMS, Flash, Online, Programmierung, Joomla, Webseite, Actionscript, Redaktionssystem, HTML


text:
Terry Teachout traces his interest in Louis Armstrong to the time his mother called him in from outdoors to see Armstrong sing (probably "Hello, Dolly") on the Ed Sullivan Show. His mother beckoned him with the sage admonition, "He won't be around forever."
By the same token, if you are in the vicinity of New York City, or visiting some time soon, I urge you to come in and see Terry Teachout's wonderful play, Satchmo at the Waldorf, now in performance at the Westside Theater. It won't be around forever.
The play follows up on Teachout's biography of Armstrong, Pops. Depicting Armstrong at the end of his career looking back, Satchmo at the Waldorf is a one-man play starring John Douglas Thompson as Armstrong. In the course of the play Thompson also portrays Armstrong manager Joe Glaser and, to a lesser extent, Armstrong critic Miles Davis.
The play is full of pain and humor. It is, in its own understated way, a meditation on appearance versus reality, or appearance and reality, and art and its audience. It is, to say it slightly differently, full of life. We saw the play last night and loved it.
Watching Thompson's performance, I kept thinking in the clichéd terms riveting and tour de force. I am in good company, as they are the words words that Nanci Callahan resorts to in her review of the play. Indeed, they are on the money, but they don't quite do Thompson's performance justice. Pete Hempstead escapes the bounds of cliché in his review with the inspired tour de megaforce. It is a brilliant, moving performance. What a privilege to see it with our own eyes.
The New York Times has posted a brief clip of Thompson performing the role here. Teachout and Thompson talk about the play in the Theater Talk video below.


text:
UK Road Signs – Order Pack is a set of 18 different signs used within the UK. These signs are beautiful looking with multiple effects used to make them stand out. Not only will you be getting these icons, you will be receiving the retina version of these!
What's included
- -Pack of 18 icons
- -Two PSD's
- -Normal & Retina version
- -PNG ready icons
Fonts required: Transport Set – http://www.cbrd.co.uk/fonts/


text:
×Want to shop in US Dollar? Try our Webshop specifically for North America!
3D Figurine Oliver Riedel
Get your personal Oliver - chose from 3 different sizes:
1:18 = 10cm, 30g
1:12 = 15cm, 90g
1: 10 = 18cm, 150g
The photorealistic 3D figurine is produced with a full color 3D printer and elaborately finished by hand.
Material: polymer plaster


text:
Renewable Energy - DC Disconnect, Overcurrent Protection and Error Signalling
As investments in the production of renewable energy continues to increase, the importance of protecting these new technologies with accurate overcurrent protection and integral error signalling builds. E-T-A's system solutions, DC disconnect switches, firefighter switches, circuit breakers, isolators, power distribution systems, electronic relays and emergency switches ensure dependable solutions for the latest state-of-the-art green technologies entering the market today including: photovoltaic technology as well as hydroelectric and wind power generation.
E-T-A works closely with companies in the renewable energy sector developing products including:
- Remotely controlled circuit breakers and DC disconnect switches
- Isolation and disconnection of high DC voltages in inverters and generator junction boxes
- Protection of stand-alone systems
- Electronic circuit protectors, ideally suited to battery-buffered DC 12 V and 24 V DC applications due to their low power consumption


text:
March 20, 2012, 11:19 am
New Nuggets JaVale McGee planking, blockititis
When the Nuggets traded Nene to the Washington Wizards they got JaVale McGee in the deal. Along with a young 7-footer that can sky, they also got a young fun-loving soul. Check out the vidoe of him planking. And with the condition known as blockititis
He's a hoot. Here's his Twitter handle @JaValeMcGee34 and http://www.facebook.com/javalemcgee
Here's one of what not to say to a woman in a club. He will definitely bring a smile to his teammates and fans.


text:
Thursday, May 29, 2008
yes the stash is alive!
5 comments:
Beeep Beeeep. haha.
Surfing posters unfortunately wont make a beach show up in Sadr city.
I'll send you some beach in the mail.
Love you.
- May 29, 2008 at 10:51 AM
- KurtMartiNick said...
Stop beeping your horn or I'll call the police. (do you have any there?)
- May 29, 2008 at 4:29 PM
i cant imagine you ripped....post pictures of that. hahahaha
i had a nice little online conversation with your mother today!
its so cute how much she adores you.
you're one lucky son!
i need to cry to you on the porch again. i sending you a plane ticket now so you can come listen to me and beat me up and couch. bahhahaha.
love you
- May 29, 2008 at 10:22 PM
- KurtMartiNick said...
When does the May 11th truce end in Sadr City? Who do you like in the Finals? The Shiites or Sunnis or the underdog Kurds. Another civil war we are in the middle of.
- June 1, 2008 at 6:57 AM
- Unknown said...
OMG!! at least you're trying!! To grow a stash, I mean! You furry little guy!
But 163 lbs, don't they feed you over there? What walls are you putting posters on? Where are you now? Do you actually, finally have a bed to sleep in? God, just gotta' love the military!! They need to do just a little more for you guys.
Sorry, I don't mean to rant, it's just that you guys are sacrificing so much, the least the Army could do is give you a place to sleep!!
Love you and wish you were here!!
Aunt Roo
- June 2, 2008 at 4:18 PM


text:
Download a Book Summary for Free!
Receive all of our new Business Book Reviews as they're released each month.
by Brendon Burchard
View Details
by Harold Burson
by Dan Barr, Krissi Barr
by Gary Vaynerchuk
by Robert Kegan, Lisa Laskow Lahey
by Dave Kerpen
by Bob Burg, John David Mann
by Carmine Gallo
by Chris Bailey
Sign up to receive in-depth summaries of the top business books of the year. Special: order now and save 15%.


text:
View in your browser
EDA Focus
IC, ASIC, FPGA Design and Related Fields
Tuesday January 28, 2020
Tech. Jobs at EDACafe.com
Search All TechJobsCafe Jobs:
Featured Ad
Featured EDA Job Opportunities
Senior Software Developer…Compilers…MA. -- EDA Careers -- Boston Area, Massachusetts
Senior Account Managers… FORMAL VERIFICATION...VALLEY -- EDA Careers -- San Jose, California
Senior Software Architect Internet -- EDA Careers -- San Jose, California
Salesforce Technical Lead East Coast -- EDA Careers -- Cherry Hill, New Jersey
Ecommerce Account Manager -- Bright Atlas LLC -- Miami Gardens, Florida
[ More EDA Jobs ]
Recruit From a Targeted Audience
Who do you want to hire today?
Using EDACafe and TechJobsCafe is the most powerful way to get your ASIC, IC, PCB, Analog, and EDA job positions filled at an extremely low price. Here is why:
Each of your jobs posted on TechJobsCafe also appears on EDACafe homepage. Visited by more than 60,000 ASIC, IC, and PCB professionals every month, EDACafe is the #1 electronics web portal in the world.
Each of your job postings is also sent to the 40,000 subscribers of our daily newsletter. This is an audience that may never visit any of the major job boards such as Monster, but we will bring your job opening to this passive job-seeking audience.
We have thousands of resumes from electronics professionals accessible to you if you sign up for a three-month membership.
This extremely targeted approach costs much less than your postings on Monster or Dice and is much more effective in finding you the right candidate.
Contact us today!
or fill out a
short registration form
and we will contact you.
Attention Job Seekers!
Only Enter Your Resume Once.
Save time when you're applying for more than one job position by posting your resume on TechJobsCafe.
After you enter your resume information it is automatically available each time you apply for a job. You also have complete editorial control of your resume information, and your resume is searched by companies who are looking for your skills and talent.
Visit our Job Seeker section now to get a personalized account
You are registered as: [_EMAIL_].
CafeNews is a service for EDA professionals. EDACafe.com respects your online time and Internet privacy.
Edit or Change
my newsletter's profile details.
me from this newsletter.
Copyright © 2020, Internet Business Systems, Inc. — 25 North 14th Steet, Suite 710 San Jose, CA 95112 — +1 (408) 882-6554 — All rights reserved.


text:
Search results
This interactive tutorial (Licensed Resource) teaches students the critical thinking skills they need to apply to their online experiences, including online safety, authenticating online information, recognizing online marketing ploys, protecting their privacy, managing online relationships and dealing with cyberbullying.
This interactive quiz, for Grades 6 to 8, is designed to increase students' knowledge and understanding of alcohol marketing aimed at youth.
This tutorial (Licensed Resource) aims to teach students essential digital literacy skills through simulating their favourite online experiences.
The three CyberPigs learn some important lessons about authenticating online information and observing rules of netiquette. They also learn how to distinguish between fact and opinion and how to recognize bias and harmful stereotyping in online content.
This interactive unit is designed to help kids between the ages of 5 and 8 recognize the marketing techniques used on commercial websites that target children.
In this game, designed for ages 8-10, the CyberPigs play on their favourite website and encounter marketing ploys, spam and a close encounter with a not-too-friendly wolf.
This tutorial introduces children, ages 7-9, to the concept of online privacy and teaches them to distinguish between information that is appropriate to give out and information better kept private – and to recognize how this may change in different contexts.
Young people – who have disposable income and a tremendous influence on family purchases – are the perfect target for marketers and advertisers. This section covers various issues related to marketing that targets children and youth.
Privilege manifests itself in a many ways. The fact that it is systemic rather than localized means that it is difficult to identify. Moreover, individual benefits of privilege may often seem small — but being outside of privilege can have staggering setbacks. This section helps identify how media and privilege intersect.


text:
Global Good Health: Providing Medical Supplies to Needy Countries
Danielle Butin is changing international health care through her organization, Afya, and countless teens are helping her along the way.
As she climbed into a tent in Tanzania for dinner in June 2007, 47-year-old Danielle Butin looked forward to swapping stories with fellow campers about the breathtaking countryside. Instead she found a British physician—who was on a short holiday from a three-month medical mission in Uganda—on the verge of tears. "She said that in her practice in England, where the patients were generally healthy, she has access to every kind of medical equipment she could possibly need," remembers Danielle, a divorced mother of three from Hastings-on-Hudson, New York. "Yet in Africa, surrounded by people in desperate need of urgent care, she felt helpless: Her office supply cabinet was completely bare."
Recently laid off from her position as an executive of a health care company, Danielle had decided to spend her unexpected free time fulfilling a long-held dream to visit Africa. Yet, while hiking and camping up and down the scenic coastline, her attention was continually drawn to the country's medical needs. "At almost every stop along the way I would hear a story from a traveling nurse or doctor about the lack of resources," she remembers. "I started thinking about finding a way to merge my connection to Africa with my health care background, but until that moment, I just didn't know how."
Listening to the doctor's story that evening made Danielle realize that something as simple as providing bandages (which are so scarce in some areas of Africa that doctors are often forced to wash and reuse them) would make a difference, and she knew exactly where she could get them. From all her years of working in various areas of health care—clinical, corporate, and academic—Danielle was well aware of the astonishing number of new materials regularly discarded by U.S. hospitals.
Global Links, an organization dedicated to making health care facilities more environmentally friendly, estimates that as much as 2,000 tons, or $200 million worth, of supplies are thrown away each year from operating rooms alone. One reason for the extraordinary amount of waste: the strict coding and regulations in place to protect patients.
If a surgical team lays out a supply of sutures, bandages, syringes, and gauze before an operation, all of the supplies in the room—even those never opened—must be thrown away afterward to prevent possible cross-contamination. Perfectly good medical equipment, such as X-ray machines, microscopes, and operating tables, becomes quickly outdated and replaced with cutting-edge models.
Danielle learned the same regulations didn't apply in developing countries, and that the equipment would be extremely valuable too. Unopened packages of rubber gloves, gently used incubators, and slightly worn delivery tables routinely discarded from American maternity wards would be welcome relief to laboring mothers in Rwanda, where physicians were delivering babies on lawn furniture and, in worse cases, dirt floors.
During her flight home from Africa, Danielle wrote up a list of all the people she knew in New York City hospitals who might help her acquire equipment. By the time her kids, Sally, Caroline, and Sam (then 9, 13, and 15), were back in school in September, Danielle was determined to launch a nonprofit foundation dedicated to collecting and redistributing discarded medical supplies. One month later she teamed up with Partners in Health (PIH), a Boston-based nonprofit that sends medical provisions to developing nations. "They started by giving me a wish list of items several hospitals in Haiti had specifically requested," Danielle says. With PIH's reputation and her own corporate health care connections to back her, Danielle found that persuading hospitals to donate was surprisingly easy. Just two months into her pursuit Danielle, who had expected to
run the entire organization from her home office, ran out of storage space.
In November 2007 Danielle had to make the tough call of dipping into the modest income she was living on—which came from a severance package and part-time salary she earned teaching—to fund a lease on a warehouse space. There, she finally had a place to stock the ever-growing flood of catheters, IV poles, bandages, sutures, wheelchairs, side tables, and stretchers flooding in from area medical centers. At the same time, she started the application process for nonprofit status for her foundation, which she named Afya, meaning "good health" in Swahili. She put the word out to friends and former colleagues—including people from the medical field, attorneys who had worked in health care, and people with experience founding other grassroots organizations—asking them to volunteer to work on Afya's board of directors.
Within weeks a group of five professionals rallied behind Danielle to pitch in with the advice and guidance she needed to run her new foundation. On a cold day in March 2008, after months of sorting and packing, Danielle, along with a group of a dozen volunteers—including her children, boyfriend Tracy Allan, neighbors, and friends—stood outside Afya's warehouse and watched as the lid was sealed shut on a packed 40-foot container. PIH was footing the costs of this first shipment, headed for Haiti, which would then be distributed by officials to several facilities. "When they closed that crate people were crying," says Danielle. "We all knew what was inside was going to breathe life into another place far away. I remember thinking, I never want this feeling to end."
Nearly three years later, in addition to the requests provided by PIH on an ongoing basis, Afya now also responds to individual hospitals, medical missions, and health clinics around the world. "I have no idea how they hear about us. It's word of mouth, really," says Danielle. To be sure that those making requests have the infrastructure to support the items they're asking for, Danielle conducts an informal screening process via telephone before supplies are sent. "I don't want to give a dialysis machine to a hospital that doesn't have a technician trained to run it, so I'll ask questions about what they already have, who their patients and doctors are, and what their plans are for the long term," she explains.
Facilities making requests also pay a procurement fee (a tiny fraction of the value of the medical supplies requested) and the shipping costs—a model Danielle learned from PIH. "The sum helps cover Afya's operating costs, including the warehouse, truck rentals, and staff salaries, but, more important, being willing and able to cover the shipping expense proves to us that these facilities are serious about receiving them," says Danielle. Afya also survives with financial support from direct donations and various fundraising events.
Thanks to a full-time staff of two (including Danielle), a group of more than 10 medical school interns, and around 450 volunteers—many of whom are teenagers pitching in at the warehouse for weekly sorting, labeling, and packing events—Afya has successfully shipped more than 700,000 tons of medical supplies to countries such as Cape Verde, Ethiopia, Ghana, Haiti, Malawi, Rwanda, Sierra Leone, and Tanzania. Hospital leaders are just as likely to call Danielle with a donation as she is to contact them with a request. Before discarding 15 slightly worn conference room chairs, Von E. Chaney, Memorial Sloan-Kettering Cancer Center's director of patient support services, contacted her. "Months later she told me that instead of being in a landfill somewhere, the chairs were being used to give people a comfortable place to sit while having blood taken," says Chaney. "Knowing this stuff is being repurposed makes my own job more gratifying."
Danielle's enthusiasm can also be credited with galvanizing kids to initiate their own projects. When Courtney Hughson, 13, learned that women in Malawi walk barefoot for miles to reach clinics to deliver babies, and the blisters they develop on their feet can expose them to deadly diseases, she spearheaded a rain-boot drive; within three months she gathered 200 pairs.
Danielle Polland, 17, collected over 1,000 pens through a drive at her Long Island high school to enable African doctors to keep medical records. After being told that patients' children often wait for hours outside Tanzanian hospitals with nothing to do, Alex Strauss, 14, acquired enough soccer cleats, balls, nets, and shin guards to start an entire league. There are so many kids rounding up the much needed ancillary supplies (like sporting equipment and kitchen utensils) requested by the hospitals that Danielle's 18-year-old son, Sam, produced a video about them. "The film helps spread my mom's work across the country so kids will know exactly what they can do in their own communities," he says. Sam's film is included in the information packets that Afya sends to teens interested in helping out, which tells kids how to start an official Afya Club— there are now a dozen in middle schools, high schools, and colleges nationwide. The packets also include handouts about the foundation, a list of the most-needed items, and directions on starting a fundraiser or collection drive.
During the five subsequent trips Danielle has made to medical facilities in Africa and Haiti, she's seen firsthand how the supplies are making a significant difference in the lives of patients, and the doctors and nurses who treat them. As word spreads about Afya's success, the number of requests has skyrocketed too. To meet the growing demand, she has ramped up collections and now receives supplies from as many as 40 different hospitals, nursing homes, clinics, and rehab centers in the greater New York area. Danielle's aiming to at least double the number of Afya Clubs in the U.S. and abroad to increase nonmedical supply donations. "Kids give Afya enormous support. When we say, 'here's a need,' whether it's funds or footwear, they're very creative about coming up with a way to fulfill it," she says.
There's another vision for the future that Danielle holds close to her heart: To get everyone, from young children to older adults, to realize they can repurpose almost anything—unused surgical supplies and hospital beds, rain boots and soccer balls. "It'll help create a world," says Danielle, "where nothing valuable ever goes to waste."
Originally published in the March 2010 issue of Family Circle magazine.


text:
Our commitments:
We guarantee the traceability of all
Learn more+
Our botanical beauty is easily assimilated
Learn more+
Our botanists put their passion to work
Learn more+
Our botanical beauty experts provide
Learn more+
Extraction of plant actives
At Yves Rocher we can tell you where all the plants and raw materials we use come from. Every ingredient can be traced because we make our own products from our own formulas which are developed by our scientists.
That means you can trust that our ingredients are effective and safe for you and the environment.
We formulate our products from botanicals because
Our botanists in Madagascar
Our botanists are constantly traveling the world for new botanicals with beauty enhancing properties. From Madagascar to Brazil we source our botanicals from all five continents and from more than 18 countries; always employing fair trade practices.
Our botanical sciences department then works to identify and isolate the active compounds of the plants that provide with visible beauty results.
With more than 50 years of botanical beauty expertise, Yves Rocher has trained beauty specialists ready to help you choose the best beauty for you and your skin, in-store, online or by phone.


text:
Dear Ari Emanuel: We're All Meeting On The Internet, Come Join Us
from the and-living-and-working-here-too deptWe recently posted about Hollywood super agent Ari Emanuel's ridiculous demands that Google somehow find the magic "stop piracy" button. That story is turning into something much more interesting. The next day, at the same conference, a Google exec, Susan Wojcicki, pointed out the obvious: that Emanuel doesn't know what he's talking about (she used a more diplomatic phrase, noting that he was "misinformed").
Emanuel has since shot back that he's not at all misinformed about the need for the geeks in Northern California to solve his problems:
I am misinformed about a lot — just ask my wife — but I'm not misinformed about this: One of our last remaining dominant American exports is our creativity, no matter how you define it, either as a story or as an algorithm. There is equal genius behind companies like Apple, Facebook, Amazon and Google as there is behind artists who create stories that resonate around the world. We need to protect America's intellectual property and Hollywood can't do it on its own. I understand that the onus is not entirely Google's, but let's stop talking at each other and get in a room with all parties to figure this out. To be clear, I don't want to rehash SOPA as we can all agree that was a reflection of Southern California's arrogance, and let's also not pretend that we're working together on this issue because we have Youtube channels together. This is a larger conversation. It's time for Hollywood, our government and Silicon Valley to step up and collectively resolve this problem. Let me know where and when and I'll be there.The problem, of course, is that his very premise is wrong. He's taking the position that we need to "protect" first, rather than just fix our business models. This is a very mercantilist viewpoint: where protectionism beats innovation. But we've got centuries of economic proof that that's not how you evolve and it's not how you innovate and compete. What you do is you figure out ways to add value and to embrace new business models. Any effort that starts from the default position that what we need is more "protection" rather than greater innovation is doomed to fail -- because that innovation is an unstoppable train, and the "protection" aspect doesn't work. So if you don't focus on the innovation, then someone else will, and you'll have wasted all your time, effort and money on a "solution" that simply drives your business somewhere else. To the place that has focused on innovation.
But, even worse, is his arrogance in thinking that this is a problem that requires "Hollywood, our government and Silicon Valley to step up and collectively resolve this problem." This is the same thing we've been hearing for months out of Chris Dodd and the Hollywood crew: it's time to get back into the backroom and craft "a deal." That's how they think, but it completely misses the point. This isn't about crafting a backroom deal, it's about recognizing the power of the internet, and the importance of the internet to people.
Every time a Chris Dodd or an Ari Emaneuel suggests a backroom deal between Hollywood, Silicon Valley and the government, he leaves out the people who actually matter: all of us, out here, on the internet.
And, to that point, if he wants to know "where" this larger conversation is happening: it's right here. On the internet. It's on news sites and social media sites. It's on Reddit and Twitter and Facebook. It's here on Techdirt and lots of other blogs. We live on the internet and this conversation has been happening for a decade. Ari and his buddies have always been welcome to join, so it's a bit disingenuous for him to suggest that he'll "be there" when we tell him where "the meeting" is. It's here. It's going on all around you and you've always been welcome to join. But you don't. And, no, I won't even get into the irony of him demanding a "meeting" when Hollywood did absolutely everything to keep the rest of the world out of the backroom meetings that led to SOPA.
Joshua Topolsky, the editor in chief of The Verge -- who challenged Emanuel, and was rudely told to "go sit down" and had Emanuel ask "where do you work?" -- has written his own response, in which he tells Emanuel he works on the internet:
What Ari seems to forget, and what maybe politicians and the film and TV industry seem to forget is the last time piracy was a flashpoint between the entertainment and tech industries, the problem was not solved by sledgehammer legislation. Or takedowns. Or yelling. It was solved by the music industry accepting that their old model was broken, and technologists figuring out a new way to do business. And that gets to the core of this problem for Ari. We didn't go back to the way things were after the RIAA sued college students — the industry changed.I'd argue it goes even further than that. We don't just work on the internet. We live and breathe the internet. It is our identity. Emanuel looks at the internet, and he doesn't get it. To him, it's just a version of television that doesn't pay as well, so that's not interesting. In his talk, he repeatedly demanded a business model that pays as well as TV. That's not how this works. Disruptive innovation doesn't wait until you go back and provide the legacy players with a business model that pays just as well as the old business model. That's not disruption. Disruption works because the legacy players are too shortsighted to see the trend lines, and so infatuated with their fat profits that they don't recognize the potential of the new mediums, and only seek to regulate against them becoming too pesky. The train companies pushed for legislation requiring all automobiles be preceded by a person walking on the road waving red flags.
He doesn't want to change his business model, and he will do anything he can to protect it — including altering the basic functionality of the internet. Pirating and Apple's resulting rise in the music business changed that business forever... and diminished its financial footprint. Entrenched companies that owned every part of the food chain suddenly discovered they were just another cog in a big wheel.
Ari doesn't want that anymore than the music industry wanted it, or traditional media wanted it. Ned Ludd and his machine wreckers didn't like change either.
But there is one simple truth that I really believe in, in life or in business: adapt or die.
You want to know where I work Ari? I work on the internet. Welcome aboard.
Emanuel is asking for everyone to come up with the next version of red flag laws for the internet. That's not how this works.
If he wanted a real conversation, it wouldn't be focused on the parameters of how do we set up protectionist, mercantilist barriers. It would be on how do we create more value and then monetize that value. And those conversations are happening all the time, all over the internet. He's welcome to join. He's always been welcome to join. But it requires doing a little actual working and living on the internet.
Filed Under: ari emanuel, copyright, innovation, internet, piracy, protection
Companies: google, william morris


text:
(In most cases, a product is unavailable because it has been discontinued by its manufacturer.)
Copyright ©2020. This site is protected by copyright. There are terms for its use. Send us Feedback on our site and your experiences. Our descriptions, pictures, and prices are mostly accurate, but cannot be guaranteed. Cookies should be enabled in your web browser for full site functionality (details).