social.tchncs.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
A friendly server from Germany – which tends to attract techy people, but welcomes everybody. This is one of the oldest Mastodon instances.

Administered by:

Server stats:

3.8K
active users

#api

34 posts31 participants0 posts today

🌘 使用 TypeScript 在 Gemini API 中搭配 OpenAI 後備方案
➤ 提升應用程式的穩定性:Gemini 與 OpenAI 的無縫整合
sometechblog.com/posts/try-gem
本文介紹瞭如何在 TypeScript 中使用 Gemini API,並設定 OpenAI 作為後備方案,以應對 Gemini API 的速率限制。作者分享了透過 OpenAI 的 TS/JS 函式庫和自定義輔助函式實現此功能的具體方法,特別是針對 Gemini gemini-2.5-pro-exp-03-25 模型每分鐘僅支援 20 個請求的限制。文章提供了具體的程式碼範例,包括定義模型類型、建立 `getCompletion` 和 `getJSONCompletion` 輔助函式,以及如何使用它們進行 API 調用。
+ 這個方法真的很有用!我一直擔心 Gemini 的速率限制問題,現在有了 OpenAI 作為
#開發 #API #Gemini #OpenAI #TypeScript

sometechblog.comUse the Gemini API with OpenAI fallback in Typescript - sometechblog.comIf you want to use Gemini’s public API, but at the same time have a safe fallback in case you have exhausted the rate limits, you can use the OpenAI TS/JS library and a few helper functions. In my particular case I needed a type-safe solution for a chartmaker app with a fallback since Gemini’s gemini-2.5-pro-exp-03-25 model is restricted to 20 request/min. First, you need to define which models you want to use so that they appear as autosuggest when you use the helper functions:

Creating 21 basic email templates in the app by hand = ~30 minutes
Coding a script to create them via API = 10 minutes studying the docs, 15 minutes coding, 5 minutes testing = ~30 minutes + easy way to create more in bulk in seconds.
Hmm, which way should I choose?
#webdev #api #email

iX-Workshop: API-Design und -Entwicklung mit HTTP, REST und OpenAPI

Lernen Sie, wie man effiziente und benutzerfreundliche APIs entwickelt, HTTP- und REST-Standards anwendet und standardisierte Referenzdokumentationen erstellt.

heise.de/news/iX-Workshop-API-

heise online · iX-Workshop: API-Design und -Entwicklung mit HTTP, REST und OpenAPIBy Ilona Krause
#API#HTTP#IT
Replied in thread

@TeachrDigital @devontechnologies
@eric

Upgrade gekauft ✅
Für mich ein no-brainer. 🥰

Die ersten 50 user:innen bekamen das Upgrade kostenlos - wow! (ich bin leider mindestens Nr. 51 ;-)

Zum Test habe ich mein #Perplexity-Konto bzw. den #API-Key davon eingebunden.

Dann kann ich direkt in einem Inspector rechts mit der KI chatten. Das ist schon nice.

Man kann auch einstellen, worauf die KI Zugriff haben darf, also z.B. die Ebene „Datenbank“ ausschließen

You might know #Graylog as a #SIEM, but did you know that it can also be a fun tool for creative, low-cost experiments in a home lab? 🏠 🖥️ 👀 Jeff Darrington recently created a DIY temperature and humidity monitor using an ESP-WROOM-32 development board and a DHT22 sensor. 🌡️

Follow along as Jeff creates a lightweight #API endpoint on the ESP32, polls it regularly using Graylog’s HTTP API input, and visualizes the results in a live dashboard. 📊 🎉

Have you tried anything fun and creative lately with Graylog? Tell us about it! 👇

graylog.org/post/iot-sensor-la #GraylogLabs #logmanagement

"API keys are foundational elements for authentication, but relying solely on them is inherently a risky proposal.

Firstly, there’s the reality that API keys are not securely designed — they were never meant to be used as the sole form of authentication, and as such, they aren’t really built for the task. These keys can often be easily stolen, leaked, or, in some cases (especially if generated incrementally), outright guessed. An API key is suitable for tracking usage but is poor for security.

There is also the additional reality that keys in their default state lack some critical functionality. There’s not a lot of verification built-in for identity management, and what does exist offers very little in the way of granular access control.

Ultimately, solely relying on API keys is a mistake common with novice developers but frighteningly common even in advanced products.

Best Practices
Instead of relying heavily on API keys as a sole mechanism, combine those keys with additional approaches such as OAuth 2.0 or mTLS. Implement rigorous expiration and rotation policies to ensure that keys which are made public are only useful for a short amount of time. Consider more advanced approaches, such as IP whitelisting or device fingerprinting, to add another layer of security atop the API key process."

nordicapis.com/9-signs-youre-d

Nordic APIs · 9 Signs You're Doing API Security Wrong | Nordic APIs |API security anti-patterns are common. From overreliance on API keys to a lack of rate limiting to no encryption, we explore the top ones.

Hoe staat het ervoor met de API Design Rules van de Nederlandse overheid? Tim van der Lippe van @Logius schreef als beheerder van de standaard een blogpost met de nieuwste inzichten en ontwikkelingen.

Werk jij met API’s in het publieke domein? Blijf op de hoogte en lees de update hier 👉 developer.overheid.nl/blog/202

developer.overheid.nl · Status update API Design Rules | developer.overheid.nlOp woensdagmiddag 26 maart 2025 kwam het Kennisplatform API's bijeen om de laatste ontwikkelingen rond API's te bespreken.