<div dir="ltr">Tone Kastlunger, +1 :)<br><br>Peter Kovacs, please, take a look at tracker implementation: <a href="https://github.com/GNOME/tracker">https://github.com/GNOME/tracker</a><br>It uses semantic nosql techniques to handle the user data (RDF ontologies).<br>it's focusing on low memory footprint ("Tracker is designed and built to run well on mobile and desktop systems with lower memory (256MB or less)"),<br>and it is "built around a combination indexer and SQLite database",<br>but you can execute sparql queries here.<br>So, if you want a graph connections: they are already there. We just have to create an apropriate clients.<br><br>If you are interested in some other triplestore implementations, also take a look at redland rdf libraries^ <a href="http://librdf.org/">http://librdf.org/</a> </div><div class="gmail_extra"><br><div class="gmail_quote">2016-06-02 15:42 GMT+03:00 Tone Kastlunger <span dir="ltr"><<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>In a distributed fashion it may make sense;<br></div>speaking of which, doesn't tracker implement a graph db?<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jun 2, 2016 at 3:40 PM, Andrew Branson <span dir="ltr"><<a href="mailto:sfdevlist@andrewbranson.net" target="_blank">sfdevlist@andrewbranson.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm missing how your contacts can be linked as a graph on your phone. I assumed it was about which of your friends know each other, but that isn't relevant information on the client side. I don't think it's even easily available in the main social networks.<br>
<br>
Andy<span class=""><span><br>
<br>
On 02/06/2016 2:34pm, Tone Kastlunger wrote:<br>
</span></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><span>
On the RDBMS vs Graph DB's discussion, the point Peter is making is a<br>
very solid one;<br>
the purpouse of the contacts app is to mange contacts; hence how they<br>
are connected;<br>
if relying on a Graph DB provides a simpler implementation (in terms of<br>
raw lines of code I mean) in upper implementation levels,<br>
whilst helping in keeping data consistency in a flawless and hassle-free<br>
way (which SQL can help with only up to a certain extent),<br>
well it definitely sounds too good to be true (at least from what I<br>
understood):<br>
I'd agree with Neo4J on a phone being somewhat of an overkill (same as<br>
having Postgres for instance); I'd wonder if there are embedded versions<br>
of it?<br>
I'd say especially within Jolla's Social/Address book/mail/calendar<br>
contacts management peculiarities, plus the dual SFOS/Android world, it<br>
requires a<br>
rock-solid contact management system, I'd assume.<br>
<br>
tk<br>
<br>
<br>
On Thu, Jun 2, 2016 at 3:22 PM, Andrew Branson<br></span></span><div><div class="h5"><div><div>
<<a href="mailto:sfdevlist@andrewbranson.net" target="_blank">sfdevlist@andrewbranson.net</a> <mailto:<a href="mailto:sfdevlist@andrewbranson.net" target="_blank">sfdevlist@andrewbranson.net</a>>> wrote:<br>
<br>
Hi!<br>
<br>
RDBMSes are not very good at graphs, or trees, or any other data<br>
structure that requires variable traversal steps in queries. I don't<br>
think we have that here though. Those social networks only have<br>
graphs when they're integrating your data with other people's, but<br>
personally you just have your own address book and your own<br>
calendars. Both of those consist of many instances of the same data<br>
structures which need to be indexed, which is a good use of<br>
relational databases.<br>
<br>
Your point about SQL being used out of habit is always pertinent<br>
though. It's important to keep on top of the NoSQL options, as SQL<br>
is definitely overused. I always find it very irritating when SQL is<br>
used only for config storage, using tables with single rows and many<br>
columns. Berkeley DB would be a good alternative for that. I don't<br>
know if the graph DBs are ready yet though - Neo4J is very<br>
interesting, but I would never run a Java server in a phone.<br>
<br>
While we're on the subject, I think the Nemo thumbnail DB is a<br>
really good candidate for a NoSQL database. It's currently a huge<br>
collection of tiny files that seems to take up way too much BTRFS<br>
allocation, and I don't think as a collection of binary files it<br>
would be a good match for SQLite.<br>
<br>
Andy<br>
<br>
<br>
On 02/06/2016 1:42pm, Peter Kovacs wrote:<br>
<br>
Well SQL is in my opinion good for grouping or conduct<br>
calculations on<br>
transactional data.<br>
Updating, or adding / sorting is not is best discipline. It is<br>
medicore<br>
in my opinion.<br>
On small sets of data as used in phones medicore performance is<br>
still<br>
quick. Phones are quite powerfull today.<br>
<br>
However the feature the DB should excel should be, in my eyes<br>
social,<br>
stuff. It is a phone after all, intended to maintain my social<br>
life, or?<br>
<br>
And Facebook, amazon, google+ does not use relational databases.<br>
They<br>
use graph databases. So I wonder why this is not used on phones.<br>
Neo4j<br>
claims to outperform relational databases by a factor of 1000<br>
when it<br>
comes to relationships.<br>
<br>
I admit these softwares are very latest technology. And maybe not as<br>
robust as sqllite.<br>
However I would love to have a contact app which knows that Mary<br>
and Joe<br>
are married live in the same place. And when I search for one of<br>
the 2 I<br>
get the shared information. And when I update one end the app<br>
knows to<br>
update the other one too.<br>
Or it can store company hierarchies would help me in my business<br>
life. I<br>
am not good at memo these.<br>
<br>
Yes you can do that with sql. But I think it is easier more<br>
naturally<br>
done in a graph db.<br>
No problem if any one does not agree. I plan to build this anyhow.<br>
<br>
I am quite unhappy with Google in that because they are not<br>
doing this<br>
for me ;)<br>
<br>
Btw Object DB is good at storing objects as the name suggests. It is<br>
even more far away from the requirements on a phone then<br>
relational db<br>
in my eyes.<br>
<br>
All the Best<br>
Peter<br>
<br>
<br>
Tone Kastlunger <<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a><br>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a>><br></div></div></div></div>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a><span class=""><span><br>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a>>>> schrieb am Do., 2. Juni<br>
2016, 11:13:<br>
<br>
Peter;<br>
I'm curious, what brings you to the conclusion SQL (as in<br>
relational<br>
dbs) is not ideal for transactional functionality?<br>
<br>
On Thu, Jun 2, 2016 at 10:41 AM, Peter Kovacs<br>
<<a href="mailto:leginee@gmail.com" target="_blank">leginee@gmail.com</a> <mailto:<a href="mailto:leginee@gmail.com" target="_blank">leginee@gmail.com</a>><br></span></span><span class=""><span>
<mailto:<a href="mailto:leginee@gmail.com" target="_blank">leginee@gmail.com</a> <mailto:<a href="mailto:leginee@gmail.com" target="_blank">leginee@gmail.com</a>>>> wrote:<br>
<br>
I would actually like to know why SQL stuff.<br>
Datastructure types I am think of on the Phone are<br>
relationships<br>
(Facebook style) or transactional.<br>
And both are not ideal to solve with relational dbs.<br>
<br>
I guess the Answer is because every one does it. But<br>
that is not<br>
really satisfactory. Would there be an interest to use<br>
something else?<br>
<br>
<br>
Tone Kastlunger <<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a><br>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a>><br></span></span>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a><div><div class="h5"><div><div><br>
<mailto:<a href="mailto:users.giulietta@gmail.com" target="_blank">users.giulietta@gmail.com</a>>>> schrieb am Do., 2. Juni<br>
2016, 09:33:<br>
<br>
Hi Chris;<br>
<br>
<br>
>2) API to access Calendar data. Correct,<br>
currently we<br>
don't provide access to calendar API in Harbour.<br>
The reason<br>
is that we want to use QtOrganizer as the public<br>
API, but to<br>
do that we need to write a QtOrganizer engine<br>
backend >for<br>
mkcal (note that one already existed in QtMobility<br>
days,<br>
which is open source, so we can potentially adapt<br>
that one<br>
with relatively little effort. Help with that<br>
effort would<br>
be greatly appreciated). Eventually, I'd like to<br>
develop a<br>
>QtOrganizer backend directly in sqlite, for<br>
performance<br>
and maintainability reasons (mkcal has several<br>
design and<br>
implementation problems, in my opinion), at which point<br>
QtOrganizer can become the platform API (not just<br>
the 3rd<br>
>party API).<br>
<br>
<br>
I guess the worload to push it all the way to<br>
QtOrganizer<br>
requires scratching the existing backend /<br>
rewriting a big<br>
part of the cal app?<br>
<br>
On Thu, Jun 2, 2016 at 5:06 AM, Chris Adams<br>
<<a href="mailto:chris.adams@jolla.com" target="_blank">chris.adams@jolla.com</a><br></div></div></div></div>
<mailto:<a href="mailto:chris.adams@jolla.com" target="_blank">chris.adams@jolla.com</a>> <mailto:<a href="mailto:chris.adams@jolla.com" target="_blank">chris.adams@jolla.com</a><div><div class="h5"><div><div><br>
<mailto:<a href="mailto:chris.adams@jolla.com" target="_blank">chris.adams@jolla.com</a>>>> wrote:<br>
<br>
Hi everyone,<br>
<br>
I will try to be at the meeting tonight, but I<br>
cannot<br>
promise (it's held at 11:30 pm in my timezone).<br>
<br>
A couple of the questions relate to areas I am<br>
involved<br>
with, so I'll try to provide some information<br>
in case I<br>
don't make it to the meeting. If you have any<br>
follow up<br>
questions or discussion, feel free to contact me<br>
directly via email or on Freenode IRC (chriadam<br>
is my nick).<br>
<br>
1) Contact Note details. This is tracked<br>
internally by<br>
JB#14734. As you mentioned, it's supported in the<br>
backend, but not in the People app UI. It was<br>
on going<br>
to be part of the apps overhaul which was<br>
planned prior<br>
to the financial difficulties last year, and<br>
since then<br>
this has fallen off the radar. It requires design<br>
input, because you can have multiple Note<br>
details in a<br>
single contact. I've just pinged our lead<br>
designer in<br>
the bug report again, in case he can fit it in<br>
sometime<br>
soon.<br>
<br>
2) API to access Calendar data. Correct,<br>
currently we<br>
don't provide access to calendar API in<br>
Harbour. The<br>
reason is that we want to use QtOrganizer as<br>
the public<br>
API, but to do that we need to write a QtOrganizer<br>
engine backend for mkcal (note that one already<br>
existed<br>
in QtMobility days, which is open source, so we can<br>
potentially adapt that one with relatively little<br>
effort. Help with that effort would be greatly<br>
appreciated). Eventually, I'd like to develop a<br>
QtOrganizer backend directly in sqlite, for<br>
performance<br>
and maintainability reasons (mkcal has several<br>
design<br>
and implementation problems, in my opinion), at<br>
which<br>
point QtOrganizer can become the platform API<br>
(not just<br>
the 3rd party API).<br>
<br>
3) Email app development. Yes, you're<br>
absolutely right<br>
that the Email application hasn't received much<br>
development effort since Valerio unfortunately<br>
left.<br>
Yes, I would personally like to see it (along<br>
with other<br>
apps like Clock, Notes, and Calendar)<br>
opensourced. No, I<br>
don't know what the status of the opensourcing<br>
discussions with the Board Of Directors is, so<br>
I cannot<br>
give a roadmap for that possibility. However, the<br>
"engine" of the email application is already<br>
open source<br>
(except for the Exchange/ActiveSync plugin) -<br>
we use QMF<br>
(Qt Messaging Framework) for email handling. See<br>
<a href="https://git.merproject.org/mer-core/qmf" rel="noreferrer" target="_blank">https://git.merproject.org/mer-core/qmf</a> and<br>
<a href="https://git.merproject.org/mer-core/messagingframework" rel="noreferrer" target="_blank">https://git.merproject.org/mer-core/messagingframework</a><br>
etc for that stuff. Speak to Matt Vogt (mvogt on<br>
Freenode IRC) for code reviews etc.<br>
<br>
In general, the Sailfish OS wiki has been<br>
updated with a<br>
lot of information about the various software<br>
components<br>
which make up the Sailfish OS stack (including<br>
links to<br>
the open-source repositories), so you should be<br>
able to<br>
find most of the information you need to help<br>
develop<br>
these components, from reading<br>
<a href="https://sailfishos.org/wiki/Core_Areas_and_APIs" rel="noreferrer" target="_blank">https://sailfishos.org/wiki/Core_Areas_and_APIs</a> and the<br>
drill-down links from that page.<br>
<br>
Finally, I don't know much about Bluetooth, but<br>
I know<br>
that we're looking at updating to Bluez 5 right now<br>
(development is currently ongoing to port the<br>
Qt stack<br>
across, possibly by using the KDE bluez-qt<br>
wrappers), so<br>
it's possible that the tethering issue will be<br>
addressed<br>
as part of that, with the new stack - but<br>
again, that's<br>
not my area so I might be incorrect.<br>
<br>
Cheers,<br>
Chris.<br>
<br>
<br>
<br>
------------------------------------------------------------------------<br>
*From:* <a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a>><br></div></div></div></div>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a>>><br>
[<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a>><br></span></span>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.sailfishos.org</a>>>] on behalf<br>
of James Noori [<a href="mailto:james.noori@jolla.com" target="_blank">james.noori@jolla.com</a><br>
<mailto:<a href="mailto:james.noori@jolla.com" target="_blank">james.noori@jolla.com</a>><br></span></span>
<mailto:<a href="mailto:james.noori@jolla.com" target="_blank">james.noori@jolla.com</a><span class=""><span><br>
<mailto:<a href="mailto:james.noori@jolla.com" target="_blank">james.noori@jolla.com</a>>>]<br>
*Sent:* Wednesday, June 01, 2016 11:15 PM<br>
*To:* <a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a>><br></span></span>
<mailto:<a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a>>><br>
*Subject:* [SailfishDevel] Sailfish OS Open Source<br>
Community Collaboration Meeting 2nd of June 2016<br>
<br>
Hi everyone!<br>
<br>
Following up last week’s postponed Community<br>
collaboration meeting on IRC, this week’s<br>
meeting is<br>
going to be held at the agreed time and date,<br>
2/6/2016<br>
at 13:30 UTC.<br>
<br>
Please see this link for your local time<br>
(Redirects to<br></span></span>
<a href="http://timeanddate.com" rel="noreferrer" target="_blank">timeanddate.com</a> <<a href="http://timeanddate.com" rel="noreferrer" target="_blank">http://timeanddate.com</a>> <<a href="http://timeanddate.com" rel="noreferrer" target="_blank">http://timeanddate.com</a>>)<div><div class="h5"><div><div><br>
:<a href="http://bit.ly/247PwwT" rel="noreferrer" target="_blank">http://bit.ly/247PwwT</a><br>
<br>
<<a href="http://redir.aspx?REF=g5j-y9bnU2VIldZnOnr8CS7-bSPOGw-1AMJwEvMljvQjLMD_gYrTCAFodHRwOi8vYml0Lmx5LzI0N1B3d1Q" rel="noreferrer" target="_blank">http://redir.aspx?REF=g5j-y9bnU2VIldZnOnr8CS7-bSPOGw-1AMJwEvMljvQjLMD_gYrTCAFodHRwOi8vYml0Lmx5LzI0N1B3d1Q</a>.><br>
<br>
Location: #mer-meeting on Freenode IRC<br>
<br>
Chairperson: Jaymzz<br>
<br>
Duration: Approximately 100 minutes.<br>
<br>
Thanks to everyone who has responded and added<br>
topics on<br>
<br>
TJC:<a href="https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/" rel="noreferrer" target="_blank">https://together.jolla.com/question/54157/sailfishos-open-source-collaboration-meeting-planning/</a><br>
<br>
<<a href="http://redir.aspx?REF=OlRBTW_rwoaCk_9FOorV7mZrXabeWUP7jnZySM69E7wjLMD_gYrTCAFodHRwczovL3RvZ2V0aGVyLmpvbGxhLmNvbS9xdWVzdGlvbi81NDE1Ny9zYWlsZmlzaG9zLW9wZW4tc291cmNlLWNvbGxhYm9yYXRpb24tbWVldGluZy1wbGFubmluZy8" rel="noreferrer" target="_blank">http://redir.aspx?REF=OlRBTW_rwoaCk_9FOorV7mZrXabeWUP7jnZySM69E7wjLMD_gYrTCAFodHRwczovL3RvZ2V0aGVyLmpvbGxhLmNvbS9xdWVzdGlvbi81NDE1Ny9zYWlsZmlzaG9zLW9wZW4tc291cmNlLWNvbGxhYm9yYXRpb24tbWVldGluZy1wbGFubmluZy8</a>.><br>
<br>
Proposed topics:<br>
<br>
-Intro (5min)<br>
<br>
-Bluetooth tethering - status of the fix (20min)<br>
<br>
-2016 roadmap (15min)<br>
<br>
-Show notes of contact (opensource contact<br>
app?) (15 min)<br>
<br>
-API to access calendar (15 min)<br>
<br>
-Email app development (15 min)<br>
<br>
- Requesting things to be added to mer-tools<br>
repo (5 min)<br>
<br>
- General Discussion (5-10 min)<br>
<br>
Please familiarize yourself with the topics<br>
before the<br>
meeting, as well<br>
<br>
as the common Meetbot commands<br>
<a href="https://wiki.debian.org/MeetBot" rel="noreferrer" target="_blank">https://wiki.debian.org/MeetBot</a><br>
<br>
<<a href="http://redir.aspx?REF=9bflfCySOf4l8VxPhhLe4rl_8CX0V51Eghusn5jTRNIjLMD_gYrTCAFodHRwczovL3dpa2kuZGViaWFuLm9yZy9NZWV0Qm90" rel="noreferrer" target="_blank">http://redir.aspx?REF=9bflfCySOf4l8VxPhhLe4rl_8CX0V51Eghusn5jTRNIjLMD_gYrTCAFodHRwczovL3dpa2kuZGViaWFuLm9yZy9NZWV0Qm90</a>><br>
(it's<br>
<br>
<br>
used for meeting management and logging)<br>
<br>
Best regards,<br>
James Noori, Community Manager at Jolla<br>
<br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br></div></div></div></div>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>>><br>
<br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br></span></span>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><div><div class="h5"><div><div><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>>><br>
<br>
--<br>
<br>
Disclaimer: Diese Nachricht stammt aus einem Google<br>
Account.<br>
Ihre Antwort wird in der Google Cloud Gespeichert und durch<br>
Google Algorythmen zwecks werbeanaöysen gescannt. Es<br>
ist derzeit<br>
nicht auszuschließen das ihre Nachricht auch durch<br>
einen NSA<br>
Mitarbeiter geprüft wird. Durch kommunikation mit<br>
diesen Account<br>
stimmen Sie zu das ihre Mail, ihre Kontaktdaten und die<br>
Termine<br>
die Sie mit mir vereinbaren online zu Google<br>
konditionen in der<br>
Googlecloud gespeichert wird. Sollten sie dies nicht<br>
wünschen<br>
kontaktieren sie mich bitte Umgehend um z.B.<br>
alternativen zu<br>
verhandeln.<br>
<br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br></div></div></div></div>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>>><br>
<br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br></span></span>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><span class=""><span><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>>><br>
<br>
--<br>
<br>
Disclaimer: Diese Nachricht stammt aus einem Google Account. Ihre<br>
Antwort wird in der Google Cloud Gespeichert und durch Google<br>
Algorythmen zwecks werbeanaöysen gescannt. Es ist derzeit nicht<br>
auszuschließen das ihre Nachricht auch durch einen NSA Mitarbeiter<br>
geprüft wird. Durch kommunikation mit diesen Account stimmen Sie<br>
zu das<br>
ihre Mail, ihre Kontaktdaten und die Termine die Sie mit mir<br>
vereinbaren<br>
online zu Google konditionen in der Googlecloud gespeichert wird.<br>
Sollten sie dies nicht wünschen kontaktieren sie mich bitte<br>
Umgehend um<br>
z.B. alternativen zu verhandeln.<br>
<br>
<br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br>
<br>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to<br>
<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<mailto:<a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a>><br>
<br>
<br>
<br>
<br></span></span><span class=""><span>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to <a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
<br>
</span></span></blockquote><span class=""><div><div>
_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to <a href="mailto:devel-unsubscribe@lists.sailfishos.org" target="_blank">devel-unsubscribe@lists.sailfishos.org</a><br>
</div></div></span></blockquote></div><br></div>
<br>_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to <a href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a><br></blockquote></div><br></div>