API Evangelist @[email protected]

Just spotted that Cloudflare have their own open source Mastodon-compatible ActivityPub server called Wildebeest: https://github.com/cloudflare/wildebeest

Looks like public code was first shared three weeks ago

"Wildebeest runs on top Cloudflare's Supercloud, uses Workers and Pages, the D1 database to store metadata and configurations, Zero Trust Access to handle authentication and Images for media handling" - so presumably it's mainly intended as a demo app to show what can be done with their stack?

Many people ask, "What's next for the Fediverse?"

Building more infrastructure!

This means protocols, frameworks, instances, and clients.

And while we're at it, documentation as well.

But what's apparent to me is that the Fediverse will *not* be built by Big Social, but by small developers and enthusiasts that believe in its mission.

It's the Fediverse's core mission (freedom, safety, open protocols, de-centralization) that makes it captivating.

Playing around with the #Mastodon #API I tried to see what was the simplest possible Mastodon client I could write.

So far I've only implemented reading of public feeds (federated, local, and hashtags), but I found I was able to implement that in about 300 lines of JavaScript and a small amount of custom #HTML and #CSS.

To keep things simple, I stuck as closely as possible to #SemanticHTML.
https://github.com/eobrain/simplodon

#GraphQL can be a great choice for client-to-server communication, but it requires investment to maximize its potential. Netflix operates a very large, #FederatedGraphQL platform. Like any distributed system, this has some benefits but also creates additional challenges.

🎧 In this #InfoQ #podcast, Tejas Shikhare explains the pros & cons of scaling GraphQL adoption: http://bit.ly/3Xla0VX

#SoftwareArchitecture #API #Microservices

T-Mobile US 🇺🇸 announced someone abused an #API to download the personal information of 37 million subscribers.

#cybersecurity #infosec #dataleak #databreach #tmobile

https://www.theregister.com/2023/01/20/t_mobile_us_data_breach/

I do not care what you use for your backend, just socialize and collaborate around the contract for the interface.

Twitter quietly updates its developer agreement with a clause banning third-party clients, after claiming the company was enforcing "long-standing API rules" (Karissa Bell/Engadget)

https://www.engadget.com/twitter-new-developer-terms-ban-third-party-clients-211247096.html
http://www.techmeme.com/230119/p31#a230119p31

"Third-party clients don't make us any money so of course we're not allowing them" is a bold stance from the one platform that doesn't share revenue with its creators. #Twitter

#AutomatedTesting is often blocked due to some well-known issues, especially in a microservices architecture. API and service simulators can eliminate five common issues that block test automation:
➡️ Issue 1: APIs or services not yet available
➡️ Issue 2: Slow or manual processes in backend or third-party systems
➡️ Issue 3: Test data issues
➡️ Issue 4: Set up hypothetical scenarios for error scenario testing
➡️ Issue 5: Third-party API and service restrictions

Find out more in this #InfoQ article by Wojciech Bulaty: http://bit.ly/3IR3eD8

#SoftwareArchitecture #API #IntegrationTesting