It means the message was sent as an SMS rather than via Apple’s internet chat protocol. There’s also a whole thing that when you write with Android users, they always get green bubbles.
In this context, yes. But I can also mean that the device could not be reached or the recipient switched to android. But for the sake of the joke it means they were blocked.
iMessage uses it’s own protocols and shit that are proprietary, and uses the standard sms protocol as a fallback. Android can use something called RCS which catches up feature wise, but doesn’t play nice with apple.
It’s to create an illusion of exclusivity and therefore social pressure to use an apple device.
This isn’t technically wrong, but to be clear, iMessage is closed source. No one can play nice with Apple, in that regard.
RCS on the other hand is a more open standard that anyone is free to implement and use. It just doesn’t come with end-to-end encryption as a part of the standard.
I mean it’s just a gsm standard with some extra features. Realistically you could probably (relatively) easily figure it out and code it yourself like beeper mini did with iMessage but I don’t think gsm or Google is going to change the standard to stop you.
Google doesn’t own the RCS protocol. This is like saying they own the SMTP protocol because they provide Gmail. They are just one company that has implemented the protocol in their default text message app. They built end-to-end encryption into their implementation, which is currently closed source. I’m guessing this is what you’re referring to.
Anyone can implement RCS. It may cost you some money and some time, but it is possible. That’s the difference I was originally trying to highlight.
No. I’m sorry. You can’t just say it and make it true. Please show me how Google owns RCS or prevents other developers from implementing it within their own apps.
I don’t have the technical knowledge to explain how what works, but there are no FOSS or 3rd party RCS apps for a reason and you can find various posts on social media from devs trying to implement or even reverse engineer RCS and failing
I’m convinced you’re incorrect. SMTP is an open transport protocol defined in RFC 2821 by the IETF. Anything that is an IP “open protocol” would be defined by IETF as an RFC. No one owns it. No license is required to operate an SMTP server. Same with other common protocols like SIP. It sets qualifications/requirements for what it is so anyone can use it.
RCS is a proprietary standard owned by the GSMA. It seems there is some support for developers that want to use RCS but it’s through an API. Meaning your use is licensed and at a cost. Also, you can’t really see what it’s doing. You’re just using an API. Your access can be revoked. So is it an open standard? No.
I did my own research and I plan to try these APIs because I have used other messaging services like twilio for paging applications. But here are some other geeks arguing about it:
The specification exists. It’s not free as in beer. This is really beside the point. Google implemented an RCS messaging client. Your cellular carriers implement the RCS endpoints the clients use.
All using Google Messages. Yep I’m sure. Samsung skins the app but it’s all Google Messages. 3rd party apps arenct supported. I’ll use RCS when there’s FOSS on Android for RCS.
Final Fantasy Legend II on the Game Boy was my introduction to this theme.
The pantheon was Greek, I think, or maybe that was just in the North American localization. But the tree was obviously influenced by Yggsrasil.
The worlds were all spread out across the branches of the world tree, and you’d physically climb up and across branches to progress to other worlds.
A very satisfying marriage of setting and gameplay.
You think you saw it there, but once you move the thing you learn it’s actually a thumbtack. The screw fell into a vent instead, and will occasionally rattle around to taunt you.
Ok I have to confess. I remembered more about the incident and it wasn’t a screw. I was putting together a gunpla (plastic Gundam model) and it was one of the pieces.
Quality-wise, Makita > DeWALT ≥ Milwaukee > Ryobi, at least, if you watch teardowns by guys like AvE.
Power tools are like cars; companies hold several brands and target them to different market segments, like Porsche and VW.
Ryobi is owned by the same company as Milwauki; it’s the budget line, Milwauki being their premium line.
DeWALT and Black & Decker are owned by the same company; DeWALT is their premium line.
The exception in this list is Makita, which is its own company. They’re also objectively more well-built than the others (here), and correspondingly usually more expensive.
The premium lines are better quality (not just more expensive) but also tend to have smaller battery-tool options. Despite being a budget line, I mostly own B&D because most of my tools these days are 24V and there are more tool options there. The few, select, DeWALT tools I have are noticably better quality.
I don’t use power tools enough to justify Makita, but also, their battery-powered line is comparatively tiny. As someone else said, there’s a lot of motivation to pick a (compatible) lane, whichever it is. For most home-gamers, the quality difference will probably not matter much. If I were made of money, though, I’d have everything Makita except for the things they don’t make.
I really like DeWALT. I think it’s a solid choice, and I doubt anyone who isn’t a professional will notice the difference in quality between those and Makita. Plus, they have some neat tools that have unusual features that make an unexpectedly large improvement in ease-of-use.
It drives me nuts that Milwaukee used to be the best line about 10 years ago. They sold out their good name and started selling shitty tools after I bought into their battery system. Grrr.
My tool experience is limited, but with Makita you seem to be describing the same anachronism principle you find in espresso machines.
Arguably the best espresso machines in a class are reminescent of the same model you found 40+ years ago. If you’re looking for the B+ range, everything worth buying has a big metal E61 grouphead with manual levers. In the S-class range, you tend to have more manual levers as often as bells or whistles. My new machine that cost more than I deserve (wife bought it) is basically an oldschool machine with nothing modern in it but a PID controller. Legend has it, it will be passed down in my family for generations to come (exaggeration, but not much).
Hmmm. You may be right. I have owned no Makitas. I’m going by tear-down videos. AvE may have gone a bit off the rails, but he’s done some really good tear-downs of different tools, and looked at the quality of the materials, the casting, the motors, switches, and so on. He consistently was impressed by Makita’s build quality… but all of those videos are, like, 6 years old, or older.
It’d be too bad if even the “good” makers like Makita went the quantity-over-quality commercial route.
One of the things that convinced me to go Makita when choosing my “house” was that they don’t have separate high and low voltage battery systems. Dewalt, Ryobi, and the others have a 18v/20v system and a 36v/40v system. Makita has bigger tools that you plug two batteries into and by the power of math you have a 36v tool off two of regular batteries.
At least when I was looking that was a unique thing to them and seemed like a great idea.
“it’s the whole internet! somebody last week said I should get a different internet, and I’m like, I like this one! it’s got titties and ebay!” -boomers everywhere
That’s my understanding. I always understood “Great Britain” to refer to the entire island composed of England, Scotland and Wales. Maybe I’m wrong or there are certain use exceptions?
lemmyshitpost
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.