So it’s not only me who belives that Google has become what Microsoft was a few years ago (only worse).
Matt Cutts, Google’s long term public face, was fairly clear saying “Google doesn’t have partners,” recently at an event we both spoke at.
It’s a blank stare Google executives give you when you express a concern, as if you’re talking to someone who doesn’t speak one word of your language.
Anyone who has Google as a partner knows this stare.
Google only sees you as a partner when they need you to run their ads or they need your content to draw in advertisers. When you need help, Google says “we don’t have partners!”
That’s why folks are so frustrated with Google, and I see that tipping over into hate more and more often. The people I meet who run Machinima, Maker and other major YouTube partners exhibit outright hate for YouTube.
That’s bad news for Google.
In fact, it’s fairly clear to this executive, who has been working with Google since Day One, that Google thinks of content creators–artists–as this necessary evil to put their ads next to.
They don’t really respect us since they won everything. If they did, they would listen to our needs and think about making their platform sustainable.
They don’t listen any more really (that is, unless you need help implementing their advertising technology).
Have a question on how to optimize your ads? They’re all ears!
Have a question about the revenue split, making your business sustainable or why you were replaced in search results by their service (see Yelp v. Zagat)?
Google Death Glare!
Maybe you’ve already heard of TYPO3 Flow, if not i can tell you that it is a PHP web application framework which is open-source, free and was created by members of the TYPO3 community. While initially it was known as FLOW3 now it has been renamed to TYPO3 Flow and is part of the great TYPO3 family alongside TYPO3 CMS and TYPO3 Neos.
You might wonder why am I talking about TYPO3 Flow. Well, lately I’ve been working more and more with this framework and i must admit that I like it very much. Actually so much that i couldn’t imagine now writing an application with any other tool that’s out there.
Some neat things that TYPO3 offers:
- fully MVC architecture
- Aspect Oriented Programming
- Domain-Driven Design
- Dependency Injection
- Test Driven Development
- Signals and slots concept
- the Fluid templating engine (Oh yeah!)
I’ve learned alot in the last month about these and i want to share some of these things with my readers. So in the next months you will see several Flow related articles, tutorials, tips & tricks on my blog. I’ve gathered all this knowledge while working on a big personal project which will be the subject of my future posts at some point. Working on this application with TYPO3 Flow was a truly inspiring endeavour for me and i can’t wait to work with and learn more about Flow.
And if we speak about inspiring things then i also wanted to let you know about an upcoming TYPO3 Flow conference called the Inspiring Conference which is held in Germany (Kolbermoor) between 28-29 March 2014. It is a meeting place for TYPO3 Flow developers, freelancers, companies and everyone who works with this framework. Obviously i already have my ticket to this conference and if you’re also going then maybe we can grab a beer and talk about Flow, TYPO3 or any other thing.
Meantime, check out this cool video about TYPO3 Flow & Inspiring Conference:
I’ve had today a small little issue with the Imagemap Wizard extension for TYPO3. This extension allows the interactive creation of imagemaps right from the TYPO3 backend. I’ve used this extension before and had no problems with it. But while installing it today on TYPO3 4.7.x i got the warning that it’s not compatible with 4.7.x and even more i’m using an unsupported PHP version (5.4.x).
Because i’m not so easily intimidated by these warnings i went ahead and installed it. No luck however because the extension just wouldn’t work. It was telling me this in the backend when editing an image map:
No Image rendered from TSFE. :(
Has the page some kind of special doktype or has it access-restrictions?
There are lot’s of things which can go wrong since normally nobody creates frontend-output in the backend
Hmm…but i really needed this extension so i went ahead trying to find a solution. And a quick search rendered the help i was desperately needing. The issue is known and was submitted to Forge more then a year ago. Still there is no official update for the extension. On the forge page however there is a patch which i have applied and the extension is working again perfectly.
So if you run into the error above just apply the patch and make sure you don’t update the extension from the repository until there is a patched version available.
I’ve read two very good articles of why Facebook si broken and why the end is near for Facebook. I pretty much agree with everything there. And it seems that Zuckerberg knows something as he is just selling lots of Facebook stocks (good idea while they are peaking).
Last year i bought myself a nice little Seagate BlackArmor 220 NAS (Network Attached Storage). I’ve set it up at my home and all is fine, the device is running properly for more then a year. At home I’m accessing it via Samba share on the local network, when travelling I was accessing it via FTP (supported by the device). This was all great but unfortunately in this mode I couldn’t directly edit files on the NAS. So i looked for solutions for doing so. One thing i discovered early is that the device supports NFS. I didn’t know much about NFS back then.
The last few days when my itch got really painful to edit files directly on my NAS I started poking around on how to set up a share via NFS which can be accessed and edited from any place where a decent internet connection is available. And after a little bit of research i managed to do that. I will tell you how to do it if you ever need to do so.
Setting up the NAS
Well, first thing your NAS must support NFS. Mine does and in the admin interface of the NAS i can enable and disable NFS. I enabled it and whitelisted the IP addresses from which i’m going to access the NAS. There is no authentication necessary. It works based on IP addresses. So if you whitelist an IP address anyone from that IP can access your NFS share if he knows your NAS’s IP address or hostname (be careful!). That’s all on the NAS side. Of course you can set up NFS not only on a NAS but with your own computer as a server. In this case you need to research the solution because i didn’t try/needed that solution.
Accessing the NFS share from Ubuntu
First of all you will need the nfs-common package. Be sure to get it:
$ sudo apt-get update $ sudo apt-get install nfs-common
Then let’s see what are you sharing via NFS
$ showmount -e server-IP-or-host-name
Ok. Now let’s create a directory on your client machine (in directory /media/username) that will be used to access the share and mount a directory from your NAS to this. For the purpose of this demo let’s assume that your NAS has the hostname imaginarynas.dyndns.org (using dyndns to map a dynamic IP to hostname)
$ cd /media/username $ sudo mkdir myNFS $ sudo mount -o soft,intr,rsize=8192,wsize=8192 imaginarynas.dyndns.org/publicShare /myNFS
Great, now you have in the myNFS directory the contents of the publicShare directory from your NAS
How to permanently mount it
First edit /etc/fstab and add the following to it
imaginarynas.dyndns.org:/publicShare /media/username/myNFS nfs soft,intr,rsize=8192,wsize=8192
And pretty much that’s all. Now i can access my NAS from pretty much everywhere where’s a decent internet connection.
So I’ve read the announcement of TYPO3 CMS 6.2 beta1 and proceeded to check out the new stuff under the hood of the newest version of TYPO3, which by the way will be an LTS (Long Term Support) version. For a long time i wasn’t impressed by new TYPO3 releases. But now i must admit the core developers surprised me. The sheer amount of new stuff under the hood is just impressive. And I think we’re on the right track with the development. New features are coming which were long overdue in TYPO3 and i think they will help in making TYPO3 more popular on the long run.
But let’s see which are the new features that will be shipped to us in early December with the final version of TYPO3 6.2.
No more dummy stuff!
The first thing which surprises right away is that the Dummy package is now obsolete and no longer needed. You install TYPO3 and all necessary files and folders (like fileadmin, typo3conf and uploads) are created automatically.
TYPO3 introduces the Package concept from Flow and has now also Composer support. What this means ? Well, extensions can be a special kind of packages and they can provide a composer.json file with dependencies. You must not take any special action however. This will work with old extensions too and when you first open your updated website it will redirect you to the Install Tool. The silent updater will take care of creating the PackageStates.php in typo3conf which actually replaces the old extension list from LocalConfiguration.php (or localconf.php in older days). There will be also a LocalConfiguration.beforePackageStatesMigration.php which is a backup of your old LocalConfiguration.php file.
Reworked Install Tool
The Install Tool got a major overhaul and i think it’s better then ever, providing a lot of useful information about your site’s settings allowing you to change things and now it has even a better organisation of the information presented. One advertised feature is the Core Updater (i couldn’t see it in action yet) which will allow you to update TYPO3 with patches and minor updates right from the Install Tool.
Configuration presets in the Install Tool
These are predefined collections of settings, allowing you to make . One very nice use of this is that you’re able to switch between Production mode, Development mode and even a custom mode for settings.
A new module in the backend showing all the manuals of your installed extensions
Broken extensions check
It happened to me often and probably to you too that one broken extension would make your TYPO3 installation unusable (crashed). Now firing up the Install Tool -> Important Actions you can check for incompatible/broken extensions and uninstall them if needed.
Extension Manager updates
Although i’m pretty fed up with how often the Extension Manager was changed during the last few major TYPO3 releases now the addition of Distribution Management is a welcomed change. I was a long time advocate of TYPO3 Distributions, even created some distributions based on TemplaVoila Framework. I retired this summer the project for a major overhaul of the way I wanted distributions to work and now i have to rethink it having the official way of using the Distribution Management in mind and this will be one major subject of interest for me in the coming year.
File Abstraction Layer
The FAL project comes with lots of new additions like Translation Support, Advanced Metadata, Categorization, Permissions and so.
Backend Layout Data Provider
An other interesting topic for me is creating themes for TYPO3 and I’ve been trying to do that in several ways, none of which were in the end satisfactory to me. I presented last year at the TUG Meetup a session about Fluid Websites. That was the closest i got to creating independent TYPO3 Themes that could be moved from one TYPO3 site to another. One major problem was the i couldn’t move the Backend Layouts with the extension itself because they were stored in the database. Now the new addition to 6.2 is a Data Provider Interface which will allow to store Backend Layouts in files also and then I can pack these files to the theme extension and distribute the themes as such. This will greatly improve the distribution of the themes.
And other changes…
Of course there are also a lot of other smaller or bigger changes in the new TYPO3 6.2, i will let you discover those by reading the announcement.
And the bad …
There are also some things i didn’t like when testing the latest TYPO3 version
Increased execution time requirement!
Recommending the setting of max_execution_time to 240 seconds is just plain senseless to me. Why would you do that ? On frontend rendering i cannot imagine anyone waiting even 30 seconds after a website so 240 is an overkill. In the backend when you do some import operations i can imagine scenarios where you would need more time but this should not warrant a site wide max_execution_time increase to 240 seconds. There is a big chance if your script didn’t run in 30 seconds it will not run in 240 either.
Performance should be the most important thing kept in mind by the core developers and encouraging badly performing scripts/extensions should be their last thing to do. Unfortunately i see this as an encouragement to bad performance.
Directory structures on my server
I get some strange red warnings in the Install Tool that my index.php and typo3 directory (the TYPO3 source) are not stored “as specified”. I understand there is a recommended and used way by the TYPO3 core developers but frankly how i organize my TYPO3 sources on the server is my and only my problem, it should not be TYPO3′s or any other CMS’s problem how my storage is organized on the server. I like to store all sources in one directory and symlink them to the needed webroot and it does not affect TYPO3′s functionality and and use.
This having being said (written down), i can hardly wait to see the final product shipped. I think this will enable some very good side projects for me and for others as well.
As you might already know between the 14th and 16th of November the Romanian TYPO3 Community organizes the first ever major international TYPO3 event in the eastern part of Europe. It is called TYPO3 East Europe and will be held at the Golden Tulip Ana Dome hotel in Cluj Napoca, Transylvania, Romania. While it’s aiming primarily at the Eastern European community we welcome also people from all over Europe and why not the whole world.
TYPO3 East Europe schedule
The event will last for 3 days. The first day is dedicated to universities and the general public. The public will be able to see introductory sessions about TYPO3. This is targeted at people who never worked or even heard about TYPO3 before. We will explain why TYPO3 is the best ECMS out there and how can TYPO3 help them to achieve their goals. Attending on these sessions will be open for everyone and free of charge.
There will be also a workshop with the universities which will focus on the use of TYPO3 in the university world. This is on an invitation only basis. If you want to attend then contact the organizers.
Days 2 and 3 will be the core of the event and here we expect TYPO3 developers and companies that work with TYPO3 to share their experiences and to learn about each other. There will be sessions on a broad scale of topics from general TYPO3 topics to more advanced like Flow/Neos and also case studies, business topics and project management. Of course each of the nights will end with a big social event which will be held in one of the many bars/pubs in Cluj (still to be decided).
Btw you should know that being a university city and a business centre, Cluj has plenty of bars, clubs and restaurants and they have generally speaking much lower prices compared to Western Europe.
Still not convinced ? Check out these top 10 reasons to attend to TYPO3 East Europe
Cluj Napoca – the location
Cluj Napoca, Romania is one of the most dynamic cities in Eastern Europe with a very large IT community, some 8000 people work in the IT industry with a growing tendency. It’s located in the north-western part of the country, close to the border with Hungary.
It is a place of legends, being located in Transylvania where according to many legends vampires roam the forests. We’ve seen some and guess what ? They were learning TYPO3!
Also it’s very easy to get here. There are direct flights to many places in Europe (more details on how to get here). I won’t say more about Cluj, i will let you see the video below and if you want you can read more here and find a nice guide here.
That being said, I’m waiting for you in Cluj in November!
So I’m back from Palma de Mallorca from the second international TYPO3Camp which was held in this beautiful city between the 20th and the 22th of September. This camp was a little bit bigger then the one from last year, there were a total of almost 170 participants from 8 countries. Germany was of course the most well represented nation, after that came the Romanian community which this year had a good presence (just as last year).
The event started on Friday with the social night at El Molino, it’s just crazy that last year i had there a coffee with my colleague Tomita and we didn’t even think it will be the location of the next year’s camp warm-up party. Anyway it was a pleasant surprise to see that this location was selected for the start of the camp.
In the morning after a quick and tasty breakfast at our hotel we went to the conference center of the Majorica hotel were the planning session started shortly after our arrival. As this was a barcamp the planning of the sessions is done right there with the participation of the attendees.
There were 5 rooms for the sessions and they quickly filled with sessions and people. For me the most interesting session was the one dedicated to the migration from 4.5 LTS to 6.2 LTS. There it was made clear that some kind of an upgrade checklist will be provided for us. Also an interesting bet was made. If the team delivers the new 6.2 LTS in time they will get 300 of liters of beer. I think that’s quite an incentive :)
Other interesting sessions were:
- SrcBuilder (a flow package builder tool)
- How to speed up TYPO3
- Deployment with FlowSurf
- NoEstimates (although i think this is kind of unrealistic)
The day continued at the Marchica club with the social event where we had some interesting discussions and i learned alot about T3Sail which seems a very interesting event and frankly i’m quite tempted to get in the boat next year.
Then the second day of the conference came with a shorter day but with interesting sessions like:
- 47 questions to ask your hosting provider
- Vaadin web apps
- Mobile Apps with TYPO3 and Titanium
- Marketing for new markets
The camp ended Sunday with a dinner at Meson Ca’n Pedro, a typical mallorcan restaurant where they serve a very delicious suckling lamb with garlic and mushrooms. I recommend it if you’re visiting Palma
And now the conclusions. The camp was interesting, you could learn some things but most important it was an opportunity to socialize and meet new people. A big thanks goes to the organizers and the sponsors of the camp because without them it wouldn’t have been possible to have such a great camp.
If you’re into events like this then i suggest coming to TYPO3 East Europe held between the 14th and 16th of November in Cluj Napoca. It won’t be such a sunny weather and beaches like in Palma but it will be lots of fun and the social events will be legendary.
Some other articles about TYPO3Camp Mallorca:
- TYPO3camp Mallorca 2013 – report of a fortunate event - By Stefan Bauer
- Das zweite internationale TYPO3 Camp auf Mallorca – by Danijela Grgic (in german)
- TYPO3Camp Mallorca 2013 – by the Wolfgang Wagner (in german)
I didn’t really write on the blog lately because i was busy and also had a lack of inspiration most of the times. But i thought that i really should post an update even if it is not that much information for now.
What cool things i did lately:
- Some of you might know my website Ropedia.ro, I’m totally rebuilding it and change the philosophy behind it. Deadline is the end of the year.
- I learned and started working with TYPO3 Flow (more posts will follow about this subject)
- I’m in the initial phase of a completely new application that i will build using TYPO3 Flow. It will be something very cool and I think will be a small revolution in that particular area.
- I went to the Paris Air Show in June
Other things that happened:
- I found my alternative to Google Reader, it is The Old Reader
- Updated my blog with a mobile theme for easier access on mobile devices
On some of these subjects i plan to write more in the coming weeks/months. Stay tuned.
I wrote last time about Google shutting down Google Reader. It seems that i can’t get over this so easily. I’m still having issues migrating to a new feed reader.
These two weeks i had plenty of time to think about this situation and i come to a few conclusions of my own. I thought about what i have lost. I have lost Google Reader. But in the same time i also lost what has left of my trust in Google. I have trusted them with my data, with my reading habits, with my RSS feeds. And what they did ? They have abused this trust by shutting down Google Reader because of their relentless war with Facebook. More importantly they have failed their own mission. They state on their company page:
Google’s mission is to organize the world’s information and make it universally accessible and useful
Well for me and many other people the RSS feeds in Google Reader were one of they way we organize our information. I fail to see how Google helped that by shutting down Google Reader.
How can i ever trust a new (or existing) service from Google when there is always the possibility that if the product won’t meet their expected numbers then they will just shut it down. We should start looking more carefully on what companies we choose as our online service providers. I bet if Google Reader was their main product and their company depended on that product then they wouldn’t have shut it down. So that’s why i think companies that focus on one single product and do it well are the ones that should earn more trust as its in their best interest to provide a good service. Of course the possibility of a shutdown (bankruptcy) still exists but it might be smaller and at least they won’t shut it down on a whim.
Yes, because that’s what happened with Reader and many other products at Google. They start all kind of services just to compete with everyone else. They are like those spoiled kids you known when you were also a kid. They want to have the same toys as you have and if they don’t have something they will force it on their parents to buy it for them. That’s what Google does. If someone else comes with a great product they just can’t stand that. They will go out of their way to try to beat that company. This is now the case with Facebook. But its not the only example. They want to stick their nose into everything : local information, airline tickets, mobile operating systems, maps, social media, TV and i could count on.
They launch services relentlessly, just last days they launched Google Keep, an application for storing notes. But in the marketing texts they forgot to mention that they already had a similar service a while ago which they shut down. It was called Google Notebook. It didn’t met their expectations and they killed it. But now when they’ve seen that others have some success with note apps (like Evernote) the spoiled kid could not take it anymore. We want too!
I have one advice to you. If you want to keep notes then use Evernote. This is their single product. Their company depends on the success of that service. Don’t trust your data to Google. Because you can wake up one morning to discover that they can’t get enough users on it and got bored of supporting that product what’s more its not even their main business anyway. So they shut it down.
You could say that no one cares about my advice. But let me tell you something about myself. I’m an early adopter, i’m a computer geek most of the times. Most of my family members and many of my friends learned using computers and software from me. I told them what software to use, i told them to open Gmail accounts for e-mail. I told them about every new noteworthy software and service. Now the time has come to stop recommending Google products. Because i can’t wholeheartedly support any Google product. After reading a little around on the internet i can see that i’m not the only one in this situation. Reader was used mostly by nerds like us. And when people like us stop recommending something or start recommending something else then inevitably the general public will follow after a while.
So in my humble opinion by shutting down Reader, Google lost more then it hoped for.