Quote
ndebord
Personal insults will not get you very far.
You are calling this:
Quote
kko
As far as I remember, it was not you, ndebord, who invested this time for the 1.0 and 1.1 releases. Think about that.
a personal insult?
Well, do you think that you're the only one who's allowed to criticize others? And when others are criticizing you then that's a personal insult? Is that your imagination of fairness? Do you think that this will get
you very far?
Quote
ndebord
If I could code, I would.
You know very well that you can participate in the project in a lot of ways that do not require any coding skills. And besides that, your postings here are demonstrating that you're not so unskilled as you pretend to be.
Quote
ndebord
Let's look at a sample of what is missing here and perhaps you can tell me what criteria you used to exclude these search engines.
As for the criteria, I dislike to repeat myself. Reread my first post and answer yourself (only one note: I've made the default list one year ago for the 1.0 release. Consequently, engines that have been added to the Wiki at a later time cannot be on this list). Since you haven't taken much care to create your list of examples (two thirds of the engines you mention are on the default list or they aren't on the Wiki list either), I see no need to go into detail.
Quote
ndebord
In addition, your claim that engines have been avoided because of adult content doesn't make any sense. If I use, say the largest and best-known search engine (Google) and type in an adult term, I would be overwhelmed with pages of links.
Is that meant to insult my intellect now, or what? I mean, when you're not holding me for completely dumb, it ought to be clear that I'm talking about 'search engines' which are actually porn sites and which are (possibly) showing explicit content on their result pages
although you haven't searched for that.
Quote
ndebord
P.S. BTW, if, as you claim, it took too much time for you to work through the search engine list, all you had to do was post a query for help in the user forum and I, among many others, would have been more than willing to help out in any way that we could.
It's rather cheap to say that now. And also rather inappropriate. I'd like to remind you that k-meleon development is driven by a team. As long as you have no insight into this team, you can hardly judge what the individual members of this team are doing. And thus you're not qualified to tell me what I could have done and what not. That's not only unfair in respect to me - as well as the others, I can only do what my time permits and I had to focus on more important things - it's also unfair in respect to desga2, since he worked through the list this time. And he did not need any invitation. Nobody asked him to work through the list (at least not me). He simply did it.
Some final thoughts:
The search engine list used by Advanced Preferences, is stored in a file called search.xml (search.cfg in km 1.0) which is located in the user's profile directory. This file is totally under the user's control, just like the bookmarks.html. Users can add, edit and remove search engines as they can add, edit and remove bookmarks. The default file is only used when you create a new profile. Thus, users will not benefit from updates to the default files when they don't create new profiles. And when they create new profiles, most users will anyway reuse their old search.xml (or search.cfg) once they've edited it, just as they will reuse their old bookmarks.html once they've created their own bookmarks. The purpose of these default files is only to provide some useful examples. The selection of these examples is always arbitrary and the collection can never be complete.
From my point of view, a discussion about what engines are in the default search.xml is as pointless as a discussion about what links are in the default bookmarks.html - it simply doesn't matter because the sense and the purpose of these files is that users make them fit their needs. If you wanted to share your search engines, also those of special interest, I'd suggest to create a new list in the Wiki. Users could then copy the engine names and URLs from the Wiki and paste them into the related dialog in Advanced Preferences to add the desired engines to their configuration. In my opinion, this would be more beneficial than adding countless engines to the default search.xml that are only useful to a split fraction of users and that actually prevent most users from finding what they're most frequently looking for. You will hardly improve usability by drowning users in a sea of engines. Can't we simply let the users decide themselves what engines are useful to them? Just as is it was best practice with the old search macros?