azdle

Interesting, I didn't know it would support pulling from other git hosts. It looks like their CI even has an API integration with GitHub at least for PRs. That's looking like a potential winner. Thanks for pointing that out.

I always had insane amounts of queue time on gitlab's CI too. I know they have self-hostable runners, do you know if those work from behind a firewall so I could run them on hardware I have at home?

Also, do you know if it's possible to use gitlab CI as a merge gate on github PRs?

I've used it in the past, but when they finally killed off the 1.0 builders (?) my company went to an "internally" hosted Jenkins[1] server and I haven't played with any of the 2.0 stuff. Have you? How do you find working with it?

[1] I did also ask about selfhosted stuff, but I'm not willing to host Jenkins for myself. I've heard nothing but complaints about managing a Jenkins install. It's been fine as a user (if a bit confusing), but I really don't want to admin it.

Well, their lowest paid tier is $69/month. I dunno about you, but that's way more than I can justify spending to be able to support doing work for free. If they had a $50/year or so plan that just restored the previous open source plan, I'd be more willing to consider something like that, but >$800 a year puts it firmly out of my price bracket for what it offers me.

I've been using Travis on a bunch of my opensource projects and was wondering why builds were getting queued for ~a day before they'd run, I guess I got my answer. :/

I don't really want to lock myself into GH actions (ideally, I wouldn't be on GH at all), does anyone have any suggestions for alternatives? I don't mind paying some money, but the almost $1K/year for Travis' lowest tier is about an order of magnitude more than I can justify. I've also got plenty of compute laying around if anyone has suggestions for something self-hosted.

When it's Firefox.

I mean, that's probably true. But if I tell myself that the problem was technical I can still hold out hope that they're secretly solving those problems and will try again. :P

I've still never seen a good retrospective on what went wrong, do you happen to have any links/stories?

I'm still sad to this day that FirefoxOS got axed. Doubly so now since I'm trying to find a new phone after my Nexus 5X stopped getting official builds of LineageOS.

I really hope that there's some diabolical plan within Mozilla to bring it back once the wasm world is more established and makes having a fully browser based OS less of a performance hit.

It's also available to buy DRM free: https://vimeo.com/ondemand/183222

I found it rather disappointing though. It didn't really go into any detail about what it was supposed to be, just "dude had this idea, got other people to sponsor some research, locals didn't like the idea, also there were funding problems so it never happened".

Just from your numbers, it sounds like it's a good deal as long as you need to (grid) store less than 1/3 of your generated/consumed energy.

If you still have the Ikea one, that was caused by a fairly wide-spread issue with the power bricks. They'll replace them under warranty with just an email with some info about the brick.

That's technically the second argument. Just like in C++, when using a chained method, the first argument is implied to be the thing you're chaining on. So this is the same thing as calling Result::expect(File::open(&input_filename), "[ ERROR ] Failed to open file!"), but I've never actually seen someone ever use expect that way.

See also the definition of expect: https://doc.rust-lang.org/std/result/enum.Result.html#method...

> ${small company with small company sized bank account} if you're reading this, please hire a new design team that is on par with ${list of massive companies with oodles of money} and a new industrial design team that has competence at the level of ${companies that are the best in the world at industrial design and compensate to match}

lol, I'm sure they'd love to, are you offering to pay the salaries?

In addition to what others have suggested you might want to check how many things you have registered under about:serviceworkers (type that in as the URL), there might be something in there running far more than is reasonable.

For me it seems to also require that you turn on "Spoof <noscript> tags" in uMatrix.

I couldn't find anything called a "Focus AXRe", looking at a few different products that came up for "Gridstream RF" the compliance docs only list that they're zigbee coordinators, not endpoint devices. ex: https://zigbeealliance.org/zigbee_products/gridstream-rf-enh... see 8.1 on pg 7. AFAIU, that means it expects to control other zigbee devices, not report to coordinators like the ST hub.

You could see if you can find your actual meter here: https://zigbeealliance.org/zigbee_products/?product_type=cer...

But how do your coworkers feel about you not having a problem talking calls at your desk?

Thank you for your hard work on rust. The intelligent error messages are a significant part of what makes rust such a joy to use.

And will do, if I encounter them.

In my experience, the vast majority are exactly like the error they show. Some are even better. I haven't hit a warning in ages that hasn't been able to be auto fixed by `cargo fix`.

However not all of them are. Back in the pre-async/await days you'd end up with some really gnarly implicit types in some really big functions with lots of returns. Then sometimes you'd make a mistake on one of the returns and the compiler would assume that your mistaken type was the right one & point out all the places where the actually correct type was returned. Then you'd have to go hunt for where you needed to add a `as Box<Future<Item = _, Error = _>>` to get it to compile again.

I haven't hit any issues like that since I started converting the gnarly stuff to infinitely simplier async/await code, but I have to imagine those kinds of issues are still lurking in other areas where you can't get away from complicated code.

Even with that I whole-heartedly recommend anyone that's thinking about it just go try it out and/or read some of the book. It's a delightful language to work with. I have way more fun working with Rust than I have with any other language. It takes care of so much of the BS that I don't want to have to think about, so I can just think about the interesting stuff.

SmartThings | Embedded Software Engineer | Full-Time | ONSITE | Minneapolis, MN

SmartThings is Samsung's home automation platform that uses a cloud-connected hub to control (and be controlled by) both local (Zigbee, Z-Wave, LAN) and Cloud-Connected (Assistant, Ring, etc.) devices. Our biggest claim to fame is that we’re an open platform, anyone can write Device Handlers to support almost any device or SmartApps for completely custom automations. We're a subsidiary of Samsung, but we're a separate company and have largely managed to retain the startup culture.

The team I'm on is hiring an Embedded Software Engineer. We're looking for someone comfortable with developing embedded linux applications. This is for the software that powers the SmartThings hub. It's primarily written in C, but our team is doing almost all Rust, except where we need to hook into existing code.

More info & to apply: https://jobs.lever.co/smartthings/026d9806-ac47-45e2-8f0e-f7...

We also have a lot of other positions open in other areas that I'm not as familiar with: https://jobs.lever.co/smartthings?lever-via=Tej-2aM_0w

There's a version that removes "ads and binaries" on F-Droid: Maps (Offline OpenStreetMap maps) - https://f-droid.org/app/com.github.axet.maps

Normal phones can record phone calls, right? I assume that this wouldn't make anything possible that isn't already possible. But, again, I really don't know what I'm talking about here, this is just my understanding from what I've read.

My understanding is that the microphone (& speakers?) isn't wired directly to the modem, but needs the CPU to replay the audio to the modem so that the modem (aka, baseband) doesn't have access to the microphone audio except when it actually needs it. So, I would think that the headphone mic wouldn't work either.

My garbage kitchen scale says 231 g.

Can confirm, I am not a promoter / paid reviewer / internal employee.

It's a black box for sure, but it's not a 'binary blob'. That's an important distinction. There's no kernel module that tied to a specific kernel version. And even better the WWAN module is in an M.2 (?) socket, so it'd replaceable in the future as new tech comes out.

> Nobody buys a phone for the operating system

I did. Pretty much because all the drivers are mainline(able). Even if purism went belly up today, I could continue to run up to date Linux on my librem 5 basically forever.

They still do: https://www.dell.com/en-us/work/shop/cty/pdp/spd/xps-13-7390...

It's basically software development project hosting (like gitlab), but for people who prefer mailing lists to web apps.

> Nielsen, while saying “everything is on hold,” stopped short of promising to terminate the petitions for cancellation the company’s IPLA attorney John Kim filed with the USPTO. Nielsen said he would be reaching out to every business targeted in those petitions to discuss how they can work together.

So, they still think they own the generic term "backcountry" and that others need their permission to use it. Nothing has changed.