Man I feel old, back in my day we weren't allowed to use anything more powerful than a TI83 on most exams and the answers were on scantrons or paper due to fears of using the internet to cheat. These days with GPT I'm surprised that's not even more of a concern.
Open source software might not directly be used in the workplace but if someone can't adapt from LibreOffice to MS Office they won't be able to adapt to MS Office updates either. It's been decades since productivity software had significantly different feature sets for most users. That weird legacy Excel formula the Finance Department uses will need training no matter how many years of Office experience a new hire has.
Thanks for posting this, really highlights all the hard work, and congrats @nutomic!
ASFAIK Signal doesn't support RCS, only Signal protocol, after they dropped SMS.
Why not switch to something not owned by Facebook like Signal (or something on an open protocol like Element)?
Why should anyone care about RCS? The trend has been to get everything into data instead of carrier owned services for two decades now, we don't need another SMS (it will likely always be a fallback). What we should move onto is a carrier and device type angnostic universal standard protocol over TCP / QUIC like XMPP or Matrix, with SMS as the backup.
When you get a phone you can get an phone system account and a telephone number already. Modern apps in the Google ecosystem should already recognize you are already signed in with Google and sync your contacts. Since almost everyone is already in the Google ecosystem, if Google supported it they could have extended their XMPP implementation in Hangouts to allow messaging directly via XMPP to those contacts and SMS for anyone not yet in the system (similar to how Signal did, Apple does, and Google does now with RCS). Unlike Apple, since its just XMPP, users can still add friends and be added by friends on other XMPP servers (ex. their ISPs, their own, or a third party). They could have supported or jumpstarted a new very simple open source alternative app for that portion for AOSP if the EU complained. Eventually Carriers could have supported passthroughs for those still on feature phones and other users of SMS to use the number@carrier accounts to hit XMPP users with generated SMS numbers for non-SMS users (pushed either by business necessity or part of a government / teleco org like GSMA staged removal of SMS and telephone numbers). It's all data at the end of the day.
Instead, they developed a whole new protocol to fluff the telecos and keep the now badly managed telephone number system even more necessary allowing spammers and allow the problems of legacy SMS to continue.
Apple, Google, and Samsung should all be shamed for not supporting fully open protocols and necessitating dependency on user harming stacks.
Can CSAM distributors use it as a test suite for workarounds?
Edit: first draft was too declarative where I meant to pose the thought as a question.
A giant electric "luxury" truck is still a giant "luxury" truck. Buying one over the other is like buying a cruelty free synthetic beaver cap over a cap made from an actual beaver. Yes it probably is better, but you are still wearing an ass on your head.
It's 2023, most people live in urbanized areas where a truck is similarly ridiculous, especially the modern "luxury" models. Those that actually use their vehicles for hauling things at a farm want real work trucks and tractors (regardless of engine type) with lower and longer beds.
Aren't these archives protected explicitly under several points in US Title 17 Section 108? https://www.copyright.gov/title17/92chap1.html#108
This shouldn't be this funny.
If you are an instance owner, you can use this tool https://github.com/rileynull/RedditLemmyImporter . However, is all of your sub's old content really that valuable to bring over? Why not just create the new community, copy the old sidebar info / rules, make a sticky with links to top posts in the old sub, let a few people know (in a way that doesn't violate the sub's rules) and let people migrate naturally?
On the microblogging side of the fedi, "fedihire" and "jobalert" hashtags seem to be frequently used for job postings, and "getfedihired" and "jobsearch" for those posting that they are looking.