MarkMail archives a bunch of OSS mailing lists with a nice web interface to the archives. Senders to the list still need to use SMTP though. http://markmail.org/
If your list is private, it appears MarkMail may still work, but you'll need to contact them for pricing. I'm sure other comments will contain better options for private email list management via web interface.
The one nice thing about regular old email is the low tech knowledge required to contribute to the discussion. From the summary, it appears all the current members know how to email already (though I'm sure top-posting is a problem).
Even if that's true, I say the better for it! With the Apache Software name behind a project, OSS developers are more willing to bet their time investment into an ASF project than an OSS project released directly by a commercial vendor.
The comments on SlashBI are great too. I also wanted to know how to query data out of your "documents" as the Wikipedia page doesn't describe that. Using the SlashBI example, show me all contact objects with state = "DC" or all records where last name ilike 'o_ama'. Does performing a search like that iterate over all records? Do you need to enable some full-text indexing of your entire document store to be able to execute queries like that?
I too was looking for the discussion as to why a high-earning VP performed this scam.
It seems like a lot of time was spent to buy all these items at retail stores, document everything on ebay, and often travel to a shipping center to fulfill the ebay orders in addition to attempting to keep a high seller rating. Even as a hobby, this seems like a lot of time spent for a major company executive.
You'll need some sort of LDAP server for the shared contacts, and other data storage (e.g. permissions, roles). The bad news is managing LDAP sucks (e.g. OpenLDAP). The good news is that almost everything supports LDAP for authentication. Even roundcube webmail works well with LDAP for auth and shared contacts.
My HOA is the same way. We can barely get enough bodies AND proxy votes to achieve a quorum each year, let alone 2/3 to change any of the CC&Rs. Everyone bitches about what they agreed to in the CC&Rs (like you can't have a white vinyl fence, but you can have a tan vinyl fence) but we'd never come close to enough votes to change them -- even if a proxy letter was mailed to each household with a self-addressed & stamped envelope!
But besides enforcing a few appearance rules and keeping the common areas kept, what should homeowners care about in their HOA? If anything, an HOA mirrors larger governments - if they work well enough and leave most people alone, no one cares enough to change anything. But maybe that's not a bad thing... stability is comforting.
The same for.jobs and.travel who's registry operator verifies the website contents before allowing the nameservers in DNS. (Which is why steve.jobs never resolved anywhere.)
Those > 3 character TLDs seem to adequately fit under their respective namespaces, unlike domain names under generic top level domains (gTLDs), as by nature, they are generic and can have non-profits under.com and for-profit companies under.org and personal blogs under.net.
Uh, no. All of these new gTLDs (generic top level domains) will be "sponsored" by ICANN and run by various registries (private corporations or public ones) under an ICANN agreement. The agreements are periodically "refreshed" through ICANN proposals (just like com/net/org/etc are today) where the statutes of the agreements may change.
So in the application for.secure, the applicant puts in whatever rules they want (e.g. for.slashdot, each registrant must list their UUID and have excellent karma) and if ICANN approves it, then the registry operator enforces those rules. Additionally, registrars (the middleman in the ICANN three tiered model of registry, registrar, registrant) must be ICANN accredited, even if they only wish to manage domains under a single TLD.
ICANN runs the root servers (with the US DoC ultimately controlling the root servers) so they can decide how new gTLDs get managed. I agree with the GP of this post, as ICANN is getting crazy with a flood of new TLDs instead of slowly deliberating over a handful of sTLDs (sponsored top level domains) like in the last decade (see.mobi,.pro,.coop,.museum, etc.)
Who cares about encrypted email when it all passes through (gets copied to) Utah as most MTAs don't use TLS by default. So your mail goes in or out in plaintext. Assuming both clients are end-to-end encrypted, emailing another user of the same ISP should be secure.
It's a good point about breaking IMAPS or other protocols that expect the contents to be unencrypted (at least in memory / ramdisk) on the server. They could provide a webmail client where local javascript performs the decryption with your private key. (Sorting and searching would still be a bitch unless like you suggested, they keep headers unencrypted.)
That and Google has been working to reduce the latency of SSL negotiation including the use of False Start (reduce round trips), Next Protocol Negotiation (IETF draft mod of TLS handshake), and Snap Start (OSCP and cert caching). [Scroll to bottom of article for links to these changes.]
This work applies to HTTP/1.1 and will be even better in HTTP/2.0
So much content is dynamically "tagged" to be unique to the current browsing session, that caching HTTP proxies are becoming less useful. CSS and JS resources are modified with unique IDs and many admins reduce cache-control on the server headers to easily update their websites so they don't have to wait for some HTTP cache to expire somewhere between their server and the client.
I would say the privacy of having HTTPS everywhere far outweighs (on a social/society/individual level) the small benefit of middle-man cache (obviously the clients can still cache resources over SSL).
It also helps thwart (somewhat) network operators from mangling your traffic as their deep packet inspection isn't as useful on encrypted traffic.
Actually, I have TitaniumBackup write to/sdcard then I mount the device over USB mass storage (though I hear that'll be removed in future versions) and rsync everything just like a regular rsync backup script (--link-dest hard links and all that jazz).
You shouldn't lose anything if you root your stock device. Installing a new rom will of course wipe everything. However, root allows you to truly backup everything on your device. (Check out TitaniumBackup once you root.)
You mean sandbox the app itself as it calls the ad library which execute the remote code? But you've already granted that app the permissions necessary to do bad things!
As each android app runs as a separate uid, it makes it easy to block net access app-by-app. The problem, of course, is when the app you don't really trust needs net access for a real reason. Sometimes you can allow net access, let the app do it's thing, then revoke it so it's not background connecting all the time.
Also the ability to set some apps wifi-only and others 3G-only is pretty handy. This saves hours of battery life.
Slashdot Mirror
That's exactly what ICANN has done with this new gTLD process!
For $185k you can apply for your own Top Level Domain. You might have to wait a few years to get in on the next round of application submissions.
MarkMail archives a bunch of OSS mailing lists with a nice web interface to the archives. Senders to the list still need to use SMTP though. http://markmail.org/
If your list is private, it appears MarkMail may still work, but you'll need to contact them for pricing. I'm sure other comments will contain better options for private email list management via web interface.
The one nice thing about regular old email is the low tech knowledge required to contribute to the discussion. From the summary, it appears all the current members know how to email already (though I'm sure top-posting is a problem).
Even if that's true, I say the better for it! With the Apache Software name behind a project, OSS developers are more willing to bet their time investment into an ASF project than an OSS project released directly by a commercial vendor.
Um, how about "in-app" or "in-game" purchases?
http://apple.slashdot.org/story/11/11/02/0619226/free-games-dominate-top-grossing-game-list-on-app-store
Don't forget to protect your .bash_history!
The comments on SlashBI are great too. I also wanted to know how to query data out of your "documents" as the Wikipedia page doesn't describe that. Using the SlashBI example, show me all contact objects with state = "DC" or all records where last name ilike 'o_ama'. Does performing a search like that iterate over all records? Do you need to enable some full-text indexing of your entire document store to be able to execute queries like that?
I too was looking for the discussion as to why a high-earning VP performed this scam.
It seems like a lot of time was spent to buy all these items at retail stores, document everything on ebay, and often travel to a shipping center to fulfill the ebay orders in addition to attempting to keep a high seller rating. Even as a hobby, this seems like a lot of time spent for a major company executive.
You'll need some sort of LDAP server for the shared contacts, and other data storage (e.g. permissions, roles). The bad news is managing LDAP sucks (e.g. OpenLDAP). The good news is that almost everything supports LDAP for authentication. Even roundcube webmail works well with LDAP for auth and shared contacts.
My HOA is the same way. We can barely get enough bodies AND proxy votes to achieve a quorum each year, let alone 2/3 to change any of the CC&Rs. Everyone bitches about what they agreed to in the CC&Rs (like you can't have a white vinyl fence, but you can have a tan vinyl fence) but we'd never come close to enough votes to change them -- even if a proxy letter was mailed to each household with a self-addressed & stamped envelope!
But besides enforcing a few appearance rules and keeping the common areas kept, what should homeowners care about in their HOA? If anything, an HOA mirrors larger governments - if they work well enough and leave most people alone, no one cares enough to change anything. But maybe that's not a bad thing... stability is comforting.
Companies incorporate in Delaware due to low state taxes.
You do not need a physical presence in Delaware to incorporate there, just a registered agent.
There are a few .museum domains in use: http://index.museum/fullindex.php
Even more .aero domains in use: http://www.nic.aero/cgi-bin/ad_search.cgi (hit the search without changing the form)
The same for .jobs and .travel who's registry operator verifies the website contents before allowing the nameservers in DNS. (Which is why steve.jobs never resolved anywhere.)
Those > 3 character TLDs seem to adequately fit under their respective namespaces, unlike domain names under generic top level domains (gTLDs), as by nature, they are generic and can have non-profits under .com and for-profit companies under .org and personal blogs under .net.
Uh, no. All of these new gTLDs (generic top level domains) will be "sponsored" by ICANN and run by various registries (private corporations or public ones) under an ICANN agreement. The agreements are periodically "refreshed" through ICANN proposals (just like com/net/org/etc are today) where the statutes of the agreements may change.
So in the application for .secure, the applicant puts in whatever rules they want (e.g. for .slashdot, each registrant must list their UUID and have excellent karma) and if ICANN approves it, then the registry operator enforces those rules. Additionally, registrars (the middleman in the ICANN three tiered model of registry, registrar, registrant) must be ICANN accredited, even if they only wish to manage domains under a single TLD.
ICANN runs the root servers (with the US DoC ultimately controlling the root servers) so they can decide how new gTLDs get managed. I agree with the GP of this post, as ICANN is getting crazy with a flood of new TLDs instead of slowly deliberating over a handful of sTLDs (sponsored top level domains) like in the last decade (see .mobi, .pro, .coop, .museum, etc.)
My 40,000 years of human ancestry from sitting around the fire like the 2700K warm & "yellow" light!
Who cares about encrypted email when it all passes through (gets copied to) Utah as most MTAs don't use TLS by default. So your mail goes in or out in plaintext. Assuming both clients are end-to-end encrypted, emailing another user of the same ISP should be secure.
It's a good point about breaking IMAPS or other protocols that expect the contents to be unencrypted (at least in memory / ramdisk) on the server. They could provide a webmail client where local javascript performs the decryption with your private key. (Sorting and searching would still be a bitch unless like you suggested, they keep headers unencrypted.)
Supposedly my dad laid down the sod in his own backyard...
Hey - I laid down sod in my own backyard... so get off my lawn!
That and Google has been working to reduce the latency of SSL negotiation including the use of False Start (reduce round trips), Next Protocol Negotiation (IETF draft mod of TLS handshake), and Snap Start (OSCP and cert caching). [Scroll to bottom of article for links to these changes.]
This work applies to HTTP/1.1 and will be even better in HTTP/2.0
So much content is dynamically "tagged" to be unique to the current browsing session, that caching HTTP proxies are becoming less useful. CSS and JS resources are modified with unique IDs and many admins reduce cache-control on the server headers to easily update their websites so they don't have to wait for some HTTP cache to expire somewhere between their server and the client.
I would say the privacy of having HTTPS everywhere far outweighs (on a social/society/individual level) the small benefit of middle-man cache (obviously the clients can still cache resources over SSL).
It also helps thwart (somewhat) network operators from mangling your traffic as their deep packet inspection isn't as useful on encrypted traffic.
Actually, I have TitaniumBackup write to /sdcard then I mount the device over USB mass storage (though I hear that'll be removed in future versions) and rsync everything just like a regular rsync backup script (--link-dest hard links and all that jazz).
The sdcard is the one thing that's trivial to backup - root or no-root! As it's removable, remove it and copy it.
You shouldn't lose anything if you root your stock device. Installing a new rom will of course wipe everything. However, root allows you to truly backup everything on your device. (Check out TitaniumBackup once you root.)
You mean sandbox the app itself as it calls the ad library which execute the remote code? But you've already granted that app the permissions necessary to do bad things!
Got root?
An iptables front-end on Android. Droid Wall is sweet: https://play.google.com/store/apps/details?id=com.googlecode.droidwall.free
As each android app runs as a separate uid, it makes it easy to block net access app-by-app. The problem, of course, is when the app you don't really trust needs net access for a real reason. Sometimes you can allow net access, let the app do it's thing, then revoke it so it's not background connecting all the time.
Also the ability to set some apps wifi-only and others 3G-only is pretty handy. This saves hours of battery life.
I want to know more about this fast-drip coffee maker! Is it like a french press that presses itself?
I pity your Nascar-influenced dreams. (And aren't the advertisements terrible? Perhaps you have some audio normalization?)
Transparent aluminum [residential house]
Pics or it didn't happen!