Re: Only temporary
And actually... good on them. Those lower-spec Pis are ridiculously cheap and I imagine commercial users take up a decent chunk of that production.
889 posts • joined 1 Aug 2009
> You'd still be stuck using the very same bank transfers you compain about.
Trade BTC into USD/EUR/GBP immediately on the exchange then transfer to bank account.
True, the transfer part still relies on traditional banking system but a faster payments in GBP back from the exchange takes a couple of hours subject to fraud checks. Still much faster than the 24+ hours of a wire transfer from the US into a legacy UK bank.
I'd be interested to see mining, transport and storage cost of traditional commodities compared to BTC. Everyone in this debate assumes that extraction and processing of traditional commodities is completely free of environmental cost. Though I appreciate energy use by crypto, even renewable, takes energy resources away from other things while crypto utility is still to be broadly developed.
Crypto is a breath of fresh air compared to legacy financial markets though when it comes to trading. I have a stock plan from a US company I worked for several years ago and every time I sell some stock it often takes a full 5 working days to go through executed->settled->wire transfer initiated->wire transfer complete. Trades in crypto are completed in less than a second and funds can be moved around within less than a minute if you use a modern chain and protocol.
What I will say is that every time China bans crypto is just a consistently excellent moment to place a massive short order for some quick profit on a dump... so thanks again!
Been using XFCE for years. Will probably continue using XFCE for years. It has a task bar, a "start menu" and a normal usable desktop area. Throw in xbindkeys and my collection of shortcut scripts, there is nothing else I need.
Thankfully there are all those other desktops to keep UI/UX people distracted in 5 year circles of pointless improvement and career-driven-development... stay away from XFCE.
This is true and very typical of PHP pre-2008/2010 era. People scratching around forums, finding a function someone wrote in 2004 and re-using it. It's all a nightmare.
In the last 10 years or so there has been such a good choice of PHP frameworks that you shouldn't ever need be involved in the security/plumbing at all. Codeigniter and cakephp were probably the first popular ones, allowing any hideous complexities to be abstracted away behind single functions/classes.
Googled-copied-pasted snippets of code of *any* language with permission to read/write to file systems and databases while being exposed to the internet will always end in tears. It was the same with Perl in cgi-bin directories all over the web in the late 90s.
To be honest I still think you need a good reason to choose something other than PHP for server-side web and HTTP API stuff.
Python, Ruby, Scala even Go, all have web frameworks. PHP and any of the many modern frameworks is still hard to beat.
People download Drupal/Joomla/Wordpress, install a bunch of plugins for whatever business requirements, then blame PHP for the fact they can't get more than a couple of hundred rps... ignoring the fact that their CMS is probably making 1000+ database queries to render each page.
Or the other side are the PHP apps developed 8+ years ago by an opinionated dev who thought they were better than using a modern framework, completely sacrificing the project's modularity and maintainability in the process. Yes Laravel might not work exactly the way you want but seriously, for the sake of future developers/employees working on your project, just use a community-developed framework. Any framework will be better than your hand-crafted gubbins.
Oh also a shout out to the PHP docs. The most accessible language documentation I've ever used. Individual pages per function/class with version history and curated examples. Compare that to the nightmare single page wall-of-text with different URLs for each language versions that you often see.
> decisions like this should be left to the user
This is literally an option the user can choose to enable. Eventually it will likely be default because most people will be fine with it and when that happens the user can disable it.
> four week update cycle
I think for most users (and web developers/engineers) frequent updates to browsers are a good thing. If that's not acceptable then there's an LTS version of Firefox available.
All of these modern messaging apps are missing the killer feature... a choice of client. Offering bloated web and mobile apps is fine for initial/occassional use but one of the strengths of something like XMPP or IRC is that there are hundreds of clients to choose from.
One of the vaguely useful features of Slack for technical teams was the IRC bridge... then they killed it off. So you're stuck with the terrible UX of a bloated web app which is no good at messaging and before long some idiot attempts to turn it into a control plane/CLI for your infrastructure.
Exactly. What I type in the address bar is what I want to visit... or probably my history will match after the first few letters. Sadly Firefox copied this omnibar-shambles.
In Firefox if I want to search then I simply ctrl+? (formerly ctrl+k, or whatever search provider and shortcut combo I had created before the search box customisation was borged to become like Chromium).
With the level of caching infrastructure required to get anywhere near acceptable performance Drupal may as well just be considered a really poor static site generator.
Does Drupal's built-in caching still pre-build the template/addon PHP into the database then eval() it back out on page load? Truly dreadful.
Shame to see DAB struggle. I happen to enjoy the sound quality of a potato... underwater.
In all seriousness though if someone can find me a DAB radio that can get through a full 5 match cricket test series on a pair of AAA batteries and is no larger in size or mass than a Roberts 984, then I'd consider DAB to have feature parity and technological progress to have been made.
DVB solved an actual problem. All of the advantages of DAB have been handled by internet devices for almost the entire duration of DAB's existence, so I think we all know which one should be switched off!
^ Says everyone who has _never_ experienced any discrimination, hardship or oppression in their personal or professional lives.
"mere words" to some are not to others. It is absolutely worth reflecting on the fact that so many words and phrases we might take as simple technical terms or have entered common parlance, have done so when the historical and oppressive origins were commonly known and widely accepted. Times have changed - we should reflect on usage of such phrases.
There's alot of hate out there for PHP but for the job of bringing up a website or webservice I would still choose it. In fact I often use it in the terminal for general text-wrangling, connecting to web services and basic DB processing. Granted there was plenty of terrible copy-pasted code out there in the 00s. And people would always be quick blame PHP for the dreadful performance of their Drupal/Joomla/whatever site, ignoring the 2k DB queries they made it do on every page load with the hundreds of plugins. But with such a wide choice of very high quality frameworks being available over the last 15 years I'd say those days of shoddy code are long in the past. IMO a huge amount of credit for PHP's wide adoption must go to the sensible layout of the official documentation on php.net - accessible, clear, easy to follow.
I went from mangled combinations of Perl and SSI to PHP in about 2004ish and I'd say even now there's no reason to completely rule PHP out of the running for new webapp-style projects.
Upvoted because I completely realise there are legacy networks. My point is that there is no need or rush to migrate those dreadful Citrix/Exchange/whatever to dual-stack. Leave it as v4-only if you have the IPs and infrastructure already in-place.
Adding up all those enterprise/business applications and legacy networks across the UK will not contribute to a country's IPv6 deployment percentage to any meaningful degree. IPv6 exists and is completely workable for new deployments if there is the knowledge and expertise in an organisation. The real increase in IPv6 adoption will be driven by end-user/home/mobile networks and deployment by sites in the Alexa top 500/500k etc. Little Bobby SMB SysAdmins likely do not need to worry about IPv6 - it will happen regardless.
> And in any case, Elastic IP doesn't even support IPv6
EC2 doesn't offer Elastic IPv6 addresses because there is no need to... there's plenty of IPv6 addresses to go around!
You add a /56 to a VPC then a /64 from that into each subnet. Easy. It's been like that for some years now.
So depressing that this is a tech website and the forum section on any IPv6 articles are full of comments about how different, wrong, funny-looking, new, scary etc IPv6 is.
Often people say something like "IPv6 is 25 years old and still crap" then no follow-up or technical justification of their opinion. Probably voted for Brexit.
Sometimes people reel off one of these:
- "IPv4 had better features" (then claim NAT is a feature)
- "But my IoT will be publicly addressable" (noone cares what random address your TV got out of the grains-of-sand-on-earth's worth that your ISP delegated to you. Your ISP gave you a box which does the same job with IPv6 as it did with IPv4)
- "But they can track my pr0n" (lol as if your v4 address in a residential ISP pool and browser user-agent isn't all up in pr0n trackers already)
- "But Android doesn't support DHCPv6" (ok, sure, you need to push out vendor-class options or PXE boot your Android device)
However people waffling away in forums and tech websites dissing some technology they don't want to learn are not the point.
IPv6 will keep being deployed to end-user networks regardless of whether `COBOLSL4Y3R` in some forum thinks it's crap for... reasons.
If you're a recent fixed-line subscriber to BT/PussNet or Sky in the UK in the last couple of years, you likely already have IPv6 enabled and it just works.
Mobile networks in the UK are a long way behind US, Europe, Asia, but I've been roaming, tethering, all of it, with IPv6 on mobile and it just works.
I'd be extremely surprised if there's an end-user ISP or mobile provider in the UK that isn't piloting or actively deploying IPv6, if not deployed already. In fact I'd welcome anyone naming any UK ISPs that are categorically saying they will never deploy IPv6.
If you're running servers in an enterprise, small biz, hosting provider, public cloud or your own shite-cloud and happy with v4 NAT to RFC 1918... then fine. Leave it. Noone will care about your dreadful Citrix/Exchange/whatever being v4-only anyway.
Is IPv6 perfect? No. It's different. Read about it. Learn all of it. Deploy it.
IPv6 will keep rolling out to end-user networks over time regardless of whether you like it or not.
Crying in a forum and waiting for IPv4-ng is just pointless my friends.
... is getting there. https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption
30% IPv6 penetration in the UK is not too bad when you consider that of the 4-5 main UK fixed-line providers only BT and Sky have mostly complete end-user deployments for new customers.
Are there any mobile providers in the UK that are offering it yet? Mobile IPv6 deployment is fairly advanced already in Europe, the US and Asia. Once mobile providers in the UK start rolling out IPv6 I'd expect UK stats to jump quite nicely to the 40-50% range.
Obviously if you're an enterprise you may as well continue using RFC1918 space - noone cares about your enterprise citrix or whatever connections being IPv4. And since you're an enterprise then enabling IPv6 for customer-facing services should just be a toggle with your edge vendor, with backhaul to origin over IPv4 if you want.
Don't be scared of IPv6, people! It's fine when you get to know it!
It is always worthwhile visiting these comment pages on IPv6 articles. When I return in several hours I expect to see a deluge of predictable "IPv6 is rubbish" comments by people who give absolutely no justification for their opinion and who don't or refuse to understand it.
I suspect a high level of overlap with people who voted for Brexit :p
> dig -6 www.theregister.co.uk still hangs
Works for me...
$ dig -6 www.theregister.co.uk +short | wc -l
Maybe you should use a resolver that is reachable over IPv6 transport? :)
I guess the point you wanted to make was this though...
$ dig www.theregister.co.uk AAAA +short | wc -l
Someone quoted complaining about lost clients... Well they actually lost them the moment they made the cost decision to use residential broadband with no failover.
Even if you don't want an additional fixed circuit then tethering off a 4G connection is perfectly acceptable to get things done these days.
Like everyone else, RSS brought me here!
Since Google killed off Reader I've been running my own ttrss instance and it's great. Does exactly what I need. Might be a good option if you're one of those people who likes spending their spare time running their own sh1t and work time running other peoples'.
You probably want to look at dnsdist for DNS load balancing. It's a great solution. I use it in a few different application environments, in front of small cluster of active-passive Stubby instances which provide DNS-over-HTTPS (multiplexed HTTP/2 connections if your upstream DoH resolver supports it).
DNSdist - https://dnsdist.org
Stubby - https://getdnsapi.net/blog/dns-privacy-daemon-stubby
... I agree.
In terms of miles from browser to, say, google, the difference in total fibre length between FTTC and ADSL is probably a couple of miles - likely less than 5% of the total.
But who wouldn't expect BT to polish a turd when there's an opportunity to grab tax payers' dosh.
DoH is actually a very cool technology. Many people already ditch their ISP's DNS servers because they are unreliable. What do they replace them with? 22.214.171.124 or whatever the Cisco/OpenDNS ones are. But there is still huge scope for manipulation and interference of any unsecured DNS queries, regardless of who your resolver is. Using dnscrypt makes things slightly trickier for snooping but you're still putting trust on whoever runs the proxy.
DNS over HTTPS means your ISP and anyone else in the path is not able to see your DNS lookups. and would bring some speed gains by re-using/multiplexing HTTP/2 connections.
Considering that a decent chunk of many sites are already served by Cloudflare's CDN, and in many cases people are already putting regular DNS lookups through Google/Cisco, I don't have much of an issue with this in terms of privacy. You've already opted-in to the Nightly builds (and all its telemetry) so being opted-in to further studies within the browser is sort of expected I would guess.
Luckily Sourceforge downloads were always mirrored. Still are I believe.
But last time I looked I had to fight through a barrage of JS/Ad farm mirror redirector pages, all refusing to give me a direct link.
Having a mirror for people to access critical projects = good.
Having ad bloat, tracking, JS, redirecting nonsense in front of your mirrors, that goes down when your site is down = poor. Really really poor.
Biting the hand that feeds IT © 1998–2021