

I’ve had great results with various refurbished Dell Latitudes from eBay over the years. I have a stack of about 5 or 6 of 'em and they’ve all run many mainstream Linux distros with fantastic out-of-the-box support. I pass 'em out to members of the household whenever a laptop is needed and they’ll usually get the job done.
I’d just type in “Dell Latitude” on eBay and filter by price and such. I suspect any model with an i5 and 8GB RAM oughta be fine for light programming work. I’ve found sellers with high ratings (like 97% or higher) and thousands of sales are pretty reliable (and tend to have return policies in case you get a lemon). Just test all the hardware (webcam, microphone, headphone jack, USB ports, ethernet, etc) as soon as you get it.
I’ve saved a lot of money over the years buying secondhand, and these machines have been running without a hiccup for years of casual use.

I took a cursory glance through the source code (for the Firefox version, at least), and I’m not seeing any calls to the gitflic.ru URL outside of the update functions (there appear to be two different places where these might be triggered) and one function for importing custom sites:
// Import custom sites from local/online function import_url_options(e, online) { let url = '/custom/sites_custom.json'; if (online) url = 'https://gitflic.ru/project/magnolia1234/bpc_updates/blob/raw?file=sites_custom.json' + '&rel=' + randomInt(100000); try { fetch(url) .then(response => { if (response.ok) { response.text().then(result => { import_json(result); }) } }); } catch (err) { console.log(err); } }I noticed in the manifest.json, there is the optional permissions array:
"optional_permissions": [ "*://*/*" ],Which seems to grant the extension access to all URLs, so maybe that’s why the HTTP request is able to fire on any given website rather than just the ones explicitly defined in the regular permissions array. Though this is speculation on my part; I’ve only ever written one or two complex Firefox extensions. I’m not sure if the “optional permissions” array can be declined upon installation (or configured in the extension settings after installation); perhaps access to the wildcard URL can be revoked so that this update call isn’t occurring constantly.
All looks okay to me, but this was a very quick audit.