OpenAI Developers (@OpenAIDevs)
AI Gateway가 OpenResponses API에 day 0 지원을 제공합니다. 하나의 API로 다중 제공자 AI 호출을 관리하고, AI Gateway를 통해 제공자 간 요청 라우팅이 가능하며 모델 문자열 변경으로 제공자를 전환할 수 있도록 지원합니다.
OpenAI Developers (@OpenAIDevs)
AI Gateway가 OpenResponses API에 day 0 지원을 제공합니다. 하나의 API로 다중 제공자 AI 호출을 관리하고, AI Gateway를 통해 제공자 간 요청 라우팅이 가능하며 모델 문자열 변경으로 제공자를 전환할 수 있도록 지원합니다.
@psoutham @Lazarou nodds in agreement…
We need an "anti-#Thiel" strategy (anti-#monopolization) strategy that empowers #OpenSource, #OpenStandards and only accepts #MultiVendor & #MultiProvider solutions that are #FLOSS as well as #SelfHosting capable (both in terms of "reproduceable builds" & auditable code as well as "you can set it ou yourself" & no bullshit setup)…
Instead #incentives must be set in terms of i.e. #EU-wide public funds for #DigitalInfrastructure that #rewards FLOSS creation and enshures the #maintenance of said projects.
@innocence well, they switched to an #AssholeLicensing model, maing the reference implementation now a worse decision and put the Matrix Protocol in danger.
And yes #AGPLv3 is an asshole license as it is inherently incompatible with a shitton of #IP laws and thus (oftentimes) cannot.be complied with.
@soop @Li @meluzzy @tauon bonus points if said corpo is subject to laws that mandate them to integrate #Govware #Backdoors and hand over data...
See #CloudAct: https://en.wikipedia.org/wiki/CLOUD_Act
This is why #IRC & #XMPP outlived #ICQ & #Skype and why #Mumble & #JitsiMeet will outlive #discord & #GoogleMeet!
Because physical SIMs, like any "cryptographic chipcard" (i.e. @nitrokey ) did all that fancy public/private crypto on silicon and unless that was compromizeable (which AFAICT always necessistated physical access to the #SIM, espechally in pre-#OMAPI devices) the SIM wasn't 'cloneable' and the weakest link always had been the #MNO /.#MVNO issueing (may it be through #SocialHacking employees into #SimSwapping or LEAs showng up with a warrant and demanding "#LawfulInterception"):
Add to that the regression in flexibility:
Unlike a #SimCard which was designed as a vendor-independent, #MultiVendor, #MultiProvider, device agnostic unit to facilitate the the #authentification and #encryption in #GSM (and successor standards), #eSIMs act to restrict #DeviceFreedom and #ConsumerChoice, which with shit like #KYC per #IMEI (i.e. #Turkey demands it after 90 days of roaming per year) und #lMEI-based #Allowlisting (see #Australia's shitty #VoLTE + #2G & #3G shutdown!) are just acts to clamp down on #privacy and #security.
"[…] [Technologies] must always be evaluated for their ability to oppress. […]
And now you know why I consider a #smartphone with eSIM instead of two SIM slots not as a real #DualSIM device because it restricts my ability to freely move devices.
Thus #Impersonation attacks in GSM-based networks are easier than ever before which in the age of more skilled than ever #Cybercriminals and #Cyberterrorists (i.e. #NSA & #Roskomnadnozr) puts espechally the average #TechIlliterate User at risk.
And then think about those who don't have privilegued access to protection by their government, but rather "privilegued access" to prosecution by the state because their very existance is criminalized...
The only advantage eSIMs broight in contrast is 'logistical' convenience because it's mostly a #QRcode and that's just a way to avoid typos on a cryptic #LocalProfileAgent link.
@action_jay everything that isn't a fully #OpenSource'd #OpenStandard with #MultiVendor & #MultiProvider support.
That's why @delta (#PGP/MIME) & @monocles / @gajim (#XMPP+#OMEMO) are superior to @signalapp , because that can be easily cracked down on due to #CloudAct, whereas truly #decentralized systems have #SelfCustody so they can't be taken down effectively.
@threemaapp don't buy #proprietary #SingleVendor and/or #SingleProvider either!
@ckrypto if@signalapp@mastodon.world wasn't complying with #CloudAct, @Mer__edith would be in jail.
Not to mention even if Signal keeps their "#OpenSource" code updated - which is doubtful, NOONE can actually #verify that it's the code you actually use - regardless if #backend / #Server or #client / #App!
Also if Signal was designed for #security, it would've been #decentralized as #XMPP+#OMEMO and not demand #PII like #PhoneNumbers which oftentimes cannot be obtained anonymously in many juristictions at all!
By comparison, @delta doesn't require any PII, only an #eMail account, and @monocles isn't a #VCmoneyBurningParty but sustainable due to #subscription and they don't even require any personal details for #payment: #CashByMail and #Monero are accepted.
Again: It's Signal alone who have to evidence they are trustworthy, and all I get are "#TrustMeBro!" replies, which means they are not to be trusted.
Whereas with #XMPP I can completely setup my own server and client, even build my own if I don't trust anyone else and pay someone to audit the code.
Whereas with XMPP & PGP/MIME #eMail I can layer @torproject / #Tor over it, make it an #OnionService and keep that thing under my bed with a literal killswitch...
@notjustbikes precisely!
Only #OpenSource & #OpenStandards can yield #MultiVendor & #MultiProvider systems necessary to prevent #monopolies and #oligopolies and enshure #ITsec, #InfoSec, #OpSec & #ComSec, thus being able to comply with #NatSec & #IntlSec demands.
Guess why #NORAD runs #BusyBox / #Linux?
@delta also the whole "BuT #mEtAdAtA?" Discussion is completely blown out of proportions by #Signal fanboys.
In fact, I'm convinced someone already made a #delta #chat #server as an #OnionService over @torproject / #Tor just for the lulz.
Not that this is something the average user encounters, but it is a big bonus for larger organizations!