Aller au contenu principal

· 2 minutes de lecture

Joplin Cloud has been out of beta for a few weeks now and since then it has been quietly running without any troubles. There is no known bugs and the service is running smoothly so it's now safe to say that it is production ready!

As a reminder, Joplin Cloud is meant to provide a more seamless Joplin experience - if you want to quickly get started, it's as easy as downloading the app and getting a Joplin Cloud account. Besides improved sync performance, that will give you the ability to collaborate on notebooks with others, as well as publishing and sharing notes.

Of course Joplin still supports other sync options such as Nextcloud, Dropbox and OneDrive or AWS S3. You can also self host using Joplin Server. The advantage of Joplin Cloud being that you don't need to maintain a server yourself - for a small fee you'll get that taken care of.

Additionally, subscribing to Joplin Cloud is a great way to support the project as a whole, including the open source applications. Such support is needed in the long term to provide bug and security fixes, add new features, and provide support.

At some level it is also an experiment, to see if such a service is financially viable and can allow me to work full time on the project. This is certainly something I would like, and perhaps Joplin Cloud combined with your donations will allow that.

· Une minute de lecture

For anyone with a beta account, if you would like to keep using it after the end of the trial period, there is now a button to do this from the Joplin Cloud home page:

If you click on it you will be sent to the Plans page via a special link. Then once you click on "Buy now" you will be sent to the Stripe page where you can start the subscription.

As mentioned in the message, the process takes into account your remaining beta trial days. So for example, if your beta account expires in 60 days, the subscription will have a free 60 days trial period. This is so you don't lose any of the beta trial days no matter when you start the subscription.

If you have any question about it, please let me know.

· Une minute de lecture

The latest Android pre-release 24 features an improved beta editor, which I hope could become a replacement for the very basic editor we have at the moment.

It's still experimental because it's based on the equally experimental CodeMirror 6, however for simple editing tasks it seems to work fine. At the moment the improvements are:

  • Syntax highlighting for various tags such as bold, italic and headings.

  • List continuation for ordered and unordered lists (I didn't try checklists but I assume it doesn't work)

  • Improved undo/redo

  • Maybe better handling of large documents? CodeMirror 6 has a demo that loads a document with millions of lines, so maybe that will solve the performance issues that some users were having

If everything works well, later on we should be able to add things like a toolbar, spellchecking and other features that are impossible with the current editor.

If you find any bug, feel free to report here. Also make sure you backup your notes regularly in case there's an issue!

· Une minute de lecture

The beta program helped narrow down a few issues and should make Joplin Cloud (and Joplin Server) more reliable. More precisely:

  • About 7 bugs have been fixed, including two major ones regarding sharing, and one security issue.
  • About a dozen improvements, new features and optimisations have been added following your feedback.

As promised if you have a beta account you can keep using it and it will remain free for the three months after the account was created. After that, you will receive a link to start the Stripe subscription if you wish to keep using the account.

If you have sent me an email before the end of the beta and I didn't reply yet, I will do so soon, and will send you the confirmation email.

Thanks everyone for participating!

· 2 minutes de lecture

The new website is finally ready at https://joplinapp.org

The previous website had been built organically over the past few years. It had a lot of useful content but finding your way was tricky and, for new users, it wasn't clear what Joplin was about. Finding out how to install the app wasn't obvious since the download buttons were lost in the clutter of information.

So the new website includes a front page with clear goals:

  • Allows people to easily download the app - for that there's a large Download button at the top and bottom of the page. It redirects to a page that automatically picks the version based on your operating system.
  • Showcase the application key features. The key features post on the forum helped narrow down what Joplin is about, so there are sections about the web clipper, the open source nature of the app, encryption, synchronisation, customisation and the ability to create multimedia notes.
  • The top screenshots have also been updated (the previous one was showing a dev version from 2016, before the app was even released). As a nod to Scott Joplin, the screenshot shows an imaginary plan to open a vintage piano store, with various tasks, tables, documents and images attached, to showcase Joplin features.
  • Finally there's a Press section, which includes extracts from some cool articles that have been written about the app.

Also many thanks to everyone who voted and contributed to the tagline discussion! It helped narrow down what the tagline should be, along with the equally important description below. If you have any question or notice any issue with the website let me know!

· Une minute de lecture

I'm going to update the website front page to better showcase the application. I have most of the sections right, but the part I'm still not sure about is the top tagline, so I'm wondering if anyone had any suggestion about it?

From what I can see on Google Keep or Evernote for example it should be something like "Use our app to get X or Y benefit", it should be a sentence that directly speaks to the user essentially.

So far I have "Your notes, anywhere you are" but I'm not certain that's particularly inspiring. Any other idea about what tagline could be used?

· 4 minutes de lecture

Since a few versions Joplin Server includes a way to share notebooks between users and collaborate on them - i.e. any participant can view or modify notes in the shared notebook. It's been present since version 2.x and the feature is getting close to be stable.

How does it work?

When connected to Joplin Server (or the upcoming Joplin Cloud service), a new "Share notebook" menu item is available when right-clicking on a notebook.

Click on it, and it will display a new dialog where you can add any number of recipients. Those recipients also need to be on the same Joplin Server instance. From this dialog you can also remove a recipient or unshare the whole notebook, in which case it will be removed from everybody's note collection, except yours.

Once this is done, the recipient(s) will receive a notification in Joplin the next time they synchronise their data:

Then, finally, once the invitation is accepted, Joplin will download all the shared notebooks and notes. A shared notebook is denoted by the usual Share icon. Now the invited user can read or modify the shared notes, add attachments, etc. and the changes will be visible to everyone with access to the notebook.

What's the availability of the notebook sharing feature?

The notebook sharing feature is available on Joplin Server and Joplin Cloud.

On desktop, you can share notebooks and of course view or modify any notebook that has been shared with you.

On mobile and CLI, you cannot currently share notebooks, but you can view or modify any notebook that has been shared with you.

If I share a notebook with someone, what access do they have?

Currently they have full access to the data, including reading, writing and deleting notebooks or notes. In a future version, access control might be implemented. For example, to only give read-only access to the shared notebook.

What can actually be shared?

All the sub-notebooks, notes and resources within the shared notebook are shared.

Does it work with End-To-End-Encryption?

Yes and no. It is possible to use the share notebook feature even with E2EE enabled, however any shared notebook or note will not be encrypted, otherwise you would have had to give your master key password to the people you share with, which you'd probably not want to do.

In a future version, this might be supported. For example by automatically creating a new master key for the shared notebook. You would then provide the recipients with that master key password.

What can it be used for?

Some ideas:

  • Plan a trip with friends or within a small organisation. For example, the notes could contain the maps, hotel and flight reservations, etc. or any document or note relevant to the trip. And all participants would have access to them.
  • Work on a project with colleagues. Everybody can access various work-related documents, add to them, modify them, etc. That could serve as a knowledge base for a project.
  • Another possible use, which has been requested many times, is to support multiple profiles. You could create a main profile that have access to all notes, and in there create a Work and Personal notebook. Then you would create a separate account for work. You can then share your Work notebook with that other account. That way the work account will only have access to the Work notebooks. You can use this technique in various ways to split your notebooks between multiple accounts and ensure strict separation between datasets.

· Une minute de lecture

Google has reviewed the project proposals we had submitted and all students have been approved. Congratulation and welcome to our six students - we're looking forward to see your work!

Below is the list of projects along with the student name and mentors. This year we will have a main mentor and a co-mentor for each project and in the list below, the main mentor is listed first:

BibTeX Plugin

Student: Abdallah Ahmed

Mentors: Laurent Cozic, Helmut K. C. Tessarek

Improving Conflict Resolution Process

Student: Ahmed Alwasifey

Mentors: Jack Gruber, Caleb John

Kanban Board Plugin

Student: Mablin

Mentors: Roman Musin, Laurent Cozic

Paste Special

Student: Siddhant Sehgal

Mentors: Helmut K. C. Tessarek, Stefan Müller

Real-Time Collaboration

Student: Akash Konda

Mentors: Stefan Müller, Roman Musin

Template Plugin

Student: Nishant Mittal

Mentors: Jack Gruber, Caleb John


The official Google of Summer Code page has also been updated with the list of projects:

https://summerofcode.withgoogle.com/organizations/6579646541332480/