![]() |
Presentation&Description
Hi,
My name is Carlos and English is not my maternal, anyway the presentation is made. I'm looking for one small group of webmasters to start working with one client api. How can I open your 'appetite'? You can see one example here -> porn.premium-sponsor.com To resume as much as possible: -> Small group(3 maximum), because I've a lot of things to organize, even the scalability. Later all the webmasters can participate. -> I require that webmasters have traffic of good quality; -> I require that promotions(pub) used have the reference of my account in it's creation. Not the sources, I'm offering the references of sources to webmasters in further development. -> I could write a lot of things, but it's better to start talking by skype or email about the possibilities. It's only the beginning and let's do it well ... Best regards, Carlos |
|
That was a flashback.[/QUOTE]
----------------------------- Hi, I don't understand what you mean with this message, anyway the flashback in my mind is not really present, what I see in the technical consequence of is straight forward ... I set my focus where it should be set, and I don't know the limits of your vision to consider this flashback. It's what I'm looking for and what others have to say about it has no value because the issue is not related. |
Quote:
|
Quote:
I'm still not understanding the context of these messages, anyway the webmasters interested should send me one message(private or not) where it's written I'm interested and from this point we'll talk by skype, email or using the system of private messages I'd write ... I don't know what people are expecting but as far as I'm concerned I need to organize the scalability, restart recovering n millions of thumbs per day and step further with several things ... For my side it's more complex than poeple think and from the webmaster's side it's kind of obvious and the requirements I described are requirements to not think differently or loose time thinking about that(...) If you tell me that one Sponsor only accepts one reference/one account, that's not my problem, it's their problem and it's them who must change for sure ... |
Let me finish this with the follwoing statement.
As far as I'm concerned, in the further development of this, things are integrated the way I consider better(technically,logically,etc) and if others don't agree, it's their problem, not mine, I don't change my opinion based in absurduties of others ... Whatever others have to say about it, have no value at all, and is certainly not an issue on the table ... or the table starts with the dispatcher of one banana to be eaten in front of me preparing the speach of absurdities that comes next, I'll just interrupt it and say, you've more sucess eating banans than saying whatever related with ... I'm being direct ... |
Bienvenido, Carlos ...
|
Plus this information...
Hi,
To finish this countless issues that I try to describe shortly ... If you think about the float (account.premium-sponsor.com) for example, that's the tool that will allow me to not charge you hosting for example, develop your member zone, etc ... And even that we'll see clearly and the solutions are naturally complex and will be sustained by several levels ... if it's one webmaster with several domains the registered users belong to the webmaster's account and to premium-sponsor.com I can't precise numbers ... but if the member zone per client api pays the hosting and drives more revenue for the webmaster's account->that's perfect! |
Welcome to GFY :thumbsup
I am totally not getting what you are trying to sell though. |
Quote:
I'm not trying to sell whatever, there is nothing to sell. If there are webmasters interested in working with the client api, few rules were described. The rest comes after and the rest is everything related with. If one webmaster has one network with 100k visits per day, pays the hosting to start developing it's business and if the hosting is paid in the promotions ... we'll see ... I'm not paying it. I need to organize the scalability, etc ... |
|
Hi,
You read what is written. Regarding dating and as sooner or later only solutions where the tracking of client apis in the webmaster's accounts with full acess to database of registered users will be accepted ... One thing are the registered users of webmaster's account of premium sponsor, another are the registered users of premium-sponsor.com and another is what you or any other similar service offer ... (...) |
I've more or less ready one complex system of sessions that will log automatically users, no matter the client api. It's unecessary to ask the same user to creater several logins per client apis ...
This will lead to technical issues of %'s in the reference of creation of account, etc when one act will occur and this act can be someone buying something somewhere ... This is not obvious and is not based in the simplicity of what others are capable of doing(...), it's technically complex and the complexity increases on time ... |
Quote:
|
Quote:
|
Quote:
|
Hi,
Ok, I started my post with that issue. What you read is how I talk&write naturally without external help or any special effort. What is important it's to get the 'main picture', the rest comes after including people preparing everything in english and even other languages ... Best regards, Carlos |
Let me add this. Regarding the issue of the language, sometimes it's not the fact of speaking/writting in the maternal language that will allow other people to understand what's written.
I speak English, French, Portuguese(maternal language) and Spanish(I understand almost everything reading) ... and I'm sure that a lot of portuguese people wouln't understand whatever of what I wrote In English if I was writing in Portuguese ... the same way I consider that a lot of people who speak English wouldn't understand it ... Is this one problem? Several issues are technical and several issues are more technical than people think ... and are not words choosen with perfection without meaning/context that solves the problem and allow people to understand ... I'm not writting more ... |
Quote:
No offence, but either you are a somewhat clever written bot or you are using some translation tool. Or so I hope, because otherwise.. wtf :1orglaugh |
Quote:
Just keep in mind the following and it's my last explanation because I'm tired, I'm not a bot and I'm not using any translation tool and if you read what I wrote, arriving here you're capable of understanding(...): a) example of client api (porn.premium-sponsor.com) b) sources (in that particular example are tubes but could be whatever, even content from conventional sponsors organized), you can expand this with your reference inviting new webmasters after(id) c) Pub, are areas related with pub where solutions kind of exoclick ,etc(even banners of conventional sponsors) can be integrated. In the Pub I require that the ID you place has the reference of my account in it's creation(referrer), and I'll touch one comission in every sale you do. d) account.premium-sponsor.com, it's how I pretend to develop/implement member zones of webmasters ,etc ... even importing content from sponsors if necessary ... Each webmaster will be able to have the database of registered users and promote services, member zones, etc. It stays also associated to premium-sponsor.com. e) Hosting, I'm not paying it, I might consider that if the promotions(pub), etc are enough to pay it. I will set my focus in the scalability and architecture of ... f) The rest is naturally complicated ... g) I'm only seeking for 3 webmasters to start ... later it will be opened to all the webmasters interested, I can't do it know, I've the scalability/architecture/etc to organize ... The isses/possibilities will be countless but what is important is to find out one good base to start, the rest comes after ... It's me who laughs, believe me ;) ... Best regards, Carlos |
Quote:
|
Let me share this with you to finish ...
When I write about scalability and architecture, these are issues that are directly related with what you do. If there are n client apis being indexed by search engines, there are several technical issues that must be taken in consideration to allow this to work well, with stability, speed, perfection, etc. Scalability and architecture here means the necessary structure expressed in servers to sustain any increase of traffic related with, If this isn't well organized it's impossible 'for the rest' to work well ... Beyond this there are the analytics, sessions, logs, etc to organize ... (...) Best regards, Carlos |
+ This information because I'm thinking about this particularity in the complexity of ...
Regarding registered users: 1 - One thing are registered users of one account of webmaster of premium-sponsor.com with several domains; 2 - Another are registered users of premium-sponsor.com 3 - Another are registered users exported to premium sponsor to develop any external network I'd write (where the example of dating factory fits) in the extension of any client apis (main sections of account.premium-sponsor.com) and this with external and internal tracking included ... One webmaster can develop the member zones associated to his/her account in his/her domains. That login can be used to acess later other member zones of different accounts and one % will be paid to the reference of the account's creation. I'm looking at this in the particularity of the adult in account.premium-sponsor.com It's important to avoid several logins(...) but in the extension of that possibility exists, when registed users are exported. This might looks like complicated to understand but it's the way it's meant to be ... And this only one concept, after are technical issues behind this ... The idea in it's simplicity remains ... account.premium-sponsor.com + (reminder) plus.google.com/115617435215657833612/ English is not my maternal language ... Best regards, Carlos |
Not forgetting the technical restrictions that are necessarly required, because the last thing I want to see are n millions of unecessary calls without any sense of reasonability ... In one call we dump 8000 records for example per search string , the pagination in the server side does not exists if it's not really necessary,etc ... the display of pub will be avoided in the indexation of search engines ,etc ,etc ... All this complex information system will work with webservices, logs, etc ... This included with the problematic of SEO ,etc ... If one client api in the indexation of search engines (level of search string) receives 100000 calls per day, n search strings(each search string dumps 8000 records),etc ,.. I hope I clarified all your reasonable doubts ... These technical issues are not to be donne the way people want -> it will follow techical restrictions -> and we won't use databases in the client api, we'll use hashed systems, complex systems of cache, systems of control of remote cache, etc(...) (...) Best regards, Carlos |
All times are GMT -7. The time now is 02:47 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc