MySQL supports [named] placeholders just fine. It is PHP that does not. PHP is the suck for databases unless you use PDO. See examples 1737 for named placeholders and 1738 and 1739 for prepared statements.
I recommend prepared statements with positional placeholders (the '?' style) as the exact same sytax is used with Java, PHP, and Perl.
I basically use emacs like I use pico - simple editing, search and replace, and most importantly syntax highlighting. (Yes, nano can do syntax highlighting too, but it is not as advanced.)
.org is "thick" -- meaning the registry stores WHOIS information..com and.net are "thin" -- meaning registrars store WHOIS information.
And yes, whois should NEVER be used for availability (and no registrar uses it for availability) -- they use the Domain Check command to see if a domain is available.
I was thinking about this.. how nice it would be to accumulate ultra-mod-points over time. Where you can bank them forever (up to a max limit of 5 or so). And when you find that gem of a comment, you can toggle the display to ultra-ratings-mode and spend your ultra-mod-point.
The ultra-mod-point would add +1 to any comment, but has the ability to move a 5 to a 6. Some special icon (a lame star?) could be used to signify comments with an ultra-mod-point attached. Of course user preferences could ignore them.
Ultra-mod-points would need to be doled out in a more conservative manner than normal mod points -- say for each 15 or 20 regular mod points (with decent meta-moderation applied to those mods), a user would receive 1 ultra mod point. As they would be rare, users would hopefully save them for the appropriate time.
The Boot has not yet kicked any uncompliant.mobi domain operators, but the guidelines are pretty clear.
I would say most corporations understood the.mobi policies before registering their domains. Unfortunately, the vast majority of the.mobi space is "dead" -- meaning no live sites. The trademark holders bought.mobi domains and they sit on them, while they serve mobile content from subdomains or URLs under the ubiquitous.com TLD.
All it would take is for a couple large web entities to advertise their.mobi domains and the TLD would take off. But as long as Joe Sixpack always types.com (on their PC or phone), dot-mobi will remain asleep.
Also, there has been a vast domain name speculation in the.mobi space -- with many short and numeric domains fetching several hundreds of dollars without any web traffic (mobile or otherwise). Most of these domains are serving pay-per-click sites while the owners hope the TLD will appreciate.
Vector graphics should scale beautifully to any size. (It might be processor heavy though.) And some simple [java]script to manage a dynamic UI will hopefully not be too processor intensive.
I don't think that [AJAX] should be used to make complex apps (such as eMail software)
Why not? AJAX just uses a basic http request (ala XMLHttpRequest() or equivalent). How is this http request any different than a non-ajax http request?
Any time you are dealing with an authenticated login, you're either reading the session ID from a cookie or the URL. The ajax request sends the cookie (in the header) or the session ID in the URL of the "get/post", just like a request from a browser.
I have a reason why SOME complex apps could benefit from AJAX: they could make the user interface more helpful and responsive. In my experience, complex apps usually require performance tuning. Enhancing the responsiveness of the GUI could be implemented with AJAX.
It is not just game developers that function in groups with "goofing off time". Any non-corporate (or non-corporate-wannabe) software company allows engineering teams to work the hours they see fit, as long as they get their shit done. And usually, they have unrealistic deadlines. So blowing off 6 hours a week (~1 hour a day) is nothing compared to their 50+ hours of real work they do.
All work and no play makes Jack a dull boy.
Creative people work creatively. Smart companies allow developers time to mess around. As generally they discover ideas about how to do their job better.
Third, using Integer opens you to NullPointerExceptions
Exactly why I use Integer over int in most cases. With int, you cannot have an undefined value, with Integer you can. Sometimes, the int/Integer may be optional. If there is data there (!= null) I can use it, else I won't. With an int, you can't do that check, it is always defined.
So, like most programming decisions, it all depends on your needs.
Dual boot is okay, but can Windows read linux FS?
on
Why Gaming Sucks On Linux
·
· Score: 2, Insightful
Dual booting is okay for games, but how about when you want to play music in the background? And all of your music is on your ext3, Reiser, or XFS file system? How is the read/write support from windows back to linux? I think there have been advances on read/writing NTFS from linux, but how about the other way around?
... or allowing mulitple passphrases to decrypt the data (thus weakening the strength of the encryption).
How does allowing multiple passphrases to decrypt / unlock the KEY weaking the "strength of the encryption"? As you said in your other posts, the passphrase[es] do[es] not encrypt the data, it [they] only unlock[s] the keys.
I don't see how multiple passphrases to the same set of keys hinders the strength of those keys. If one passphrase is somehow compromised (say, the post-it was found, but the laptop was away) you have to recreate all passphrases. This is the same as having only one passphrase to begin with - you'll still need to recreate the passphrase.
As long as you employ the same method of weak passphrase checking, it doesn't matter if you have one passphrase, or 10. (I guess it might matter if you have an order of magnatude more passphrases, as statistically, it might be easier to brute force one -- but really, how many people are sharing this one laptop?)
Apart from a layer of security, just how complex does the software have to be?
This software was developed with resources from government contacts. By that definition alone, it must not be simple software.
Why the hell does something of this level of incomplexity even need to be closed source?
If the hardware and software were open source, the public could discover that the hardware/software allows the altering of votes. Thus, to ensure government contracts, granted by people/parties that wish to stay in power by altering votes, the source must remain closed and secret.
I wonder how difficult it might be to get a stack of CDs containing truecrypt, GPG, [insert favorite crypto software here], etc. at one of those airport bookstores? You would include the source and binaries for as many operating systems and languages as possible. Proceeds from the CDs could go to the project authors.
Heh, you better not rely on javascript to validate your forms. What happens when the malicious user disables/modifies the javascript? You still need to send that data to a server-side process for validation.
Using asynchronous javascript to send the data to the server and get the response is a way of saving time by drawing less of the page. But you still need to server-validate.
SSL doesn't prevent phishing. A signed SSL cert from a trusted Certificate Authority only assures the user that the information passing between the user and the domain is encrypted. SSL can't tell you if a site is "real" or not.
How does paying "extra" for a DNS server do anything with respect to phishing? The days of cache-poisoning DNS servers are going the way of the open SMTP relay. They are almost non-existant.
Not a bad idea, but it does stifle growth in new areas. Wikipedia's already gone to the extreme on pages that get too many edits (locked for awhile). But hiding pages that have only a few edits doesn't help make the content any better.
You could take the time to edit the pages you belive to have false information. Then they would be reviewed.
Slashdot Mirror
MySQL supports [named] placeholders just fine. It is PHP that does not. PHP is the suck for databases unless you use PDO. See examples 1737 for named placeholders and 1738 and 1739 for prepared statements.
I recommend prepared statements with positional placeholders (the '?' style) as the exact same sytax is used with Java, PHP, and Perl.
Emacs is the next logical step from pico/nano.
I basically use emacs like I use pico - simple editing, search and replace, and most importantly syntax highlighting. (Yes, nano can do syntax highlighting too, but it is not as advanced.)
Monotone is so 1960s.
The hottest pepper record has been broken.
In the Scoville Organoleptic Test, the Bhut Jolokia pepper scores over 1,000,000
The .name registry charges for WHOIS contact details already.
https://whois.nic.name/
.org is "thick" -- meaning the registry stores WHOIS information. .com and .net are "thin" -- meaning registrars store WHOIS information.
And yes, whois should NEVER be used for availability (and no registrar uses it for availability) -- they use the Domain Check command to see if a domain is available.
However, registrars do use WHOIS for Transfers.
I was thinking about this.. how nice it would be to accumulate ultra-mod-points over time. Where you can bank them forever (up to a max limit of 5 or so). And when you find that gem of a comment, you can toggle the display to ultra-ratings-mode and spend your ultra-mod-point.
The ultra-mod-point would add +1 to any comment, but has the ability to move a 5 to a 6. Some special icon (a lame star?) could be used to signify comments with an ultra-mod-point attached. Of course user preferences could ignore them.
Ultra-mod-points would need to be doled out in a more conservative manner than normal mod points -- say for each 15 or 20 regular mod points (with decent meta-moderation applied to those mods), a user would receive 1 ultra mod point. As they would be rare, users would hopefully save them for the appropriate time.
ExtJS appears to have interesting license requirements.
It is released under a commercial license and LGPL 3, but only for certain uses.
The Boot has not yet kicked any uncompliant .mobi domain operators, but the guidelines are pretty clear.
.mobi policies before registering their domains. Unfortunately, the vast majority of the .mobi space is "dead" -- meaning no live sites. The trademark holders bought .mobi domains and they sit on them, while they serve mobile content from subdomains or URLs under the ubiquitous .com TLD.
.mobi domains and the TLD would take off. But as long as Joe Sixpack always types .com (on their PC or phone), dot-mobi will remain asleep.
.mobi space -- with many short and numeric domains fetching several hundreds of dollars without any web traffic (mobile or otherwise). Most of these domains are serving pay-per-click sites while the owners hope the TLD will appreciate.
I would say most corporations understood the
All it would take is for a couple large web entities to advertise their
Also, there has been a vast domain name speculation in the
Does anyone use .mobi domains?
Vector graphics should scale beautifully to any size. (It might be processor heavy though.) And some simple [java]script to manage a dynamic UI will hopefully not be too processor intensive.
Agreed -- I want my quad core on one chip!
Why not? AJAX just uses a basic http request (ala XMLHttpRequest() or equivalent). How is this http request any different than a non-ajax http request?
Any time you are dealing with an authenticated login, you're either reading the session ID from a cookie or the URL. The ajax request sends the cookie (in the header) or the session ID in the URL of the "get/post", just like a request from a browser.
I have a reason why SOME complex apps could benefit from AJAX: they could make the user interface more helpful and responsive. In my experience, complex apps usually require performance tuning. Enhancing the responsiveness of the GUI could be implemented with AJAX.
It is not just game developers that function in groups with "goofing off time". Any non-corporate (or non-corporate-wannabe) software company allows engineering teams to work the hours they see fit, as long as they get their shit done. And usually, they have unrealistic deadlines. So blowing off 6 hours a week (~1 hour a day) is nothing compared to their 50+ hours of real work they do.
All work and no play makes Jack a dull boy.
Creative people work creatively. Smart companies allow developers time to mess around. As generally they discover ideas about how to do their job better.
Exactly why I use Integer over int in most cases. With int, you cannot have an undefined value, with Integer you can. Sometimes, the int/Integer may be optional. If there is data there (!= null) I can use it, else I won't. With an int, you can't do that check, it is always defined.
So, like most programming decisions, it all depends on your needs.
Dual booting is okay for games, but how about when you want to play music in the background? And all of your music is on your ext3, Reiser, or XFS file system? How is the read/write support from windows back to linux? I think there have been advances on read/writing NTFS from linux, but how about the other way around?
How does allowing multiple passphrases to decrypt / unlock the KEY weaking the "strength of the encryption"? As you said in your other posts, the passphrase[es] do[es] not encrypt the data, it [they] only unlock[s] the keys.
I don't see how multiple passphrases to the same set of keys hinders the strength of those keys. If one passphrase is somehow compromised (say, the post-it was found, but the laptop was away) you have to recreate all passphrases. This is the same as having only one passphrase to begin with - you'll still need to recreate the passphrase.
As long as you employ the same method of weak passphrase checking, it doesn't matter if you have one passphrase, or 10. (I guess it might matter if you have an order of magnatude more passphrases, as statistically, it might be easier to brute force one -- but really, how many people are sharing this one laptop?)
If the hardware and software were open source, the public could discover that the hardware/software allows the altering of votes. Thus, to ensure government contracts, granted by people/parties that wish to stay in power by altering votes, the source must remain closed and secret.Interesting use of lots of small files (with few lines) to store information, versus a few files (with lots of lines) to store information.
Also, a filesystem IS a database already. It is a hierarchical database, not a relational database.
Also add Portland, OR
Just a thought.
Heh, you better not rely on javascript to validate your forms. What happens when the malicious user disables/modifies the javascript? You still need to send that data to a server-side process for validation.
Using asynchronous javascript to send the data to the server and get the response is a way of saving time by drawing less of the page. But you still need to server-validate.
The review needs to include information from the book -- give at least 2 example hacks so I can understand what types of hacks these are.
This was _not_ a "book review" it was a fluffy "opinion about a book".
SSL doesn't prevent phishing. A signed SSL cert from a trusted Certificate Authority only assures the user that the information passing between the user and the domain is encrypted. SSL can't tell you if a site is "real" or not.
How does paying "extra" for a DNS server do anything with respect to phishing? The days of cache-poisoning DNS servers are going the way of the open SMTP relay. They are almost non-existant.
Not a bad idea, but it does stifle growth in new areas. Wikipedia's already gone to the extreme on pages that get too many edits (locked for awhile). But hiding pages that have only a few edits doesn't help make the content any better. You could take the time to edit the pages you belive to have false information. Then they would be reviewed.