[ANN] com.walmartlabs/lacinia-pedestal 0.16.1

[Howard Lewis Ship]

lacinia-pedestal adds support for accessing Lacinia GraphQL as an HTTP endpoint

GitHub repo: https://github.com/walmartlabs/lacinia-pedestal

Documentation: http://lacinia-pedestal.readthedocs.io/en/latest/

Featured changes in 0.16.1:

- Updated the version of the packaged GraphiQL; this included adding
the request headers editor

-- 
Howard M. Lewis Ship

Senior Mobile Developer at Walmart Labs

(971) 678-5210
http://lewisship.net

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/CACd-vsNJ0kMmBXB%3DL-2Euj%3DVD2wzCN-zdU1cg%3D%2Bs1RJxS5ucpw%40mail.gmail.com.

Re: [ANN] Discontinuing 4clojure.com

[Robert Levy]

Just wanted to correct a mistake in what I wrote above. Obviously you can't
clear the password hashes while retaining a link between people and their
accounts, so it would more accurately be stated as all accounts are gone
and you have to create a new account.

On Tue, Jul 6, 2021 at 12:42 AM Robert Levy  wrote:

> Hi Alan,
>
> Just as a thought.  If it's minimal work on your end (eg. if the folks
> from Roam research who chimed in above pick it up) why not clear the
> password hashes and let the new maintainer handle the communication that
> passwords need to be reset?
>
> Rob
>
> On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy  wrote:
>
>> TL;DR: Turning off 4clojure.com by the end of July 2021
>>
>> Hello, 4clojure problem solvers. You've probably noticed SSL errors on
>> 4clojure.com over the last week. The old decrepit system 4clojure runs
>> on has finally gotten out of date enough that I can't even figure out how
>> to get it recent enough that SSL certs will auto-renew anymore.
>>
>> In principle I could start from scratch on a new server and move 4clojure
>> over, but I won't. 4clojure has been piggybacking along on a server that I
>> use for personal reasons, and over the years I have less and less reason to
>> keep paying for that server - it's now pretty much just 4clojure costing me
>> an embarrassing amount of money every month because I haven't wanted to
>> disappoint the community by shutting it down. This SSL thing is just what
>> made me finally pull the trigger.
>>
>> I don't have a specific EOL date in mind, but sometime near the end of
>> the month, since that's the billing cycle. Until that time, 4clojure still
>> works, as long as you don't mind clicking through the security warnings -
>> it really is still me hosting the site, and since the connection is still
>> HTTPS (albeit with an invalid cert) I think that means your data is still
>> safe. If you have solutions to problems you're proud of, you've still got
>> some time to print them out and put them up on your refrigerator.
>>
>> I'm not seeking new maintainers. I'd feel uncomfortable handing over a
>> database with so many email addresses and password hashes in it to anyone.
>> The service has had a good run - just over a decade since the first
>> release
>> .
>> I hope you enjoyed it during that time.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clojure@googlegroups.com
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/CAEToNjiTvXHpZj653-Urho1Z7r7%2BXKU6u%2BxZ-ihob%2BQE_3WCjQ%40mail.gmail.com.

Re: [ANN] Discontinuing 4clojure.com

[oxalorg]

Thank you Alan for all your contributions :)

Hosting things and maintaing them is really hard. We, the LambdaIsland 
team, are already maintaining clojurians-log and clojureverse and it's 
definitely not easy!

With a wonderful idea from @borkdude and his `sci` library, I built 
"4ever-clojure": a completely static version of 4clojure which runs using 
cljs + sci. It interprets the code in the browser itself. 

It's live at: 4clojure.oxal.org  (Source code at: 
https://github.com/oxalorg/4ever-clojure  I'm planning to move it under the 
clojureverse github org)

I have 2 asks from you if it is feasible:
1. An export of all solutions (only solutions, no user data needed) - the 
community is already coming up with some amazing ideas of hooking up user 
solutions to automatically commit to a Github repo 
2. Possibility of transfering *4clojure.com *-or- *4clojure.org *over to us 
so that we can host 4ever-clojure there (instead of on a separate domain)

Thanks!
- Mitesh

On Tuesday, July 6, 2021 at 5:56:10 PM UTC+5:30 Srihari Sriraman wrote:

> Hey Alan, we really like 4clojure. We've suggested using it for training 
> most people at nilenso and we're very thankful to you and all the 
> contributors for that!
> We (nilenso) would be up for picking up the hosting costs, and also some 
> other operations or development work if needed.
>
> It would be even better if we could work together and turn this into a 
> community owned project (ex: clojurists together 
> ). That might also assuage your concerns 
> about data ownership.
>
> The questions, and solutions that the community has put together on 
> 4clojure over the last decade are very valuable as a learning tool. Perhaps 
> we can find a way to keep them around without attributing them to a user? 
> One idea might be to deactivate all existing accounts, and remove the user 
> data (email, passwords, other PII) etc while keeping the questions and 
> solutions from those users.
>
> We would be sad to see 4clojure go away, hope we can find a way for it to 
> live on.
>
> Cheers,
> Srihari
>
> On Tuesday, July 6, 2021 at 1:12:44 PM UTC+5:30 Robert P. Levy wrote:
>
>> Hi Alan,
>>
>> Just as a thought.  If it's minimal work on your end (eg. if the folks 
>> from Roam research who chimed in above pick it up) why not clear the 
>> password hashes and let the new maintainer handle the communication that 
>> passwords need to be reset?
>>
>> Rob
>>
>> On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy  wrote:
>>
>>> TL;DR: Turning off 4clojure.com by the end of July 2021
>>>
>>> Hello, 4clojure problem solvers. You've probably noticed SSL errors on 
>>> 4clojure.com over the last week. The old decrepit system 4clojure runs 
>>> on has finally gotten out of date enough that I can't even figure out how 
>>> to get it recent enough that SSL certs will auto-renew anymore.
>>>
>>> In principle I could start from scratch on a new server and move 
>>> 4clojure over, but I won't. 4clojure has been piggybacking along on a 
>>> server that I use for personal reasons, and over the years I have less and 
>>> less reason to keep paying for that server - it's now pretty much just 
>>> 4clojure costing me an embarrassing amount of money every month because I 
>>> haven't wanted to disappoint the community by shutting it down. This SSL 
>>> thing is just what made me finally pull the trigger.
>>>
>>> I don't have a specific EOL date in mind, but sometime near the end of 
>>> the month, since that's the billing cycle. Until that time, 4clojure still 
>>> works, as long as you don't mind clicking through the security warnings - 
>>> it really is still me hosting the site, and since the connection is still 
>>> HTTPS (albeit with an invalid cert) I think that means your data is still 
>>> safe. If you have solutions to problems you're proud of, you've still got 
>>> some time to print them out and put them up on your refrigerator.
>>>
>>> I'm not seeking new maintainers. I'd feel uncomfortable handing over a 
>>> database with so many email addresses and password hashes in it to anyone. 
>>> The service has had a good run - just over a decade since the first 
>>> release 
>>> .
>>>  
>>> I hope you enjoyed it during that time.
>>>
>>> -- 
>>>
>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clo...@googlegroups.com
>>> Note that posts from new members are moderated - please be patient with 
>>> your first post.
>>> To unsubscribe from this group, send email to
>>> clojure+u...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>> --- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Clojure" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to clojure+u.

Re: [ANN] Discontinuing 4clojure.com

[Srihari Sriraman]

Hey Alan, we really like 4clojure. We've suggested using it for training 
most people at nilenso and we're very thankful to you and all the 
contributors for that!
We (nilenso) would be up for picking up the hosting costs, and also some 
other operations or development work if needed.

It would be even better if we could work together and turn this into a 
community owned project (ex: clojurists together 
). That might also assuage your concerns 
about data ownership.

The questions, and solutions that the community has put together on 
4clojure over the last decade are very valuable as a learning tool. Perhaps 
we can find a way to keep them around without attributing them to a user? 
One idea might be to deactivate all existing accounts, and remove the user 
data (email, passwords, other PII) etc while keeping the questions and 
solutions from those users.

We would be sad to see 4clojure go away, hope we can find a way for it to 
live on.

Cheers,
Srihari

On Tuesday, July 6, 2021 at 1:12:44 PM UTC+5:30 Robert P. Levy wrote:

> Hi Alan,
>
> Just as a thought.  If it's minimal work on your end (eg. if the folks 
> from Roam research who chimed in above pick it up) why not clear the 
> password hashes and let the new maintainer handle the communication that 
> passwords need to be reset?
>
> Rob
>
> On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy  wrote:
>
>> TL;DR: Turning off 4clojure.com by the end of July 2021
>>
>> Hello, 4clojure problem solvers. You've probably noticed SSL errors on 
>> 4clojure.com over the last week. The old decrepit system 4clojure runs 
>> on has finally gotten out of date enough that I can't even figure out how 
>> to get it recent enough that SSL certs will auto-renew anymore.
>>
>> In principle I could start from scratch on a new server and move 4clojure 
>> over, but I won't. 4clojure has been piggybacking along on a server that I 
>> use for personal reasons, and over the years I have less and less reason to 
>> keep paying for that server - it's now pretty much just 4clojure costing me 
>> an embarrassing amount of money every month because I haven't wanted to 
>> disappoint the community by shutting it down. This SSL thing is just what 
>> made me finally pull the trigger.
>>
>> I don't have a specific EOL date in mind, but sometime near the end of 
>> the month, since that's the billing cycle. Until that time, 4clojure still 
>> works, as long as you don't mind clicking through the security warnings - 
>> it really is still me hosting the site, and since the connection is still 
>> HTTPS (albeit with an invalid cert) I think that means your data is still 
>> safe. If you have solutions to problems you're proud of, you've still got 
>> some time to print them out and put them up on your refrigerator.
>>
>> I'm not seeking new maintainers. I'd feel uncomfortable handing over a 
>> database with so many email addresses and password hashes in it to anyone. 
>> The service has had a good run - just over a decade since the first 
>> release 
>> .
>>  
>> I hope you enjoyed it during that time.
>>
>> -- 
>>
> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clo...@googlegroups.com
>> Note that posts from new members are moderated - please be patient with 
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+u...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to clojure+u...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/d49cb64d-30f9-4839-a652-954bb0683608n%40googlegroups.com.

Re: [ANN] Discontinuing 4clojure.com

[Sami Kallinen]

Hear, hear! Thank you for your wonderful work. It has been such a joy to be
able to use the service throughout the years. If you do end up dumping a
dataset with the problems, it would be great to also get the solutions if
feasible. For me personally I have perhaps learned the most by studying
other peoples solutions, plus it is an interesting corpus to study or for
instanceto  use as training material for NLP type of ML situations etc in
the future. /sami

On Tue, 6 Jul 2021, 13.22 Colin Fleming, 
wrote:

> Thanks for all the work (and money!) that's been spent over the years
> maintaining 4clojure, I know it's been much appreciated by many in the
> community. Is it possible to provide a data dump of the problem set? As far
> as I can tell this data isn't in the Github repo, it seems to be in a Mongo
> database somewhere? I for one would appreciate a copy if possible.
>
> Cheers,
> Colin
>
>
> On Sun, 4 Jul 2021 at 20:26, Alan Malloy  wrote:
>
>> TL;DR: Turning off 4clojure.com by the end of July 2021
>>
>> Hello, 4clojure problem solvers. You've probably noticed SSL errors on
>> 4clojure.com over the last week. The old decrepit system 4clojure runs
>> on has finally gotten out of date enough that I can't even figure out how
>> to get it recent enough that SSL certs will auto-renew anymore.
>>
>> In principle I could start from scratch on a new server and move 4clojure
>> over, but I won't. 4clojure has been piggybacking along on a server that I
>> use for personal reasons, and over the years I have less and less reason to
>> keep paying for that server - it's now pretty much just 4clojure costing me
>> an embarrassing amount of money every month because I haven't wanted to
>> disappoint the community by shutting it down. This SSL thing is just what
>> made me finally pull the trigger.
>>
>> I don't have a specific EOL date in mind, but sometime near the end of
>> the month, since that's the billing cycle. Until that time, 4clojure still
>> works, as long as you don't mind clicking through the security warnings -
>> it really is still me hosting the site, and since the connection is still
>> HTTPS (albeit with an invalid cert) I think that means your data is still
>> safe. If you have solutions to problems you're proud of, you've still got
>> some time to print them out and put them up on your refrigerator.
>>
>> I'm not seeking new maintainers. I'd feel uncomfortable handing over a
>> database with so many email addresses and password hashes in it to anyone.
>> The service has had a good run - just over a decade since the first
>> release
>> .
>> I hope you enjoyed it during that time.
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Clojure" group.
>> To post to this group, send email to clojure@googlegroups.com
>> Note that posts from new members are moderated - please be patient with
>> your first post.
>> To unsubscribe from this group, send email to
>> clojure+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/clojure?hl=en
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "Clojure" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to clojure+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com
>> 
>> .
>>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/clojure/CACK23Ac1anTi1yTDHpW7Xj11QdJNPQEVVMmFT-dLC%3D_COsUB%3Dw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
Fo

Re: [ANN] Discontinuing 4clojure.com

[Colin Fleming]

Thanks for all the work (and money!) that's been spent over the years
maintaining 4clojure, I know it's been much appreciated by many in the
community. Is it possible to provide a data dump of the problem set? As far
as I can tell this data isn't in the Github repo, it seems to be in a Mongo
database somewhere? I for one would appreciate a copy if possible.

Cheers,
Colin


On Sun, 4 Jul 2021 at 20:26, Alan Malloy  wrote:

> TL;DR: Turning off 4clojure.com by the end of July 2021
>
> Hello, 4clojure problem solvers. You've probably noticed SSL errors on
> 4clojure.com over the last week. The old decrepit system 4clojure runs on
> has finally gotten out of date enough that I can't even figure out how to
> get it recent enough that SSL certs will auto-renew anymore.
>
> In principle I could start from scratch on a new server and move 4clojure
> over, but I won't. 4clojure has been piggybacking along on a server that I
> use for personal reasons, and over the years I have less and less reason to
> keep paying for that server - it's now pretty much just 4clojure costing me
> an embarrassing amount of money every month because I haven't wanted to
> disappoint the community by shutting it down. This SSL thing is just what
> made me finally pull the trigger.
>
> I don't have a specific EOL date in mind, but sometime near the end of the
> month, since that's the billing cycle. Until that time, 4clojure still
> works, as long as you don't mind clicking through the security warnings -
> it really is still me hosting the site, and since the connection is still
> HTTPS (albeit with an invalid cert) I think that means your data is still
> safe. If you have solutions to problems you're proud of, you've still got
> some time to print them out and put them up on your refrigerator.
>
> I'm not seeking new maintainers. I'd feel uncomfortable handing over a
> database with so many email addresses and password hashes in it to anyone.
> The service has had a good run - just over a decade since the first
> release
> .
> I hope you enjoyed it during that time.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/CACK23Ac1anTi1yTDHpW7Xj11QdJNPQEVVMmFT-dLC%3D_COsUB%3Dw%40mail.gmail.com.

Re: [ANN] Discontinuing 4clojure.com

[Robert Levy]

Hi Alan,

Just as a thought.  If it's minimal work on your end (eg. if the folks from
Roam research who chimed in above pick it up) why not clear the password
hashes and let the new maintainer handle the communication that passwords
need to be reset?

Rob

On Sun, Jul 4, 2021 at 1:26 PM Alan Malloy  wrote:

> TL;DR: Turning off 4clojure.com by the end of July 2021
>
> Hello, 4clojure problem solvers. You've probably noticed SSL errors on
> 4clojure.com over the last week. The old decrepit system 4clojure runs on
> has finally gotten out of date enough that I can't even figure out how to
> get it recent enough that SSL certs will auto-renew anymore.
>
> In principle I could start from scratch on a new server and move 4clojure
> over, but I won't. 4clojure has been piggybacking along on a server that I
> use for personal reasons, and over the years I have less and less reason to
> keep paying for that server - it's now pretty much just 4clojure costing me
> an embarrassing amount of money every month because I haven't wanted to
> disappoint the community by shutting it down. This SSL thing is just what
> made me finally pull the trigger.
>
> I don't have a specific EOL date in mind, but sometime near the end of the
> month, since that's the billing cycle. Until that time, 4clojure still
> works, as long as you don't mind clicking through the security warnings -
> it really is still me hosting the site, and since the connection is still
> HTTPS (albeit with an invalid cert) I think that means your data is still
> safe. If you have solutions to problems you're proud of, you've still got
> some time to print them out and put them up on your refrigerator.
>
> I'm not seeking new maintainers. I'd feel uncomfortable handing over a
> database with so many email addresses and password hashes in it to anyone.
> The service has had a good run - just over a decade since the first
> release
> .
> I hope you enjoyed it during that time.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clojure@googlegroups.com
> Note that posts from new members are moderated - please be patient with
> your first post.
> To unsubscribe from this group, send email to
> clojure+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
> ---
> You received this message because you are subscribed to the Google Groups
> "Clojure" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to clojure+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/clojure/385cdef8-fa40-47ba-b5b1-0b3a7cc34935n%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/clojure/CAEToNjhC%3DXh-c%3DnyLT1mitYQrh1gBiAmGqKLRC7P9B5VJrhxhw%40mail.gmail.com.