TINYSPARQL-XDG-POR(1)
β¨ NAME β¨
okay so this is tinysparql-xdg-portal-3 β the Portal to Tracker endpoints, bestie π
and yes we're diving into the TinySPARQL manual rn, buckle up π
π¦ SYNOPSIS π¦
tinysparql-xdg-portal-3 [--version | -v]
that's it. that's the whole vibe check π short and iconic π
π₯ DESCRIPTION π₯
so this little daemon right here lets you access TinySPARQL endpoints in a controlled manner β like, it's not just handing out keys to the whole kingdom, it's giving bouncer-at-the-club energy π
by default, access to every single service is disallowed. nothing. nope. zero. zilch π the services only get let in if you whitelist them through some extra policy in the .flatpak-info file β¨
and when you do whitelist a service, the policy can define:
- specific graph names to allow access to π
- the
defaultkeyword β which allows access to the default unnamed graph π - the
*keyword β which allows access to all graphs π (iconic, honestly)
π§ CONFIGURATION π§
when it's interacting with sandboxed clients, the service expects this exact format in the .flatpak-info file π
[Policy Tracker3]
dbus:org.example.SparqlEndpoint1=graphA;graphB;default
dbus:org.example.SparqlEndpoint2=*
so what does that actually do, you ask? π€ it allows access to the endpoints behind the org.example.SparqlEndpoint1 and org.example.SparqlEndpoint2 bus names πβ¨ but listen carefully:
- on the first endpoint, only to the
graphAandgraphBgraph IRIs and the default unnamed graph π - on the second endpoint, to all graphs πΈ
ngl that's a pretty clean policy, periodt π
you can set this policy when building or running the sandboxed application through the --add-policy option π§ it can be set via finish-args in the flatpak manifest, specified along the build chain in flatpak-build-finish(1), or modified at start time with flatpak-run(1) β for example:
$ flatpak run \
--add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=graphA \
--add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=graphB \
--add-policy=Tracker3.dbus:org.example.SparqlEndpoint1=default \
--add-policy=Tracker3.dbus:org.example.SparqlEndpoint2=* \
org.freedesktop.ExampleSandbox
look at that manifest go π it's giving organizational queen π
β οΈ real talk: those--add-policyvalues have to match the.flatpak-infoformat exactly β no improvising, no freestyle, bestie π
π SEE ALSO π
go read these next, iykwyk π«Ά
and that's the whole page, bestie!! π this was TinySPARQL manual 3.12.0, dated 09/15/2026 β screenshot it, cite it, live by it, mwah ππΈ
π¦ where this page comes from
- arch rolling: tinysparql 3.12.0-1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms