Searching We.Love.Privacy.Club

Twts matching #documentation
Sort by: Newest, Oldest, Most Relevant

How to Recover Unsaved Word Documents on Mac with AutoRecovery
While you should get in the habit of frequently saving your documents as you work in them, including in Microsoft Word, things don’t always go as planned. Many modern Mac apps will automatically save progress as you work in them, and Microsoft Word is one of them. Thanks to a feature called AutoRecovery, which saves … [Read More](https://osxdaily.com/2024/02/26/how-to-recover-unsaved-word-documents-on-mac-wit … ⌘ Read more

⤋ Read More

Mathieu Pasquet: slixmpp v1.8.5

Highlights
  • Moving away from self-hosted gitlab (mathieui)
  • Fix connection to Snikket instances (pep., mathieui)
  • Performance fix for XEP-0115 queries
  • New documentation listing projects using slixmpp (genghis)
  • Bugfix and improvements (nicoco, mostly)
Details
  • Gitlab migration: see the otherblogpost
  • Fix connections to Snikket instances:

Snikket decided to forbid PLAIN
authentication, which is good but exposed … ⌘ Read more

⤋ Read More

Ignite Realtime Blog: REST API Openfire plugin 1.10.2 released!
Earlier today, we have have performed a maintenance release for the REST API plugin for Openfire. In this release, version 1.10.2, we have made a warning in documentation more visible. This is aimed at reducing confusion around installation with Openfire 4.7.5.

Also in this release a translation into Ukrainian, gracefully provided by community member Yurii Savchuk (svais) and his son Vladislav Savchuk (Bruhmozavr)!

Th … ⌘ Read more

⤋ Read More

When Apple built MacOS… for Solaris and HP-UX. In 1994.
Listen now (16 mins) | Back in 1994, Apple released the Macintosh Application Environment for UNIX. And it was kind of amazing. Read the full article (with links to documentation and screenshots) at The Lunduke Journal: https://lunduke.locals.com/post/4812552/remember-when-apple-built-a-mac-os-running-on-top-of-solaris-and-hp-ux-seriously-it-happenedRead more

⤋ Read More

Getting Started with JupyterLab as a Docker Extension
JupyterLab is a web-based interactive development environment (IDE) that allows users to create and share documents that contain live code, equations, visualizations, and narrative text. It is the latest evolution of the popular Jupyter Notebook and offers several advantages over its predecessor. We provide an overview the JupyterLab architecture and explain how to start using JupyterLab as a Docker extension. ⌘ Read more

⤋ Read More
In-reply-to » Erlang Solutions: Blockchain in Sustainable Programming The benefits of blockchain implementation across multiple sectors are well-documented, but how can this decentralised solution be used to achieve more sustainable programming?

@Planet_Jabber_XMPP@feeds.twtxt.net

The benefits of blockchain implementation across multiple sectors are well-documented

WTF are you talking about? The only thing well-documented about “the blockchain” is that it sucks and its primary use case is creating Ponzi schemes.

⤋ Read More

Erlang Solutions: Blockchain in Sustainable Programming
The benefits of blockchain implementation across multiple sectors are well-documented, but how can this decentralised solution be used to achieve more sustainable programming?

As the effects of the ongoing climate crisis continue to impact weather patterns and living conditions across the planet, we must continue to make every aspect of our lives, from transport and energy usage to all of our technology, greener and more sustain … ⌘ Read more

⤋ Read More

Erlang Solutions: Effortlessly Extract Data from Websites with Crawly YML

The workflow

So in our ideal world scenario, it should work in the following way:

  1. Pull Crawly Docker image from DockerHub.
  2. Create a simple configuration file.
  3. Start it!
  4. Create a spider via the YML interface.

The detailed documentation and the example can be found on HexDocs here: [https://hexdocs.pm/crawly/spiders_in_yml.html#content](https://hexdocs.pm/crawly/spiders_in_yml.html#c … ⌘ Read more

⤋ Read More

An official FBI document dated January 2021, obtained by the American association “Property of People” through the Freedom of Information Act.

This document summarizes the possibilities for legal access to data from nine instant messaging services: iMessage, Line, Signal, Telegram, Threema, Viber, WeChat, WhatsApp and Wickr. For each software, different judicial methods are explored, such as subpoena, search warrant, active collection of communications metadata (“Pen Register”) or connection data retention law (“18 USC§2703”). Here, in essence, is the information the FBI says it can retrieve:

  • Apple iMessage: basic subscriber data; in the case of an iPhone user, investigators may be able to get their hands on message content if the user uses iCloud to synchronize iMessage messages or to back up data on their phone.

  • Line: account data (image, username, e-mail address, phone number, Line ID, creation date, usage data, etc.); if the user has not activated end-to-end encryption, investigators can retrieve the texts of exchanges over a seven-day period, but not other data (audio, video, images, location).

  • Signal: date and time of account creation and date of last connection.

  • Telegram: IP address and phone number for investigations into confirmed terrorists, otherwise nothing.

  • Threema: cryptographic fingerprint of phone number and e-mail address, push service tokens if used, public key, account creation date, last connection date.

  • Viber: account data and IP address used to create the account; investigators can also access message history (date, time, source, destination).

  • WeChat: basic data such as name, phone number, e-mail and IP address, but only for non-Chinese users.

  • WhatsApp: the targeted person’s basic data, address book and contacts who have the targeted person in their address book; it is possible to collect message metadata in real time (“Pen Register”); message content can be retrieved via iCloud backups.

  • Wickr: Date and time of account creation, types of terminal on which the application is installed, date of last connection, number of messages exchanged, external identifiers associated with the account (e-mail addresses, telephone numbers), avatar image, data linked to adding or deleting.

TL;DR Signal is the messaging system that provides the least information to investigators.

⤋ Read More

** Moon maker **
I recently re-read Peter Naur’s“Programming as theory building”. Afterwards I set out to write my own text editor. The paper posits that it’s really hard, if not impossible, to fully communicate about a program and sort of gestures at the futility of documentation…what spun around inside my head as I read was that our primary programming medium — text files — is silly. Like, some folks would totally 100% s … ⌘ Read more

⤋ Read More

Gajim: Gajim 1.7.0
Gajim 1.7.0 is mostly a bug fixing release. Due to fundamental changes in the build system, we decided to jump from 1.6.x to 1.7 directly. Thank you for all your contributions!

What’s New

Gajim’s build system had significant changes, which makes it necessary for package maintainers to change some things, as documented in the readme file.

More Changes
  • Account creation: Don’t allow to add account twice
  • File previews: Y … ⌘ Read more

⤋ Read More

I remember when doing this process with my wife. During the halfway point we brought all sorts of documentation to show commingling of assets and showing we had “built a life together” .. we get to the interview and they just ask if we have a Costco card together. :|

good luck to you!

⤋ Read More

Erlang Solutions: GraphQL interfaces in MongooseIM 6.0
MongooseIM is a robust, scalable and highly extensible instant messaging server. Recent releases have improved its configurability and opened new use cases, and the latest version 6.0 continues that trend. By introducing the brand new GraphQL API, we made MongooseIM much easier to integrate with external web services. The entry barrier is also lower than ever because of the automatically generated API documentation, interactive web UI, an … ⌘ Read more

⤋ Read More

Unboxing fork improvements and unwrapping fork docs
We’re always trying to improve the GitHub developer experience in meaningful ways, and we love learning from our customers. In the last several months we released several new fork capabilities, and we’re publishing revised fork documentation that gives more details with clearer explanations to make fork concepts easier to understand. ⌘ Read more

⤋ Read More

** uxn exit **
This evening I sat down on the couch sleepy. We’d just gotten the kids into bed. I hadn’t planned on writing any code but figured I’d round the evening out with some reading.

First I read through the docs and glossary of uf, a forth system for uxn. Then I read through an example program provided by uf.

…with my palette whetted I [re-visited some other forth documentation](https://eli.li/_assets/bin/P … ⌘ Read more

⤋ Read More

Some IndieWeb protocols are complicated and there are sometimes no programming libraries to simplify the use of them, but ActivityPub is another beast. Although the standard is documented, the way the specific implementations (Mastodon etc.) work often isn’t and it’s hard to debug. So huge respect for the big rework. 👍 ⌘ Read more

⤋ Read More

Tigase Blog: Tigase XMPP Libraries

Our software philosophy

Actually nothing new and nothing surprising here. We want to have as much of a reusable code as possible. And this
reusable code should have a simple but powerful API to be useful for quickly creating software.

That’s it.

And this is how we design and develop our XMPP libraries. Check them out.

Documentation to all our projects is available online and sample codes? Take a look at our XMPP Chat apps which are
open source too. ⌘ Read more

⤋ Read More