@menel @patrick and #Signal despite their #FUD and #MarketingLies is a very #cebtralized, #SingleVendor & #SingleProvieer system relying on #GAFAMs and their #API|s as well as neither allowing #SelfCustody nor #SelfHosting.
Not to mention it's toxic followers that avt like cultists!
Someone already reverse-engineering the Nintendo Today app: https://github.com/ranidspace/nintendo-today-scripts
Here's a fun fact. You don't need to pay for the Twitter API if you know the post you want to retrieve.
The Twitter embedding service provides a fully inflated JSON response. It includes parents to replies, quote posts, links to media, total number of likes, retweets, replies, etc.
Here's an example of someone replying to me:
https://cdn.syndication.twimg.com/tweet-result?id=1095659600420966400&lang=en&token=abcdefg
You need to add a token to the end, but it can be any random string. No other restrictions.
Very useful for archiving.
@walkinglampshade @jrredho @fj It's basic #InfoSec, really:
Thus #Signal fails at protevting #Journalists and theor sources because they do have that data and can be #subopena'd for it if they don't already provide #BulkSurveillance & #LawfulInterception #API|s to comply with #CloudAct. (Or are you guys so naive and believe @Mer__edith will risk dying of old age in jail for non-paying users?)
And if you believe "this won't ne used/abused me because I'm from 'Murica!" and point at #ANØM as an example, then you really ignored all tze #Cyberfacism since 9/11…
@froge @forthy42 @fj to me, @signalapp being centralized and not even doing tue absolute minimum of supporting @torproject / #Tor and having at least an #OnionService as #API-Endpoint makes them #UsefulIdiots.
It's several things like that that rubvme the wrong way and that make it uncomfortable.
Garage - An open-source distributed object storage service
Does any of you know about this and also use it professionally and if so in what context and how? Honestly, I'm standing up a little.
@kubikpixel yeah, for that money they can propably bribe half the security team at #Telegram and integrate custom #Govware #Backdoors or at least get the #API keys they have for #UAE's #Telco compliance to enable automatic "#LawfulInterception"...
[#TRADESHOW] The 92nd #API #China, scheduled for May 21–23, 2025, at the #China #Import and #Export #Fair Complex in #Guangzhou, is the premier #trade #show for the #pharmaceutical and #biopharmaceutical #industries. As part of a larger #event alongside the 90th #PHARMCHINA and the 2025 #NHNE, this comprehensive #exhibition will feature 1,200 #exhibitors, welcome 30,000 visitors, and span over 70,000 square meters. https://cnbusinessforum.com/event/92nd-api-china-2025/
@expertenkommision_cyberunfall @dideldum @leachimus @EUCommission @BaFin @ecb
Dass dies technisch möglich ist - inkl. Einhaltung von #Identifikationspflichten (#KYC) und #Geldwäscheprävention (#AML) beweisen Zahlungsdienstleister wie #NowPayments regelmäßig!
Und natürlich nicht mit irgendwelchem #Blockchain-Müll, dafür #dezentral, #P2P mit Förderation (vgl. Fediverse)...
Die Technologien dazu existieren...
Do you know the difference between #Microsoft #Azure #API #documentation and the #Necronomicon?
None. Nobody could read them and keep their sanity.
@kuketzblog das größte Problem si d #Zahlungsdienstleister.
Merke: rein regionale oder gar nationale Lösungen sind keine Alternative zum #VISA / #MasterCard / PayPal - #Tripol und sowohl #Stripe als auch #Klarna sind nicht wirklich konkirrenzfähig.
Eher werden wir #Monero als #Zahlungsmittel beim Durchbruch in den globalen Mainstream sehen!
Android: Vulkan predefinito, ADPF ottimizzato e giochi PC in arrivo
#ADPF #Android #API #DiscoElysium #DREDGE #Gaming #Google #GooglePlayConsole #Grafica #MediaTek #MobileGaming #Notizie #Novità #PCGaming #Porting #Prestazioni #Sviluppatori #TechNews #Tecnologia #Unity #Vulkan
https://www.ceotech.it/android-vulkan-predefinito-adpf-ottimizzato-e-giochi-pc-in-arrivo/
@hn50 this sounds geckibg #cursed.
Discover the new OpenAIRE Graph #API!
Join our webinar to explore its powerful new features for #bibliometric analysis, #research discovery, and #OpenScience monitoring. Learn how it streamlines access to the #OpenAIREGraph’s rich research data, see real-world applications, and get your questions answered in our live Q&A!
Register now! https://tinyurl.com/45zenwr
»KI-Trainingsdaten – Tausende gültiger API-Keys in gecrawlten #Web-Daten entdeckt:
Bei der Analyse eines frei verfügbaren #Archiv's mit rund 400 TBytes an #Website #Daten haben Forscher fast 12.000 gültige #APIKeys und Passwörter gefunden«
Nein!!! Ob dies nun die #KI (Automatisierung) oder/und "#Hacker" nun knacken spielt keine Rolle. #API-Keys wie #Passwort'er speichert man nicht im #Code als #Klartext direkt. Dies ist absolut dilettantisch und macht mensch nicht.
I’ve recently taken a closer look at the #Foursquare #API (updating the long unmaintained Platypush plugin, details on why coming soon).
At first their new API versioning schema seemed a bit confusing (why would anyone use arbitrary YYYYMMDD strings as versions?), but a closer look at how they implemented it revealed a quite clever design decision:
Versioning is controlled by the
vparameter, which is a date that represents the “version” of the API for which you expect from Foursquare. It is designed to give developers the freedom to adapt to Foursquare API changes on their own schedule. The value of the v parameter is a date in YYYYMMDD format that lets you tell us “I’m prepared for API changes up to this date.”
You know when you look at an engineering decision that is so elegant and obvious that you think “damn, how could nobody think of this before?”
Nearly two decades spent managing /v1, /v2, /v2.5, /v2.almost3, /v3, managing migrations and deprecations, documenting breaking changes, introducing exponentially thicker layers of schemas and converters, and the obvious solution was just there under our nose.
Why don’t you just start with defining the base schemas of your API objects at the time of their first release, and then every time you add, modify or delete a field, or change some return type, or add a value to an enum, you just version the change with a timestamp?
Let the developer say “I understand the language that your API spoke 3 months ago”, and you just dynamically create the schemas, GraphQL or ORM snippets to parse requests and responses as of that date.
No more breaking changes. No more forced migrations. No more boilerplate to explicitly convert payloads across different API versions.
You construct the response by first applying the base schema, and then gradually patching it - just like you would do with a git rebase, or an ORM migration tool.
A downside may probably be that you can never really delete a column from the db if it was ever used by any version of your API.
And a challenge may also be to adapt tools like #OpenAPI / #Swagger that were designed around static schemas to also work with “dynamically versioned” selections.
But to me the problems it solves far outweight the downsides.
@buyeuropean @european_alternatives #WhatsMissing:
#Europeam #Alternative to #PayPal, #Stripe #VISA & #MasterCard that is as easily accepted worldwide!
I'm disappointed to learn that #Suunto is just as bad with its #API access as #Garmin. :(
"We currently don't offer the API access for personal use. We are reviewing the applicants based on for example the fit to our brand [...]"
Is there a brand with decent #running watch and open enough data policies?
Werden Sie auch öfter gefragt, was eine API ist?
Eine API (Application Programming Interface) verbindet Softwaresysteme und ermöglicht den Datenaustausch. Sie definiert, wie Anwendungen miteinander kommunizieren und erleichtert Integrationen.
Bei mailbox.org automatisiert die API z. B. die Benutzerverwaltung für Geschäftskunden.
Wir haben es simpel in einem Vergleich zusammengefasst. Haben Sie auch ein Beispiel, das jeder versteht?
