I'm still using a first gen Raspberry Pi Model B to run an adblocking DNS server (github.com/0xERR0R/blocky), and PiVPN (Wireguard). For the most part, it works great except apt-update occassionally maxing out the CPU/RAM which causes my services and sshd to be killed.
LinkedIn pulled something similar a few years back. At the time, I was using the same password for both my email and LinkedIn account, and found that people from my email address book were showing up as suggested connections. I can only assume "consent" for this was buried in the T&Cs.
In case of Linkedin, they do ask for consent. But, even if you didn't allow it to export your contacts, other people may have allowed it, linking their linkedin profile with your email address. LinkedIn then shows them to you as suggested connections.
This personally bothered me for a while then.
FTTC provides a decent connection speed ("up to" 76Mbps according to BT) but my main gripe with it is that I have to continue with the archaic process of "renting" the copper telephone line between the exchange and my house - for a sum almost the same as the broadband itself. Openreach have clung onto this cash cow by opting for FTTC over FTTP, forcing customers to rent a telephone line they don't want
I recently changed ISP and told them the copper line was part of the broadband package with my previous ISP (for an extra £10/month) and was assured everything was fine.
One month after the transfer, Openreach ceases the PSTN line and the reaction from my new ISP was "well it's your responsibility to keep up your BT subscription" (never had BT).
Two weeks later, the PSTN line is still dark, and I'm waiting for Openreach to install a new MPF line provided by my current ISP (for an extra £10/month of course).
Apparently the reason for doing this rather than re-start the PSTN line is part of a process called "Local-loop unbundling".
I'm amazed they still can't get LLU -> BT/LLU -> LLU migrations right. We sold ADSL as a second tier provider and once upon a time if you were on an LLU service and needed to migrate to another LLU provider the only sure-fire way of doing it so it didn't fuck up was to migrate back to a BT based service then migrate again. We once had a business customer, paying proper business coin migrate from one LLU provider to another. On the day of the migration the gaining provider's engineer didn't turn up to pick up the pairs and jumper onto their rack which left the customer without service for over 24 hours. So glad I don't have to deal with that crap any more.
I have this gripe too. I recently received a letter from BT to say that my line rental was increasing by £1/month so that they could offer more "great services and a wider selection of content".
The only reason I have the line is for the FTTC connection that runs over it (using Goscomb as my ISP, rather than BT) There isn't even a phone connected to it.
I'm in the midst of using Ionic to build a simple app that consumes a JSON API and am finding it very good to work with. It seems pretty solid for a beta product. I'm new to Angular but it seems like you can get a lot done without knowing all that much about it's inner workings, which is great.
I would suggest sitting down and seeing what you accomplish using it for a few hours. I did this to compare Ionic and jQuery Mobile. The app is far from complete, but I'm liking it so far.
