Blasta/blasta/assets/template/questions.xhtml

384 lines
17 KiB
HTML
Raw Permalink Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="color-scheme" content="dark light" />
<title>Blasta / questions</title>
<link rel="shortcut icon" href="/graphic/blasta.svg"/>
<link rel='icon' type='image/svg+xml' href='/graphic/blasta.svg'/>
<link rel='stylesheet' type='text/css' media='screen' href='/stylesheet/stylesheet.css'/>
<script src="/script/regulator.js" />
</head>
<body>
<div id="container">
<div id="header" class="row">
<h1>
<img src="/graphic/blasta.svg"/>
&nbsp;
<a href="/">
Blasta
</a>
/
<a href="/help">
help
</a>
/ questions
</h1>
<dl id="navigation">
<dd>
<a href="/">
<img alt="Main"
src="/graphic/blasta.svg"/>
</a>
</dd>
{% if jabber_id %}
<dd>
<a href="/save">Add</a>
</dd>
<dd>
<a href="/jid">Public</a>
</dd>
<dd>
<a href="/private">Private</a>
</dd>
<dd>
<a href="/read">Read</a>
</dd>
{% endif %}
<dd>
<a href="/search{% if jabber_id %}/jid/{{jabber_id}}{% endif %}">Search</a>
</dd>
<dd>
<a href="/popular">Popular</a>
</dd>
<dd>
<a href="/recent">Recent</a>
</dd>
<dd>
{% if jabber_id %}
<a href="/disconnect">Disconnect</a>
{% else %}
<a href="/connect">Connect</a>
{% endif %}
</dd>
</dl>
</div>
<div id="main" class="row">
<div id="content">
<h2>
<img alt="💡" src="/graphic/xmpp.svg" width="18" height="18"/>
&nbsp;
PubSub bookmarks
</h2>
<p>
» Queries about Blasta.
</p>
<h3>
Questions
</h3>
<p>
This document enumerates questions that were referred to the
project Blasta.
</p>
<h4 id="what-is-jid">
What is JID and what does it mean?
</h4>
<p>
JID is an abbreviation of Jabber ID.
</p>
<p>
A Jabber ID is the address of your XMPP account with which
Blasta identifies you.
</p>
<h4 id="what-is-instance-keyword">
What is the instance:keyword method?
</h4>
<p>
The method instance:keyword is a practice which improves
bookmarks organizing, archiving, filtering and searching, as
it narrows the context of a given bookmark, and therefore
improves <a href="/help/about/folksonomy">Folksonomy</a>
practices.
</p>
<p>
Suppose you have two bookmarks; one is related to
maintenance and removal of rust, while the other is related
to the computer language which is called rust.
</p>
<p>
To make the tagging more efficient for you and others, the
bookmark which is related to maintenance be tagged with
"rust" and "tutorial:maintenance", while the bookmark which
is related to computer language rust be tagged with
"code:rust".
</p>
<h4 id="why-blasta">
Why did you create Blasta?
</h4>
<p>
We have created Blasta out of necessity.
</p>
<p>
We have felt that there are no viable solutions that would
provide a sensible management of URis, and also a mean to
share URIs.
</p>
<p>
We are well aware of project YaCy which indeed provides
exactly what we desire, yet, the interface that is provided
by YaCy does not fulfill the interface which we have
determined to be fit for the cause, and which would be fit
with certain functionalities that we deemed to be necessary.
</p>
<p>
We also wanted a system that would be independent and in
current sync, and we have decided that XMPP is the perfect
platform for this task.
</p>
<p>
Hence, we have created Blasta, which is a combination of
YaCy and Shaarli, and is built on top of XMPP.
</p>
<h4 id="why-free">
Why do you provide Blasta for free?
</h4>
<p>
While we want to make profit, and feed our wives and
children, we are aware that we must be providing the Blasta
system for free, because this is a matter of urgency; and
</p>
<p>
Because some people do bad things, such as attempting to
centralize the internet, and revoke privacy, which is
crucial; and
</p>
<p> We can not afford to have another centralized service which
later becomes clandestinely subdued to thugs from government
or intelligence, which is the worst of all circumstances.
</p>
<h4 id="perspective">
What is your perspective?
</h4>
<p>
Our perspective is that people should be living for the sake
of eternity, which is what we are doing by creating and
distributing Blasta.
</p>
<p>
As conveyed in verse 77 of Hávamál
</p>
<p class="quote" title="“Deyr fé, deyja frændr, deyr sjalfr it sama, ek veit einn, at aldrei deyr: dómr um dauðan hvern.”">
“Kinsmen die, and cattle die and so must one die oneself;
<br/>
But there is one thing I know which never dies,
<br/>
and that is the fame of a dead man deeds.”
<br/>
― Hávamál: Sayings of the High One
</p>
<p>
The German philosopher Arthur Schopenhauer expressed
essentially the same idea when he said, that
</p>
<p class="quote">
“The very most any man can hope for:
<br/>
Is a heroic passage through life.”
<br/>
― Arthur Schopenhauer
</p>
<p>
To explain it in other words:
</p>
<p>
Greatness, rather than happiness, is
<span class="instances-degree-first">
the mark of a good life
</span>
&#8203;
.
</p>
<p>
Live for the sake of eternity, for the past, and towards the
future.
</p>
<h4 id="why-xmpp">
Why did you choose XMPP as a platform?
</h4>
<p>
The <a href="/help/about/xmpp">XMPP</a> platform (which is
also known as Jabber), is a reputable and a strong
telecommunication platform which almost every intelligence
and militant agency on the world is making use of as a
premier telecommunication mean.
</p>
<p>
Because we did not want to use databases, which sometimes
are too complicated for most of the people who are
interested in sharing links publicly and privately, we have
determined that XMPP would be the best choice for this task.
</p>
<p>
XMPP was chosen as a platform, because it is a standard and
it is extensible; it has all the features that are necessary
to integrate other standardised mechanisms to store data
which does not necessarily has to require a database (e.g.
SQLite); XMPP provides exactly that, whether we want to make
use of Atom Syndication Format and even JSON, if at all
needed.
</p>
<p>
So we chose the specification XEP-0060:
<a href="/help/about/xmpp/pubsub">Publish-Subscribe</a>
(PubSub) as a base mechanism for a data storage platform.
</p>
<p>
In addition to it, XMPP offers a robust and stable mechanism
of storing of contents, on both XMPP and HTTP, and more, or
even most, importantly, the PubSub mechanism of XMPP is
truely private and is truely owned by the account owner,
which is also a major advantage to Blasta, not only for the
sake of privacy and data integrity, but also for an
immediate recovery of the bookmarks sharing system, if the
Blasta database would be to diappear or should be
restructured anew.
</p>
<p>
Use XMPP. Spread XMPP. Be XMPP.
</p>
<h4 id="other-platforms">
What platform would you choose if not XMPP?
</h4>
<p>
If we were to choose another platfom, it probably would have
been DeltaChat (SMTP and IMAP), Nostr or Session.
</p>
<h4>
Why did you decide to make Blasta open source?
</h4>
<p>
One of the main reasons is for freedom to thrive.
</p>
<p>
We are worried due to various of PsyOps that are being
conducted by governments, military and intelligence
agencies, and we realize that most of their success relies
on the centralization of information hubs; and
</p>
<p>
We are further worried of the awful measures that are being
dictated by HTML browser vendors, who distort the original
intentions and expectations for the internet, that were
presented to the public during the 90's, and instead these
vendors are
<a href="https://openrss.org/blog/browsers-should-bring-back-the-rss-button">
conspiring</a> to make people to forget about the existance
of crucial technologies such as
<a href="https://camendesign.com/blog/rss_is_dying">
syndication</a> and XSLT, and they are also committing
crimes against people, and the worst of all crimes is of
attempting to revoke the privacy of people.
</p>
<p>
Hence, we have decided that it is crucial to make a resource
sharing platform to utilize standards that can be utilized
outside of browsers, and
</p>
<p>
We have further decided to make Blasta available in an open
source form, that would allow public examining and auditing
of the mechanism that Blasta offers, including
<a href="/help/about/philosophy#trust">gaining the trust of
people</a> by showcasing that the data is truely private,
and that the data is truely owned by the people, and that
the data is backed by true standards.
</p>
<p class="quote">
“No reason to explain this. It is absolutely insane to
use a software to browse the internet of which source
code is not publicly auditable.”
<a href="https://lukesmith.xyz/articles/every-web-browser-absolutely-sucks/#free-and-open-source-software">
Luke Smith
</a>
</p>
<h4 id="logic">
Does Blasta deploy ECMAScript (JavaScript)
</h4>
<p>
Yes. Blasta utilizes ECMAScript in order to confine the
client version activity to itself. This will be changed in
near future, once pywebview will have a more extensive
support for intercepting HTTP requests.
</p>
<!-- p>
Blasta does not make any use of ECMAScript.
</p -->
<p>
We have decided not to use unecessary components nor "toxic"
features that would compromise the intended experience that
Blasta attempts to offer, neither waste power resources on
your end for no just reason, nor to compromise your privacy.
</p>
<p>
To compensate this, Blasta is designed in a fashion that
would make it easier to customize appearance and
functionality with <a href="/help/utilities#greasemonkey">
userscripts and userstyles</a>.
</p>
<h4 id="conclusion">
Conclusion
</h4>
<p>
Please <a href="/contact">contact us</a> and ask us
anything. We will be happy to read from you!
</p>
<br/>
<p class="quote bottom">
“Trust is the basis for social value and self-organisation,
but technical assurances are what help make it trustworthy.”
<a href="https://nlnet.nl/assure/">
NGI Assure
</a>
</p>
</div>
</div>
<div id="footer" class="row">
<dl>
<dd>
<img src="/graphic/blasta.svg" alt="logo"/>
<a href="/">blasta</a>
</dd>
<dd>
<a href="/help/about">about</a>
</dd>
<dd>
<a href="/help/about/xmpp">xmpp</a>
</dd>
<dd>
<a href="/help/about/xmpp/pubsub">pubsub</a>
</dd>
<dd>
<a href="{{journal}}">journal</a>
</dd>
<dd>
<a href="/help">help</a>
</dd>
<dd>
<a href="/help/policy">policy</a>
</dd>
<dd>
<a href="/help/feeds">rss</a>
</dd>
<dd>
<a href="/contact">contact</a>
</dd>
</dl>
</div>
</div>
</body>
</html>