dpora Updates

dpora.com

Open call for collaborators!

We now have a working Android prototype, although admittedly a bit janky. As a single developer, I would love some help! If you’re familiar with the Flutter framework and share a similar vision for dpora, please send me a message at

Version 1.4

There are some improvements and new features debuting with version 1.4. You can now change groups whenever desired. So, if changing the topic doesn’t help stimulate the conversation, perhaps a group change is in order. Also, when all

Live on-device translations!

A new killer feature is now integrated into dpora (version 1.3): live on-device translations! What does that mean? The live means it happens instantly. On-device means the text is not sent to the cloud or to any server for translation (or

Email support

If you discover a software bug or have a problem with dpora, please email [email protected] If something is wrong with a topic (misspelled, offensive, outdated, dumb or incorrect in some way), email [email protected] If you want a new

Logo, Website, Email and Twitter

Four (and a half) new additions to dpora! There’s a new logo — a yellow phi symbol against a black background. The phi combines the first two letters of dpora (dp) to represent a shorthand of the name. The website is https://dpora.com

Version 0.1 is done!

The Android version of dpora is finally here. It’s merely version 0.1 but has all the basic elements it needs to be usable. It still needs to be tested much more rigorously and there are certainly a few kinks that will need smoothing, bugs

Welcome dporians!

One of the most basic tenets of dpora is to keep users of dpora (i.e., dporians) private. There is no registration process, no email or other data mining, etc. Nonetheless, in order for dpora to work in a technical sense, dporians have to

New UI additions

The user interface (UI) has been improved. Simple instructions (or a topic category) now show up alongside the discussion topics, with a related small icon. Over time, the icon will be enough of a hint without having to read the simple

We have a DB!

All the content has been uploaded to a back-end cloud-based server-less database and connected to the app. Now work is being done to integrate the database (DB) into the app to handle CRUD (create, read, update, delete) functions with the

Newer