Jump to content
Sign in to follow this  
Followers 0
all Wright

fighting over TB?

Recommended Posts

I picked up a TB from a local cache, and when I went to log it I noticed that it was still in the "possession" of the previous holder. So.....I grabbed it from him, and dipped it in the cache where I found it (to log the miles) I also put a note that said something like "I may have retrieved it immediately after it was placed here, so I will dip it to make sure it gets the miles".

 

After that I "retrieved" it from the cache. Currently it's in my caching backpack.

 

Then the newbie cacher that had it before me GRABBED IT BACK! He wrote a note saying something like "All Wright retrieved it two days after we placed it". Okay, so maybe I did. But then he didn't put it anywhere - it says it's in his possession. WTHeck? I don't think he read the log I posted or maybe he would've seen that it was all taken care of. I wrote him an email - very polite and told him something like this:

 

"I guess I caused some confusion regarding (TB). Sorry about that. I did dip it in the cache I found it in though, so the miles should be fine, unless you are planning on dipping it in some other caches you visited with it prior to dropping it. Let me know what you plan to do. The TB is currently in my possession, so I will have to grab it back from you before I leave it off anywhere"

 

I haven't heard from him,,,, he hasn't dipped it in any caches, or "placed" it in the one he left it in. What should I do? All I can think of is give him till this weekend (when I plan to take it somewhere) and grab it back from him.

He is a newbie.....maybe this is how they get all messed up!

Share this post


Link to post

Sometimes I find that if I have to wait for the last person to Drop it, I'll send them a friendly reminder to do the Drop. If I don't get a response after a couple days I'll Grab it away.

 

I'm going to guess that your follow up email was sufficient and now he's waiting for you to do something with it. Give it a couple days if you can and then grab it away again. I would then wait to see if he grabs it back. If so, then we need to involve the bug owner.

Edited by BlueDeuce

Share this post


Link to post

Okay, looking into this further the guy did later post a note saying - Trying to add the miles.

 

He has not logged back into the site since then so I wouldn't rush things. Sometimes life get in the way of caching, give it more time.

 

Edit: I'm also going to send you an email.

Edited by BlueDeuce

Share this post


Link to post

Okay, looking into this further the guy did later post a note saying - Trying to add the miles.

 

He has not logged back into the site since then so I wouldn't rush things. Sometimes life get in the way of caching so I'd give it more time.

 

Edit: I'm also going to send you an email.

 

So probably he didn't understand the miles were already fine once I dipped it there.....(unless he wanted to add other caches to the TB's travels).

 

So I will wait it out and see what happens. Sometimes the TB stuff gets all mangled up like this, now I see why. He just needs to place it back where he left it - or let me grab it.

Share this post


Link to post

Okay, looking into this further the guy did later post a note saying - Trying to add the miles.

 

He has not logged back into the site since then so I wouldn't rush things. Sometimes life get in the way of caching so I'd give it more time.

 

Edit: I'm also going to send you an email.

 

So probably he didn't understand the miles were already fine once I dipped it there.....(unless he wanted to add other caches to the TB's travels).

 

So I will wait it out and see what happens. Sometimes the TB stuff gets all mangled up like this, now I see why. He just needs to place it back where he left it - or let me grab it.

 

Probably. He's only been caching for a couple weeks so he might be trying to figure out how to do the logging properly. It's just taking him some time. (Bug logging isn't always that obvious when first starting out)

 

Per our emails I think we have a decent solution.

Share this post


Link to post

Sounds like a juvenile reposte to grabbing. Either they'll grow out of it or leave caching.

 

Geocaching is a social activity, even if you think you geocache alone, you are caching with those who have visited the caches before you and will afterwards. Geocaching would not happen without people placing caches.

 

If you have to be anti-social, you'd best find a hobby where you can do it all by yourself.

 

Hammer_sickle_clean.png

Geocaching - For peoples great glory socialist endeavour!

Share this post


Link to post

Geocaching - For peoples great glory socialist endeavour!

 

What in tarnation are you talking about.

 

Do you really think a two-week cacher already has an agenda?

 

Slack up and try helping out.

Edited by BlueDeuce

Share this post


Link to post

Geocaching - For peoples great glory socialist endeavour!

 

What in tarnation are you talking about.

 

Do you really think a two-week cacher already has an agenda?

 

Slack up and try helping out.

 

Read the top part of the post, the bottom part is for humor. :)

Share this post


Link to post

Geocaching - For peoples great glory socialist endeavour!

 

What in tarnation are you talking about.

 

Do you really think a two-week cacher already has an agenda?

 

Slack up and try helping out.

 

Read the top part of the post, the bottom part is for humor. :)

hey, your next post is post 1000, better make it memorable! My recent 1000th was rather mediocr http://forums.Groundspeak.com/GC/index.php...=249615&hl=

Edited by Andronicus

Share this post


Link to post

Well, Blue Deuce, you knew it was coming...

 

all Wright,

You should wait a week or so, to allow the previous holder time to log the TB into the cache. Or, after a few days, e-mail the previous holder, to find out what is going on. I once waited two weeks for a vacationing geocacher to place the TB. (He was the owner.) It is rude to grab the TB before the previous holder has had the opportunity to log it properly. As Dragons West pointed out: this is a social activity.

It annoys me greatly when people grab a TB before I've even driven home! (The most recent case: TB was grabbed from me an hour after I placed it. Wifi was not working at the hotel, so I did not get to try to log it until the next day. Still consdering reporting the bug grabber for the offensive language in his e-mail! We worked it out (on a semi-combative basis), and the bug has moved on. Should be in Texas soon!

Share this post


Link to post

One good way to see what is up is to look at when the cacher who still has it in their inventory logged the cache you found it in. If the cacher has not logged the cache find, probly he is away from a computer. If it was logged a week or so ago, he probably forgot to log the bug or is mentaly deranged; one or the other.

Share this post


Link to post

Read the top part of the post,...snip

 

I would still disagree with the first part since I do not see that that cacher was being blatantly angsty. Being new somethings mean that they try to fix things as they think it should work.

 

When that happens we should try to help.

 

The rest of your post was nothing but editorial claptrap.

Edited by BlueDeuce

Share this post


Link to post

I dropped some TBs at GW8 and before I could log a couple, others, quite experienced gecachers, had grabbed them from me - one explained it was necessary because it was going to an event the next day.

 

Sigh. :)

 

Well, it does happen and I took an understanding tack - it isn't mine and it does need to move.

 

Of 4 personal bugs, launched for the trip at significant locations (GC1169, GC1QM7K, GC12, GCGV0P) all have not budged until I got them placed. Two are now logged on the move, while two are not yet logged out of the cache/event. I'm certain they are all in the hands of geocachers and will register at some point.

 

Read the top part of the post,...snip

 

I would still disagree with the first part since I do not see that that cacher was being blatantly angsty. Being new somethings mean that they try to fix things as they think it should work.

 

When that happens we should try to help.

 

The rest of your post was nothing but editorial claptrap.

 

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

Edited by DragonsWest

Share this post


Link to post

Well, Blue Deuce, you knew it was coming...

 

all Wright,

You should wait a week or so, to allow the previous holder time to log the TB into the cache. Or, after a few days, e-mail the previous holder, to find out what is going on. I once waited two weeks for a vacationing geocacher to place the TB. (He was the owner.) It is rude to grab the TB before the previous holder has had the opportunity to log it properly. As Dragons West pointed out: this is a social activity.

It annoys me greatly when people grab a TB before I've even driven home! (The most recent case: TB was grabbed from me an hour after I placed it. Wifi was not working at the hotel, so I did not get to try to log it until the next day. Still consdering reporting the bug grabber for the offensive language in his e-mail! We worked it out (on a semi-combative basis), and the bug has moved on. Should be in Texas soon!

 

ONE WEEK?!?! No way - you have until the next night to drop that bug. I agree - you have the opportunity to drive home and log it, which is why I wait until the next night, after that, I believe it is rude for the dropper to wait so long. If you can't drop it online the same day you physically drop it in a cache, the person who grabs it from you is not the rude one.

 

By the way, the Groundspeak site etiquette says to try not to hold on to them for more than two weeks. One week in and you're half way there.

Share this post


Link to post

You should wait a week or so, to allow the previous holder time to log the TB into the cache. Or, after a few days, e-mail the previous holder, to find out what is going on. I once waited two weeks for a vacationing geocacher to place the TB. (He was the owner.) It is rude to grab the TB before the previous holder has had the opportunity to log it properly. As Dragons West pointed out: this is a social activity.

 

It annoys me greatly when people grab a TB before I've even driven home!

+1

Edited by hydnsek

Share this post


Link to post

Well, Blue Deuce, you knew it was coming...

 

After my response to DragonsWest, sure, but I don't see where it came from. Maybe I'm too involved with getting a bug back on track to see the hive.

 

Checking...

 

I don't see an issue with the bug mission.

 

I'm missing it. (not that I really care)

Share this post


Link to post

I drop trackables when I am traveling and may not have computer access for a couple of days. I put a note on the log which says, "Dropped trackables. Will log into the cache within" however many days I think it will take until I get internet access. Usually two to three days.

 

I also had one of the geocoins I dropped at GW grabbed the day of the event before I could log it in. I didn't worry too much about it as they dropped it into the event and then retrieved it although it would have been nice if they had given me time to drop it.

Edited by OHail

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

I concur. If someone wants to log the TB before I get a chance to drop it - by all means grab it from me. I just hope they will take the time to drop it into the cache they retrieved it from too.

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

I concur. If someone wants to log the TB before I get a chance to drop it - by all means grab it from me. I just hope they will take the time to drop it into the cache they retrieved it from too.

 

Hey guys, as troublesome as it may seem don't forget that logging bugs can be tricky. A response might come across as angsty, but that doesn't mean the cacher doesn't want to log it properly.

 

Helping them goes a long way.

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

I concur. If someone wants to log the TB before I get a chance to drop it - by all means grab it from me. I just hope they will take the time to drop it into the cache they retrieved it from too.

 

When I pick up a trackable which isn't logged into the cache I plucked it from I'll look at its last location.

 

Often they are registered in another cache. If the date is more than a couple weeks past then I'll just grab it, dip it where I found it, retrieve it and then move it along.

 

Once in a while they show in the hands of other cachers. If they visited the cache months ago I'll just grab it. never had anyone moan or pitch a fit over it. Usually they forgot or didn't have the tracking number (back in the day they tracking number wasn't shown in your inventory.)

 

If the visit was recent I'll wait a week or two and sit on the bug (sorry to the owner, but I'm exercising courtesy) If it hasn't been dropped, I'll gently prod the current holder with a note.

 

Never had any problems, such as the OP had, though have heard of them occasionally. Usually someone with an overdeveloped sense of propriety believes they should be the one to log the drop, no matter how long they wait to do it.

Share this post


Link to post

 

Once in a while they show in the hands of other cachers. If they visited the cache months ago I'll just grab it. never had anyone moan or pitch a fit over it. Usually they forgot or didn't have the tracking number (back in the day they tracking number wasn't shown in your inventory.)

 

 

You don't need the tracking number to drop a bug. If they didn't have the tracking number to log the bug, then it would still be in the previous cache.

Share this post


Link to post

 

Once in a while they show in the hands of other cachers. If they visited the cache months ago I'll just grab it. never had anyone moan or pitch a fit over it. Usually they forgot or didn't have the tracking number (back in the day they tracking number wasn't shown in your inventory.)

 

 

You don't need the tracking number to drop a bug. If they didn't have the tracking number to log the bug, then it would still be in the previous cache.

 

A few years ago you did need the tracking number. There are still some traces on the pages of how the site worked. Notice if you go to Trackables, enter the tracking number, to make a log entry you have to enter the number a second time (try to log a pick-up without it and it will bark at you.)

 

I remember my early frustration with travel bugs and tracking numbers. It is much better now, though I would like to see the real tracking number carried from page to page as a form variable, so I don't have to type it in twice when doing pick ups.

 

The obnoxious cacher (not the OP) clearly has the number written down and was trying to make some sort of statement of propriety by grabbing it back (despite no longer having the trackable in the cache or his/her possession.) Sad to see them act in such a manner as they have evidently forgotten the trackable belongs to someone else who is probably quite confused and would just like to see the bug move.

 

Never forget, some trackables are watched by children and they'll be quite puzzled if they see a tug-o'-war going on over who gets to place their travel bug.

Edited by DragonsWest

Share this post


Link to post

Seems to be a bit of angst, rhetoric, and just plain bull-headed-ness here...

 

I have read through the "wait a while", "grab it now", "wait one day only", etc., and the near-arguments that arise from such posts in disbelief.

 

Not that it helps the OP, nor the "other" involved in this tug-O-war but there is a solution for future loggings and placements that really is quite painless. This is from a thread posted quite some time ago. Surprisingly, the technique is simple and (to date) it has worked like a charm. Do read it over.

 

http://forums.Groundspeak.com/GC/index.php...t&p=4189821

 

Try it -- you'll like it, Mikey!

Share this post


Link to post
If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

If by juvenile, you mean inexperienced, I agree with you. But from the OP I got the impression that the original person was a little confused, which says inexperienced to me.

 

I forget who said it, but "never attribute to malice what can be explained by stupidity." (or in this case, inexperience)

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

It's common (OK, maybe not so common) courtesy to PM the current holder to ask 'what's up' before grabbing it like a kid in a candy store.

If behaving in a civilized manner is too much trouble, perhaps that cacher should eschew TBs.

Share this post


Link to post
It's common (OK, maybe not so common) courtesy to PM the current holder to ask 'what's up' before grabbing it like a kid in a candy store.

If behaving in a civilized manner is too much trouble, perhaps that cacher should eschew TBs.

 

Problem is that BOTH cachers are new. Both are inexperienced. I don't think either one intended any malice with their actions.

Share this post


Link to post

As someone who has slogged through a bunch of juvenile, inexperienced, confused, spiteful, hopeful bug owners and finders, I know that a little friendly guidance can do a lot of good things

 

I know it doesn't seem like much to some folks, but it does make a difference.

Share this post


Link to post
I drop trackables when I am traveling and may not have computer access for a couple of days. I put a note on the log which says, "Dropped trackables. Will log into the cache within" however many days I think it will take until I get internet access. Usually two to three days.

 

If I'm traveling and drop a trackable, I'll leave a note with the bug (also note in the cache log) as to when I expect to be home and be able to log the drop. Writing a note in the log is fine but I can see an instance where someone picks up a TB but doesn't read the previous log(s) to note that that the TB hasn't been logged yet. I also note that if someone wants to grab it away from me before I log the drop, feel free but please make sure to drop it into the cache it was found in and then retrieve it back out.

Share this post


Link to post

It's not a disparaging remark aimed at the original poster, the juvenile riposte was made by the other cacher in question. Sorry that's not more clear to you, but this IS a social activity and people with their knickers in a twist can pop up at any point, regardless who actually owns the TB (hint: not necessarily either of the cachers in the original post.)

 

This is where we differ. From experience I don't see this as a juvenile cacher.

 

Experience is one reason I can get a held bug back into circulation.

 

Well, we'll differ.

 

If I drop off a travel bug and someone grabs it before I have time to log the drop, I won't be of a 'HOW DARE THEY!!' mind and grab it back. That's a petty and juvenile response.

 

I concur. If someone wants to log the TB before I get a chance to drop it - by all means grab it from me. I just hope they will take the time to drop it into the cache they retrieved it from too.

 

Well, that's what I thought too, but apparently it's bad TB etiquette to grab it before they log it. I'm gonna reply to my original post to give an update.

Share this post


Link to post

Okay! Thanks for all the info! I can't believe how many opinions there are on this!

 

I have learned that I should not have grabbed it from the guy - didn't realize that there was any kind of hurt feelings involved in that.

I was friendly to the guy in my emails. I guess I was shocked that he grabbed back, he may have been shocked that I grabbed in the first place! Obviously I have a lot to learn too! In the future I will wait - didn't know that was an issue.

Now, I found out the problem, and why he grabbed it back. He wants to see the miles added on. In the "view map" he can't see that it's been in utah at all. The cache he left it in, and I dipped it in (yes, I did do that) shows that the TB has been there. The TB page shows it's been in that cache.

 

Is this an example of why the TB owner has to "recalculate the miles"?

 

Now I feel crappy about this whole situation and wish I never grabbed it away from him. well....sorry guy, let's be friends?

Share this post


Link to post

I must be one of the rare ones that wouldn't care if someone grabbed a TB before I logged that I dropped it. I hardly ever move a bug cache to cache in the field so I can always log that i picked it up but sometimes I drop it and I know at least once someone found it before I could log the drop. And I just didn't care. I didn't see a lick of reason to go grab it back from him...

Share this post


Link to post

 

ONE WEEK?!?! No way - you have until the next night to drop that bug. I agree - you have the opportunity to drive home and log it, which is why I wait until the next night, after that, I believe it is rude for the dropper to wait so long. If you can't drop it online the same day you physically drop it in a cache, the person who grabs it from you is not the rude one.

 

I didn't see that this post was responded to.

 

One day is far too short of a time to be grabbing travel bugs that have not been placed on the cache page. You might not have taken vacations or 3 & 4-day weekends into account and that not every one has a laptop or even the time at the end of a vacation day to be logging. They should try to get the tbs logged immediately but not everyone can.

 

Folks on vacations longer than one week should find a way to drop the bug within a week and preferably a few days.

 

Others have already stated that a note with the tb is a good idea if it will take more than a few days to log it in. I agree.

 

One week seems very logical to me based on years worth of seeing and trying several options. If people do wait more than one week, regardless of their situation, then they should not be put-out if someone grabs it from them before they place it.

Share this post


Link to post

I am moving this thread from the Geocaching Topics forum to the Travel Bug forum.

Share this post


Link to post

Okay! Thanks for all the info! I can't believe how many opinions there are on this!

 

I have learned that I should not have grabbed it from the guy - didn't realize that there was any kind of hurt feelings involved in that.

I was friendly to the guy in my emails. I guess I was shocked that he grabbed back, he may have been shocked that I grabbed in the first place! Obviously I have a lot to learn too! In the future I will wait - didn't know that was an issue.

Now, I found out the problem, and why he grabbed it back. He wants to see the miles added on. In the "view map" he can't see that it's been in utah at all. The cache he left it in, and I dipped it in (yes, I did do that) shows that the TB has been there. The TB page shows it's been in that cache.

 

Is this an example of why the TB owner has to "recalculate the miles"?

 

Now I feel crappy about this whole situation and wish I never grabbed it away from him. well....sorry guy, let's be friends?

 

Sometimes it takes a while for the website to catch up with the miles. See the pinned thread at the top of this forum about that subject.

Share this post


Link to post

I'm still trying to figure out why the first guy kept a record of the number on the TB and was able to grab it after it was out of his hands.

Share this post


Link to post

I'm still trying to figure out why the first guy kept a record of the number on the TB and was able to grab it after it was out of his hands.

 

Well...

 

I scribble a few notes in a book at every cache we visit and that includes the tracking numbers of any trackables we pick up or drop off. It's very useful when writing logs and ensures I get all the trackables' movements correct.

 

MrsB

Share this post


Link to post

Tip of the day: Try to make it a habit to write down and save the tracking number of every bug you find. You'll need it to retrieve the bug if you accidentally drop it into the wrong cache listing.

Share this post


Link to post

I'm still trying to figure out why the first guy kept a record of the number on the TB and was able to grab it after it was out of his hands.

 

I ALWAYS write down tb numbers as soon as I get home. I was in a similar situation a while back, after bringing a bug across the country with me. As I was on vacation, I didn't get a chance to log the bug for a few days. I returned to internet access to find an email from someone who had found the bug the same day that I dropped it off. The email was sent mere hours after I had been at the cache, and less than 24 hours later the bug was grabbed from me. It wasn't even dipped in the cache before the new person sent it on its way. After that, I started writing down all tb numbers to prevent future missed caches.

Share this post


Link to post

It annoys me greatly when people grab a TB before I've even driven home!

That sort of happened to me today... I dropped a bug into a cache on my way home, and by the time I was done reading bedtime stories the bug had been grabbed from me. It's not a big deal, but it was only about three or four hours between me dropping it and me intending to log.

Share this post


Link to post

I'm still trying to figure out why the first guy kept a record of the number on the TB and was able to grab it after it was out of his hands.

agreed....I recently took a number of coins and bugs from Ga out to California. Found 2 caches the first day, dropped a coin in each, logged them, then got to thinking about it and realized I had switched them, logging both into the incorrect cache. Had I had the numbers written down, I wouldn't have had to revist both caches to correct the situation.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  
Followers 0

×
×
  • Create New...