13 Jun
2024
13 Jun
'24
1:26 p.m.
Good day Jérôme!
Thank you for joining to this thread and sharing insights!
Please pardon me for not posting to your post ID.
Your message was not delivered to my email.
Hi Schimon,
can you tell use more about your end goal (end-user use-case)?
Is it something for social sharing (e.g. I publish a book I'm
reading, I want to allow comments, reactions, repeat, etc.) or is it
something like having a collection of books/citation, etc?
It is more similar to the latter: Storing of bibliographic references
on PubSub nodes and also publishing and sharing (restricted to
authorized contacts) of those references.
Bibliography on PubSub:
* Storing (privately);
* Publishing (publicly);
* Sharing (restrictedly).
I am currently focued on systems which are commonly referred as
"bookmark managers" or "links directories".
Example: https://codeberg.org/bouncepaw/betula/issues/9
In the later case, you can have a look at XEP-0346:
Form Discovery
and Publishing, which is a way to share Data Form over Pubsub, I'm
already using it to share various kind of things (TODO list, shopping
list, tickets, merge requests), and I have plans for books too.
It would actually great to have something usable with both, as both
use cases are legitimate, in which case it could be describing the
data to share and the fields to use in a Data Form, which could then
be used either as attachment in a blog item (e.g. with XEP-0470), or
directly with XEP-0346.
This appears to be a wonderful idea!
I will strive to make BukuBot utilizable with PubSub in both fashions
you have described.
Best,
Goffi
P.S. Please read the following notes.
Important notes to understand my thoughts and approach to the subject:
1. I refer to Bibliogrphy as a list of anything textual, not only a
reference of articles, books, and other sorts of publications.
2. To me, bibliographic references are mistakenly known as "Bookmarks",
"Favorites" (terms used by HTML browsers), "Social Bookmarking
Systems" (term used by HTML based systems) etc. and those terms
cause for confusion to many people who consequently and
inadvertently neglect the potential of posessing (i.e. holding and
owning) a personal bibliography.
3. I have a different approach to what some attempt to indoctrinate the
public, and I refer to bookmarks, contacts and even magnet links
(ed2k, gnutella, torrents) etc. as *bibliography*.
4. To store my contacts, I use a directory with vCards (each contact
has its own vCard file.
See https://codeberg.org/magdesign/sxmo-userscripts/issues/1
5. Recently, I have been using my bookmarks manager, buku, to store
also contacts and magnet links, so I, in fact, use a software (buku),
which is originally intended to be a "bookmark manager" (for HTTP
links), as a general system for everything which is textual (i.e.
bookmarks, contacts (irc, telephony, voip, xmpp), gemini, gopher,
magnet links, ssh etc.), albeit buku is not intended for storing
this information, it does that task well, and even better than any
solution I have been striving to find.
See: https://github.com/jarun/buku
6. In a similar context if not in the same context, YaCy search engine,
which, like buku, is a links directory system has began as a
"bookmarks manager".
See: https://yacy.net/
7. I understand that a "search engine", so called (what does "engine"
mean in this context?) is really a jargon which some of the public
has been indoctrinated to use, and is actually a links directory - of
course it has a larger caching system for text to look up, but it is
nevertheless a database of textual links directory of publications
(bibliography), just like the one that some HTML browsers have.
8. To me, buku is a static bibliography manager, Falkon is an HTML
browser and a static bibliography manager, Liferea (Syndicated Feed
Reader) is a dynamic bibliography manager, YaCy, as it also supports
Syndicated Feeds, is both a static and a dynamic bibliography
manager.
9. XMPP PubSub is all of the above.