9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Aram Hăvărneanu" <aram.h@mgk.ro>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] acme and sam - mouse suggestions?
Date: Fri, 28 Jan 2022 19:31:34 +0100	[thread overview]
Message-ID: <CAEAzY383pOqhezNkUzbNb0j1aJOXRvL0NjQOyJR7oYxXh4FsrA@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5iposaPJXxhw3vCtFh9OwAnDTUKyS0RSzS_zaoKtXUPxw@mail.gmail.com>

For over a decade I have been using the soon-discontinued Contour
mouse. I have tried both the wired and the wireless versions, but
the wireless version has too much latency for me, although I am
particularly sensitive to latency, so YMMV.

I have been using the exact same unit since I got it, it has been
very reliable for me, however I know for a fact that the newer
versions of the mouse, even though they superficially appear to be
the same are not as reliable. They changed the plastic used in some
internal shaft and that seems to break quite often. Many of my
friends have broken Contour mice that fail in the exact same way.
That internal shaft breaks.

One friend managed to get hold of a bag of spare shafts. I suspect
they could be easily 3D printed, or replaced with a metal shaft.

In any case, since Contour announced they discontinued the model,
I ordered about 30 mice from retailers that lied about having stock
stock. I got three. With these three, I have in total about ten
spares, which I hope will last me for a while.

-- 
Aram Hăvărneanu

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T49f3cceea70d2b61-M390895ff6f8a7015c13ee272
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-01-28 18:32 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  3:48 Ben Hancock
2022-01-28  4:00 ` Rob Pike
2022-01-28  4:21 ` John Floren
2022-01-28  4:30   ` Mark van Atten
2022-01-28  4:39 ` Kurt H Maier via 9fans
2022-01-28  4:42   ` Kurt H Maier via 9fans
2022-01-28  4:47     ` Rob Pike
2022-01-28  4:53       ` umbraticus
2022-01-28  4:56       ` Kurt H Maier via 9fans
2022-01-28  4:59         ` Marius Eriksen
2022-02-02  7:02           ` David Arroyo
2022-01-28  5:05       ` Ben Hancock
2022-01-28  5:15       ` Bakul Shah
2022-01-28  5:38         ` Rob Pike
2022-01-28  6:08           ` adr
2022-01-28  7:14             ` umbraticus
2022-01-28  7:48               ` sirjofri
2022-01-28  8:04               ` adr
2022-01-28  9:33                 ` David Leimbach via 9fans
2022-01-28 11:09                 ` fijal
2022-01-29  1:22                 ` adr
2022-01-29 11:30                   ` fijal
2022-01-29 11:54                   ` Steve Simon
2022-01-29 14:07                     ` adr
2022-01-28 12:16               ` Kurt H Maier via 9fans
2022-01-28 12:43                 ` Steve Simon
2022-01-28 14:36                   ` Charles Forsyth
2022-01-28 18:31                     ` Aram Hăvărneanu [this message]
2022-01-28  4:55   ` ori
2022-01-28  5:06     ` Alex Musolino
2022-01-28 20:24     ` Tony Mendoza
2022-01-29 22:33 ` Oleg Finkelshteyn
2022-02-01  4:25   ` Ben Hancock
2022-02-02 10:37     ` Oleg Finkelshteyn
2022-02-02 11:06       ` hiro
2022-03-22 20:01         ` contact
2022-03-22 23:09     ` Stuart Morrow
2022-03-22 23:20       ` hiro
2022-03-22 23:32       ` Kurt H Maier via 9fans
2022-03-23  0:00         ` Stuart Morrow
2022-03-23  0:48           ` Kurt H Maier via 9fans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEAzY383pOqhezNkUzbNb0j1aJOXRvL0NjQOyJR7oYxXh4FsrA@mail.gmail.com \
    --to=aram.h@mgk.ro \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).