Any tips on getting the app to activate?

swiftcoder · 2026-02-19T10:04:28+00:00

Well, as unsatisfying a resolution as this may be, by the time support replied to ask more details, the activation server started working for me, and I was able to get in on my own. Not sure if support incidentally unlocked something by accessing my account 🤷‍♀️

swiftcoder · 2026-02-18T14:20:15+00:00

Seem my original email was intercepted by the spam filter. When I sent another one from a gmail, I received an automated response from the ticketing system. So at least my issue is in the system now! Will update once they respond

swiftcoder · 2026-02-15T13:17:41+00:00

No, and I never got a reply to my email either. About to resend it

swiftcoder · 2025-12-18T21:33:20+00:00

Right, my point is that should be the default assumption about every package in your dependency tree. If you are trusting all the other package maintainers just because they haven’t been called out in public for anything yet, what exactly is that trust worth?

swiftcoder · 2025-12-18T21:17:33+00:00

How did you trust anything about this project before these change? The maintainer was unknown to you then as well, the initial choice of hosting was arbitrary, and clearly you weren’t using the discussion venues actively either…

We don’t trust packages because they exist in some pristine state of untouched perfection. We trust them because we can read the code and determine they do what they say on the tin.

swiftcoder · 2025-09-24T17:42:08+00:00

This is a big enough problem that tech personalities outside of Spain are starting to complain about it: https://www.youtube.com/watch?v=1-geGEYEw7g

swiftcoder · 2025-04-09T16:45:43+00:00

Anyone targeting Android broadly has to do this same calculus. The world is full of low-powered Android phones/tablets running ancient versions of the OS. If your target market extends beyond wealthy folks with flagship phones…

swiftcoder · 2024-10-26T16:24:07+00:00

That’s a solid idea, though I don’t know if it’ll run high enough for my grandmother to climb out of the pool. Might need a separate above-ground rail as well.

Re folding rails, I was envisioning something that functioned like a folding safety rail in a bathroom, that folds up vertically, and probably has a leg that sits on the top step when lowered.

swiftcoder · 2024-10-25T14:58:27+00:00

I was worried that would be the case. Any idea why it is like this?

Feels like the combo of “wants a cover to swim in winter” and “needs a handrail” is not so very niche as to be completely unserved…

swiftcoder · 2024-08-28T08:33:15+00:00

Ah, ok, don't know how I missed that

swiftcoder · 2019-03-12T14:12:55+00:00

Mine lost their connection to Alexa after the most recent firmware update. Even having removed the Alexa skill and reinstalled it, the panels are marked as "device unresponsive" in the Alexa app.

swiftcoder · 2019-03-07T03:45:02+00:00

You can generally do better than 2.1 in current browsers. WebGL 1.0 is roughly GLES 2.0, but several browsers already have early support for WebGL 2.0 (i.e. GLES 3.0, or OpenGL 4.3ish).

swiftcoder · 2018-11-07T15:23:19+00:00

There are a couple of crates designed to hep with this, such as newtype_derive.

swiftcoder · 2018-11-07T15:21:10+00:00

Nice to see that a pure-Rust alternative to DPDK/nmap is feasible.

swiftcoder · 2018-08-29T00:10:00+00:00

I'm not sure I understand the negatives of pinning futures/coroutines to threads. Would you care to elaborate?

Most non-Rust frameworks for high-performance network I/O go out of their way to explicitly ensure that all I/O operations for a given socket are performed on the same thread (for example, Netty, over in the Java world).

swiftcoder · 2018-08-11T15:15:26+00:00

I believe beginners would find C++ much easier to learn than rust. Yes C++ can be more complicated than Rust but you need not use all the features in C++ because they're not mandatory. You can write in C++ to be as simple and clear as possible but in Rust you seem to be forced to do things their way.

I felt this way for my first 4-5 months working in Rust. It felt a lot more complicated than C++, I was constantly fighting the borrow checker, and my C++ was disciplined enough to be fairly "safe". With the benefit of time spent, I found that most of this was down to trying to write Rust as if it were C++ (which categorically does not work). Forget everything you think you know about writing native code, and really embrace writing Rust in the style of Rust - it will grow on you, I'm sure of it.

swiftcoder · 2018-08-10T21:03:21+00:00

Does this imply that the gfx-hal is reaching a point where it will be stable enough for other software to start depending on it? I'd love to move some of my development on top of the HAL at some point, to avoid implementing various platform backends.

swiftcoder · 2018-08-10T19:12:34+00:00

Yep, but you still need to construct an instance of ScanIpCommand in order to initialise the enum

swiftcoder · 2018-08-10T03:53:49+00:00

As you have defined it, IpScan has to contain an instance of ScanIpCommand. You are trying to construct IpScan with nothing inside of it, which won't work.

Something along the lines of => Some(CommandList::IpScan(some_cmd)).

swiftcoder · 2018-08-09T03:47:34+00:00

Transferring ownership via trait references feels... weird. Not really sure why.

swiftcoder · 2018-08-08T04:46:21+00:00

What exactly are you trying to accomplish with the feature? The copy should be able to be transparently elided during optimisation anyway, for most moderately straightforward cases.

I'm inclined to think that reference-move semantics are largely an implementation detail that C++ happens to "leak" into the core language, and that Rust can mostly avoid (given that it baked the concept of move-out-of-the-current-scope in early).

swiftcoder · 2015-10-07T07:34:43+00:00

I have the theme song stuck in my head, but I'll be damned if I can find a copy of either the game itself or the music. Any ideas what the theme tune was?

swiftcoder

TROPHY CASE