Search Results: "ag"

9 September 2007

Miriam Ruiz: Warsow: The problem of having non-licensed data

I sadly read that Warsow are having internal problems. It’s a pity, because it’s a great free game (even with its non-free game data), and they deserve the best. In any case, I just wanted to talk about this because of something that’s quite usual in the development of free games: having non-licensed data. According to tigerchas’ note: “The non-licensed state of warsow media is what has allowed this to happen - and the team is now working on rectifying this. This whole episode has been very unsatisfying and has highlighted the problems of not having a global media license for warsow”. I’m not worried about the future of the game at all, it’s not that the reason I’m writing this entry. As they also say in the same post: “Don’t let this announcement affect you too much, warsownians. warsow has hit minor stumbling blocks in the past and this is simply another. Maps can come and go. Rest assured that the current mapping team will be working on other great maps for you to enjoy”. What I wanted to point out with all this, especially to games developers and teams, is that even when licenses are boring stuff and many of you might think that you can safely ignore them and it won’t affect you, especially when you start the development, reality shows that these things happen. I wish all the best for the Warsow team anyway, and to go soon over this. Keep up the good work! :)

Neil Williams: GPE updates

OK, gpe-bluetooth updated and migrated to unstable from experimental.
gpe-calendar updated (after getting it into testing finally) so libsoundgen can actually have a useful role.
gpe-shield updated in experimental.
Also begun discussions with GPE upstream about avoiding common names for library names (along the lines of existing policy on application names) and arranged to send all my .desktop file patches upstream too. That should make future updates easier.
gpe-expenses has also been updated in Debian to fix a problem building against the new library. gpe-expenses is already GPL-3+ and now deb-gview and pilot-qof have also migrated and the second pre-release of quicklist in experimental is also GPL-3+.

Christian Perrier: RWC: being in the stadium is magic

Today was the day we had tickets for *the* match of the day between South Africa and Samoa (59-7). Of course, the Springboks won this game after the Samoan players were exhausted of their battle after 60th minute. However, we really enjoyed a great game during 1st half (21-7) with solid play by RSA (without great vista, as usual, but, well, I'm not a Springboks fan) and ultra-solid defense by Samoa. And, well, as long as the Samoans have the ball in their hands, everything can happen, especially with Henry Tuilagi, impressive number 8, which has been acclaimed by the Parc des Princes public when finally quitting the game on 60th minute. Three great moments in the game: South-Africa is however much more organized, of course, and their attacks were terribly devastating sometimes, with Bryan Habana scoring 4 tries. They're however a little bit hesitating with the ball in hands and their defense wasn't *that* impressive. While writing this, I'm watching Scotland-Portugal (56-10) as we came back from the Parc des Princes. This game happens in St-Etienne, my home town. I imagine the noise and feast in town, where we still remember a famous Scotland-Morocco during Soccer WC 1998. Apparently, the Scots like St-Etienne. Apparently, Portugal resisted during about one half and they even scored a try and sometimes endangered Scotland. Good game by the Scots who can hope to qualify for 1/4th finals. Tonight, Ireland-Namibia. If we aren't too much rugbyfied, I'll watch even if the result is quite predictable. Both teams are in France's pool, so watching team will be interesting. And even now, 2h before the game, there are 25.000 Irish people in Bordeaux. Probably interesting noise over there. Another match today, which I didn't watch because we were on our way to the stadium: Wales-Canada (42-17). Canada was leading 12-7 on half-time and even 17-7 on 45th minute. So, well, not very brilliant for the Welsh. Finally, their most experienced players came back (S. Jones, Gareth Tholas and Collin Charvis) and they easily came back and overscored Canada...who never resigned and were very close to score again at the end of the game. Brilliant day and, believe us, watching rugby *in* the stadium is really a great experience (we don't do this often enough...).

Jeff Bailey: End of week 1 in Santa Clara

In Santa Clara and still adjusting. The corporate housing that I'm in is nearly 4 hours by transit to the office according to the magic computers at 511.org. If I walk a mile on this side, and take a Google shuttle from the Caltrain, I should be able to get that down to an hour.

ahahahah, yeah right. I get a ride from Angie in the morning. It takes 15 minutes.

But *people*, c'mon.. This is California, right? Where are the people caring about the environment and hoping into mass-transit? Get out of your shiny Prius' and take a bus somewhere. Oh wait. You can't. Because it takes 4 hours to go 8 miles.

I'm thinking about this as I'm looking at churches and trying to decide if I feel like going to one this morning. I remember when I first joined the Beacon Unitarian Church, it was (as much as anything else) because I could walk to it. From the church, I could visit a half-dozen people who also lived walking distance from the church. How shall I build my community from inside temporary corporate housing in the middle of Santa Clara?

But we're starting to settle in a bit. We've swapped the van we used to drive across the country for a car. We've got a bank account. We've got a GrandCentral phone number which should follow us everywhere, and next we'll get an POBox so that as we move around a bit before settling in we'll at least have a permanent place to receive mail. It turns out that the State of California wants us to retake our written and road tests to move our licenses to here. That should be fun. Do you suppose it's an auto-fail if I yell "Christing fuck, people! Learn to drive!" as I merge onto the freeway? It's become a bit of a regular chant.

David Welton: Wiki Spammer

http://www.google.com/search?q=211.46.221.34 Yuck... look at all the damage one idiot with some scripts can do. I wish there were a way to make people like this pay.

Biella Coleman: The King of Kong: A Fistful of Quarters

I spent much of my early childhood at the video arcade. I was fortunate enough to have a best friend who 1) Lived in the old quarters of San Juan where you could walk everywhere 2) Had three older teenage sisters who would take us when we were still quite young to the arcade, which also doubled as a fantastic ice-cream parlor. My favorite game there was galaga, and I played it incessantly (and had to use a foot stool too!!) As a result of all that childhood gaming, I am still pretty half decent at it. For example, I more often than not beat my partner (except under less than auspicious conditions, like being sleep deprived), which is pretty unbelievable as he is much more of a video game wizard than I and otherwise beats me in everything.
Back in my first year in grad school, a cohort of us would play Galaga after our large theory class, and I would also always win (and by a lot and then get crushed at foosball). So of course when I heard that there was a documentary on the very genre of arcade games that consumed so much of my early childhood, King of Kong and a movie that was rumored to leave you at the edge of your seat (which seemed like an impossibility to me), I decided to fork over the cash and check it out in the movie theatre last night. And it was well worth every penny. The movie somehow managed to capture a story and set of subjective experiences that I think are incredibly hard to portray via film: the individual and social intimacy that comes with machine interaction. The story lines revolves around two very different characters who are masters at conquering one of the hardest video games in the world, Donkey Kong and are trying to clinch the world record. The tale of rivalry between them is really good in and of itself and probably without this drama, the movie would have not worked. But what I also found amazing was how the movie conveyed the persistence of the (older) game. They live on in the lives of individuals and collectives, despite the rise of a whole, new class of games that are much more popular today. I am not sure how much longer they will live on, or if the movie was also inadvertently portraying the rise and slow decline of an era that will, in another 50 years, become part of the archive of dead history. Whatever the case, if you had a loving relationship with these games (or your friends or parents did), check out the movie. It really has some incredible footage and moments and will make you want to run to that old arcade, once again.

Gunnar Wolf: Do good things come to those who wait?

So they say.
So, yes, lets wait, even if that means waiting with the trembling heart of the foreigner in Juan Jos Arreola's "El Guardagujas". Sometimes, the wait will be only eight minutes long - who knows? Sometimes, the wait will last for months, even a lifetime - be ready, stay at the nearby hotel, and be ready to rush out once the moment comes.
What cannot ever be guaranteed, though, is what happens after the train has arrived - Whether it will travel according to your personal (and extremely na ve) plans, or it will take you to a whole different life you never envisioned before. So... Well, I'm waiting for my train to R. We shall in due time see about it

Russell Coker: Comparing Debian and Fedora

A common question is how to compare Fedora [1] and Debian [2] in terms of recent updates and support. I think that Fedora Rawhide and Debian/Unstable are fairly equivalent in this regard, new upstream releases get packaged quickly, and support is minimal. They are both aimed at developers only, but it seems that a reasonable number of people are running servers on Debian/Unstable. Fedora releases (previously known as “Fedora Core” and now merely as “Fedora”) can be compared to Debian/Testing. The aim is that Fedora releases every 6 months and each release is supported until a release two versions greater is about to be released (which means that it’s about a year of support). The support however often involves replacing the upstream version of the program used to make a package (EG Fedora Core 5 went from kernel 2.6.15 to kernel 2.6.20). I believe that the delays involved in migrating a package from Debian/Unstable to Debian/Testing as well as the dependency requirements mean that you can get a similar experience running Debian/Testing as you might get from Fedora. Stable releases of Debian are rare and the updates are few in number and small in scope (generally back-porting fixes not packaging new upstream versions). This can be compared to Red Hat Enterprise Linux (RHEL) [3] or CentOS [4] (a free re-compile of RHEL with minor changes). Regarding stability and support (in terms of package updates) I think that Debian/Stable, RHEL, and CentOS are at about the same level. RHEL has some significant benefits in terms of phone support (which is of very high quality). But if you don’t want to pay for phone support then CentOS and Debian/Stable are both good choices. Recently I’ve been rolling out a bunch of CentOS 5 machines for clients who don’t want to pay for RHEL and don’t want to pay for extensive customisation of the installation (a quick kickstart install is what they want). The benefit of Fedora and Debian/Testing over RHEL, CentOS, and Debian/Stable is that they get newer packages sooner. This is significant when using programs such as OpenOffice which have a steady development upstream that provides features that users demand. If you want to try new features then Fedora and Debian/Testing are both options that will work. One reason I had been avoiding serious use of Debian/Testing is that it had no strategy for dealing with security fixes, but it seems that there are now security updates for Testing [5] (I had not realised this until today). References:
  1. http://fedoraproject.org/

  2. http://www.debian.org/

  3. http://www.redhat.com/rhel/

  4. http://www.centos.org/

  5. http://secure-testing-master.debian.net/

Michal Čihař: Nikon D80 or Pentax K10D?

That's the question I'm trying to solve right now. From wide range of cameras, I reduced to this choice, but the decision is now quite hard. Both have their advantages and disadvantages and there is not easy to choose as it was to cut down previous list. I used Google a lot in last weeks to find some experiences with both cameras, but none of them really helped me. Pentax pros: Pentax cons: Nikon pros: Nikon cons: From the list it is visible that I was able to find more pros and cons on Pentax. Nikon seems to do its job pretty well, but does not provide any extra gimmicks. This is also reason why Pentax is winner for now. I'll buy the camera sometimes during next week, so things can still change.

Frank Lichtenheld: Introducing sourcedeps.d.n

I get regulary annoyed by the fact that I find random -dev packages on my main system and can't figure out which package's build-depends I satisfied by installing them. Also they don't disappear if the package changes its build-depends. So I decided to solve this problem. Since I'm not really a C/C++ hacker and didn't want to learn hacking APT for this I choose to solve this problem with brute force and Perl ;-) The result is sourcedeps.debian.net, a APT archive which contains one binary package for each source package. The following mapping was done:
     source package name => binary package name, but with appended '-build-depends'
     Build-Depends       => Depends
     Build-Depends-Indep => Recommends
     Build-Conflicts     => Conflicts
     Binary              => Suggests
     Binary              => Provides (with appended '-build-depends')
If any of the Build-Depends fields contains arch limiters, arch-dependent packages will be created, otherwise one arch-independent package. This allows easy installation of build-depends by installing the corresponding meta package, tracking them, and removing them automatically in case you deinstall the meta package. It only works for known architectures though and it requires creating around 60,000 binary packages. It also doesn't allow tracking build-dependencies for more than one version of a package (e.g. unstable and experimental). You can use this by adding something like
deb http://sourcedeps.debian.net/ sid main contrib non-free
to your sources.list. The archive is signed with the following key, available from a keyserver near you and signed by me:
pub   1024D/ED505694 2007-09-08 [expires: 2008-09-07]
      Key fingerprint = 4ECF DF07 F419 0B5B 45C4  51D0 00E9 C47B ED50 5694
uid                  SourceDeps.Debian.Net Archive Key 
Comments welcome.

Pierre Habouzit: git awsome-ness [git rebase --interactive]

With the last git release, git-rebase gained a new option: --interactive. If you already had the feeling that in a patch series of yours you should have ordered patches differently, or merged some, then this command is what you dreamed of. Here is how it works Let's pretend you want to rework your last 10 patches, you'll run:
   $ git rebase -i HEAD~10
It will launch your $EDITOR and you'll see something like:
   # Rebasing 16d3800..14f3d11 onto 16d3800 
   # 
   # Commands: 
   #  pick = use commit 
   #  edit = use commit, but stop for amending 
   #  squash = use commit, but meld into previous commit 
   # 
   # If you remove a line here THAT COMMIT WILL BE LOST. 
   # 
   pick 6270640 Simplify write_tree using strbuf's. 
   pick 27c528a Further strbuf re-engineering. 
   pick fd82c9a Eradicate yet-another-buffer implementation in buitin-rerere.c 
   pick eee488f More strbuf uses in cache-tree.c. 
   pick 16878b5 Add strbuf_rtrim and strbuf_insert. 
   pick e9081af Change semantics of interpolate to work like snprintf. 
   pick 99c3ef5 Rework pretty_print_commit to use strbufs instead of custom buffers. 
   pick 203db5d Use strbuf_read in builtin-fetch-tool.c. 
   pick a20d939 Use strbufs to in read_message (imap-send.c), custom buffer--. 
   pick 14f3d11 Replace all read_fd use with strbuf_read, and get rid of it.
   ~
   ~
   ~
   ~
   ~
   ~[1]
Then you can rewrite "pick" into "edit" if you want to change something in a commit, or "squash" if you want to merge it with the one from the line before. What the small help doesn't say is that you can actually reorder your commits, and it will do what you expect it to do. I used it 10 minutes ago, because I have this string buffer module I extend on a regular basis, I squashed every API extension of that module in one commit using that. Each time one change needs you to edit anything because either you asked for it, or that one of the change you asked for generated a conflict, then as usual the rebase will stop. You will be prompted to make the change, or fix the conflict, or merge comments (in case of a squash), and when all is in order, you just need to:
   $ git rebase --continue
This is just awsomely simple and intuitive
Notes [1] if you don't have those, your $EDITOR sucks btw

8 September 2007

Wouter Verhelst: EMIRATES HERITAGE LOTTERY

Some spam was sent to a Debian list with that subject (sorry, no link, that would increase the pagerank). I guess spammers are now trying to combine two strategies in one: I have 1.000.000.000.000.000.000 US$ that I want to get off, but I can't possibly do so without getting into trouble. Therefore, I declare that you have won the LOTTERY!!!1! Now please claim your prize, and help me out of my problems. Thank you. Whether it'll work is another matter, of course.

Christian Perrier: RWC: first day

First day of the Rugby World Cup around here. Here are some of my impressions (for those of you not aware, I'm a rugby fan for ages and this event in my country will definitely affect my work on free software in the next 6 weeks). France-Argentina (12-17): being beaten by Argentina is a surprise only for people who don't know that much about Argentina in rugby. Argentina is currently ranked 6th in the world national team ranking, very close to Ireland (5th) and before England (7th), the last RWC winner. The argentinians played the best rugby they could play against a very hesitating French team. All players know each other very well as 2/3 of the Argentinian team plays...in France. The world's top player (imho), Juan Mart n Hern ndez, lead his team to victory while the french were anything but brilliant. Nothing really harmful, indeed: in rugby, completely screwing a match happens and does not necessarily mean anything for other games. Only drawback, if France qualifies, it becomes more and more likely that the 1/4 final could be France-New Zealand. Ouch... New Zealand-Italia (76-14): I haven't seen that one, therefore missing the first "haka" of that RWC. All Blacks are still the favourites of the RWC and they scored the quickest try as of now. Italy team fought quite well, from what I read, with one of my favourite players (Maurizio Bergamasco) scoring a try. Australia-Japan (91-3): in the past, Japan was closer to the top rugby world teams, particularly because of a long tradition of playing 7-players rugby and therefore being very efficient in rear lanes play. However, rugby changed last years and the power is the key. The japanese team was obviously lacking it...and then they had 14 tries scored against them by a very strict Australian team. England-USA (28-3 as I'm writing this): England is not that impressive but serious, still. The USA team plays well around the scrum and defend pretty well. On the English side, Mike Catt could be one of the stars of that RWC. And, yay, while writing this, USA scored a try against England *and* Lawrence Dallaglio got expelled for 10 minutes. Two occasions for me to be happy..(sorry in advance to my friends in England). Tomorrow, we'll attend South-Africa vs Samoa at Parc des Princes, Paris. That will definitely be a great feast and a nice rugby match. We'll of course put our heart on the Samoan side (I'm afraid I've never been enthusiast with the South African way to play rugby).

Lior Kaplan: CcPublisher: When upstream says don t package our software

A month ago Marcela Tiznado let me take over the CcPublisher ITP. I checked the upstream tarball for installation instructions, and saw something like “gunzip and run for the source directory”. I’ve contacted Nathan Yergler (= upstream) to find out how does he think the program should be installed. The reply I got included this “I actually would encourage you not to package for Debian at this point.” Nathan also said that the details for installation where never worked on. As the last CcPublisher version was released a year ago, I don’t see any point to package it right now, especially when upstream don’t think it the right time. I hope that they will find some time to make their software ready for distributions.

Michal Čihař: First usage of lazygal

After searching for new gallery and investigating lazygal, I finally decided it's time to give it some real world usage. My current album from Japan is being processed by this damn fast tool. It needed a bit of hacking, but as the core was already there and Alexandre Rossi is quite cooperative upstream. I managed to implement almost everything I requested in original post. The only thing I'm still not completely happy with is the theme, but I hope I will improve it over time. From original requirements, I completely dropped links to full size images. There is simply no reason to put here crappy pictures which my only camera I currently have here (built in camera in Nokia 6234) produces. Also once I'll buy new camera (what will be most likely Pentax K10D), I probably won't upload huge 10Mpix images on web server as I don't think it would be good for anything else than wasting my bandwidth.

Clint Adams: See Siemens first

Maintenant j'ouvre la fen tre et une mouche la chambre entre
Ni la moche ni l'italienne ne peut  tre trouv e plus   son centre
This place with its wood and its shingles, this place
with birdshit splattered down the bricks
This place with drunken girls screaming Meat Loaf lyrics
and behaving like abject pricks
Maintenant je suis bien loin
But yet oh so close
Cerca de la criatura del lago
Not Iago as has been previously claimed
Humming, screeching, gurgling, squeaking
Not unlike Barbie's mom on a Thursday night
It goes through the motions of accomplishing something
When really it is advancing its own sinister agenda
An agenda so sinister that you'd name it Dexter if you could.
You can't.
Then, as the disruptive forces destabilize reality, like
they destabilize the rhyme and scansion and hyperlinklessness
of
This Poem
Then, like
Mike Stone
expressing
gratitude,
like something demanding its $3.50 (but oh, oh, it does not want its $3.50; it wants
something far more visceral and ephemeral), it makes a simple statement.
F01.
Natuurlijk.

Neil Williams: g-wrap breaks gnucash in unstable

Just trying to get some data "out-there" on this issue because I'm seeing duplicate bugs being filed and I can't get any response from GnuCash Bugzilla - probably because bug-buddy is busy filing lots more duplicate bugs upstream about a problem that is entirely within Debian.
The latest upgrade of g-wrap is borked and this leads to the g-wrap binary being installed at version 1.9.9-1 when the rest of the g-wrap package is held back due to the transition from libgwrap-runtime0 to libgwrap-runtime2.
This broken transition breaks gnucash. A simple error message if only g-wrap is upgraded, a complete seg fault crash if guile-g-wrap is upgraded too.
So far, we have 3 bugs in Debian:

Please don't add any more. The real bug is 441103 in the g-wrap package and the fix is described in my response to 441248 as:

GnuCash is usable if you can revert to the version of g-wrap in
testing. I'm running it now with:
$ cat /etc/apt/preferences
Package: g-wrap
Pin: version 1.9.6-3.2
Pin-Priority: 1001

Package: guile-g-wrap
Pin: version 1.9.6-3.2
Pin-Priority: 1001

i.e. there isn't anything wrong with gnucash and if g-wrap had
transitioned properly, the g-wrap binary would not have been upgraded
to 1.9.9 on your system until gnucash could use libgwrap-runtime2
instead of libgwrap-runtime0. With the correct dependencies set in
g-wrap, this whole gnucash problem would have been avoided cleanly.


There is a separate RC bug against gnucash because of this transition: gnucash: FTBFS due to g-wrap transition. which does NOT affect the currently installable and usable version of gnucash in sid.

Thanks.

Russell Coker: ISP Password Change by Untrusted People

After dealing with Optus phone support [1] in regard to a routine request for a password change I have been thinking about better ways of managing password changes for a large ISP. The first criteria is that the user must have a password that is difficult to brute-force attack at all times. Changing a password to a supposedly temporary value that can be easily guessed (such as “changeme“) is never acceptable. The next criteria is that the help-desk operator should be trusted as little as possible and it would be ideal if they never knew the password. One possibility that occurred to me is that each bill could have a six-digit pseudo-random number printed on it. This number could be used as an alternate password. When a customer calls up because they lost their password they almost always have their last bill (this is why they print the number for phone support on each bill). The help-desk operator could then push a button on a web based form that makes this pseudo-random number be their new password, thus the help-desk operator would not know the new password and the user would also have it printed out clearly which avoids the confusion from having a password read out in a foreign accent. Another possibility is to have the password change infrastructure integrated with the CTI [2] system, then the help-desk operator could push a button and have the computer dictate the password without the help-desk operator being able to listen in. There will always be corner cases where a help-desk operator has to change the password, but if these are rare because the automated system handles most cases then the potential for damage would be limited. Of course it would also be a really good idea to do some statistical tracking of the number of password change requests performed by each operator and investigate those who do significantly more than average. In the past AOL has experienced a variety of security problems related to trojans [3] which probably would have been discovered by such analysis. Another possible option is that customers with mobile phones could have their new password sent to them by SMS. It’s quick, easy, cheap when done in bulk, and is much harder to intercept than most methods that might be used for transferring passwords. References:

  1. http://etbe.coker.com.au/2007/09/03/optus-password-changeme/

  2. http://en.wikipedia.org/wiki/Computer_telephony_integration

  3. http://www.wired.com/techbiz/it/news/2003/02/57753

Andrew Pollock: [life] Homecoming, part 1

Sarah's Mum arrived this morning. Sarah was discharged from hospital this afternoon. By some freaky coincidence, one of our friends from Australia who's been through the same thing as us happened to be nearby, and rearranged his travel plans to swing by and spend a day with us on the way home. I'm extremely grateful for that. The flowers, emails, and number of visitors we've received in the past four days has been nothing short of overwhelming. We are truly grateful for having so many wonderful friends over here (and all around the world). It's going to take some time, but we'll acknowledge all of them. This afternoon I signed the paperwork to have Joshua cremated. We've decided against having any sort of funeral service. The house looks like a bomb hit it, and then a florist moved in. I've barely been home all week, and the fridge is still overflowing with leftovers from last week's baby shower barbecue that we had. I guess I know what I'm doing tomorrow... Next, we need to pack up the baby's room.

7 September 2007

Mike Hommey: Javascript performance in browsers

Ars Technica has recently posted an article about the new Opera alpha release, with some Javascript benchmark results showing it is quite faster than version 9.23. It also goes to compare with Firefox and IE7, but omits some other not so unimportant browsers. I think the main reason is because they seem to have only tested Windows browsers. Sure, Safari has been released recently on Windows, but it is still quite marginal. Anyways, I was wondering how all this was going under Linux, and also, how (good?) WebKit would perform compared to others. So, I tried the same Javascript speed tests on various browsers under Linux on my laptop, which happens to be a Pentium M 1.5GHz. And the winner is…
Test Iceweasel 2.0.0.6 Epiphany 2.18.3/libxul 1.8.1.6 GdkWebKit Opera 9.23 Opera 9.50 alpha 1
Try/Catch with errors 80 81 41 18 22
Layer movement 250 214 76 53 47
Random number engine 280 190 57 72 68
Math engine 343 274 82 101 91
DOM speed 205 225 18 41 54
Array functions 97 97 72 82 44
String functions 14 12 12 46 52
Ajax declaration 178 127 16 21 17
Total 1447 1220 374 434 395
So, It seems the speed gain Opera got on Windows doesn’t happen much on Linux. An interesting result, is that Iceweasel, with a bunch of extensions installed, is slower than Epiphany, despite both using the same rendering engine and Javascript library. Running Iceweasel in safe mode makes it the same speed as Epiphany, though. So having extensions does not only clutter the UI, but actually has an impact on how fast the Javascript code in web pages is going to run. And well, WebKit is the fastest for this testcase, though it stays behind Opera on some specific tests.

Next.

Previous.