Skip navigation.

Opera Unite

Opera 10 Beta 2 and Unite

, , ,

As mentioned in the by Manuela in the Desktop Blog and the My Opera blog, today we have two desktop releases:

  • Opera Beta 2: This version is intended for those running Beta 1 and does not contain Opera Unite.
  • Snapshot: Includes all the bug-fixes and improvements of Beta 2, plus Opera Unite.

Most of you installed the Opera Unite labs release a month ago. So don't worry, the auto-update will use the snapshot release and you won't notice any changes other than improvements.

If for some reason you installed beta 2 yourself and now don't have Opera Unite, just download the latest snapshot from the desktop blog and you will be up and running with Unite again.

What's the plan?

Nav already mentioned in the post below that the team is hard at work ironing out the proxy issues. While some client-side fixes are included in this release, we want to be confident with the stability and scalability of the infrastructure before we incorporate Unite into the desktop pre-releases. But we're sure it won't be long :wink:

As always, let us know what you think.

Fixing Proxy problems

, , ,

If you've tried to use Opera Unite over the past few days, you might have noticed that your friends aren't able to access your services. You might have just seen a yellow triangle on the Opera Unite icon in the bottom left side of the browser.



This has been largely due to our Unite proxy acting funny. One of the main purposes of the Opera Unite Alpha launch was to test our systems in the real world and make sure we go out with a stable system if this is to become a regular browser feature. Sure enough, there are things to fix and bugs to iron out based on all the feedback you guys have been sending in. So hang on, we're working to fix this ASAP

Also, we've seen some new services being uploaded to http://unite.opera.com/services/. Do check them out.

TIP: You can get the latest uploaded services at http://unite.opera.com/services/new/


Btw, to those who are heading out for summer vacations, Have Fun :D !!

"Terms of Services" updated

After we launched the labs version of Opera Unite, some of you pointed out some oversights in the "Terms of Services" that you have to agree with in order to get your services published at http://unite.opera.com. We realized that revision was needed and so we have now updated the Terms of Services.

We'd like to thank you guys for pointing this out and we hope that we keep getting such support from everyone in the future :smile:

From the new Terms of Services, I'd like to point out:

"Opera does not claim ownership in your Content, and uploading does not transfer ownership rights of the Content to Opera."

There was a lot of confusion around the ownership of the content, and we hope this addresses most doubts. Opera needs to have rights to approve, reject, suggest changes and publish your services on Opera's Web sites, without charge. This is to ensure service integrity and to avoid publishing faulty services, which can result in a negative user experience.

We have updated the Terms of Service at http://widgets.opera.com as well. This is an ongoing process and we are looking into providing even more flexible licensing policies to developers. Keep an eye on this blog for updates.

We are always open for feedback, so do let us know what you think.

Some Unite preference settings

, ,

The Opera Unite Webserver isn't designed for full-scale production web serving on major traffic sites. It's meant to make it really easy for people to share their own stuff, without having to worry about getting a domain name, setting up the configuration, managing ports and firewalls and a remote copy of your content on the server and so on.

But it isn't completely stupid either. There are a few things that even simple users might decide they want (I know, because I did), that can be set using opera:config. The preferences that affect Opera Unite are grouped as "Web Server", and this is just a couple of the cool ones.

Please remember that this is based on the experimental version, so check the real documentation when the final version comes out.

For those who have never used opera:config to set preferences before, it's not that hard.

Preferences are listed by various topics, and there is a link that will take your Opera browser to that particular preference (for you, on your computer). You can change the value, then at the bottom of each section is a button called "save" - you need to save the new preference for it to take effect. Sometimes you will need to restart Opera, too, but sometimes it will take effect straight away.

The preferences that affect Opera Unite are grouped as "Web Server", and this is just a couple of the ones that make cool things simpler.

"Throttle" the connection

Yep, you can decide how much data you want to upload. If you set this to 0 (as it is when you first install), there is no limit, but you might decide that you don't want to let more than, say, 20kb be transferred per second. (I chose that because it is the value I use for the equivalent preference to make sure BitTorrent doesn't eat my household internet connection). It's pretty simple - set to 20, then save it.

Port

By default, the web server listens to (i.e. sends content through) port 8840. If you don't know what that means, you needn't worry. But if you do know, you might be pleased to learn first that you can connect to your webserver at http://localhost:8840/ and even more that you can change it to run on a different port, like 80 (the default for the Web, and the one that browsers try to connect to unless you tell them something different).

Do Not Use Opera Account

This is where the previous option gets interesting. If you select this, you still have to log in to start the service (this is an experimental version, remember? It's actually to let the Opera Unite system know that you are the service owner). But after that, the operaunite.com proxy will not recognise that your server exists, and your connections will not go through it. If your computer already has a domain name, it will respond to that, or to your IP address.

That will be the only way to get to it while you have this option set. The service provided by the proxy, of giving you a domain name getting requests to you from users who couldn't normally find you, and providing those people with the stuff you want to share, will be turned off. You might want to do this for privacy, or so people can't see that you are running a service, or for any other reason. We don't mind - we just made it an option that you can choose.

As you will see, there are other things there too. If you are experimenting, you can play with them... and there is a default button to restore anything to its original value (without changing any other setting) if it does something unexpected.

Use your own domain names (and more ..)

If you have tried Opera Unite, you will know that as soon as you log in, we set up a domain for you. It usually looks like: http://<device_name>.<user_name>.operaunite.com and is unique to you as is uses your My Opera username in the URL. Some of you have asked if it's possible to set up Opera Unite to use your own private domain names. The answer is, yes, and my colleague Lachlan Hunt posted an excellent article on how to do this at http://dev.opera.com/articles/view/custom-domains-opera-unite/

We did put a link to it in yesterday's post, but in case you missed it, do give it a read.

Also, Vladim Makeev from our Open the Web team published the "Opera Unite developer's primer" in Russian http://dev.opera.com/articles/view/opera-unite-developer-primer-ru/ :D

There are a lot of developer focussed articles and tutorials on Opera Unite at http://dev.opera.com/articles/unite. You might find, the Unite API at http://dev.opera.com/libraries/unite/ and the File I/O documentation at http://dev.opera.com/libraries/fileio/ quite useful as well.

We are working on more documentation and we'll publish updates on this blog whenever we publish something, so keep checking back!
Download Opera, the fastest and most secure browser