Wednesday, June 29, 2016

Having maintained an Open Source project for almost 20 years now, there are some ways to deal with bad users.

One is to not take it personally. Annoying people should get ignored or banned. They're just not worth the effort.

Two, is to recognize that your time is limited. If the person filing the bug can't (or won't) help track it down, well... too bad. Maybe no one else runs into the bug, and your best response is "works for me". (Note that this is the approach taken by most commercial software vendors in my experience)

Three, is to recognize that there are idiots out there, and you can't help them all. It's OK to be on the lower end of the bell curve, but sometimes it's like the kids rides: "You have to be THIS TALL to go on this ride". If the user can't comprehend something, perhaps he shouldn't be using it. And perhaps you shouldn't waste your time trying to get him to understand something he just can't understand.

My general approach is to be nice to people who ask good questions, and who try. When people ask terrible questions, and make it clear that they have no interest in lifting a finger, but demand that you do all of the work... well... they get told in no uncertain terms to shape up, or get banned.

You don't owe these people anything. If they had an ounce of human decency, they would understand that they got the software for free, and that they don't deserve anything. And that they need to put some effort into it on their end.

The main response I have with these people is If you're too lazy to help solve the problem, then I'm too lazy to help, too.

from lizard's ghost

what a conversation


from lizard's ghost

Monday, June 27, 2016

littlefinger & lyanna stark?

from lizard's ghost

Saturday, June 11, 2016

not just s3

from lizard's ghost

on feature requests..

The key is to ignore the feature request, and focus on the problem.
Users don't come to you with problems, they come to you with shitty solutions.
You need to take their solution, reverse engineer their real problem from that, then work out a good solution for that problem that fits well with your product..

from lizard's ghost

Sunday, June 05, 2016

on identity theft

Consumer identities are never "stolen". Maybe a criminal gets to know some numbers associated with you. Then, the fraud protections of a bank are breached by a fraudster. Thats a crime between the fraudster and the bank, and it's really a crazy innovation to say the consumer is responsible for the loss in that situation. -

from lizard's ghost

Friday, June 03, 2016


Göppingen/Germany, May 23, 2016. A recent article warns, “TeamViewer users have had their bank accounts emptied by hackers gaining full-system access”. TeamViewer is appalled by any criminal activity; however, the source of the problem, according to our research, is careless use, not a potential security breach on TeamViewer’s side. Therefore TeamViewer underscores the following aspects:

Neither was TeamViewer hacked nor is there a security hole
TeamViewer is safe to use and has proper security measures in place
Our evidence points to careless use as the cause of the reported issue
A few easy steps will help prevent potential abuse
Ad 1.) As always when we receive alerts about potential security alerts, we look at the issue at hand. This is what we have done in this case: There is no evidence to suggest that TeamViewer has been hacked. Neither do we have any information that would suggest that there is a security hole in TeamViewer. Therefore it it is important to stress there are no TeamViewer hackers, but rather data thieves that will steal information from other sources. It is critical to make sure attention is not diverted from the real issue.

Ad 2.) TeamViewer is safe to use, because TeamViewer has proper security measures in place including end-to-end encryption to prevent man-in-the-middle attacks, anti-brute-force means, and more. Additional information about TeamViewer’s security is available at:

Ad 3.) Unfortunately, users are still using the same password across multiple user accounts with various suppliers. While many suppliers have proper security means in place, others are vulnerable. The latter ones tend to be targeted by professional data thieves. As TeamViewer is a widely spread software, many online criminals attempt to log in with the data gained from compromised accounts (obtained via the aforementioned vulnerable sources), in order to discover whether there is a corresponding TeamViewer account with the same credentials.

Storing or caching of account credentials in your browser is yet another example of careless use. The security means to protect such sensitive data do not suffice to guarantee an acceptable level of security. Additionally, cybercriminals may use certain tools to identify and visualize sensitive data in the browser.

Ad 4.) TeamViewer encourages users to …

… create different passwords for each account … not share your passwords. … change passwords regularly. … not use personally identifiable information for passwords. … use two factor authentication: … use password safes. More information about these recommendations are available at:

The TeamViewer support team is happy to answer any potential technical issues or queries at:

TeamViewer recommends that users who have been the victim of criminal activities get in touch with their local police departments, in order to report their case. This is particularly important because TeamViewer is subject to very strict data protection and privacy regulations, and can release sensitive data only to authorized individuals and authorities.

About TeamViewer

Founded in 2005, TeamViewer is fully focused on the development and distribution of high-end solutions for online communication, collaboration and remote monitoring of IT systems. Available in over 30 languages and with more than 200 million users worldwide, TeamViewer is one of the world’s most popular providers of remote control and online meeting software. airbackup, a powerful cloud-based backup solution, and ITbrain, a valuable remote monitoring, anti-malware and IT asset tracking solution, complement TeamViewer’s product portfolio.

For more information, visit:
Follow us on Twitter at @TeamViewer and on our blog at

TeamViewer GmbH
Jahnstr. 30
73037 Göppingen

from lizard's ghost

Thursday, June 02, 2016

blameless postmortems

but on the other hand

SOP is to tell you don't worry be happy while loading you up with blame coming down from your director/VP. If you quit, everything they tried to secretly pin on you now focuses on your managers so they are desperate to keep you from quitting. Once you get to OLR the next year you'll get an unpleasant surprise and probably fired. This is called burn and churn managemenent... -

from lizard's ghost

owncloud and openoffice and mysql


Community-Fork and new companies : Next cloud is the "restart" for ownCloud

Leading ownCloud developers, including the founder Karlitschek, start with a cloud Next Fork of the code and a new company. The goal is a better balance between companies, customers and users. For the team to Karlitschek has big plans.

End of April the ownCloud project founder and former chief technology officer of the eponymous company has Karlitschek announced to leave this. He was followed by several other core developers. Common to all was the vague announcement to want to leave anyway not the community. Now it is clear what the group has meant to Karlitschek: You justify a run by the Community elimination (Fork) of the codes and a new company to support the free server platform for synchronizing files. Both are Next cloud hot.

With Next cloud the team wants to put as early as next July a complete replacement for ownCloud is available which can be used by both home users and corporate customers' problems instead of ownCloud. The new entity is formed here in cooperation with that combines a WebRTC server as videoconferencing solution with ownCloud and thus pre-installed computer under the name Spreedbox sold. Will lead the new company Karlitschek and Niels Mache, who has hitherto been responsible for and co-founder of Red Hat Germany.

Next cloud is more than just file synchronization

The focus of next cloud should be on giving users complete control over their data. For the development team wants to extend the Web application on the core functionality significantly further. In addition to the parts and synchronizing files to the server WebRTC Spreed and the corresponding application will be integrated. Similarly to frequently used ownCloud applications like calendar or contact management of cloud Next maintained and are officially supported. Also conceivable is a further expansion of cooperation with LibreOffice to edit Office documents collaboratively in the browser.

The Next cloud company promises enterprise customers fully continue the contracts previously concluded with ownCloud. Customers should so continue to get the scheduled expert support they need to continue to run their servers. The change of the core developers in the new company will not adversely affect the customer, thanks to this offer.

Dissatisfied with the old company

The former community manager at ownCloud and now for communication at Next Cloud responsible Jos Poortvliet designated the project as a "restart" . Speaking to Karlitschek and Poortvliet give as a reason for the re-establishment "structural problems" and some "economic decisions" of ownCloud company, which had caused great dissatisfaction. For more details do not want to call both though. The business model of Next cloud is however based on longevity and sustainability. This could not provide the desired extent the ownCloud company the team the next cloud founder apparently.

Moreover Next cloud should restore a balance between the needs of the company, its customers and the developer community. Thus the ownCloud companies have increasingly withdrawn from the community development since 2014, which led to a variety of unprocessed contributions from external developers.

Next Cloud will improve the situation, inter alia, that (CLA) or proprietary enterprise apps should be dispensed blocking elements such as a Contributor License Agreement. Karlitschek commented "There are many things to improve and to do so with the community to work together and for this we have the contributors." . All developments would happen with Next Cloud logical public.

In the tradition of LibreOffice

In addition to project founder Karlitschek and Poortvliet far the developers Arthur Schiwon and Björn Schiessle , responsible for the security Luke Reschke , the Desing CEO Jan-Christoph Borchardt and the for critical customer responsible Morris Jobke made ​​public, to have left the ownCloud companies. It is assumed that those named will continue to work at Next Cloud. Probably some developers will follow even, at least look for Next Cloud actively seeking additional staff.

Poortvliet compares the Fork and the reestablishment of the Next cloud company with the development of LibreOffice and MariaDB. The latter two projects emerged as Forks of or MySQL. The reason for this was the dissatisfaction Forks community about the growing dominance by the new owner Oracle.

Probably to stop the looming loss of a large part of the development team and to respond to the already expressed problems in dealing with the community, the ownCloud company announced the creation of two days ago ownCloud Foundation announced. The Foundation is projected to the announcement as "independent homeland for ownCloud" serve with more than 10 million users and a total of 1,000 contributors, this goal will probably find it hard to reach.

from lizard's ghost