Has anyone managed to load adserver code with this method successfully? I'll be trying myself this weekend and will report back....!
61 karma · joined February 19, 2010
Has anyone managed to load adserver code with this method successfully? I'll be trying myself this weekend and will report back....!
I'm glad it didn't work on my own mobile as I would have definitely integrated it into my site and no doubt run into the same huge problem here!
I'm actually investigating using Chargify myself even though it means signing up for a new IPSP and getting a new business bank account with Barclays (the only one they support).
http://dev.mysql.com/doc/refman/5.1/en/what-is-mysql.html
I only ever use MySQL, so have always said "Ess Que Ell". I work with guys who say "sequel" by default.... it's not caused any friction as yet.
I studied Physics @ Nottingham so pretty cool to see my lecturers getting involved!
I think it boils down to a communication problem, support / request are fragmented between phone, get satisfaction and our own support ticket system. We also don't have a good way of sending out information.
Perhaps if we had a regularly updated blog and a single support and feature reqeusts system it would eliminate the cause of the problem.
But that's more coding for me!
The long and short of it is that I'm under enourmous pressure, because according to our users it's already behind schedule.
I don't want to break face by just saying that my co-founder has jumped the gun massively and was in no position to make the promises, so at the moment I'm just living with the embarassment and trying to keep my head down an get it out.
In his defense, there is a reason for this and I wonder what advice HN peeps would give.
Day-to-day senario......
User: Is feature xyz available? Company: No User: Will it be available in the future? Company: This does seem be a worthwile addition and we will discuss it in our next development meeting. User: When will this feature be added? Company: We don't have a launch date. User: Ok, when will this feature be available becuase I need to use it now? Company: We don't have a launch date available. User: When will it be available, I'm getting annoyed.
At this point my co-founder usually breaks cover and gives a vuage, fairly distant forward projection; "in a month".
Should we really just be saving "no" and keeping silent on good ideas even though we are developing them?
Tip: if you have some UK or German traffic, consider Adjug (http://www.adjug.com/) you can set a CPM floor (we set £0.40) and your own backfill. We are setup like this:
Premium Ads (via our agent) > £1 guaranteed backfill > £0.40 backfill (Adjug) > Adsense & House Ads
The only problem is slight delay in tags loading is one of the servers is slow.
You still have to pay Authorize.net (or whatever gateway) and then ontop of that have a monthly fee to Chargify....
Surely better to drop a one-off development cost on software to sit in Chargify's place, bespoke to your site...
I suggest you get in the gym!
You just have to accept that the quantumn world concerns probabilities (wave functions) rather than finite "locations" which we are used to in the non-quantum world.
It's a hugely interesting subject.
Yes, we know our agent isn't up to scratch but we are struggling for alternatives. I'll drop you an email.
This is the exact opposite of what we are experiencing at the moment. We have reasonable traffic (500k UVs / month, 9million PVs), but regularly miss out on campaigns that would fit our site perfectly. Infact, we usually see them on other websites (same industry, different space) and then call up the buying agency who have "already spent all the budget".
Frustrating! We have an advertising agent which is currently taking 35%. Between them and our backfill we still only monetize around 50% of our inventory each month.
Surely the best defense against this is writing every query yourself rather than letting Rails do it? (As implied in the article).
My argument isn't Ruby execution speed vs PHP execution speed, it's Ruby writing it's own SQL vs me writing it.
I agree 100% that the database is usually the bottleneck, it certainly is for my site.
I'm sure Rails is great for getting an application up quickly, but once you get some traffic and the application gets more complex surely you'd end up hacking it so much you might as well have written from scratch in PHP or similar?
That article just confirmed that I made the right decision when staying well clear of Rails.