Recent searches

No recent searches

Search options

Only available when logged in.
mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

mastodon.ie: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#graphql

1 post1 participant0 posts today
Brian Clozel

Here it is, the first Spring for #GraphQL 2.0 milestone!

This new major version builds on top of Spring Framework 7.0 and ships new features like JSPecify nullability support, flexible binding for input types, optional input types for request variables, Multiple queries with the DGS client.

We've started working on the second milestone and we can't wait to get your feedback.

spring.io/blog/2025/07/22/spri

Spring for GraphQL 2.0.0-M1 releasedSpring for GraphQL 2.0.0-M1 releasedLevel up your Java code and explore what Spring can do for you.
Peter Sanchez

I haven't had a ton of time lately but we just released a new version of LinkTaco. Lots of bug fixes but the big piece is the Pinboard API -> GraphQL bridge. You can now use all your existing Pinboard tools or integrations directly with LinkTaco.

https://linktaco.com/blog/new-linktaco-release-0.5.0.html

https://lists.code.netlandish.com/~netlandish/links-discuss/%3C20250719074538.OEOCFANOYMWV@thinkpad%3E

#pinboard#bookmarks#linktaco
Richard Hughes

Okay, I'm at my wits end. I'm doing a #Cloudflare #GraphQL request locally from python and it works really well. Deploy the *exact* same code, with the *exact* same headers, query and variables to ECS on AWS and it no longer works.

The query httpRequestsAdaptiveGroups returns the correct integer count locally, and returns an empty array when running on AWS. Does anyone have any suggestions on things that might affect this? Thanks!

洪 民憙 (Hong Minhee)

We're migrating Hackers' Pub to a pretty unconventional tech stack, and I'm honestly excited about it!

Thanks to my friend @xiniha, we're diving into #Solid, #SolidStart, #Pothos, #GraphQL, and #Relay. In a world dominated by Next.js and React, this feels refreshingly different. And yes, we're sticking with #Deno instead of Node.js too.

Some might call it contrarian, but I like to think of it as exploring what's possible beyond the mainstream. Sometimes the road less traveled leads to interesting places.

hackers.pubHackers' PubHackers' Pubは、ソフトウェアエンジニアが知識と経験を共有する場所です。また、ActivityPubに対応したソーシャルネットワークでもあり、フェディバース（fediverse）で気に入ったハッカーをフォローして、最新のコンテンツをフィードで受け取ることができます。
Martin D.

1/1 End of last year @redwoodjs removed their funding of their graphql framewor, put it im maintenance ans create a new one. It felt like a redwood tree fell on our foot. Redfoot, we decide, will be the untangled underlying fastify framework. It took us half a year, but we managed it. Redwood was a great help, but we wont look back. The new framework gives us some advantages:

#nodejs#fastify#redwoodjs
洪 民憙 (Hong Minhee)

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.

What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?

The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.

#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.

Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?

Curious what others think about this approach.

graphql.orgGraphQL | A query language for your API
#fedidev
*
HoldMyType

exposing a query language to untrusted clients increases the attack surface of the application. Nevertheless, the variety of attacks to consider was even broader than I imagined, and mitigating them is quite a burden.
> if a field resolver hits an external data source such as a DB or HTTP API, and it is nested in a list containing N items, it will do those calls N times.
in REST, we can generally hoist nested N+1 queries up to the controller, which I think is a pattern much easier to wrap your head around:
#graphql
bessey.dev/blog/2024/05/24/why

bessey.devWhy, after 6 years, I’m over GraphQLGraphQL is an incredible piece of technology that has captured a lot of mindshare since I first started slinging it in production in 2018. You won’t have to ...
TrendingLive feeds
About