How to destroy your startup in 15 easy steps
Photo: Nick Schumacher/Unsplash
I raised $500,000 at 19. I was on my way to change the world. Three years later everything burned down.
This post is not about how to shoot for the stars or run a company. Others are better at that.
This is about what not to do.
I’ve made every mistake possible. But ironically, I’m constantly meeting teams doing the exact same things that caused my first startup to implode. Everything I’m writing about I’ve experienced first hand through my own startups as well as various businesses I’ve been involved in. It’s been all my fault and this is my story.
Some of you will disagree with me. Others will have things to add. I’m happy to discuss in the comments.
Here’s my attempt.
ZUCKERBERG SYNDROM
My girlfriend didn’t know what I was working on for nine months. I slept with a chair blocking the front door. My phone was tapped. Corporate America and Uncle Sam were listening. Someone was going to kill me to steal the idea.
I really believed this. So I did everything possible (literally) to avoid getting feedback out of the fear of having our idea stolen.
 Three years and hundreds of thousands later, we released an alpha version to a modest 30 people for the first time. Everyone hated it. Our capital was gone. Our moral: zero.
I see this all the time. Startup founders hiding their ideas because of the fear that someone will steal it. Remember: no one cares about you. Your biggest issue is getting discovered. If someone steals your idea, that means you’re doing something right.
Because of this syndrome, most startups are wasting their time and money building products no one wants. Why? Lack of testing. The biggest mistake a company can make (product wise) is to avoid talking to and testing with potential and current users. Every day. It’s also one of the main reasons startup’s fail.
If you’re not constantly releasing and looking for feedback you’re either a) delusional (me) thinking too many people will sign up/buy your product and you won’t be able to scale b) scared that it’s not good enough (me) or c) someone will steal your idea (as I was).
A. SCALING
“Your priority, in short, is proving that people will use your product at all. If they won’t, then it won’t matter if you can’t scale. If they will, then you will figure out a way to scale.   — Guy Kawasaki [Emphasis mine]
I’ve done this and I’ve experienced this in the past three startups I’ve worked in. It’s completely delusional. If five out of five people tell you that they wouldn’t use your product (before you build), quit. If eight out of ten people tell you that they hate this feature and you empirically see that they’re not using it, kill it. Don’t assume. Always be testing.
More on feedback below.
b. TESTING
See point A.
C. STEALING(!)
No one will steal your idea. It takes time, money, skills and immorality to steal. Not everyone is born that lucky.
Most importantly, no one cares about your idea.
They’ll only start caring when there’s a massive amount of initial traction (50,000+ users). By then, you’ve already established a strong user/customer base and it’s too late for the others.
HIRING FOR WEAKNESS
Only hire for a strength that needs to be filled in your company. Never for a weakness.
Not once did any of the startups I worked in hire for a strength. I repetitively recommended hiring people purely out of loneliness, fear and scarcity repetitively. Each time it sunk us deeper.
But what does that mean?
Hiring for a weakness means that you attempt to fill a weakness in the fundamentals in your company by hiring for a weakness. Example: If you’re building a product and it’s not gaining traction and your company doesn’t have inherent fundamentals, hiring Ryan Holiday to sell your product won’t help. You can’t fight weakness with weakness.
However, if you have a rockstar engineering team and you want to add a marketing person to help take the product get to another level, then you’re adding a strength.
Hiring for weakness also means:
a. You hire a B+ player instead of a A+ player.
b. You hire people so that they go through the struggle with you, so that they share your fears and paranoia. Not so they execute on what’s needed.
c. Hiring someone to fill a position. Not to compliment the rest of the company.
d.  It means hiring someone because you think there’s no one else. Scarcity.
f. Hiring a client’s friend. Because you’re scared.
It’s ultimately about the fundamentals. If the fundamentals of the product and the team aren’t there, adding someone is just adding a weakness. It won’t help, because it’s not a strength.
PAINTER’S DILEMMA
Approving emails? One week treks. Our first wireframes? $40K and four months. Did we have a working product after all this? No. We failed.
The Painter’s Dilemma is when you’re so deep in the details of your project that you don’t even know what the idea is anymore. You’re blind. When you’re too deep you need help.
How to solve it? Stop. Talk to people. Get feedback. Iterate and build. Release. Breathe.
Repeat the loop.
The more feedback you get the healthier you and your product are.
FEEDBACK
I can’t emphasize this enough.  I never got feedback. EVER. Well, until the cash ran out. Oops.
If you’re not getting qualitiative and quantitive feedback/data everyday, the cancer will start.
It’s easy: speak to people, Google Analytics, send surveys. Just don’t hide from it.
This is the crucial and worth a dedicated blog post in the future.
COMMUNICATE
“Don’t talk to him, he doesn’t understand. He’s out of the picture next funding round anyways.” I hid everything internally. It was easy, we were in 5 different countries! Our developers were remote (I’ll get to that) and Basecamp was our only means of communication. In other startups, I wouldn’t included people from discussions because “it isn’t necessary. That isn’t their job”
New features, awful designs, conniving plans were all pushed through a funnel. I was the leader of the deceiving. Architecting a blue print to push my own delusional “never test and succeed” agenda. My style? The longer the email the less likely someone important will read it. What a strategy.
I don’t care if you’re a church, a tech startup or a non-profit. If you don’t have a system of communication in place that keeps everyone aware of what everyone is doing in the company, in real-time, for every milestone, everyday, you will die very soon.
Lesson: Live and breath Scrum.
SCREW LAWYERS
Lawyers are criminals.
I spent $15,000 on legal documents/fees we never used. Every entrepreneur/startup I’m involved with thinks lawyers are the first step to success.
DOCS
All the legal documents you ever need are available online. If you’re B2B, all companies that you’ll work with have their own standard LOEs, NDAs, etc., that they anyways steal from Fortune 500 companies. Request it. Then use it. B2C? Here.
BUT I NEED A TRADEMARK!
Unless you have 10,000 clients you don’t need to think about copyright or even the name. Prove the concept first. Worry later. If you do have to worry, those are very nice worries to have.
PATENT IT!
Patenting something that isn’t validated with at least 10,000 clients is moronic. Ironically, this is the only mistake my first startup didn’t follow through with (fully, at least).
DECISION MAKING
I was traumatized from taking decisions. Most startups never take decisions. In other statups I work in, decisions took weeks. People join startups for the reason of avoiding bureaucracy but everyone still does it. Why? Lack of trust and overview of the team, so they choke the process (have I suggested Scrum?).
The board should decide on the vision and the group should decide what to execute on by creating a backlog for the week. The team should then have the power to execute it. With a great communication process in place, teammates should be able to take decisions without reporting to anyone while keeping everyone updated with everything’s that going on, live. Have a flat structure to achieve this by using Scrum.
Let people do their jobs. Trust them. Don’t have a tedious review process as most startups do. Don’t suffocate the system. Empower your people.
Read Scrum by Jeff Sutherland on how to manage your team. Then read Team of Teams by General Stanley McChrystal for how to organize the information flow. Both books compliment each other perfectly.
THE BOARD
The ideal board is 3–5 people maximum if you’re a startup. Anything above that means that either no decisions will ever be taken (my first company) or someone has a hidden agenda and profits from a discombobulated board.
A business is not a democracy. Unanimous decisions don’t work and will never work.
Who’s should I put on the Board?
Only investors/shareholders who hold a large stake and are extremely active in the success of your venture.
INVESTORS
Smart Money vs Still Money
Just because someone is offering you cash almost always means youshouldn’t accept it.
Your investor can have the greatest contacts in the pharmecutical industry. She can be CEO of Merck. If she doesn’t have a massive network in whatever industry you’re in, it’s worthless. The money will be worth nothing. This is true 100% of the time.
Always onboard investors that can help you in your niche industry.
MEETINGS
This is my top 3 favorites. Most won’t agree with me on this.
I’ve never been to a meeting that has made me money/funded my venture. I don’t think anyone has. Has anyone ever handed you a check at a meeting? I doubt it. Today, it usually happens by wire-transfer.
Meetings are pointless. Every team I meet, consult for/work with all think that going to meetings is the most crucial part of business. Most importantly, the whole team should be there.  Travel is time and money expensive. Even if you’re taking a cab.
I would fly 10,000 miles for a 3 hour meeting and then fly back to Europe that same day. $30K. Gone.
Most of the discussion can be ironed out over email and FaceTime.
Ok yes, I agree. Meeting in person is important. But not until it’s necessary. Most of the time, it’s unecessary. And even when it is, it shouldn’t always be an excuse to leave work for a business lunch or to Shanghai for the day.
Avoid meetings. Get more done.
It’s a waste of time 99% of the time.
FOUNDING PARTNERS = YOUR SPOUSE
You will be married to your partners and investors for the next 7–10 years. Choose wisely.
Know your team. Speak to your investor’s enemies. Get references for everyone.
Don’t be a deceiver. Use Scrum.
WORKING HOURS
We worked 16 hour days. Yey! Startup life!
No.  Don’t believe me. It’s proven.
Working 18 hour days leads to a burn out, which leads to painter’s dilemma, then delusion, then deceiving others around you, then depression. Then it’s too late.
Ultimately, the more you work the more mistakes you’re prone to make. Mistakes made are mistakes that need to be corrected. Mistakes that aren’t correct can take up to 24x longer to correct than if they were corrected immediately.
But you can’t see that. You’re burned out. You’re in Painter.
PRODUCT / MARKET VALIDATION
Another reason I refused to test in the three product startups I was involved in was because “the ideas work successfully elsewhere. They will also work here.” Doesn’t work like that.
Just because you’re making a mishmash of several products that have product/market validation elsewhere doesn’t mean people are willing to useyour product. I have yet to meet a new founder who hasn’t claimed this.
In order for someone to switch to your product, your product needs to be at least 8x better.*
Is your product really 8x better than your biggest competitor? If the answer isn’t a clear yes, quit.
Read Hooked by Nir Eyal and Ryan Hoover for how to build habit forming products.
RECREATING THE WHEEL
“God gave you eyes, so plagarize.” —Michael Lewis
No need to re-create the wheel. Everything is out there already for a reason. Use APIs, read books (many books), steal functions, designs, ideas, marketing slogans, branding, on boarding processes, software, colors, clients, everything from other people/companies who are successful.
This doesn’t mean that you shouldn’t test it in your own environment. You must validate every single function that you put out there. Use the Lean Startup Kansan by Ash Maurya for this.
DILUTION
We gave away 51% for our first funding round. How much did we plan to keep when we “exited?” Think about that. It doesn’t make sense.
Startups do this all the time. If you retain 51% after the seed round, how much does the founding team plan to keep by Series B? 20%? If you take the average of what you got paid for equity after the exit + your salary you’ll be paying more in taxes with a minimum wage paycheck for the past 8 years it took you to exit. Might as well work in a shoe store.
If you don’t have the bargaining power (a validated product) to raise money with, quit.
GUYS IN SUITS
Our tech partners wore suits. That made us comfortable. They ended up quoting $100k. We ended up with nothing.
If you see tech people in suits, run.
OUTSOURCING
I lost well over $100,000 for our first version that was outsourced. We were smart enough to not learn from our mistakes so we found another team to outsource with. Another hefty sum gone. Only myself to blame.
I’ve had terrible experiences with outsourcing and great experiences with in-house development.
However, many products (we all use everyday) have found great success in outsourcing. I also know many entrepreneurs who outsource and are extremely succesful. While there are massive benefits, there are also downfalls. If you plan to, find a free consulting company that has pre-screened teams.
Either way, using Scrum increases your chances of success in-house or out.
YOUR TEAM
Entrepreneurs read about Steve Jobs’ management style and think he was a tyrant. So they curse at their employees and tell everyone that they are “shit.” They think that’s how a company should be run and that’s how teammates should be treated. Wrong.
Either way, that’s not how Steve Jobs did it. Steve Jobs empowered his team.  Because they are the best in the industry. He made them feel good. He challenged them and today Apple is Apple because of that.
On the other hand, I lied. Didn’t speak about the hard things and repressed whatever fear or worry we had. We were scared that someone would quit or that we would look bad if we showed our emotions in front of our investors.
You should always be able to tell your teammates all the fears and worries you have. Chances are, if you’re worried about something, everyone is worried about the same thing. Bring it up. Talk about it. I keep mentioning Scrum* because it encourages team members telling each other what’s bothering them and what’s impending the growth progress. This is key to not failing.
Not once, in any of the startups I was in, did I or other get credit for great work or for their ideas that ended up being implemented. Not once did anyone congratualte a teammate on a engineering triumph, a beautiful design or a new lead. Startups think “business is business. This isn’t a cute place to pat each other on the backs.”
 You should be holding each other up, helping one another and listening to the problems in the team. Because ultimately, you’re on the same mission.
The second the negativity flows in people become scared. They stop raising issues, telling you how they feel and how to improve the business.  Six months later, you’re on the street.
Empower your team. Congratulate people. Love each other. When someone screws up, tell them that, but also tell them how to improve and ask them why they think they screwed up and how to make their job easier.
You’re a team. Be one.
Believe it or not, I’m not affiliated with Scrum in anyway. I’m not even a Scrum Master.
When I reflect on all the stupidity I’ve personally done and the startups I’ve been involved in, I realize that the only thing I ever followed up through and executed with absolute perfection, were the things that eventually ended up killing us: not telling a soul what our idea was. Talking to lawyers. Partnering with bad teams. Hiring out of weakness. Going to too many meetings. No decision making system. Not using Scrum. Hiring people out of fear. Hiding from reality.
Mistakes are simple to make but hard to correct. They’re usually the first option that pops up. But as entrepreneurs we do thing because they’re hard, not because they’re easy.
Hard choices take a long time to get right. It takes guts, intuition, experience and lots of luck. But never settle. Never accept your situation.
Life can always be better.


I am a multi-disciplinary designer based in New York City.
1 Name:
Nika Simovich
2 DOB:
April 2, 1991 1:50pm
3 Birthplace:
Belgrade, Serbia
4 Current location:
Ridgewood, NY
5 Eye color:
Brown
6 Hair Color:
Brown
7 Height:
5'6 ¾"
8 Heritage:
50% Serbian, 25% Bulgarian, 12.5% Czech
9 Piercings:
Ears
10 Tattoos:
0
11 Favorite Band/Singer:
Easy Aloha’s
12 Favorite Song:
Xtal Aphex Twin, If You Leave Me Now Chicago
13 Favorite Genre of Music:
Soundcloud
14 Favorite Color(s):
this color
15 Favorite TV show(s):
Homeland. True Detective; Degrassi. Chopped; Diners, Drive Ins, and Dives; Dinner Impossible; House Hunters; WWII in Color;
Forensic Files; Twin Peaks; Mad Men
16 Favorite Movie(s):
The Beautiful Person, The Dreamers, Prisoners
17 Favorite Book:
1Q84 by Haruki Murakami, Kafka on the Shore by Haruki Murakami,
79 Short Essays on Design by Michael Bierut, The Virgin Suicides by Jeffrey Eugenides,
The Defining Decade by Meg Jay
18 Favorite Store:
Parrot Coffee Grocery, Woodlands Market
19 Favorite Number:
I like odd numbers, but I also like 2.
20 Favorite Cocktail:
Margarita
21 Favorite Cuisine:
Indian
22 Favorite Meal:
Vegetable curry, cucumber salad
23 Favorite Animal:
Cat, Kangaroo
24 Favorite Pizza topping:
I don't like pizza
25 Favorite Season:
Fall
26 Favorite Month:
November
27 Favorite Holiday:
Halloween
28 Favorite Flower:
Cactus
29 Sunny or rainy:
Rainy
30 Chocolate or vanilla:
Chocolate
31 Fruit or veggie:
Both
32 Night or day:
Morning
33 Sour or sweet:
Sweet
34 Love or money:
Love♥
35 Phone or in person:
Text
36 Poor & happy or rich & miserable:
Poor & happy
37 Looks or personality:
Emotional connection
38 Coffee or tea:
Coffee
39 Hot or cold:
Weather: cold, anything else: hot
40 Goal for this year:
Find a full-time job
41 Most missed memory:
I don't miss anything
42 Best physical feature:
Hands
43 First thought waking up:
Bother Dylan
44 Do you wanna get married:
Yes
45 Do you wanna have kids:
Yes
46 If so, how many:
1–3
47 Do you wanna go to college:
I went to college
48 What do you want to be:
Graphic Designer/developer
49 Do You Dance in the rain:
No
50 Do You Smoke:
No
51 Do You Drink:
Socially
52 Do You Shower daily:
Yes
53 Do You Like thunderstorms:
Yes
54 Do You Curse:
Sometimes
55 Do You Sing:
Only show tunes I learned in my fifth grade chorus class
56 Do You Play an instrument:
No
57 Describe Yourself in 3 Words:
Resourceful, bold, inquisitive
58 Speak any foreign languages?
Serbo-Croatian
59 Can you whistle:
Yes
60 Right or left handed:
Ambidexterous
61 Your bedtime:
When I'm tired
62 Biggest fear:
Cancer, mice
63 3 things you can't live without:
Internet
64 Color of your room:
White
65 Siblings:
1 older brother
66 Middle name:
I don't have one
67 Pets:
Moji the cat
68 Nicknames:
Nikarelli
69 Hobbies:
Working out, reading, surfin' the 'net, Sims
70 Best year so far:
2013
71 If you could be anywhere right now where would you be:
Where I am right now
72 Do you wear contacts/glasses:
Yes
73 Are you afraid of the dark:
Only if there are mice
74 Where is your dream vacation spot:
Australia
75 Was this survey good:
It was ok


{% extends "index.html" %} {% block content %}
Its so easy to use that even kids will be able to use it!
With easy searching and everything organized, you are more productive
With Markdownn support, its easy to write articles/ notes with rich text formatting


|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object javax.print.ServiceUIFactory
public abstract class ServiceUIFactory
Services may optionally provide UIs which allow different styles of interaction in different roles. One role may be end-user browsing and setting of print options. Another role may be administering the print service.
Although the Print Service API does not presently provide standardised support for administering a print service, monitoring of the print service is possible and a UI may provide for private update mechanisms.
The basic design intent is to allow applications to lazily locate and initialize services only when needed without any API dependencies except in an environment in which they are used.
Swing UIs are preferred as they provide a more consistent L&F and can support accessibility APIs.
Example usage:
ServiceUIFactory factory = printService.getServiceUIFactory(); if (factory != null) { JComponent swingui = (JComponent)factory.getUI( ServiceUIFactory.MAIN_UIROLE, ServiceUIFactory.JCOMPONENT_UI); if (swingui != null) { tabbedpane.add("Custom UI", swingui); } }
| Field Summary | |
|---|---|
static int |
ABOUT_UIROLE
Denotes a UI which performs an informative "About" role. |
static int |
ADMIN_UIROLE
Denotes a UI which performs an administrative role. |
static String |
DIALOG_UI
Denotes a UI implemented as an AWT dialog. |
static String |
JCOMPONENT_UI
Denotes a UI implemented as a Swing component. |
static String |
JDIALOG_UI
Denotes a UI implemented as a Swing dialog. |
static int |
MAIN_UIROLE
Denotes a UI which performs the normal end user role. |
static String |
PANEL_UI
Denotes a UI implemented as an AWT panel. |
static int |
RESERVED_UIROLE
Not a valid role but role id's greater than this may be used for private roles supported by a service. |
| Constructor Summary | |
|---|---|
ServiceUIFactory()
|
| Method Summary | |
|---|---|
abstract Object |
getUI(int role,
String ui)
Get a UI object which may be cast to the requested UI type by the application and used in its user interface. |
abstract String[] |
getUIClassNamesForRole(int role)
Given a UI role obtained from this factory obtain the UI types available from this factory which implement this role. |
| Methods inherited from class java.lang.Object |
|---|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
| Field Detail |
|---|
public static final String JCOMPONENT_UI
public static final String PANEL_UI
public static final String DIALOG_UI
public static final String JDIALOG_UI
public static final int ABOUT_UIROLE
public static final int ADMIN_UIROLE
public static final int MAIN_UIROLE
public static final int RESERVED_UIROLE
| Constructor Detail |
|---|
public ServiceUIFactory()
| Method Detail |
|---|
public abstract Object getUI(int role, String ui)
role
- requested. Must be one of the standard roles or
a private role supported by this factory.ui
- type in which the role is requested.
IllegalArgumentException
- if the role or ui is neither
one of the standard ones, nor a private one
supported by the factory.public abstract String[] getUIClassNamesForRole(int role)
role
- to be looked up.
IllegalArgumentException
- is the role is a non-standard
role not supported by this factory.
|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.


A tumblelog named XD had a post on adding nice half-icon overlays to Leopard stacks (the below image is from that post).
The log does not allow comments, so I’m blogging some minor improvements to this technique:
Handle any sorting
I want my Downloads
stack to be sorted by date added, not date modified as in that post. Just change the m
to an a
:
1
|
|
Note that I’ve named the icon ” Icon” with an initial space. This is so that I can use the same naming scheme with stacks that I sort by name (in my case, my home folder). The reason for using a consistent naming scheme is revealed below.
Hide the overlay icon in Finder
A necessary evil to the overlay trick is that you need to keep an icon file sorted at the top of the stack. To my knowledge, you can’t hide it from the expanded stack – well, you can (by renaming it to something starting with a .
, like .Icon
) but then it’s not overlayed…
You can, however, hide it from the Finder by toggling the file’s invisible bit. It will still display in the expanded stack (alas) and as an icon overlay (w00t). You can do
1
|
|
If you want to unhide it, do
1
|
|
However, it turns out that the next time the stack refreshes – that is, the next time a file is added, renamed or removed – it will notice that the file is hidden, and you lose the overlay.
Now, this is a bit too kludgy even for me, but I couldn’t resist. I made a folder action that is triggered when a file is added, renamed or removed, and that will show the icon, force a stack refresh, and then hide the action again. What this amounts to is that when the stack changes, you’ll only see a short flash of non-overlayness, and then the overlay is re-applied, and does not appear in Finder.
I didn’t particularly mind seeing the overlay icon my Downloads
folder, but the ” Icon” file next to the folders in my home directory was quite annoying.
The folder action is here: Peekaboo Stack Overlay.scpt
See this post for how to apply it.
This folder action explains why I used the ” Icons” (with an initial space) name in the Downloads
stack as well – the same folder action, with a hard-coded icon name, can be used for multiple stacks.
The code
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 |
|


22.2
The EPIRB Buoys
The ESTONIA was equipped with two modern EPIRB buoys (Emergency Position Indicating Radio Beacons) of type Kannad 406 F.
The last check of the radio beacons was reported to have been made about one week prior to the disaster by the radio operator. The check confirmed that the EPIRBs were in full working order and it has to be assumed that both were left in "switched-on" condition after the test.
Nevertheless, no signals from the two buoys were received in the course of the rescue operation.
22.3
The Rescue Operation
The investigation of the performance and success of those having participated in the rescue operation is not the subject of this report. Nevertheless, the rescue operation is a vital part of the ESTONIA catastrophe and therefore just the chronology reflecting the developments since the "first", weak Mayday message at 01.22 hours on Wednesday, 28 September 1994, until Thursday, 29 September 1994, shall be outlined.
As explained in Subchapter 22.1 it has to be considered likely that the "1st Mayday" had been transmitted already 30 minutes earlier, i.e. around 00.50 hours.
The now following information has been partly received from the Finnish part of the JAIC and has partly been taken from Enclosure No. 2 of the Finnish book "Uutinen Estonia". All times are in Finnish = Estonian time = ship's time. The SAR Log of MRCC Stockholm and the Alarm Log of ARCC Arlanda - attached as enclosures - are in Swedish time, i.e. Finnish time minus one hour. Accordingly the following vessels - all proceeding along the Finnish coast from East to West - have participated in the rescue operation and their tracks were plotted by the Finnish radar stations between Porkaalaa and Utö:SILJA EUROPA - plotted track see Enclosure 22.3.378
MARIELLA - plotted track see Enclosure 22.3.379
FINNJET - plotted track see Enclosure 22.3.380
FINN MERCHANT - plotted track see Enclosure 22.3.381
FINN HANSA - plotted track see Enclosure 22.3.382
WESTÖN - plotted track see Enclosure 22.3.383The plots begin as early as 20.59 hours (SILJA EUROPA) and show the tracks of the vessels throughout the entire rescue operation until the next morning at 07.00 hours or so.
Also SILJA SYMPHONY on voyage from Stockholm to Helsinki, thus sailing from the West to the East, had been plotted since 01.03 hours when she was still West of Utö. The tracks of most rescue vessels during the operation has been transferred on to one sheet - see page 642. This sheet even includes two unidentified vessels to the east respectively south-east of the casualty area.
On all available plotting sheets, however, ESTONIA is only shown at her casualty position, although it is stated in the report of the Coast Guard Section Turku - Skärgårdshavets Sjöbevåkningssektion Abö - dated 28.04.95 on page 3, at the bottom, that»From the moment of her departure Estonia was under the Finnish Coast Guard's radar surveillance, the same as the other vessels' traffic. The vessel disappeared from Utö's automatic radar follow-up at 01.48 hours. At the same time the vessel also disappeared from MARIELLA's and SILJA EUROPA's radar screens.«
The complete report is attached as Enclosure 22.3.384.
Note: According to the above information the vessels were tracked auto-matically (and apparently recorded by radar), although it is stated in the Utö log that "the target had been tracked by Utö radar only from 01.40-01.48 hours" and that "at 01.48 hours radar supervisor Eija Viiala lost the target from the screen". In another report put into the INTERNET already on 01.10.94 by Kari Ili-Kuha from Tampere, Finland it is stated: »According to today's papers the ship seems to have been in trouble already over one hour before the distress signal. A female radar operator on duty in Utö fort noticed that the ship had gradually gone astray from her normal route, so that by the time of the distress signal the ship was already about 15 km South off the course and the signal was weak. The operator was surprised that the ship had not called for help earlier if they had problems. The ship had obviously had both engine and electrical problems. It remains a mystery why the crew on the bridge delayed the alarm, didn't they realise how serious the situation was? In the aftermath this is just plain useless speculation, but had they acted earlier in giving the alarm both in the ship and over the radio the number of casualties would likely not have been as high as they are now.«
Since "Eija" is a female name in Finland, the radar operator Eija Viiala stated in the Utö log could be identical to the "female radar operator" mentioned in the INTERNET message quoted above, although accor-ding to the Utö log she tracked ESTONIA only from 01.40-01.48 hours, when ESTONIA's stern was probably just settling down on the sea bottom and her bow rose out of the water, thus ESTONIA could not have changed her position very much during these 8 minutes. Two alleged radar plots were received from the Finnish Navy in this respect which are shown below.
Apparently the Navy was more talkative in the early days as obvious from the quoted INTERNET message which is apparently based on a newspaper report. The complete message is attached as Enclosure 22.3.385.
In order to find out what the Finnish Navy records had on file, a meeting was held with Commander Vesa Ennevaara at the head office of the Finnish Navy in December 1998 and the results of the discussions are summarised as follows:»The 1994 radar system was based on the equipment from the 1980s. The software was not as comprehensive as the current one. The main difference was that the 1994 system did not record data in permanent memory, which the new system will do when fully implemented.
Tracking units, such as radar stations, aeroplanes and ships etc pick up targets and report all new objects to the next level op's centre. The acquisition of targets involves all military arms (navy, air force and army) as well as pilots, coast guard and customs. New targets are assigned a number ID and as soon as identification is possible, either by VHF or visually, the name of the object is determined. The new system will operate the identification process also by radar transponder codes, combined with the old system.
Tracking was done by one radar station at a time - feeding data to the OP's centre - until the target was formally "handed over" to the next tracking station. At the same time an object could be visible and followed on the screens of other tracking stations, as well, but they would not feed data into the system.
Tracking details were stored and transmitted in bursts from radar stations to the OP's centres. The data was stored in buffer memories. Overflow of data in a buffer memory would automatically cause deletion of the oldest data. Depending on the amount of data on each separate object this could mean anything from hours to maybe a full day or more of data remained in each buffer. The buffer for Estonia (if the ship was within range and was tracked at all, which according to Ennevaara is unclear) probably would have contained data all the way from Tallinn/Nayssaar, but no one thought to ask for it imme-diately after the accident. All old data was lost due to the lack of memory storage space and unavailability of such a software facility in 1994, because when the and rescue operation commenced much older information was quickly lost from the buffers since intense tracking at short time differentials will rapidly fill a buffer.
The area of interest to the Navy Command charged with synchronising the rescue efforts was narrow, comprising the area between Utö and Hangö only. According to Commander Ennevaara no one thought about saving historical tracking data from other areas in time.«Note: This is obviously wrong as far as the ESTONIA is concerned, because the plot received and which is titled "40H 28/09/94 ESTONIA" was sent by fax on the day of the casualty - 28.09.94 - at 16.45 hours to the Navy's head office, thus then the stored data must still have been available as also confirmed by the also received list of times/positions/ bearings which reportedly refer to the radar station Örö (between Russarö [Hangö] and Utö). While the times and positions are mostly reflected by the plot, the bearing/speed items do not make sense and are - according to the Navy - based on the Coast Artilleries' own system which they could not explain.
»Any ship could enter Finnish territorial waters at night, without being properly identified, and leave again - unless the manoeuvre was interesting enough to cause an investigation. After such a visitor had left, the buffer memory would be used again when needed and such historical data would be lost. Coast guard stations, responsible for shipping security, would sometimes call such targets (ships) to advise them if they were heading towards danger. In case there was reply a positive ID would have been established - otherwise none at all. This could be the case irrespective of whether a target was a "red" object, unless this was known in advance and the target duly picked up and identified by plane or surface ship.«
Note: "Red" objects are warships of "unfriendly" nations.
»Coast guard radars are not operated by dedicated and trained personnel on uninterrupted duty - like the Navy and Air Force radar stations are. Even when tracking, the operator may leave the radar set for coffee or lunch or even for watch duty, without a replacement at the screen. Coast guard, pilot and customs radars are commercial equipment, without the refined electronics of military equipment. Range and resolving power, as well as tracking accuracy are therefore inferior.
The most reliable plotting is always obtained by hand. Plots obtained from stored data is always less reliable and contains spurious data. This is due to the fact that stored data contains past, present and predicted data. The predicted data may be incorrect and will be corrected on the next sweep or data transfer sequence. Even a stationary target will thus from time to time show a vector although it does not move at all.
The Navy's Estonia track was obtained from stored "buffer data" and is therefore not entirely reliable, besides not having an absolutely reliable identification (name of the ship). Nevertheless, according to Commander Ennevaara the Navy is about 90% sure that it was the Estonia. The plot in question is layed into chapter 22.
If it was not the Estonia, it would be an unidentified vessel. The radar weather was said to have been very bad and the radio communications were frequently interrupted according to the Utö radar station notes.«Note: In any event, the radar observer Eija Viiala saw a radar target which she believed to have been the ESTONIA from the time she took over from Örö radar station apparently at 00.33 hours. Apparently she told the local newspaper shortly after the casualty what she had seen for more than 1 hour before the 'Mayday' at 01.22 hours, which makes it even more difficult to understand why the respective data should not have been secured although the respective data of all the other vessels were secured.
Commander Ennevaara explained instead that
»the radar range was only barely sufficient to pick up the site of the accident due to the distance and the very bad radar weather. The track, designated Estonia by the Navy, was named Estonia without any optical or secure identification of the target. The identity has been checked backward from the known location of the wreck by the Navy - but may have been an entirely different ship as well.«
Ennevaara offered that the radar operators may be interviewed and that the station logs be searched which, to his knowledge, has never been done so far.
Note: For time reasons it has also not been done by this 'Group of Experts".
In reply to a respective question Commander Ennevaara said that
»the Finnish Intelligence service in 1994 did not listen with the objective of locating the transmissions but in order to pick up contents of messages. Interesting messages would be transmitted to op's centres without confidentiality. (This of course must depend on the contents of the intercepted message, although Commander Ennevaara did not say so.)«
In a subsequent telephone interview the watch officer of SILJA EUROPA, Teijo Seppelin (the MARIELLA witnesses could not be reached), stated the following:
»- as far as he could see, the Estonia was never in front of SILJA EUROPA - but came up from the south-east. This track would be different from the Navy radar track designated Estonia - and would be similar to the one put forward by the JAIC. Seppelin said that the Estonia normally came up straight from the south-east, i.e. from what must have been the Estonia/Nayssaar sound and crossed the track of the SILJA EUROPA. One crew of the Estonia would arrogantly cross the SILJA EUROPA track close under the bow and force the Officer to pull back on the engines, while the other crew would always pass politely under the stern. This was in the summer when the SILJA EUROPA entered at Sandhamn and the Estonia at Söderarm.
- he does not believe that the Navy track is that of the Estonia. Neither does the officer (Capt. Ltn. Niemelä from Utö), who was in charge of the radar station, primarily because the Navy track follows the normal routing system, initially west then, west-south-west.
- he does not recall radio interruptions but remembers that the MARIELLA's inability to reach Helsinki Radio on VHF Ch 16 and MF 2182 was widely discussed afterwards. He recalls the Mayday signals were of distinctly different character, one very weak and the other quite normal in strength.«So much for the Finnish Navy.
While searching through the files of the public prosecutor in Stockholm a copy was found referring to a drawing belonging to an article which had appeared in the Estonian newspaper ILTA-SANOMAT on 01.10.1994. It shows the deviation of ESTONIA to the South of the normal route (see interview above of the Utö radar observer in the INTERNET message - Enclosure 22.3.385) and the apparent existence of another vessel in the vicinity of the casualty position, viz. the BALANGA QUEEN which had allegedly passed "very close" to the casualty position. On the above-mentioned copy it is handwritten in Swedish:
»If the BALANGA QUEEN had not been ahead of schedule and if ESTONIA had called for help when her problems actually started, then hundreds of lives could have been saved.«
»Why ESTONIA's emergency messages or other radio communica-tions were delayed and did not reach BALANGA QUEEN is still unclear.«
The (available) files of the prosecutor do not contain any more documentation in regard to BALANGA QUEEN nor do the (available) files of the Swedish and Finnish parts of the JAIC. The logbook page 2 is attached as Enclosure 22.3.386.
Consequently another INTERNET search was performed and under the date 29.09.94 the following was found:»Not that my opinion of Estonian seamen is much higher. The papers quote surviving truck drivers who had asked why their trucks were not chained to their places, stormy weather and all. "It's not necessary', they were answered. And there was an Estonian passenger ship, Balanga something, that was only 30 sea miles south of "Estonia" but didn't pick up the emergency signal while four Finnish ones did and went to help.«
Further inquiries revealed that the BALANGA QUEEN was a car/passenger ferry bareboat chartered by TALLINK, the ferry subsidiary of ESCO, the 50% shareholders of the ESTONIA. The ferry was trading between Travemünde and Tallinn and had an Estonian crew.
Her particulars are as follows:BALANGA QUEEN ex SCANDINAVIAN SUN ex CARIBE
9963 GRT / 4759 NRT / 2337 TDW
length: 134.45 m breadth: 21.87 m draught: 5.52 m
main engine: 20EW-Pielstick 16,000 hp - 21.0 kn.
built: 1968 by LMG, Lübeck
The ferry departed from Travemünde on 26.09.94 at 18.20 hours, i.e. based on a service speed of 18.0 kn she should have been abeam of Ristna (western tip of Hiumaa Island) at 22.30 hours plus 1 hour time difference = 23.30 hours and turned on a north-easterly heading towards Glotov buoy.
Between 00.00 and 00.30 hours ESTONIA must have passed BALANGA QUEEN at a distance of 12-13 nm, i.e. the vessels saw each other. As in all probability ESTONIA was already in trouble then, it would have been a matter of good seamanship and proper care for the passengers to ask the company vessel to standby in the vicinity and escort ESTONIA into the shelter of the Island Hiumaa, but apparently nothing the like occurred.
To the contrary - reportedly the master of the BALANGA QUEEN had offered help at some time which had been rejected by the Estonian Coast Guard. This information comes from a source in Travemünde who spoke to the master of BALANGA QUEEN after his return from the voyage in question. According to the report of the JAIC - Table 7.6 on page 107 - the ferry arrived on site at 14.31 hours only, i.e. when she was already on her way back to Travemünde. The early passing is not mentioned.
A further product of the above-mentioned INTERNET search for the BALANGA QUEEN is the LEONID BYKOV incident, because on the same page the following is reported:»To Dragon Fly and all other fans of Russian seamanship, a minor news item from today's Aamulehti, bottom corner of page 13:
On Wednesday night, an hour after "Estonia" had sunk, the coast guards of Jussar Lighthouse noticed a ship sailing off course towards underwater rocks. They tried to alert the crew with searchlights and radio messages in Finnish, Swedish and English. No response. The ship passed the lighthouse, averted the first rocks by sheer luck, then turned sharply to south and safety. After radio contact was established the captain of the "Leonid Bykov" explained that the fresh First Officer keeping watch didn't know any English, but when the radio messages continued, he figured out that maybe he needed to wake up the captain (who had made the safety move).
Earlier this month another Russian vessel, "Volgoneft 104", was in a similar situation near Jussar.«Further inquiries in the INTERNET revealed that the vessel is a "research vessel", owned by the Moscow River Shipping Company, which is owned by the Ministry for Post and Communication. The vessel is said to have 4540 GRT and was built in 1991.
The other vessel mentioned, the VOLGONEFT 104, is owned by the same organisation of the same type - "research vessel".
After initial problems, the copies of the logbook entries from Jussar Coast Guard Station have been received. This station is located about 18 nm east of Hangö. The entries read - office translated - as follows:»Time 0122 Phoned to operations centre [MVAK] regarding an unidentified target in position 59 degrees 46' P [longitude] 23 degrees 45' l [latitude], heading 265 degrees.«
»Time 0132 Enquired the position of Valpas [patrol boat?], it was east of Porkkala.«
»Time 0135 Tried several times to get contact via VHF-16 without result. The heading of the target still straight to Segelskär. AP [abbreviation of aluepäällikkö = district chief] is informed about the situation.«
»Time 0205 I tried to get in radio contact via VHF-1 without result. The reserves have been awakened.«
»Time 0225 RV-124 left the quay. As master Illman and as crew Englund and Lehtinen.«
»Time 0256 The target (cargo) turned in position 59 degrees 45'4 P, 23 degrees 31',31 to the south.«
»Time 0257 Achieved radio contact via VHF-16 with the vessel "Leonid Bykov" from St. Petersburg, on voyage from Vyborg to Pori. The name of the master Juri Chikov. According to the master the explanation for the odd heading was that the helm man did not know the position and did not understand English.«
»Time 0310 Commanded RV-124 to return.«
»Time 0344 "Leonid Bykov" left the territorial waters in position 59 degrees 41',8 P 23 degrees 29',5 l.«A further inquiry with Lloyd's Maritime Information Services has revealed the following:
»1. The Russian flag motor general cargo vessel "Leonid Bykov", of 4,096 tonnes gross, 4,540 deadweight, built 1991, has a draught of 3.16 m, a length overall of 138.40 m, and an extreme breadth of 16.75 m. Vessel's former name is "Volzhskiy-41".
2. With regard to her whereabouts on 27th to 30th September 1994, the "Leonid Bykov" was reported to have arrived at Vyborg, Russia, on 24th September 1994, then to have sailed from Vyborg on 27th September 1994. Vessel was then next reported to have arrived at Mantyluoto, Finland, on 1st October 1994.«It was subsequently confirmed by the port authorities of Pori (Mantyluoto) that the LEONID BYKOV arrived at this port on October 1st, 1994 and discharged 4326 ts of coal. Consequently it has to be assumed that this vessel had nothing to do with the sinking of the ESTONIA. However, it has been known for many years that the Russian Intelligence name their "research vessels", equipped for electronic surveillance and other activities, the same as their ordinary merchant vessels, i.e. while the research vessel is doing its job silently - not too far away - the ordinary vessel with the same name is attracting the attention of the authorities one way or the other by some spectacular activity as the merchant vessel "LEONID BYKOV" indeed did. The distance between the ESTONIA's casualty position and the "near-grounding" of "LEONID BYKOV" was about 65 kn.
So much for the vessels and shore stations having participated or not participated in the ESTONIA drama before, during or after the distress communication.Next the schedule of the rescue operation, the alert of the media, the notification of the government and other activities shall be outlined from the Finnish point of view:
Thereby following abbreviations are used:DVS = Disaster Victims Investigation
MRCC = Maritime Rescue Co-ordination Centre
MRSC = Maritime Rescue Sub Centre
STT = Finnish News Agency
TT = Swedish News Agency
TYKS = The University Hospital in TurkuIn detail:
01.22 Received weak Mayday, probably from ESTONIA.
01.24 The Mayday message from ESTONIA is picked up at least by the following stations:
MRCC Turku, MRSC Turku, MRSC Mariehamn, Coast Guard Kökar, Utö Fortress, the ferries: ANETTE, FINNJET, FINN MERCHANT, MARIELLA, SILJA EUROPA, SILJA SYMPHONY.
01.25 MRCC Turku calls Nauvo to instruct MRSC Turku to alert the coast guard vessel TURSAS.
01.24/25 ESTONIA informs SILJA EUROPA about her problems, the last communication with ESTONIA ends at 01.29m39sec.
01.29 MARIELLA tries to reach Helsinki Radio on VHF-Channel 16 and 2182 kHz , in vain. MRSC Turku (Nauvo) informs TURSAS about the casualty. MRSC Mariehamn alerts the commander of the rescue area, Pekka Kiviniemi, who arrives at the MRSC at 01.45.
01.31 MRSC confirms that MRCC Turku has been informed.
01.33 MRCC Turku alerts Mikko Montonen, who is on watch. He arrives at the MRCC at 01.40.
01.35 The bridge of ESTONIA is submerged. MARIELLA observes that the lights of ESTONIA black out. MRCC Turku transfers the alarm to the SAR-helicopter crew on standby. The alarm is confirmed by the crew.
01.42 SILJA EUROPA relays the distress call of ESTONIA by mobile phone to MRCC Helsinki (after they had tried to reach them in vain on channel 16 and 2182 kHz). MARIELLA informs Helsinki Radio simultaneously.
01.45 MRCC Helsinki informs MRCC Turku that they are aware of the distress case.
01.47 SILJA EUROPA in communication with Helsinki Radio on channel 16, they are going to transmit a PAN PAN message.
01.48 ESTONIA disappears from the screen of the Utö radar station. This is also observed by MRCC Turku and MRSC Mariehamn. MRCC admonishes Helsinki Radio to transmit a "Mayday relay" message on channel 16 instead of PAN PAN.
01.50 Helsinki Radio begins transmitting the PAN PAN message on channel 16.
01.52 MRSC Mariehamn informs MRCC Stockholm about the casualty (this was recorded in Stockholm at 01.55).
01.57 MRCC Stockholm calls MRCC Helsinki and offers help. They are informed that MRCC Turku is co-ordinating the rescue operation.
01.58 MRCC Stockholm calls MRCC Turku, they are brought up-to-date and are requested to send helicopters. MRCC Stockholm alerts ARCC Arlanda and requests the activation of all available helicopters.
02.00 M. Montonen (MRCC Turku) calls for the first time at Commodore Raimo Tillikainen's home at Espoo and informs him about the Mayday call. The second call follows about 5 minutes later when the sinking of the ferry is already reported. Tillikainen advises that he shall proceed to Turku.
02.03 Heikki Himanen, on standby service, arrives at MRCC Turku.
02.05 MRCC Turku appoints Esa Mäkelä, Master of the SILJA EUROPA, as Commander-on-scene of the rescue operation.
02.06 MRCC Turku informs MRSC Hangö about the casualty.
02.07 The Swedish helicopter Q98 is alerted in Visby.
02.10 Helicopter Q91 is alerted in Ronneby.
02.12 MARIELLA is sighting lights, lifevests, lifeboats, liferafts.
02.15 MRCC Turku informs the District Emergency Centre Turku.about
02.15 The serviceman of TT-Stockholm calls the serviceman of STT-Helsinki and requests information about the casualty. STT knows nothing. Some minutes later TT-calls again. The serviceman of STT phones MRCC Turku and receives the respective information, informs the manager of STT and puts into motion the alerting of the media, draws up a flash message which is transmitted at 02.43.
02.18 MRCC Turku requests MRCC Helsinki to call the standby helicopter crew on standby.
02.20 MRCC Turku appoints Utö as evacuation centre. Vice Commander Simo Pitkänen arrives at MRCC Turku.
02.21 MRCC puts on alert the standby helicopter. (at 03.36 hours the helicopter departs from Helsinki).
02.30 MARIELLA, at the casualty position, confirms that the ferry sank and that passengers are in the water, drops liferafts into the water, observes one person in a lifeboat, at 02.34 MARIELLA reports that several persons are in the water. Super Puma helicopter departs from Turku airport. MRCC defines casualty as "large casualty" and puts into motion the respective alarm, a/o the leading group of the rescue area is called to the MRCC.
02.36 MRCC Turku requests the SAR Centre to send one helicopter, subsequently - at 02.52 - to send more. According to the SAR Centre the first contact was at 02.50.At 02.58 the SAR Centre is requesting the Airforce to send as many helicopters as possible, as soon as possible.
02.43 STT-Flash: "ESTONIA capsized and sank. Lifeboats and people in the sea."
02.44 SILJA EUROPA arrives at the casualty position.
ca. 02.45 A propeller plane flies over the liferafts.
02.50 MRCC Stockholm contacts the Estline representative, Mats Björnudd, and asks for the passenger list.
02.55 MRCC Helsinki is asking MRCC Tallinn for information about the passengers and is informed that ESTONIA sailed from Tallinn on the previous evening with 679 passengers and 188 crew members. Helsinki does not inform Tallinn in detail about the casualty, only that something has happened and that people are in distress.
03.00 MRCC Stockholm offers 2 helicopters from Denmark.
03.05 The first helicopter, a Super Puma OH-HVG from Turku, arrives at the casualty site, is at first searching for people in the water, in vain, is then searching the liferafts. By 04.15 four persons have been winched up, landed on SILJA EUROPA, whereafter the helicopter returns to Turku for refuelling and to pick up another surface rescuer.
03.08 MARIELLA rescues 6-7 persons by means of her own raft.
03.15 The transport air fleet of Uti is alerted.
03.30 MRCC Helsinki reports the casualty to the watch officer of the border police. He contacts MRCC Turku at 03.40 and receives the latest news. He alerts the commander of the border control and the Government.
03.35 *MRCC Turku informs SAR Tallinn that no further search vessels are required.
03.39 2nd flash message from STT: The sea watch Turku was alarmed at about 02.00. By 03.00 some persons were found in the sea. On the ferry there were 679 passengers and 188 crew members.
03.49 STT: at 05.00 press conference at the police headquarters Turku.
03.50 The first special news by Radio Finland, thereafter up-date reports every half hour.
04.05 *MRCC Helsinki informs SAR Tallinn that no further search vessels are required.
04.15 Commodore Raimo Tillikainen arrives at the MRCC Turku. The helicopter crew of Rovaniemi's watch fleet is alerted.
04.28 STT: Up until 04.00. 7 persons rescued.
04.30 Text TV is from now on continuously reporting about the casualty.
04.38 The first helicopter of the military forces (HS-14X-92) departs from Uti.
04.40 The watch officer of the border guard staff is reporting the casualty to the safety adviser of the Government, who re-checks the facts with MRCC Turku and who calls the Speaker of the Government at
04.50. He in turn informs the Prime Minister at 04.55. The members of the Government are informed up until 05.40.
05.00 Press conference at police headquarters Turku. News from Radio Finland: A more detailed telegram and a telephone interview with Per-Erik Cederqvist, information manager of MARIELLA, who reports that a Swedish passenger, interviewed by him, has said * According to the book by Andi Meister "The Unfinished Logbook". that the casualty occurred very quickly. Shifting of cargo might have caused the casualty. The question whether all people could have been rescued is answered with: hopeless.
05.35 STT: According to doctors, the situation of the people in the water is almost hopeless due to hypothermia.
05.40 STT: It is feared that about 850 people have died, because up until 05.00 only 10-20 were picked up.
05.50 The Estonian coast guard reports to MRCC Helsinki that a plane from Estonia is flying to the casualty position. MRCC replies that the plane is not needed, it would only disturb the helicopters.
06.00 Radio Finland News, among other things an interview with Raimo Tillikainen, telephone reports from Stockholm and Tallinn. First news from Radio Mafia, thereafter news every half hour. MTB/BBC News: ESTONIA sank within 5 minutes, 677 passengers and 188 crew, of which 25 rescued, presumably several hundred drowned. "Uncertainty about the cause, but shifting of cargo is possible."
06.14 MTV 3 / Good morning, Finland: Launi Karhuvaara: "Information about the sinking, 640 passengers and 188 crew, about 20 rescued, a photo from Sandell, reporter from Turku, who just returned from the press conference, VIKING SALLY in the background, Sandell about the reasons: The rescue people say, in case of blackout such a large ferry cannot be controlled in a storm, probably the cargo shifted, the list increases and the ferry capsizes! Interview with Cederqvist from MARIELLA: They have picked up 12. I am fearing the worst, it looks bad, hundreds died. Everything happened very fast, maybe in 5 minutes only."
06.38 MTV 3 / Good morning, Finland: Chief pilot Hartikainen from the helicopter service takes off with a cameraman from MTV in order to film on site. In the studio remains Kristian Rehuström from the Finnish Rescue Service who stayed all morning.
07.00 The first special news from TV 1 from Uleis-Radio (TV - Radio), logo of ESTONIA in the background, report from Turku: distress call, chart, picture of press conference, interview with Raimo Tillikainen. News from Radio Finland: Interviews with- Raimo Tillikainen -
Antti Jääskelainen
- Jarkko Miettinen (Utö)
- Juha Niinikowski (University Hospital, Turku)
- Esa Mäkelä - SILJA EUROPA
- Cederqvist - MARIELLA
- Ulla-Maija Määttänen from Tallinn (criticises the bad information policy of Estonia).
07.10 TV-Nytt: The first Swedish news (in Finland)
07.30 MTV 3 / Good morning, Finland: News/Telegram: "Cause of the casualty possibly shifting of cargo. 28 trucks on the ferry." Government in special meeting.
07.35 STT: According to information from Stockholm most of the passengers are Swedes, 3 Finnish passengers, 1 Finnish crew member.
07.56 MTV 3 / Good morning, Finland: Raimo Tillikainen in a direct telephone interview.
08.13 SILJA EUROPA reports to have rescued about 90. At 09.19 MRCC Turku informs Stockholm that about 90 were rescued.
08.15 MTV / Good morning, Finland: Direct telephone interview with Lennart Meri (President of Estonia), picture in background: "I received the first reports at about 03.00. I am thankful that the Finnish rescuers have been so effective and active."
08.24 STT: Survivors are continuously being brought to Utö. According to Lieutenant Miettinen they are shaken and cold, hardly remember the casualty and are unable to report how they got into the water.
08.25 STT: According to the doctors and rescue crew the situation for those still in the sea or in the ESTONIA is hopeless.
08.44 MTV 3 / Good morning, Finland: A direct telephone interview with Raimo Tillikainen: 90 rescued. Lauri Karkuvaara: 90 in such a short time? How is this possible? RT: The rescue operation is carried out effectively, a plane is guiding the helicopters all the time. At 08.56 from Turku: a picture is shown of a patient being brought from a helicopter into Turku Hospital (the first action picture on TV).
08.54 STT: The Finnish Government has been informed, has agreed the co-ordination of the activities, has ordered the rescue organisations from Estonia and Sweden to come to Finland and has nominated a working team of 4 Ministers (Pekkarinen, Norrbach, Huuhtanen, Jää Heenmäki). According to the Minister of the Interior, Pekkarinen, the rescue operation has gone well up to now.
09.00 The last survivor is brought to Utö. A press conference at the police headquarters Turku.
09.00 Yle TV 1 Extra News: 90 rescued, the reason for the sinking is unknown to us. Apparently the ferry sustained a bad list after the trucks had shifted. Interview with Raimo Tillikainen. A telephone call from Ulla-Maija Määttänen from Tallinn, the speaker asks: "This casualty will raise serious questions about the safety of Estonian shipping. Has this already been mentioned?" Ulla-Maija Määttänen reports about the ferry traffic to Tallinn, "the ferries are all Swedish, i.e. it is for sure that subsequently the seaworthiness of jumbo ferries shall be discussed." Yle's first picture of the survivors: a Swedish helicopter at Turku Hospital.
09.10 TV-Nytt: Interview with a Swedish helicopter pilot refuelling at Mariehamn.
09.35 STT-Ako: Government is shaken. Ahtisaari expresses his sympathy to Lennart Meri. After Ako also Bildt expresses his appreciation to the Finnish Authorities for their well organised rescue operation. "The Swedish rescue units found good working conditions, in that respect everything went well according to the circumstances", said Ako.
10.00 Press conference of the Finnish Government in Helsinki.
10.03 STT: A group of volunteers from the Finnish Red Cross and a psychological organisation commence working.
10.05 STT: According to Pekkarinen the co-operation with the Swedish Authorities is very good. Pekkarinen reports that the Estonian Authorities were informed at 02.00 by the Finnish Authorities. The flow of information is functioning well assures the minister.
10.11 STT: According to Norrbach the rescue operation has gone well up to now. Norrbach warns not to draw too early conclusions concerning the ferry traffic between Sweden and Finland.
10.14 STT: Bildt expresses his thanks to the helicopter crews for their good performance.
10.22 STT: Press conference of the Finnish President, whereby, among other things, also the contacts to the King of Sweden and to the Estonian President are reported. Both thereafter expressed their thanks to those participating in the rescue operation.
10.44 STT: The Ministry of the Interior orders a flag-mourning day for Finland, in Estonia it is a mourning day.
11.00 Yle TV 1, News: Interview with Raimo Tillikainen (taken at about 10.00): Is it possible to still find survivors in the afternoon? RT: I hope so. The first interview with relatives in Stockholm harbour; an interview with Lennart Meri (the most quiet and devout part of a rather hectic news broadcast). The flow of information between Finland, Sweden and Estonia has gone well, the Estonian Authorities were informed already shortly after 02.00. Statements by Esko Ako and Mauri Pekkarinen.
11.26 STT: One of the survivors reports at Utö Fortress "that he was awakened, in his cabin near the car deck, by loud banging noises from this deck".
12.00 MTV 3: The first interview with a survivor (Karmet). The first of the bodies are landed at Utö. Press conference in the police headquarters Turku.
12.46 STT: A rescued Estonian crew member tells TT that "one of the car doors in the bow could not be closed during the night. The door which was used by the cars let water in. According to Sillaste the ferry heeled over only thereafter."
13.00 Yle TV 1, News: More than 100 have survived, bodies found so far: 5. An interview with was Vassili Märtson, Estonian, just being transported on a stretcher into the hospital of Tammisaari informs about the causes of the casualty: "A crew member of the ferry told me that one of the bow doors could not be closed during the night and through that water was flooding on to the car deck." STT: ".... the reasons for the casualty are still completely in the dark."
13.20 TV-Nytt: The cause of the casualty: "Slarvigt lockt, lucka", i.e. a care-lessly/or sloppily closed lock. The first interview with Vihlo Itäranta (from the hospital in Tammisaari). 13.25-15.30: The first helicopter flight with journalists to the casualty site and to Utö.
15.00 Yle TV 1: "According to an eye witness from the crew the cause for the casualty was a bow door left open. According to the eye witness it was not possible to close the door and before midnight water started to flow on to the car deck." An interview of Sillaste.
17.19 STT: Report by a Dutch truck driver that the trucks were not secured.
19.58 STT: The Prime Ministers decide on mutual co-operation. Finland and Sweden are to send experts to the Estonian Investigation Commission.
20.40 STT: Swedish inspectors of Sjöfartsverket ascertain defects on the ESTONIA on Tuesday evening (overaged lashings, worn sealings, no lashing manual). "The deficiencies, however, were not so big that they could have caused such a large casualty. We are of the opinion that the ferry was well maintained."
22.24 MRCC Tallinn is requesting MRCC Helsinki to find out whether Capt. Avo Piht has survived. Helsinki asks Turku. There is no information on Piht.
Thursday, 29.09.94:
09.15 STT: The search for the wreck begins today for investigation purposes. "We can neither deny nor confirm the theory that the casualty was caused by opened doors", says Kari Lethola.
20.50 Captain Avo Piht is not on the list of survivors. Tallinn is informed respectively.
The above is an office translation of Enclosure No. 2 of the Finnish book "Uutinen Estonia". The German version is attached as Enclosure 22.3.387. Further attached are in Swedish original- the SAR Log of MRCC Stockholm - Enclosure 22.3.388
- the Alarm Log of ARCC Arlanda - Enclosure 22.3.389In summary the following statements made by surviving crew members at a very early stage after just having been rescued and still suffering from hypothermia shall be quoted:
28.09.94:
- 11.26 STT: One of the survivors reports at Utö Fortress "that he was awakened, in his cabin near the car deck, by loud banging noises from this deck".
- 12.46 STT: A rescued Estonian crew member tells TT that "one of the car doors in the bow could not be closed during the night. The door which was used by the cars let water in. According to Sillaste the ferry heeled over only thereafter."
- 13.00 Yle TV 1, News: More than 100 have survived, bodies found so far: 5. An interview with was Vassili Märtson, Estonian, just being transported on a stretcher into the hospital of Tammisaari informs about the causes of the casualty: "A crew member of the ferry told me that one of the bow doors could not be closed during the night and through that water was flooding on to the car deck."
- 13.20 TV-Nytt: The cause of the casualty: "Slarvigt lockt, lucka", i.e. a care-lessly/or sloppily closed lock. The first interview with Vihlo Itäranta (from the hospital in Tammisaari).
- 15.00 Yle TV 1: "According to an eye witness from the crew the cause for the casualty was a bow door left open. According to the eye witness it was not possible to close the door and before midnight water started to flow on to the car deck." An interview of Sillaste.
- 17.19 STT: Report by a Dutch truck driver that the trucks were not secured.
- 20.40 STT: Swedish inspectors of Sjöfartsverket ascertained defects on the ESTONIA on Tuesday evening (overaged lashings, worn sealings, no lashing manual). "The deficiencies, however, were not so big that they could have caused such a large casualty. We are of the opinion that the ferry was well maintained."
29.09.94:
- "We can neither deny nor confirm the theory that the casualty was caused by opened doors", says Kari Lethola.
The above is the only comment made by a member of the JAIC to the effect that the casualty might have been caused by "not properly" or even "opened" doors.
Thereby it is unclear whether the visor - also called 'bow door' or the 'bow ramp', sometimes also called 'door' or 'gate' - is meant.
It is also interesting that the President of Estonia, Lennart Meri, told the press that he had been informed about the catastrophe already at about 03.00 hours, while the Finnish Government, first of all the Prime Minister, was informed only at 04.55 hours and the other Government members thereafter until about 05.40 hours. At that time the chairman of the Finnish part of the JAIC, Kari Lethola, was already on his way to Turku.
On the other hand, MRCC Helsinki did inform MRCC Tallinn at 02.55 hours, but "not in detail, only that something had happened and that people were in distress", whilst subsequently - at 10.05 hours - the Finnish Minister of the Interior Pekkavinen told the press that "the Estonian Authorities were informed at 02.00 hours by the Finnish Authorities".
Apparently there were "other authorities" also involved in the casualty which had nothing to do with the rescue services and which must have been informed already that ESTONIA was in trouble while the vessel was still afloat.
It also has to be assumed with certainty that there had been intense communication between the ESTONIA and Tallinn, at least during the last hour, and that ESCO knew what was going on onboard the ESTONIA much before the first, weak 'Mayday' was received by MARIELLA.  These figures do not include the Iraqis in the trailer on the car deck, the unregistered Pakistanis and the also unregistered relatives of crew members also said to have been on board.
In the previous subchapters many of the survivors have made a number of relevant observations of which the following shall be quoted:
Motorman Elmar Siegel: He saw from the liferaft the "man over board" boat proceeding away from the ESTONIA without caring for those in the water or in the liferafts.
Note: This boat is a motor launch located on the starboard side behind the bridge. It is lifeboat no. 1 specially equipped for emergency actions, e.g. if somebody has fallen over board. - See further in Subchapter 23.1.
Passenger Thure Palmgren: He saw from the liferaft something like a fishing boat proceeding away from the vessel without taking care for those in the water and in the liferafts.


Education
University of Illinois at Urbana Champaign(Class of 2021)
I currently attend the University of Illinois at Urbana Champaign, where I major in computer engineering. Currently, I specialize in artificial intelligence and robotics, but also enjoy learning about cybersecurity. Outside of ECE, I also enjoy learning about physics and have taken courses on special relativaty.
Harry D. Jacobs High School (Class of 2017)
I graduated from Harry D. Jacobs High School in Algonquin, Illinois. Most of my electives were in the realm of computer science, robotics, and physics courses. I would even spend my lunch period in the physics office or robotics lab working on independant projects.


| UNIX Shell Scripting Links |
| Resource | Address |
| Mark Virtue's (the course author) Home Page |
http://www.zip.com.au/~mvirtue There's nothing about UNIX here, just me |
| Mark Virtue's email address |<EMAIL_ADDRESS>Feel free to drop me a line and tell me what you thought of the training course |
| UNIX man pages | http://www.rt.com/man One of the many online man page collections |
| UNIX Shells |
http://www.looking-glass.org/shell.html A comprehensive guide to the variety of UNIX shells out there |
| Free UNIX Shell accounts |
http://caselogic.hypermart.net A list of organisations that offer free shell accounts |
| UNIX and Shell Programming Stuff |
http://www.ling.helsinki.fi/users/reriksso/unix A collection of links relating to UNIX Shell Scripting |
| A Comprehensive vi command reference |
http://www.cs.wustl.edu/~jxh/vi.html Every command you would ever use in vi |
| sed Overview |
http://www.math.fu-berlin.de/~guckes/sed A good place to start to learn fully about sed |
| awk Programming Language |
http://www.cl.cam.ac.uk/texinfodoc/gawk_toc.html A complete awk tutorial |


So I won the AUC Widget Challenge… huzzah! I'm keen to see the other entries as well… I'll post a link to them as soon as there is a page available.
This is a newer version than the one that was judged, with an excellent new visual design by Domenic Lattari.
Basically it lets you post an entry to your weblog, it definitely works with blojsom, both the normal version, and the one that Apple distributes with Tiger Server. It should actually work with any MetaWeblog API compatible blog server, but I haven't tested it with heaps of them.
Update: Now with full support for WordPress.
Here's a screenshot:
You can download it here.
And you can download the ReadMe file for it here
If you are interested in the source code, you can download that here. It uses CoreServices to do the XML-RPC stuff.
Well…
AFAIK, the posting works and it seems to be better than WordPressDash on the Diacritics fields. However, Categories are not retrieved from the plugin. I’m using WordPress. Any Idea ?
I can give you temporary access to the blog for testing I you feel like it…
Are you on an Intel or PPC Mac?
To be honest, I haven’t used this widget for quite a while… and tend to just write everything in TextMate with markdown these days. “Edit in TextMate” is kind of a simpler solution for me.
The source should still be around if you feel like poking into it, but I did notice this issue with Intel Macs and the latest version.
Thanks…
My categories:
1. Are sometimes Nested
2. Contains “Special” Characters (?!) (Ã‰Ã©)
I tried with my Girlfriends blog and it works. She doesn’t have nested nor (?!) chars in her categories…

I’ll try to figure what’s wrong… And give you a hint…
Oh, and BTW, I’m on a PPC Mac… (Cube)
ah. That is an issue with international characters, someone else reported that one to me, and me being so ethno-centric didn’t even think about it when I whipped it up.
I’m kind of a bit flat out until I finish some talks at MacWorld, but after that I promise to try and have a look at it, but it’s probably something really obvious in the source code.
Are you done with you talks ?
I can help you ! If you make that widget work !
PLEEEEEEASE…
Nice bottle of whisky or if you fix it.


TreeView / Animated ExpandBox
This sample demonstrates how to show/hide expand boxes in the TreeView using a CSS animation.
Whenever mouse cursor hovers over TreeView space, the expand boxes will appear slowly become fully visible. After mouse cursor leaves the TreeView space, the expand boxes will remain visible for 1s and than slowly become hidden.


I only have a rewards viewer: dexstats.info/rewards.php
I can try to host booststraps if i don't need to stop the daemon I could host it for all Assetchains. I will give it a try.
KMD mentioned in this article for Atomic Swaps and Dex(edited)
Wolfcoins (King of the DenICX)27-Dec-18 11:05 PM
No rebrand for 2018,
Can the team confirm me this information ?
SD28-Dec-18 04:34 AM
What is the relation with KMD and Amazon
blackjok3r28-Dec-18 04:55 AM
We have an advanced teir partnership and access to vast resources of their Data Centres. It was secured for the 1 millkion tps test, which has been ready for months. Not sure what the go is now.  I forgot how most of it works.
2
Deleted User28-Dec-18 05:46 AM
@Deleted User Is your first name "Harry"?
1
1
mazyar_lp28-Dec-18 07:31 AM
Hello merry Christmas everyone .how can i claim my komodo 5% every month?
polycryptoblog28-Dec-18 07:36 AM
It's 5% yearly , you just have to send your balance to yourself
mazyar_lp28-Dec-18 07:38 AM
After one year?
blackjok3r28-Dec-18 07:38 AM
every month
mazyar_lp28-Dec-18 07:39 AM
Tnx
jorian28-Dec-18 11:07 AM
@SHossain i see coinpayments has now enabled KMD support again, thanks for that, but the merchant I'm paying at doesn't want to support KMD because coinpayments doesn't allow direct conversion of KMD to BTC(edited)
Based on the study conducted by Better Than Cash Alliance (BTCA), The Philippines has an estimated 2.5 billions of payments per month…
tolken28-Dec-18 08:09 PM
@blackjok3r is anyone coordinating the scaling test effort? I’m a bit confused about the state of this. It was all the rage then just fell off the map. You seemed to be a very key dev in executing this test, is this just a casualty of decentralization? (edited)
They did find some very interesting bugs. Also, they all require physical access. IF you think your HW is actually brand new and nobody else has touched it, you are safe. But it points out that it is easier to give somebody a HW wallet that is backdoored
wallet.fail presented 3 attack paths at the CCC which wrongly give the impression that critical vulnerabilities were found on Ledger devices.
indeed, dukeleto
start taking extra measures even if it is new though
dukeleto29-Dec-18 12:32 AM
never ever ever buy a used HW wallet, based on this data. And even then, be very very paranoid
Torankoku29-Dec-18 12:33 AM
yes, exactly
dukeleto29-Dec-18 12:33 AM
opendime wallets don't have these issues, I believe. For instance, they use a clear case so you can see if any internal components are different
but opendime are meant to be single-use, so they are not exactly the same
Torankoku29-Dec-18 12:33 AM
personally, i never used hardware wallets
just brought one recently when it was on sale
still have not used it to this day
blackjok3r29-Dec-18 12:46 AM
@tolken not sure the go man. Was waiting on marketing then MoMoM was broken so we went off to fix that and it took 8 months... Is fixed now though. So test can be run
tolken29-Dec-18 01:07 AM
@blackjok3r that’s odd. Well hopefully we can see this baby fired up son the not too distant future, before you completely forget how it all works anyway
blackjok3r29-Dec-18 01:08 AM
Lol we already forgot how it works
I can make it again tho
tolken29-Dec-18 01:08 AM
I think it’s good to always have skepticism about the security of anything. It becomes a management inconvenience, but like everything, usually best not keep all eggs in one basket.
@blackjok3r I thought you had it down to a single command to launch that shit
blackjok3r29-Dec-18 01:10 AM
We will be doing a cross chain stress test in #kmdlabs in the next few weeks, hope to fill blocks with cross chain txs... After that the actual scale test should probably be run, even if just 250k txs a second.
Yes close to that
Bit more than 1, its just a docker conatainer that polls a URL for the start time
tolken29-Dec-18 01:11 AM
250k a sec, not good enough. Must melt their faces.
i seem to have misplaced my pin or dont remember the file name, i have my dat files. is there a way to get my pin so i can encrypt my wallet?
Gordon Komodo29-Dec-18 05:20 PM
try #support
PTYX29-Dec-18 05:43 PM
@georgecrypto gravity?
bishop29-Dec-18 05:51 PM
@Deleted User I don't think you can recover your pin. If you have your dat files, most likely you'll need to dump privkeys, then import them into a new encrypted wallet.
PTYX29-Dec-18 06:35 PM
@Deleted User are you talking about the pin file in Agama?
The one you decrypt with a password?
passcombo.com 🏴☠🏴29-Dec-18 06:43 PM
I think KMD needs an icon, publicly recognizavble person with good tech understanding and well speaking to represent KMD.
BTC got Antonopoulos, ETH got Vitalic, BCH got Roger and Rick... can KMD get someone like that? Maybe Miketout ? Somehow people like faces and emoitions beside intelligence, competence and knowledge(edited)
ph03nix29-Dec-18 06:45 PM
i vote for computergenie
4
passcombo.com 🏴☠🏴29-Dec-18 06:46 PM
@ph03nix if robots could take that position I would place myself
1
soul- must have one(edited)
NutellaLicka29-Dec-18 06:46 PM
Bitcoin benny?
actionslacks29-Dec-18 06:46 PM
my vote's for Genie, cause math
1
1
2
2
ComputerGenie 👴👴👴29-Dec-18 07:47 PM
Any conversation that has "Maybe Miketout ?" as a point of reference to speak on technicals is a league or 3 above mine
Lumbi29-Dec-18 09:11 PM
@ComputerGenie 👴👴👴 is smart & cute, too? Hasn't his grandmother auctioned him off as a husband yet?(edited)
Thread by @TuurDemeester: "1/ People often ask me why I’m so “against” Ethereum. Why do I go out of my way to point out flaws or make analogi a bad light? 2/ First, ETH’s architecture & culture is opposite that of Bitcoin, and yet claims to off […]"
Anyone else read this yet? Interesting read
1
Deleted User30-Dec-18 07:02 AM
Any update on the Agama Mobile Wallet for iOS?
Cryptoon30-Dec-18 07:34 AM
@Deleted User#deleted-channel
Deleted User30-Dec-18 07:37 AM
@Cryptoon Thx
KomodoWorld30-Dec-18 09:44 AM
@jspook16 I always take what Tuur says with caution, he has some points but the same could apply to BTC and others


--- layout: post title: Google's "Net Neutrality" Guide categories: [] tags: - business - geek - google - internet - net_neutrality status: publish type: post published: true meta: _original_post_id: '' _original_import_author: John Duprey author: ---
A Guide to Net Neutrality for Google Users
"Net neutrality" is an issue that will shape the future of the Internet. Google has created this guide to net neutrality, which includes a brief overview of the subject, an update on where things stand in the U.S. policy debate, a set of actions you can take to protect the Internet, and the text of an open letter from our CEO, Eric Schmidt.


Indiana
I'm a Junkie-Monkey!
Registered: Oct 2001
Location: Incommincado Tyler Durden says: Do we really need another women?
Posts: 3087 |
KC didn't like it. I wonder why? I liked it. I liked the opening speech. I did not try to think that He was a villian. I wanted to believe he was fighting for good. And so I became an optomist during this episode. However as it went on I believed that by Teal'c and Bra'Tacs facial expresions even they believed something was not right.
The photography in this Episode was very good. I think that the guy the hired to play Imhotep was specially trained in Martial Arts. I would like to see this new Photography developed. It's very good. The series is constantly trying to do feature film type visuals and stories and it is being done well here. I would like to see some type of battle done with this type of Photography except it would be interesting to see a battle between two Goa'ulds with hand devices. And it should be saved for the feature, if there is to be one.
I enjoyed the funny opening line. It was just out of nowhere. Jack said something about Deliverance and asked Bra'Tac if he had seen what happened in that film. I thought this was so funny. No really. You know Ronny Cox was in that film also?
I liked Raknor's character and enjoyed seeing him once again. And I am Glad that Yu is not dead as well. I've always believed him to be the most honourable of The Goa'uld, albe he still a Goa'uld he is certainly the unbaddest as was mentioned several times above by some members.
__________________
"Now I'm cleaning up and I'm moving on, going straight and choosing life. I'm looking forward to it already.  The washing machine, the car, the compact disc and electric tin opener, good health, low cholesterol, dental insurance, mortgage, starter home, leisure wear, luggage, three piece suite, DIY, game shows, junk food, children, walks in the park, nine to five, good at golf, washing the car, choice of sweaters, family Christmas, indexed pension, tax exemption clearing gutters, getting by, looking ahead, the day you die."
Report this post to a moderator | ? + *
|


"Sonic" - a Digital Audio Programming Language
This page was last updated 10 November 1998.
Table of Contents
Introduction
Sonic is a computer programming language I have designed. Its purpose is to facilitate the synthesis and processing of digital audio recordings, with emphasis on concise coding and rapid development. Sonic contains constructs which will be familiar to users of languages like C++ and Pascal, such as assignment statements, procedures, local variables, while loops, and if statements. However, because it is so specialized for working with digital audio, Sonic is not intended to be a general-purpose programming language.
Features of Sonic
- Concise, powerful syntax for expressing many DSP algorithms.
- Many useful digital audio programs can be written in less than 10 lines of code!
- Built-in support for efficient sinewaves, sawtooths, Fast Fourier Transforms (FFT), and linear filters (IIR).
- Language is user-extensible: write your own C++ classes and import them into Sonic programs.
- Automatic scaling of output levels - Sonic uses temporary floating point files to hold output, then scales to fixed point before exiting.
- It's free! I'm doing this for fun, not money.
Limitations of Sonic
- Only the WAV audio format is currently supported. (Want your favorite format supported? Point me to a good file format specification and I'll see what I can do...)
- No console text I/O yet. Currently you cannot write the classic "Hello World" program in Sonic, unless perhaps you want to output Morse Code!
- Input and output audio files must be specified on the command line in a Sonic program in order to persist after program execution terminates. Programs may create temporary files to aid in creating persistent output files, but these temporary files are automatically erased when the program quits.
How it works
Installation Procedure
This is the recommended installation procedure for getting Sonic up and running on your computer. All of the files you need can be downloaded below.
- Create a directory on your system for Sonic, e.g.
/sonic
on a Unix machine, or C:\SONIC
on a DOS/Windows machine.
- Create a directory under the Sonic directory for the runtime library, e.g.,
/sonic/runtime
or C:\SONIC\RUNTIME
.
- Download the file
runtime.zip
into the directory you created in the previous step. Unzip the contents of the file into the same directory.
- Create a directory for the Sonic/C++ translator source code, e.g.,
/sonic/src
.
- Download the file
sonicsrc.zip
into the source directory from the previous step. Unzip its contents into the same directory.
- If you are using 32-bit Windows (95, 98, or NT), and you don't want to bother with getting the translator source code to compile, then create a directory like
C:\SONIC\BIN
and download the file sonicexe.zip
there. Unzip the contents of this file into the same place. Add this directory to the PATH
by editing your AUTOEXEC.BAT
file, so that the operating system can find SONIC.EXE.
- Alternatively, if you are not running 32-bit Windows, you will have to compile the Sonic/C++ translator yourself. Use your favorite C++ compiler to compile and link all of the
*.cpp
files in /sonic/src
. All of the source and header files you need come from sonicsrc.zip
. You don't need the runtime.zip
to compile and link the translator itself; that source code is used only to compile and link C++ source code generated by the translator. Make sure the resulting executable is in your search path so that the operating system can find it.
Revision History
Here is a revision history of the Sonic/C++ translator and its runtime library. Look here if you want to see what changes have been made and what bugs have been fixed.
Feedback requested!
In its current state, Sonic is rather limited. I make no pretense that it is the ultimate language for its stated purpose. Nonetheless, I am excited by its potential as a digital audio programming language. I think I'm onto the germ of a good idea here. I'm publishing this language because the feedback of a community of users is invaluable for a well-rounded system. My intent is to spark interest in others interested in digital audio programming, and see if this language can become something truly valuable.
Please send any comments, questions, or suggestions about Sonic to the email address at the top of this page. I can't promise I will satisfy every request. As Sonic changes and matures as a language, there will be conflicting forces trying to pull it in different directions. I will have to make decisions on how to steer it in the "right direction", whatever that means. However, I will definitely strive to fix any bugs reported, and suggestions for future development of Sonic will influence my decisions and priorities. Ideas are always appreciated, even if I end up deciding not to use them.
[
home
]


{%extends "base/page.html"%} {%load pgfilters%} {%block title%}Contributor Profiles{%endblock%} {%block contents%}
These are the fine people that make PostgreSQL what it is today!
{%for t in contributortypes%}{{t.extrainfo}}
{%endif%}| Contributor | Contribution |
|---|---|
| {{c.firstname}} {{c.lastname}} ({{c.email|hidemail}})
{%if c.company %} {{c.company}}{%endif%} {{c.location}} |
{{c.contribution}} |
| {{c.firstname}} {{c.lastname}}{%if c.email%} ({{c.email|hidemail}}){%endif%} | {%if forloop.last%}{{c.firstname}} {{c.lastname}}{%if c.email%} ({{c.email|hidemail}}){%endif%} | {%endif%} {%endif%} {%endfor%}
All contributors are listed in alphabetical order. Please report omissions or corrections to the webmaster.
{%endblock%}


Moves
|
Name Petal Dance
|
Type Grass
|
Category Special
|
Power 70
|
Atk. Dice 3
|
Accuracy 20
|
Priority 0
|
Targets 1m x 20m line originating from the user
|
|
Description The user of Petal Dance attacks for 3 turns (including this one), during which it loses its regular action (but not movement), and then becomes confused. A new target may be chosen for each attack. The user cannot cancel the move on their own. However, if Petal Dance is disrupted (e.g. if the move misses, the user flinches, the user cannot attack due to paralysis, or no more targets are within range) then it will stop and not cause confusion. Pokémon with the ability Own Tempo or those behind a Substitute cannot be confused.
|
|
Name Petal Dance
|
Type Grass
|
Category Special
|
Power 70
|
Atk. Dice 3
|
Accuracy 20
|
Priority 0
|
Targets 1m x 20m line originating from the user
|
|
Description The user of Petal Dance attacks for 3 turns (including this one), during which it loses its regular action (but not movement), and then becomes confused. A new target may be chosen for each attack. The user cannot cancel the move on their own. However, if Petal Dance is disrupted (e.g. if the move misses, the user flinches, the user cannot attack due to paralysis, or no more targets are within range) then it will stop and not cause confusion. Pokémon with the ability Own Tempo or those behind a Substitute cannot be confused.
|
|


Home
Tech News
Contact
About
Log in
Course
Website
Cloud computing
cybrary.it
Data center management
classcentral.com
Computers
edX.org
Servers
classcentral.com
MongoDB
university.mongodb.com


31
July
2012
Input Fields
Not all form fields are supported in all browser.
Demographic Data Entry Form
Password:
Email:
Website:
Number:
Telephone:
Message:


A discovery that does nothing.
This discovery can be used if you need to inject a discovery instance in
some code, but you don't want that discovery to do anything (for example
in tests).
Methods summary
public
Puli\Discovery\Api\Binding\Binding[]
|
#
findBindings( string $typeName, Webmozart\Expression\Expression $expr = null )
Returns all bindings bound to the given binding type.
Returns all bindings bound to the given binding type.
Parameters
- $typeName
- The name of the binding type.
- $expr
- The expression to filter by.
Returns
Implementation of
|
public
boolean
|
#
hasBindings( string|null $typeName = null, Webmozart\Expression\Expression $expr = null )
Returns whether the discovery contains bindings.
Returns whether the discovery contains bindings.
Parameters
- $typeName
- The name of the binding type.
- $expr
- The expression to filter by.
Returns
boolean Returns whether the discovery contains matching bindings.
Implementation of
|
public
Puli\Discovery\Api\Binding\Binding[]
|
#
getBindings( )
Returns all bindings.
Returns
Implementation of
|
public
boolean
|
#
hasBinding( Rhumsaa\Uuid\Uuid $uuid )
Returns whether the discovery contains a binding.
Returns whether the discovery contains a binding.
Parameters
- $uuid
- The UUID of the binding.
Returns
boolean Returns true if a binding with the given UUID exists and
false otherwise.
Implementation of
|
public
Puli\Discovery\Api\Binding\Binding
|
#
getBinding( Rhumsaa\Uuid\Uuid $uuid )
Returns the binding with the given UUID.
Returns the binding with the given UUID.
Parameters
- $uuid
- The UUID of the binding.
Returns
Throws
Implementation of
|
public
boolean
|
#
hasBindingType( string $typeName )
Returns whether a binding type exists.
Returns whether a binding type exists.
Parameters
- $typeName
- The name of a binding type.
Returns
boolean Returns true if the binding type exists and false
otherwise.
Implementation of
|
public
Puli\Discovery\Api\Type\BindingType
|
#
getBindingType( string $typeName )
Returns the binding type with the given name.
Returns the binding type with the given name.
Parameters
- $typeName
- The name of a binding type.
Returns
Throws
Implementation of
|
public
boolean
|
#
hasBindingTypes( )
Returns whether any binding types have been defined.
Returns whether any binding types have been defined.
Returns
boolean Returns true if the discovery contains binding types and
false otherwise.
Implementation of
|
public
Puli\Discovery\Api\Type\BindingType[]
|
#
getBindingTypes( )
Returns all defined binding types.
Returns all defined binding types.
Returns
Implementation of
|
public
|
#
addBinding( Puli\Discovery\Api\Binding\Binding $binding )
Adds a binding to the discovery.
Adds a binding to the discovery.
Parameters
- $binding
- The binding to add.
Throws
NoSuchParameterException If an invalid parameter was passed.
MissingParameterException If a required parameter was not passed.
Puli\Discovery\Api\Type\NoSuchTypeException If the type of the binding does not
exist.
BindingNotAcceptedException If the type of the binding does not
accept the binding.
Implementation of
|
public
|
#
removeBinding( Rhumsaa\Uuid\Uuid $uuid )
Removes a binding from the discovery.
Removes a binding from the discovery.
Parameters
- $uuid
- The UUID of the binding.
Implementation of
|
public
|
#
removeBindings( string|null $typeName = null, Webmozart\Expression\Expression $expr = null )
Removes all bindings from the discovery.
Removes all bindings from the discovery.
Parameters
- $typeName
The name of the binding type or null
to remove all bindings.
- $expr
- The expression to filter by.
Implementation of
|
public
|
|
public
|
#
removeBindingType( string $typeName )
Removes a binding type from the discovery.
Removes a binding type from the discovery.
Parameters
- $typeName
- The name of the binding type.
Implementation of
|
public
|
#
removeBindingTypes( )
Removes all binding types and bindings from the discovery.
Removes all binding types and bindings from the discovery.
Implementation of
|


| Function name | Function info |
|---|---|
quick_sort(2) : Function quick_sort(desc, original_list) returns a sorted list of an arbitary number of parameters. If desc is true (or 1), list elements are from largest to smallest, otherwise (desc is false or 0), from smallest to largest. For example, quick_sort(1, [5,6,7,9,4])'s result is [9,7,6,5,4] while quick_sort(0, [5,6,7,9,4]) is [4,5,6,7,9]. |


Here you can add all elements you want in this left panel
Here you can add all elements you want in this right panel


Abstract
Basal-like breast cancers (BLBCs) are very aggressive, and present serious clinical challenges as there are currently no targeted therapies available. We determined the regulatory role of Y-box binding protein-1 (YB-1) on epidermal growth factor receptor (EGFR) overexpression in BLBC, and the therapeutic potential of inhibiting EGFR. We pursued this in light of our recent work showing that YB-1 induces the expression of EGFR, a new BLBC marker.
Primary tumour tissues were evaluated for YB1 protein expression by immunostaining tissue microarrays, while copy number changes were assessed by comparative genomic hybridization (CGH). The ability of YB-1 to regulate EGFR was evaluated using luciferase reporter, chromatin immunoprecipitation (ChIP) and gel shift assays. The impact of Iressa on monolayer cell growth was measured using an ArrayScan VTI high-throughput analyser to count cell number, and colony formation in soft agar was used to measure anchorage-independent growth.
YB-1 (27/37 or 73% of cases, P = 3.899 x 10(-4)) and EGFR (20/37 or 57.1% of cases, P = 9.206 x 10(-12)) are expressed in most cases of BLBC. However, they are not typically amplified in primary BLBC, suggesting overexpression owing to transcriptional activation. In support of this, we demonstrate that YB-1 promotes EGFR reporter activity. YB-1 specifically binds the EGFR promoter at two different YB-1-responsive elements (YREs) located at -940 and -968 using ChIP and gel shift assays in a manner that is dependent on the phosphorylation of S102 on YB-1. Inhibiting EGFR with Iressa suppressed the growth of SUM149 cells by approximately 40% in monolayer, independent of mutations in the receptor. More importantly anchorage-independent growth of BLBC cell lines was inhibited with combinations of Iressa and YB-1 suppression.
We have identified for the first time a causal link for the expression of EGFR in BLBC through the induction by YB-1 where it binds specifically to two distinguished YREs. Finally, inhibition of EGFR in combination with suppression of YB-1 presents a potential opportunity for therapy in BLBC.