# Websocket Squid endpoint mandatory for cursor vs offset scrolling in data?

**URL:** https://forum.duniter.org/t/websocket-squid-endpoint-mandatory-for-cursor-vs-offset-scrolling-in-data/12942
**Category:** Indexers
**Created:** [19 February 2025 19:26 UTC](https://forum.duniter.org/t/websocket-squid-endpoint-mandatory-for-cursor-vs-offset-scrolling-in-data/12942 "2025-02-19T19:26:35Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![vit](https://forum.duniter.org/user_avatar/forum.duniter.org/vit/32/2775_2.png) [@vit](https://forum.duniter.org/u/vit)
#### Post date: [19 February 2025 19:26 UTC](https://forum.duniter.org/t/websocket-squid-endpoint-mandatory-for-cursor-vs-offset-scrolling-in-data/12942/1 "2025-02-19T19:26:35Z")

</div>

I see in the graphql schema that only the StreamXXX objects get a cursor to navigate in data lists.

Those objects are only available in subscription, so using a long lasting connection to the server.

As I see no websocket endpoints exposed publicly in the official list, I wander if we should be exposing and publish them to allow the use of StreamXXX objects.

A Subcription on websocket allow to make query and mutation as in http.

But http endpoints can not do cursor navigation nor subscription…

([appollo javascript client can do this, using http multipart protocol](https://www.apollographql.com/docs/react/data/subscriptions#http)))

What is the best practice to handle navigation in graphql for the history of transactions ? What Cesium2 and Gecko are using ?

---

<div class="post-metadata">

### Author: ![HugoTrentesaux](https://forum.duniter.org/user_avatar/forum.duniter.org/hugotrentesaux/32/6396_2.png) [@HugoTrentesaux](https://forum.duniter.org/u/HugoTrentesaux)
#### Post date: [5 March 2025 20:20 UTC](https://forum.duniter.org/t/websocket-squid-endpoint-mandatory-for-cursor-vs-offset-scrolling-in-data/12942/2 "2025-03-05T20:20:08Z")

</div>

> [@vit](#):
>
> As I see no websocket endpoints exposed publicly

Some endpoints are available in websocket though. Look at duniter panel for examples (repo [Hugo Trentesaux / duniter-vue · GitLab](https://git.duniter.org/HugoTrentesaux/duniter-vue)). I am using websocket to display latest indexed block in live.

This is the reason of the “upgrade” lines in squid nginx config : [Duniter | Duniter squid](https://duniter.org/wiki/duniter-v2/indexers/duniter-squid/).
