HTTP/2 200 cache-control: max-age=900, public content-language: en content-type: text/html; charset=UTF-8 etag: W/"1561641449" expires: Sun, 19 Nov 1978 05:00:00 GMT last-modified: Thu, 27 Jun 2019 13:17:29 GMT link: ; rel="canonical" link: ; rel="shortlink" link: ; rel="revision" server: nginx x-content-type-options: nosniff x-drupal-cache: HIT x-drupal-dynamic-cache: HIT x-frame-options: SAMEORIGIN x-generator: Drupal 8 (https://www.drupal.org) x-pantheon-styx-hostname: styx-fe2-a-5fd9fb4bc-l779d x-styx-req-id: 9ad60b51-a74c-48d3-b317-5038b10055cc x-ua-compatible: IE=edge via: 1.1 varnish accept-ranges: bytes date: Thu, 27 Jun 2019 17:25:03 GMT via: 1.1 varnish age: 0 x-served-by: cache-mdw17370-MDW, cache-yul8927-YUL x-cache: MISS, HIT x-cache-hits: 0, 1 x-timer: S1561656304.565479,VS0,VE1 vary: Accept-Encoding, Cookie, Cookie, Cookie content-length: 51541 Nextcloud Has a New Collaborative Rich Text Editor Called Nextcloud Text, GNOME Announces GNOME Usage, Linus Torvalds Warns of Future Hardware Issues, Red Hat Introduces Red Hat Insights and Offensive Security Launches OffSec Flex | Linux Journal Skip to main content [1]
Synaptic Web News
Nextcloud Has a New Collaborative Rich Text Editor Called Nextcloud Text, GNOME Announces GNOME Usage, Linus Torvalds Warns of Future Hardware Issues, Red Hat Introduces Red Hat Insights and Offensive Security Launches OffSec Flex
- Written by: J D
- Category: News
- Hits: 296
News briefs for June 27, 2019.
Nextcloud announces a new collaborative rich text editor called Nextcloud Text. Nextcloud Text is described as not "a replacement to a full office suite, but rather a distraction-free, focused way of writing rich-text documents alone or together with others." See the Nextcloud blog post[2] for more details.
GNOME announces GNOME Usage[3], a new app for visualizing system resources. The app was developed by Petr Stetka, a high-school intern in GNOME's Red Hat office in Brno. From the announcement: "Usage is powered by libgtop, the same library used by GNOME System Monitor. One is not a replacement for the other, they complement our user experience by offering two different use cases: Usage is for the everyday user that wants to check which application is eating their resources, and