• 0 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle
  • ugh I remember my last straw on Facebook was my high school alumni group becoming a shit-storm of sea-lioning and a couple folks blocking people and also spamming nostalgia-posts to drown out and push down more serious discussion. A high school famous for it’s science-focus but alas, the older (but not much older) folks were openly commenting about that black-people-crime-percentage “statistic” and gay people.



  • This post is posed as the next big step in internet pricing, not something necessarily happening today.

    Today, it’s not standard procedure outside of some specific segments (that I know of, maybe airfare? But the data fed in is more limited) but tapping into the vast amounts of data we leak through the services we use is far too big of a gold mine for companies to overlook researching and tapping into. There’s a lot of things that need to happen (who supplies data? Google is the hypothetical here but what’s their price? etc.) but it’s absolutely feasible at scale.





  • Oh yep, not the same person here but price varies widely.

    In my apartment complex, we have Blink network EV chargers at $0.03/kWh which is a crazy price. The complex next door’s Blink chargers charges $0.50ish/kWh (both of those are Level 2) and our apartment rates (for the hypothetical out-the-window Level 1 charging) is somewhere $0.14-0.18/kWh.

    DC fast charging for trips will likely will charge closer to that $0.50/kWh mark depending on the location and will be a problem for those who don’t have lower-cost charging at home.

    That’s a big range for “home” (but still commercial) charging and depending on the efficiency of the vehicle, the cost per mile will vary. The range will likely be around 2 mi/kWh to 4 mi/kWh.










  • We don’t know any details. Google is trumpeting a success and indicating a willingness to assist but it doesn’t really tell us much of what it will look like. Apple is committing to RCS, the industry standard as it is (and I assume will be as I hope it breathes new life into the standard…) and not Google’s current RCS + proprietary bits implementation.

    When MS created a Windows Phone YouTube app, Google blocked it with requirements that were either arbitrary (it needs to be HTML5 for example despite iOS and Android apps being native) or impossible to meet. (requiring specific access that Google would not provide)

    So while Google framed it as “Microsoft just needs to do X, Y, Z and it’ll be all good!” - sounds good but it intentionally made said requirements impractical or impossible to complete.

    Since Google’s been conflating their RCS implementation with RCS the standard, I think it’ll be a funny (if unfortunate) monkey’s-paw result if Apple’s adopts RCS completely as the backup to iMessage but continued carrier and Google implementation fumbling results in no change and the iPhone having to resort to SMS/MMS anyway.

    (see: a while back when AT&T’s RCS could only be used between a couple AT&T Samsung phones - but I do hope it’s different this time, I got a group chat I rather take off Instagram.)




  • I don’t think Apple will need (or want) to do anything “malicious” since Apple is implementing RCS the standard which between the carriers and Google mismanaging and fragmenting messaging for years - see: X carrier phones can only send RCS messages to X carrier phones, Google’s implementation is not the RCS standard and is partially proprietary - it’ll take a while to get S.S. RCS, The Standard steered right.

    I hope Apple’s involvement is ironically a kick in the butt to get everyone on the same page and get a standard rather than the current “Google iMessage” solution.

    Edit: Typo