this makes no sense. if i sell a virtual item for USD, that is income and it is already taxed. stocks in a company are 'virtual' and existing in a 'computer simulation'. non-physical items are nothing new.
the other interpretation is impossibly ludicrous which is to tax items created and sold in-game with no real-world value. if thats the case then they must collect the taxes in the form of in-world items.
wireless access points could reinvent a local computer community. there is software being worked on to provide a "friendster" like site for those using the same wireless access point.
in the motherboard/cpu department at fry's i find the employees to be very knowledgeable. some of them are actually pc hardware nerds and know their stuff.
kinema - would you contact me about the portland GIS db request? im donp at personal telco dot net
first and foremost, use a publish/subscribe system. no more polling! jabber may be a good framework for this. upon joining an rss subscription you get a refresh and after that you get deltas.
as has been mentioned many times already, a swarming delivery service would be helpful.
I completely agree with the statement made that the tracker/non-tracker distinguishment is a problem in bittorrent. Each participant in the network should have full power to include new members to the network. An outside member should be able to point at any of the existing members and get whatever initial setup information is needed to join.
It sounds like Exeem is also addressing the cataloging/search problem, which grows the scope from file transer to a distributed filesystem. Gnutella's flood searches may be less than optimal but they're great for adapting to changes in the topology.
the funny thing is these problems have almost certainly been solved by the almighty p2p protocol: freenet.
waste is also interesting because it provides a "walled garden"/native application approach to a distributed filesystem.
amen! I was not happy about it, but I was ready to swallow the idea that blu-ray had won the format war. when I read this i thought no!!! just let one format win. one format will win, but it hard to say which one. I think Sony has an ace up its sleeve with the PSP using blu-ray discs.
push doesn't have to mean the server opens a connection to the client.
push can mean the client opens a connection to the server, like any other HTTP transaction, and the client leaves the connection open. the server 'pushes' data whenever it wants over this open TCP connection.
That is mind bogglingly inefficient. Its like POP clients checking for new email every X minutes. Polling is wrong wrong wrong! Check out the select() libc call. Does the linux kernel go into a busy wait loop listening for every ethernet packet? no! it gets interrupted when a packet it ready!
mod_pubsub is a set of libraries, tools, and scripts that enable publish and subscribe messaging over HTTP. mod_pubsub extends Apache by running within its mod_perl Web Server module.
What's the benefit of developing with mod_pubsub?
Real-time data delivery to and from Web Browsers without refreshing; without installing client-side software; and without Applets, ActiveX, or Plug-ins. This is useful for live portals and dashboards, and Web Browser notifications.
Jabber also saw a publish/subscribe mechanism as an important feature.
where are the IPv6 native ISPs?
on
IPv6 is Here
·
· Score: 4, Insightful
I live in Portland Oregon and every once in a while I survey the local DSL ISPs about IPv6. The answer has been consistenly "We have no plans to deploy IPv6." and "No customers have been asking for it."
Can someone point out ISPs that offer native IPv6 service to home users?
exactly. the other people who repiled to this comment dont get it. they point out the usefulness of having a URL in meatspace, thats not your argument. a URL in meatspace is great, but there is no value to having a big blocky barcode be the mechanism for communicating to a machine. A semacode strikes me as a very low-density way to store information, using unnecessarily high contrast colors.
I think an encoding mechanism could be made that is much more subtle. Possibly something that is not even visible to humans but something an image processor could still pick out. Then have a universal logo (the @ with radiating lines is not bad) to signify that something is there.
Even better, RFID, as you suggested, is the way to do this. I imagine very soon every palm will have an RFID reader in it and the RFID tags will be sold in hardware stores for $5/100 tags.
Set up a thousand little 802.11 hotspots with point-to-point links to send all sorts of data across cities and towns from senior centers, dorm rooms and attics! Its already legal! The hardware is already cheap!
Now you've not only got local content streaming radio, you've got VoIP services, freely distributable media sharing, local news blogs, etc etc.
This is the dream of many wireless community networking groups, including The Personal Telco Project in Portland, Oregon, USA.
i agree completely. i was AMAZED at how flexable it was and how aware it appeared to be of its own balance and physics in general. do you think its completely remote controlled? i would image it would need one very complex control or two operators.
I can imagine the toy company new product people wetting their pants over this little guy.
what matters is the patent. its possible they submitted details about the codec to SMPTE as a way to placate the people concerned about M$ locking down a new DVD format, all the while knowing that they can strong-arm a per-DVD-player fee whenever they feel like it.
invented? thats a strong word. patented may be closer to reality. I havent gone through each patent but its likely that only iBiquity can say who makes these new HD-FM radios.
If the FCC is going to be blessing a new standard for radio, it should be a free and patent unencumbered standard.
Re:How does this reduce spam in any shape or form?
on
SPF Design Frozen
·
· Score: 1
If you control the DNS for a domain, you can say who is allowed to send mail for that domain. Therefore, if a spammer attempts uses your domain in the "From:" header then it will only be delivered to those hosts that are NOT checking the SPF records. That's an important distinction, because getting everybody on the planet to do something is very hard
nice summary. SPF becomes useful long before everyone on the planet starts using it. In fact, once you get yahoo.com, aol.com, hotmail.com and a hundred other top domains to add one simple TXT record, you have dealt a major blow to spammers. SPF makes the From: address mean something.
And there are the possible negative effects here, for example employees not being able to send company email while on the road without hassle.
the SPF site addresses this. The answer is client authentication, SMTP AUTH with SASL.
But that aside, how does it reduce spam? The spammers will always be able to find a domain to stick in the "From:" header.
By only allowing mail from domains with DNS records, the spammers are limited to existing domains. So they start picking domains at random. Now thats been working well. Once SPF gets adopted on the top ten domains, many spammers will have to work harder to find a good domain to use. As the system catches on more and abuse@example.com starts getting more email, example.com will add an SPF record. The adoption will cascade and the amount of SPF-free domains will dwindle.
They can choose to use a domain that they do not control that has not yet added SPF to their DNS or they can choose to use a domain that they control.
I am working under the assumption that spam delivery houses have a genuine interest in remaining anonymous. If SPF forces spam delivery houses to use domains which they control, then suddenly the whois database provides a much stronger link back to the original spammer. Now there is much more of a papertrail, and that adds a lot of power in getting spammer shut down.
In either case it's trivial for them to get their mail from their system to yours, and that's all that they really care about anyway -- the "From:" header has always been meaningless to spammers anyway, it's not like they would be forfeiting the ability to receive replies or something.
exactly. SPF makes the From: address mean something. One technique that Ive seen spammers start to use is to spam me from email addresses of my friends! This gets around even whitelists. With SPF, this cannot happen.
Note that in the case of using a domain that they don't control, we're back to the issue of "until everyone on the planet does this, there will always be some domain somewhere that can be forged."
The important day is when your organization can start dropping email on the floor that does not have a From with an SPF record. I assert that this day will come long before everyone on the planet uses SPF. If unix admins can be convinced that SPF is a good idea and the mail delivery agents all have SPF support in their next release, the takeup rate could be amazing.
And even should those run out, spammers can just register anything for $7 a year, or less for bulk registrations.
paper trail.
Now, you might say that at least with this implemented you could discover what those domains are that the spammer is registering for use with his spamming. That is true. But, we've had the concept of a blocklist for ages, that's nothing new.... You're back to playing whack-a-mole with the spammers. They make a spam run with example.com, you block example.com; they make another run with examp
I want hardware and software crypto, but I can only reasonably trust people who share the same values as I do.
If ASUS and A-BIT start putting out motherboards that only support the NGSCB BIOS (is it more than BIOS? is there hardware too?), you can bet I'll be supporting the underdog motherboard manufacturer that uses verifiable code built from open source.
save us linuxbios! What other open source BIOS projects are out there?
Slashdot Mirror
this makes no sense.
if i sell a virtual item for USD, that is income and it is already taxed.
stocks in a company are 'virtual' and existing in a 'computer simulation'.
non-physical items are nothing new.
the other interpretation is impossibly ludicrous which is to tax items created
and sold in-game with no real-world value. if thats the case then they must
collect the taxes in the form of in-world items.
http://www.youtube.com/watch?v=TayWdhBbiPY
good news clip on the 'shouting' CCTV cameras.
have you seen this movie of an HL2 rube goldberg machine?
wireless access points could reinvent a local computer community. there is software being worked on to provide a "friendster" like site for those using the same wireless access point.
in the motherboard/cpu department at fry's i find the employees to be very knowledgeable. some of them are actually pc hardware nerds and know their stuff.
kinema - would you contact me about the portland GIS db request? im donp at personal telco dot net
http://www.rcgroups.com/forums/showthread.php?t=30 2503
that might interest you.
first and foremost, use a publish/subscribe system. no more polling! jabber may be a good framework for this. upon joining an rss subscription you get a refresh and after that you get deltas.
as has been mentioned many times already, a swarming delivery service would be helpful.
I completely agree with the statement made that the tracker/non-tracker distinguishment is a problem in bittorrent. Each participant in the network should have full power to include new members to the network. An outside member should be able to point at any of the existing members and get whatever initial setup information is needed to join.
It sounds like Exeem is also addressing the cataloging/search problem, which grows the scope from file transer to a distributed filesystem. Gnutella's flood searches may be less than optimal but they're great for adapting to changes in the topology.
the funny thing is these problems have almost certainly been solved by the almighty p2p protocol: freenet.
waste is also interesting because it provides a "walled garden"/native application approach to a distributed filesystem.
amen! I was not happy about it, but I was ready to swallow the idea that blu-ray had won the format war. when I read this i thought no!!! just let one format win. one format will win, but it hard to say which one. I think Sony has an ace up its sleeve with the PSP using blu-ray discs.
"Some of the best known innovations, like the net, have swiftly become part of the furniture for millions,..."
I've tried to interpret that in different contexts but nothing works out. part of the Furniture? I think their editors were alseep.
whoops that should be 48 half hours in a day :). 3x48x5 = 720 steps.
Its the load of receiving a new TCP connection, processing its request for new data that is the problem.
Say you read boingboing.net's RSS feed over one work week and it has two new articles a day. the server load would be something like this:
Monday:
8am 1. TCP Session open
8am 2. Receive request for new articles, send any new articles.
10am 3. Send new article
12pm 4. Send new article
Tuesday-Thursday:
10am 1. Send new article
12pm 2. Send new article
Friday:
10am 1. Send new article
12pm 2. Send new article
5pm 2. Client closed TCP session
I know this is really vague but thats about 12 "steps" of work.
Now instead, for the same 2 new articles a day, have the RSS client check every 30 minutes.
Monday-Friday
12:30am 1. Client Opens TCP session
12:30am 2. Client asks for new articles, send any new articles
12:31am 3. Client closes TCP session
Thats 3 x 24 half-hours in a day x 5 days or 360 "steps"!
using a publish-subscribe mechanism would greatly reduce the load on the server, even if the clients are still initiating the TCP connection.
i believe the win XP implementation of IPv6 is complete and stable. I agree that Microsoft is a big piece of getting IPv6 adopted.
push doesn't have to mean the server opens a connection to the client.
push can mean the client opens a connection to the server, like any other HTTP transaction, and the client leaves the connection open. the server 'pushes' data whenever it wants over this open TCP connection.
NAT is not a problem. The client connects to the RSS server and holds a TCP connection open. Then updates are "pushed" at will.
That is mind bogglingly inefficient. Its like POP clients checking for new email every X minutes. Polling is wrong wrong wrong! Check out the select() libc call. Does the linux kernel go into a busy wait loop listening for every ethernet packet? no! it gets interrupted when a packet it ready!
http://www.mod-pubsub.org/
The apache module mod_pubsub might be a solution.
From the mod_pubsub FAQ:
What is mod_pubsub?
mod_pubsub is a set of libraries, tools, and scripts that enable publish and subscribe messaging over HTTP. mod_pubsub extends Apache by running within its mod_perl Web Server module.
What's the benefit of developing with mod_pubsub?
Real-time data delivery to and from Web Browsers without refreshing; without installing client-side software; and without Applets, ActiveX, or Plug-ins. This is useful for live portals and dashboards, and Web Browser notifications.
Jabber also saw a publish/subscribe mechanism as an important feature.
I live in Portland Oregon and every once in a while I survey the local DSL ISPs about IPv6. The answer has been consistenly "We have no plans to deploy IPv6." and "No customers have been asking for it."
Can someone point out ISPs that offer native IPv6 service to home users?
exactly. the other people who repiled to this comment dont get it. they point out the usefulness of having a URL in meatspace, thats not your argument. a URL in meatspace is great, but there is no value to having a big blocky barcode be the mechanism for communicating to a machine. A semacode strikes me as a very low-density way to store information, using unnecessarily high contrast colors.
I think an encoding mechanism could be made that is much more subtle. Possibly something that is not even visible to humans but something an image processor could still pick out. Then have a universal logo (the @ with radiating lines is not bad) to signify that something is there.
Even better, RFID, as you suggested, is the way to do this. I imagine very soon every palm will have an RFID reader in it and the RFID tags will be sold in hardware stores for $5/100 tags.
Set up a thousand little 802.11 hotspots with point-to-point links to send all sorts of data across cities and towns from senior centers, dorm rooms and attics! Its already legal! The hardware is already cheap!
Now you've not only got local content streaming radio, you've got VoIP services, freely distributable media sharing, local news blogs, etc etc.
This is the dream of many wireless community networking groups, including The Personal Telco Project in Portland, Oregon, USA.
i agree completely. i was AMAZED at how flexable it was and how aware it appeared to be of its own balance and physics in general. do you think its completely remote controlled? i would image it would need one very complex control or two operators.
I can imagine the toy company new product people wetting their pants over this little guy.
its an interesting tactical move.
what matters is the patent. its possible they submitted details about the codec to SMPTE as a way to placate the people concerned about M$ locking down a new DVD format, all the while knowing that they can strong-arm a per-DVD-player fee whenever they feel like it.
the last couple fbi-power-expanding laws include being able to gag the raided company from answering just such questions.
invented? thats a strong word. patented may be closer to reality. I havent gone through each patent but its likely that only iBiquity can say who makes these new HD-FM radios.
If the FCC is going to be blessing a new standard for radio, it should be a free and patent unencumbered standard.
nice summary. SPF becomes useful long before everyone on the planet starts using it. In fact, once you get yahoo.com, aol.com, hotmail.com and a hundred other top domains to add one simple TXT record, you have dealt a major blow to spammers. SPF makes the From: address mean something.
the SPF site addresses this. The answer is client authentication, SMTP AUTH with SASL.
By only allowing mail from domains with DNS records, the spammers are limited to existing domains. So they start picking domains at random. Now thats been working well. Once SPF gets adopted on the top ten domains, many spammers will have to work harder to find a good domain to use. As the system catches on more and abuse@example.com starts getting more email, example.com will add an SPF record. The adoption will cascade and the amount of SPF-free domains will dwindle.
I am working under the assumption that spam delivery houses have a genuine interest in remaining anonymous. If SPF forces spam delivery houses to use domains which they control, then suddenly the whois database provides a much stronger link back to the original spammer. Now there is much more of a papertrail, and that adds a lot of power in getting spammer shut down.
exactly. SPF makes the From: address mean something. One technique that Ive seen spammers start to use is to spam me from email addresses of my friends! This gets around even whitelists. With SPF, this cannot happen.
The important day is when your organization can start dropping email on the floor that does not have a From with an SPF record. I assert that this day will come long before everyone on the planet uses SPF. If unix admins can be convinced that SPF is a good idea and the mail delivery agents all have SPF support in their next release, the takeup rate could be amazing.
paper trail.
I want hardware and software crypto, but I can only reasonably trust people who share the same values as I do.
If ASUS and A-BIT start putting out motherboards that only support the NGSCB BIOS (is it more than BIOS? is there hardware too?), you can bet I'll be supporting the underdog motherboard manufacturer that uses verifiable code built from open source.
save us linuxbios! What other open source BIOS projects are out there?