Enlarge (credit: Aurich Lawson)

Ars Technica is pleased to announce the return of Ars Frontiers, our single-day event that explores tech's most vexing and fascinating issues. This year's event will be held on May 22, and everyone is invited! Attendance this year is virtual, so we'll be streaming all six sessions over the course of three and a half hours.

Readers who stop by the front page every day already know that Ars is a leader in bringing smart people together to talk about important topics—whether that means interviewing experts about current events or watching our highly skilled readers dissect an issue in the comments. In that same spirit of fostering brilliant discussions, this year we've curated a list of topics that explore the modern interconnectedness of innovation, with panels led by our subject matter authorities like Eric Berger and Dr. Beth Mole. All sessions will be streamed live on the Ars YouTube channel.

The main event

Ars Frontiers 2023 will feature six virtual sessions on May 22, starting at approximately 13:30 US Eastern Daylight Time (-4 UTC). Ars Technica Editor-in-Chief Ken Fisher and I will host the event from our studio in Manhattan. Each session will run about 30 minutes, which will include some time at the end for audience questions. Here's the line-up! (Session order might change between now and when the event happens.)

It is now possible to change your #Movim #blog privacy level using a new setting in the Configuration page.

All the Movim blogs used to be restricted to the users following them, now you can give access to your content to everyone visiting it 🥳

You can also know if a blog is restricted or not by visiting it.

Enjoy this new #feature !

Movim 0.21, codename Whipple, is finally out!

Let's have a look of all the new and improved things that you can find in this big #release 🥳

Message replies

You can now reply to messages thanks to the implementation of the XEP-0461: Message Replies.

More and more clients in the XMPP ecosystem supports this feature, including Slidge, new XMPP gateways project that is allowing you to bridge Movim with Telegram, Discord and many others chat platforms.

Push Notifications

Movim now integrates WebPush. Never miss a message, even when Movim is closed. This feature is also working when you install Movim as a Progressive Web App on your Android or iOS device.

Improved account configuration

The configuration panel has been redesigned to be more accessible.

You can now block contacts directly from your Movim instance and manage your block-list from the panel.

Microphones and webcams can also be configured and tested from the Audio & Video configuration tab.

New emojis

This version brings the support of Unicode 14 and many new emojis that you can use in your messages, posts, replies and reactions.

Redesign

Movim is following the #Material Design guidelines since 2014. This release is bringing a fresh redesign of the components and animations based on Material 3.

The main menu was reorganized to clarify the navigation and hide the second-level pages in a sub-menu that appears when hovering the account item.

Following this redesign Movim accounts can now set a banner next to their avatars.

Share and Send To

The Send To feature, that allows you to send articles to contacts was completed by a Share feature allowing you to share the article in a new publication on your personnal blog on in a Community that you're in. Useful to share things around !

Audio messages

Movim can now play and record #audio messages.

Gallery Communities

When creating or configuring your Communities you can now set a Community type. The Gallery Community forces the publications to contain at least one image and display them as a grid.

This feature is the result of a long clarification and standardization work made on XMPP Pubsub with the pubsub#type attribute, the introduction of a new XEP based on that change called XEP-0472: Pubsub Social Feed and the support of pubsub#type in ejabberd (related ticket).

Performances, memory consumption and stability

A very important work was done to limit the Movim processes memory consumption.

The daemon and subprocesses are now using PHP Opcache to load and share only once lots of files that were previously loaded multiple time during the Movim runtime. PHP modules are also loaded using a predefined whitelist to limit the usage of useless modules in memory.

DotEnv configuration

The old configuration system has been moved to the DotEnv standard. This change merges all the previous configuration (database, daemon and paths) into an unique .env file.

They can also be set using environment variable directly in your Docker Compose, or Web Server (using SetEnvin Apache for example).

The official Movim Docker image was also updated to fit those changes.

Migration from Movim 0.20

If you are planning to upgrade your current Movim instance please follow those few steps:

1. Copy and rename the .env.example file in .env and complete the few configuration variables in it. They should be the same as the one you set in the previous db.inc.php file and your daemon parameters.
2. Remove the db.inc.php file
3. Remove all the daemon.php parameters from your init.d, systemd services or other scripts. The daemon launch command should look this way: $ php daemon.php start.

...and as always, don't forget to run the migrations (php composer.phar movim:migrate) and restart your daemon.

XMPP Pubsub node security and restrictions

Movim 0.21 is not trusting anymore posts, likes and comments that are not containing the explicit identifier (Jabber ID) of the publisher and therefore now rely on this part of the XEP-0060: Pubblish-Subscribe - 12.16 Associating Events and Payloads with the Generating Entity.

All the existing likes and comments might be not counted anymore or seen as "Non trusted" ones. All the new published ones will be configured properly.

Migration from Movim 0.20

On ejabberd

You can update all the existing stored node configuration to force the new default configuration using the following SQL request. You might do a backup of your database before doing such changes:

update pubsub_node_option set val = `publisher` where name = `itemreply` and val = `none`

...and load those changes without restarting ejabberd:

$ ejabberdctl clear-cache

On Prosody

Ensure that you have the expose_publisher = true set in your configuration, see the related documentation.

What's next?

Movim 0.22 should include two big projects.

OMEMO rewrite ?

The cleanup, rewrite and refactoring of the OMEMO support that is quite buggy and not opmized. We are not promising anything on this side, OMEMO is always a complex beast to handle.

Multi-part audio and video-conference feature

The audio and video conferencing features were already introduced a few years ago in Movim. Some preparation work has been done in this 0.21 release to be able merge back the pop-up video-conference window inside the main window for the upcoming release.

The multi-part audio and video-conference feature is also one of the main feature that miss in Movim and is requested quite often by our users. Let's see if Movim 0.22 finally include this long awaited #feature.

Regarding the amount of work that need to be done regarding those features it might be possible that specific funding will be requested for it to free up enough time to work properly on their integration.

Enjoy!

A big thanks to the #Movim community that is growing more than ever. You can find us on our main support chatroom movim@conference.movim.eu.

If you find issues or if you want to contribute to the project you can find everything on our Github page.

And if you want to support us, fund the development of new features and help us pay our servers, domains and communication we are actively looking for supporters and sponsors on our Patreon.

That's all folks!

The idea would be to post quick articles with like a photo and/or short video and allow your contacts to see it for like 24h. Yes ? Na ? 🤔 #movim #feature #stories

Enlarge / Ahhh, the easy button! (credit: Aurich Lawson | Getty Images)

This is the second episode in our exploration of "no-code" machine learning. In our first article , we laid out our problem set and discussed the data we would use to test whether a highly automated ML tool designed for business analysts could return cost-effective results near the quality of more code-intensive methods involving a bit more human-driven data science.

If you haven't read that article, you should go back and at least skim it . If you're all set, let's review what we'd do with our heart attack data under "normal" (that is, more code-intensive) machine learning conditions and then throw that all away and hit the "easy" button.

As we discussed previously, we're working with a set of cardiac health data derived from a study at the Cleveland Clinic Institute and the Hungarian Institute of Cardiology in Budapest (as well as other places whose data we've discarded for quality reasons). All that data is available in a repository we've created on GitHub, but its original form is part of a repository of data maintained for machine learning projects by the University of California-Irvine. We're using two versions of the data set: a smaller, more complete one consisting of 303 patient records from the Cleveland Clinic and a larger (597 patient) database that incorporates the Hungarian Institute data but is missing two of the types of data from the smaller set.

Read 3 remaining paragraphs | Comments

Enlarge / Believe it or not, this fictional version of NORAD shows off the idea of the "connected battlespace" even better than the reali thing. (credit: MGM/UA)

Since the earliest days of warfare, commanders of forces in the field have sought greater awareness and control of what is now commonly referred to as the "battlespace"—a fancy word for all of the elements and conditions that shape and contribute to a conflict with an adversary, and all of the types of military power that can be brought to bear to achieve their objectives.

The clearer a picture military decision-makers have of the entire battlspace, the more well-informed their tactical and strategic decisions should be. Bringing computers into the mix in the 20th century meant a whole new set of challenges and opportunities, too. The ability of computers to sort through enormous piles of data to identify trends that aren't obvious to people (something often referred to as " big data ") didn't just open up new ways for commanders to get a view of the "big picture"—it let commanders see that picture closer and closer to real-time, too.

And time, as it turns out, is key. The problem that digital battlespace integration is intended to solve is reducing the time it takes commanders to close the "OODA loop," a concept developed by US Air Force strategist Colonel John Boyd. OODA stands for "observe, orient, decide, act"—the decision loop made repeatedly in responding to unfolding events in a tactical environment (or just about anywhere else). OODA is largely an Air Force thing, but all the different branches of the military have similar concepts; the Army has long referred to the similar Lawson Command and Control Loop in its own literature.

Read 33 remaining paragraphs | Comments

Read 2 remaining paragraphs | Comments