That's the point! Copyright the exact work, while the concept is available for anyone to re-implement. This happened in software for years before software patents.
When the employee dies the copyright could still go away.
Unfortunately, companies would attempt to hire only young and healthy employees.
Better to make copyright a small fixed term like 15 years. Then even legal persons (companies) could own the right to limited monopoly of that work, as long as it expires in a relatively short period of time.
I do too, but it's a pain for *.google.com and similar properties, because they have concurrently use certs from two or more CAs. Thus when bouncing between random webservers for google, the cert appears to change. Trusting even the CA doesn't help as the CAs change. So I just look at the CAs themselves and the dates and sometimes investigate the details like key size and TLS mentions and email address; things a sloppy attacker may miss if they're trying to MITM me.
The Toshiba Thrive android tablet (an early one) has 2x full size female USB ports for connecting card readers, keyboards, mice, etc. and full size HDMI out and a full size SD card slot (not microSD). Yes, the tablet is larger, and heavier than other 10" models. Yet I think many consumers would accept the larger size for the full size ports.
Except chmod breaks the camera on some devices. Fixes were outlined in the xda-developers thread to white-list specific DMA regions for the camera to function, instead of all lowmem.
Once you root, you need to disable all the built-in shitty apps. I wrote a script to mkdir/system/app/disabled and then mv/system/app/${shittyapp}/ to/system/app/disabled/
Easy to regex search/replace that disable.sh script to undo it (enable.sh) when you want to un-root so you can OTA upgrade (if you so choose).
Script disables I500_BingSearchAndroid_07152010.apk so I can install EnhancedGoogleSearchProvider.apk to "de-Bing".
I'm still on stock Fascinate 2.2 (didn't see the point of 2.3 on this phone, plus the fonts look worse) but rooted with all the bloatware removed and Droidwall, etc installed. I get great battery life with 3G, Wifi, Bluetooth, GPS all turned off - and only turn them on when wanted.
Using SPF is a bare-minimum for even a self-run SMTP server that only has a handful of users with no mailing lists. Anything larger needs DKIM.
One other thing Bennett can try is to have a pipeline of registered domains ready to be used. Each domain in each URL is scanned by spam filter, and young domains (via registration age in WHOIS or the daily registry-published zone-file which yahoo/hotmail/gmail all have) are more "spammy" than older domains, simply because spammers do the same thing here - register new domains and mass-email them out as URLs.
What a whiny non-response from Jono Bacon. His counter argument to Stallman is: [summarized] "Privacy is personal, there is only one RMS who cares about privacy in his own way, so we can collect your data. Look at Facebook and Apple: see, we're better!".
The community is fine with new features and trying out new things, but we just want the defaults to be sane. Only turn on Amazon searches or Canonical feedback as an op-in mechanism. A default install of any gnu/linux distro should be privacy-aware and not require disabling any features.
If you disable local indexing, and use Dovecot IMAPS with full text indexing, searching is beautiful in Thunderbird.
That said, tagging always is problematic for me; if multiple tbird clients connect to the same imap mailbox, and they each customize their tags (even just the color!) the tags are not shared. It seems Thunderbird does not write to the message on the server, but stores the tag locally (or instance B does not recognize instance A's tags).
Also, font-family and font-size switching commonly occur in the editor, which is annoying. HTML tables usually work really well for me, more so than other clients.
XMPP + email is perfect for the small business or even corporate setting. Many corps have an internal jabber server and Exchange; Thunderbird would handle those both with only one program + settings for IT to manage. Google Wave was just ahead of its time.
Include some sort of shared document viewer/launcher attached to various network shares and it would be a corporate work horse. Chat, calendar, email, documents, rss reader - all in one extensible package.
Agreed. I've been using 'place replies in folder of the original message' for years. The Sent folder is only used to quickly find what only I send, while I use the threaded view (in triple pane mode) to see all the messages in a thread.
Almost all mail clients that send will keep the same Thread-Topic and Thread-Index header in each email so viewing mail clients can easily piece them together. Thus the subject can change, but the thread will stay the same. Gmail fails at this as it forces the same subject in a thread. (Arguably, it's not a bad limitation, but with Thread- headers it is unnecessary.)
What is interesting about all of this is Afilias (the registry operator for.info) appears to be using the Spamhaus DBL in an automated fashion to add "serverHold" status to listed domains. ("serverHold" effectively removes the domain from the TLD root servers and can only be modified by the Registry. "clientHold" does the same thing, but can be modified by the Registrar, in this case eNom.)
In all of those documents, I see no mention of the registry operator (Afilias) being able to invoke their rights of RRA section 3.6.5 in an automated (API-used) fashion. You could email Afilias about it, but doubt they would respond. If we want to get to the bottom of how they are auto-serverHold-listing domains, it seems a lawsuit is the only way. Perhaps someone really did email abuse@afilias.info, and a human checked the SBL and looked at the batch of domains created near the same time from the same registrar.
Thanks, Bennett Haselton, for posting this article and telling us about these shady practices from Afilias.
If you wish to continue using.info, and eNom (namecheap), then it appears you should create separate accounts, and register 1-2 domains in each account, so at least they are not blocked as a group. Additionally, using multiple sets of nameservers will make the domains look "different" from each other.
Thanks for the response! I was hoping it was all mdadm, as I love to use software raid.
May I ask, what was your use-case for using this hybrid approach? Did you do much benchmarking with the applications you were trying to benefit from faster reads? Did you also tune FS parameters like +noatime and tweak block sizes and such to minimize writes?
Would a system like this with full disk encryption be any better/worse off? The first enc pass (say with truecrypt where it writes to the whole drive) adds extra wear, but it should happen only once with subsequent writes changing small portions of the disk.
Was this really 'dmraid' or 'mdraid ' ? I'm curious how you got reads to only come from the SSD, and also how do you force a write buffer when programs use fsync() calls? (Though I could live with slow writes with fast reads.)
It sounds awesome to use the SSD for reads, and 1 (or more) HDDs as a mirror in RAID1.
For firefox, use this excellent add-on for white-listing sites to allow cookies. Block all cookies by default, then only click to allow when you need it (login, shopping cart, etc.) A few poorly-coded websites "require" cookies; luckily Cookie Monster has a "Temporary Allow" which lasts for the current browser instance - or until you "Revoke" the temporarily allowed cookies.
A long open transaction (that's used the table in question) will block auto vacuum for those rows.
You can set options in postgresql.conf to auto-kill long transactions if you like (set a hard limit for transaction time).
I solved this another way by only examining IDLE transactions via pg_stat_activity. Any long running transactions are left alone, while long idle transactions are killed.
Slashdot Mirror
This is also the same as no-till farming and is growing in popularity worldwide.
That's the point! Copyright the exact work, while the concept is available for anyone to re-implement. This happened in software for years before software patents.
When the employee dies the copyright could still go away.
Unfortunately, companies would attempt to hire only young and healthy employees.
Better to make copyright a small fixed term like 15 years. Then even legal persons (companies) could own the right to limited monopoly of that work, as long as it expires in a relatively short period of time.
I do too, but it's a pain for *.google.com and similar properties, because they have concurrently use certs from two or more CAs. Thus when bouncing between random webservers for google, the cert appears to change. Trusting even the CA doesn't help as the CAs change. So I just look at the CAs themselves and the dates and sometimes investigate the details like key size and TLS mentions and email address; things a sloppy attacker may miss if they're trying to MITM me.
Do these dash cams have options to disable audio recording?
The Toshiba Thrive android tablet (an early one) has 2x full size female USB ports for connecting card readers, keyboards, mice, etc. and full size HDMI out and a full size SD card slot (not microSD). Yes, the tablet is larger, and heavier than other 10" models. Yet I think many consumers would accept the larger size for the full size ports.
Fixes were outlined in the xda-developers thread to white-list specific DMA regions for the camera to function, instead of all lowmem.
Except chmod breaks the camera on some devices. Fixes were outlined in the xda-developers thread to white-list specific DMA regions for the camera to function, instead of all lowmem.
Once you root, you need to disable all the built-in shitty apps. I wrote a script to mkdir /system/app/disabled and then mv /system/app/${shittyapp}/ to /system/app/disabled/
Easy to regex search/replace that disable.sh script to undo it (enable.sh) when you want to un-root so you can OTA upgrade (if you so choose).
Script disables I500_BingSearchAndroid_07152010.apk so I can install EnhancedGoogleSearchProvider.apk to "de-Bing".
I'm still on stock Fascinate 2.2 (didn't see the point of 2.3 on this phone, plus the fonts look worse) but rooted with all the bloatware removed and Droidwall, etc installed. I get great battery life with 3G, Wifi, Bluetooth, GPS all turned off - and only turn them on when wanted.
Using SPF is a bare-minimum for even a self-run SMTP server that only has a handful of users with no mailing lists. Anything larger needs DKIM.
One other thing Bennett can try is to have a pipeline of registered domains ready to be used. Each domain in each URL is scanned by spam filter, and young domains (via registration age in WHOIS or the daily registry-published zone-file which yahoo/hotmail/gmail all have) are more "spammy" than older domains, simply because spammers do the same thing here - register new domains and mass-email them out as URLs.
What a whiny non-response from Jono Bacon. His counter argument to Stallman is: [summarized] "Privacy is personal, there is only one RMS who cares about privacy in his own way, so we can collect your data. Look at Facebook and Apple: see, we're better!".
The community is fine with new features and trying out new things, but we just want the defaults to be sane. Only turn on Amazon searches or Canonical feedback as an op-in mechanism. A default install of any gnu/linux distro should be privacy-aware and not require disabling any features.
If you disable local indexing, and use Dovecot IMAPS with full text indexing, searching is beautiful in Thunderbird.
That said, tagging always is problematic for me; if multiple tbird clients connect to the same imap mailbox, and they each customize their tags (even just the color!) the tags are not shared. It seems Thunderbird does not write to the message on the server, but stores the tag locally (or instance B does not recognize instance A's tags).
Also, font-family and font-size switching commonly occur in the editor, which is annoying. HTML tables usually work really well for me, more so than other clients.
XMPP + email is perfect for the small business or even corporate setting. Many corps have an internal jabber server and Exchange; Thunderbird would handle those both with only one program + settings for IT to manage. Google Wave was just ahead of its time.
Include some sort of shared document viewer/launcher attached to various network shares and it would be a corporate work horse. Chat, calendar, email, documents, rss reader - all in one extensible package.
You, good sir, paint a scary but accurate picture of the future. Kinda reminds me of the conversation tele-screen "walls" of Fahrenheit 451.
Agreed. I've been using 'place replies in folder of the original message' for years. The Sent folder is only used to quickly find what only I send, while I use the threaded view (in triple pane mode) to see all the messages in a thread.
Almost all mail clients that send will keep the same Thread-Topic and Thread-Index header in each email so viewing mail clients can easily piece them together. Thus the subject can change, but the thread will stay the same. Gmail fails at this as it forces the same subject in a thread. (Arguably, it's not a bad limitation, but with Thread- headers it is unnecessary.)
Why don't you purchase one of these properties?
Yes, the answer to the poster's problem is to not use .info domains with this highly restrictive policy: http://info.info/information/anti-abuse-policy
What is interesting about all of this is Afilias (the registry operator for .info) appears to be using the Spamhaus DBL in an automated fashion to add "serverHold" status to listed domains. ("serverHold" effectively removes the domain from the TLD root servers and can only be modified by the Registry. "clientHold" does the same thing, but can be modified by the Registrar, in this case eNom.)
This is the official ICANN agreement and related documents that allows .info to function: https://www.icann.org/en/about/agreements/registries/info
This is the Registry-Registrar Agreement (RRA) containing section 3.6.5 referred do by the .info anti-abuse-policy: https://www.icann.org/en/about/agreements/registries/info/appendix-08-08dec06-en.htm
In all of those documents, I see no mention of the registry operator (Afilias) being able to invoke their rights of RRA section 3.6.5 in an automated (API-used) fashion. You could email Afilias about it, but doubt they would respond. If we want to get to the bottom of how they are auto-serverHold-listing domains, it seems a lawsuit is the only way. Perhaps someone really did email abuse@afilias.info, and a human checked the SBL and looked at the batch of domains created near the same time from the same registrar.
Thanks, Bennett Haselton, for posting this article and telling us about these shady practices from Afilias.
If you wish to continue using .info, and eNom (namecheap), then it appears you should create separate accounts, and register 1-2 domains in each account, so at least they are not blocked as a group. Additionally, using multiple sets of nameservers will make the domains look "different" from each other.
Thanks for the response! I was hoping it was all mdadm, as I love to use software raid.
May I ask, what was your use-case for using this hybrid approach? Did you do much benchmarking with the applications you were trying to benefit from faster reads? Did you also tune FS parameters like +noatime and tweak block sizes and such to minimize writes?
Would a system like this with full disk encryption be any better/worse off? The first enc pass (say with truecrypt where it writes to the whole drive) adds extra wear, but it should happen only once with subsequent writes changing small portions of the disk.
Was this really 'dmraid' or 'mdraid ' ? I'm curious how you got reads to only come from the SSD, and also how do you force a write buffer when programs use fsync() calls? (Though I could live with slow writes with fast reads.)
It sounds awesome to use the SSD for reads, and 1 (or more) HDDs as a mirror in RAID1.
For firefox, use this excellent add-on for white-listing sites to allow cookies. Block all cookies by default, then only click to allow when you need it (login, shopping cart, etc.) A few poorly-coded websites "require" cookies; luckily Cookie Monster has a "Temporary Allow" which lasts for the current browser instance - or until you "Revoke" the temporarily allowed cookies.
https://addons.mozilla.org/en-US/firefox/addon/cookie-monster/
And add Cookie Monster to use white-listed only [regular http] cookies!
Troll? That was funny!
https://www.youtube.com/watch?v=rdIWKytq_q4
Enjoy watching Apple fans "fall in love" with the "new" iPhone 5 !
(Spoiler: they're all playing with an iPhone 4s, thinking it's the new iPhone 5)
That's great and all, but what happens when you read page 200 and say "uh, I don't agree with this"?
Response: "Sorry, no house for you!"
A long open transaction (that's used the table in question) will block auto vacuum for those rows.
You can set options in postgresql.conf to auto-kill long transactions if you like (set a hard limit for transaction time).
I solved this another way by only examining IDLE transactions via pg_stat_activity. Any long running transactions are left alone, while long idle transactions are killed.