Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)FO
Posts
0
Comments
558
Joined
2 yr. ago

  • They don't need your message contents to harvest data. They can see who you talk to, when you talk to them and the type of messages (text/images/videos).

    Connecting people together can expand the amount of advertising impressions they can sell. If your speaking to someone at the same time they are googleing a new trampoline, Google can infer your likely to be interested in trampolines as well.

  • The headlines misleading. They have to store any data they store on Russian inside Russia. Not in a foreign (to Russia) server. If they stored no data they would be okay.

    This type of policy is generally good for privacy. If a company is limited to storing users data in the user's country, that country can enforce their privacy laws.

    Imagine a Chinese company that operates in the EU. GDPR provides citizens in the EU protections on how they data can be handled and the right to have it deleted. So this Chinese company can't sell or misuse customer data without the users permission. However, if the company has no assets in the EU then EU courts have no real remedy to GDPR abuses. The Chinese company with EU citizens data in Chinese servers will tell the court to 'jog on'. However, if the company has to use EU servers then there are assets to target and in extreme cases data to be wiped manually.

    Whilst this type of law can protect users privacy when organisation are abusing data (which is the usual situation in liberal countries). It can also aid governments in abusing their citizens data. A company can't protect their customers from the state the data is stored in very well (if the courts are complicit in the privacy invasion).

    If Russia wants access to a Google's users data their only option is a strongly worded letter, if the data is stored in the US. If the data is stored in Russia the threat of violence or imprisonment can be used.

  • Apple should block it. It requires people to hand off their apple accounts to an organisation. Someone using an account like this should be blocked by apple's servers. As they clearly aren't the account owner.

    Many online accounts will return a password incorrect message, even when the password is correct, if they believe your aren't the account holder (bots, scammers etc). To allow this puts users accounts at risks.

    Some bad actors are likely to mimic this setup. Advertise access to iMessage for Android users, then use the apple account to defraud or blackmail them. It will be very attractive to previous iPhone users that will have payment details, addresses and media stored with their apple account.

  • Google wants everyone's message data, that's why their pushing it so aggressively.

    RCS is technically an open standard. But in reality it completely depends on Google's Jibe system to make it work for many carriers.

    The recent anti competitive trials has shown Google is willing to pay apple billions for people's internet activity to go through them. With Google currently pushing anti iMessage ads to shame apple into supports RCS, Google has most likely offered Apple a lot of money to use RCS. Apple has decided it's not worth it.

    Why apple isn't supporting RCS is unknown. But it either user privacy or user retention to their ecosystem. Either way they don't think more exposure to Google is good for their users. This 'open' standard is a joke. If it doesn't make Google money soon, they kill it like all their previous messenger projects.

  • You get the self centering speed of Phillips with less cam out. It's standard for most construction style work, very useful when you need to do 100+ screws a day.

    It can be a bit of a nightmare when you first start doing DIY. Because you may not recognise the difference between Pozi and Phillips. Both drivers will turn each screw, but the wrong driver will make cam out and stripping more likely.

  • I rarely see imperial hex. Many Allan key set still come with imperial sizes but all contemporary products and screws come as metric now (in my experience in the UK).

    Even with the metric there are still many sizes needed, which I agree is frustrating. However, it ensures the correct bit size is used for the correct screw. Unlike Phillips, pozidriv and slotted. It also limits the amount of torque that can be applied to a screw that is proportional to the screws thickness.

    The prevalence of low quality screws and tools for hex drives is because they are cheaper to manufacture. Its unfair to reduce the rank of the drive mechanism for that. If the average hex screw and driver were built with the same quality of materials as the average torx this would be less of an issue.

    I would recommend you use a screwdriver with hex bit heads instead of Allen keys, if you need to use hex screws a lot. Much more pleasant experience and much less likely to bend and twist like Allen wrenches.

    Well designed things and screws should come with appropriate drives. I wouldn't recommend using a wrench on internal hex drives. If they needed high torque they should be external hex like a traditional bolt. Only external hex, large torque and large internal hex should be applied with a wrench. Other drive systems should be used when hand tightening is all that is needed. I've learned the hard way tighter isn't always better.

  • If you use the right driver and right size of driver. It's very good. In my experience it's much better than Phillips.

    Torx, hex and Robertson are better, but they don't self centre. So if your doing a lot of screwing, pozi drive is king. Because it self centres, it's much faster. It's great for construction type work (decking, plasterboard, walls etc).

    If your doing more fine work, or need to apply a lot of torque it's shouldn't be used. But very long/thick screws tend to be external hex, torx or combinations of these at Screwfix/Toolstation.

  • If you get the CPU performance you can't get the battery life performance. Apples the only manufacturer that manages this. Their price reflects the reduced amount of compromises they make. If you really need good performance across the board in a laptop, the value is their. If you need a browser and office suite on a budget, the value isnt their.

  • You can't get a machine this powerful. Intel/amds laptop chips are blown out of the water by apple silicon. If you try to match all the specs you'll struggle to get many offerings below the price apple charge.

  • It remains to be seen whether Profiles are an RCS feature or something that Google (Messages) is managing and hosting itself.

    This misconception that RCS isn't just Google in a big hat is strong.

    If your using RCS it is highly probable you or one of your contacts are being provided with RCS through Jibe.

    Jibe is Google's proprietary RCS backend. Carriers aren't implementing RCS so Google does it for them. RCS isn't a proper open standard, it's Google trying to jam it's messaging service into your life through the backdoor.

    Developers can't make custom frontends for RCS because Google won't let them. Only Google and device manufacturers can.

    They are trying to force apple into this system as well. They hope to get iMessage to support it. So they'll have their messaging system embedded into every Android or iPhone.

    The worst part is it barely works. I'll get more unable to deliver over RCS than I've ever seen on Signal, Telegram and WhatsApp. As soon I switch back to SMS it delivers straight away. The fact it doesn't switch automatically further frustrates me because it'll leave messages hanging, when you expect the text messaging app to send texts.