FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public

Request on post #2166 : FW3A, a TLF/BLF EDC flashlight - SST-20 available, coupon codes public - #2160 by Riku :wink:

Thanks MascaratumB
Edit post
I edit list
Apologies
.
.
. EDIT: Your number is on #950
.
Editor

I’m # 796…and that’s the only place I see me…I had mentioned getting 2, so I don’t know if that would be 2 different spots or just the one…oh well…the Miller said “it’s done when it’s done”

The Miller assigned him nº. 343

pepinfaxera assigned him nº. 796
.
Your number is on #343 and #796

You could swap the settings. That way, normal “off” would have a dark button and lockout “off” would be illuminated. Or you could have them both dark. Or one high and one low, or both high or both low.

If it helps at all, lockout mode also functions as a momentary moon mode, which can be handy in the middle of the night. I find it useful when I wake up and want to see something without getting blinded.

Or maybe quick access to blinding turbo is desired? Is this an “in case of intruder” thing?

I probably just don’t understand your use case or what problem is being solved.

Didn’t realize I did it twice. Thank you.

As an extra interesting factoid, when in lightning mode the side switch mimics the primary emitter, within the 3 levels it has of course. :slight_smile:

Also, the side switch will glow in low level when the light is on utilizing the single 7135 chip and in high level when the ramp level passes the 7135 into the FET range. The switch light will also increase from low to high if ramping candlelight up beyond the 7135 chip. It makes it fairly easy to see what channel is in use. :wink:

Edit: This is in reference to Anduril, sorry I didn’t clarify.

Yeah. The FW3A doesn’t have a lighted switch, but on lights which do have one, it can be used to tell at a glance whether the light is at a regulated level or not. Anduril updates that as a side effect of changing the main emitter brightness, so it’s always completely in sync.

I did it that way because it was simple and easy, but I like how it turned out.

count me in for 1!

Lightbringer: The Miller has not included him in the list

Your number is on #106
You have ordered 2 units
The Miller put him in a

You want second unit

Mstevens113 The Miller has not included him in the list

I also don’t see myself on the list. I asked for 1 but now I would like to get 2. Is the list in the OP or where can I see the most updated list? Thanks.

You are number 844 on this post, updated by pepinfaxera:

After seeing your post above he will probably add you for the 2nd one.

I’m tempted to write an interest-tracking bot which would monitor the thread, look for specific types of messages, and maintain an interest list automatically. It’d require people to phrase their requests in very specific ways though… like “TKbot, sign me up for 2” or “Minion, cancel #456”.

Shouldn’t the list be maintained in the OP instead of burried in the thread? That way it’ll be easier for everyone to track.

Op went AWOL

Op went AWOL

The Miller has been absent since about Nov 20th. He is the only one who can change post one. At some point in the future we can have the moderator (forum owner SB) reassign post one to Team Fritz or whatever. Then it can be updated. We just haven’t got to that point, yet.

I have the beginning of an interest-list bot. It’s a long way from being usable, but at least it does a few things so far:

  • Parses posts
  • Looks for and acts on things like “I’m in for N”, plus explicit commands like “TKbot, command arg1 arg2 …”
  • Maintains a database of pledges and cancellations for each user for each product
  • Remembers multiple projects which can have multiple products
  • Remembers which posts it has seen before, and ignores those
  • Detects new users in project threads and schedules a task to welcome them to BLF

However, it does not yet:

  • Run automatically
  • Download new posts
  • Post updates
  • Actually interact with BLF directly, at all
  • Detect which project a thread is about
  • Detect which product a request is about, if a project has more than one product
  • Import old interest lists
  • Generate updated interest lists
  • Ignore quoted text (so quoting a request for a product is parsed the same as actually requesting a product)
  • Have a web interface
  • Handle polls or voting (sometimes the “pick one” approach isn’t sufficient, so it might do Approval and Condorcet-style polls)

So it’s a super early proof of concept and there’s much left to do. Anyway, it’ll probably turn out something like this…

… except probably less chipper and less chatty, since talkative bots tend to end up like this: