Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Untitled ⌘ Read more

Ignite Realtime Blog: Openfire 4.8.1 Release
The Ignite Realtime Community is pleased to announce the release of Openfire 4.8.1. This release addresses a number of issues found with the major 4.8.0 release a few months back.

Interested in getting started? You can download installers of Openfire here. Our documentation contains an [upgrade guide](https://download.igniterealtime … ⌘ Read more

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

The last entry in my voice memos is a 436 minute mp3 recording documenting a period in the life of my pants pocket.

I finally found the NASM assembler.

https://nasm.us/index.php

I had heard that name before, many times, but somehow never looked into it. Weird. 🤨🤔

This is the kind of program I was looking for.

1. It is free software. Especially in the DOS ecosystem, free/libre software is a very scarce resource.
   
2. It’s a small command line program, not a huge behemoth.
   
3. Documentation appears to be well written.
   
4. It can even cross-compile DOS binaries from Linux.

@prologic@twtxt.net pretty nothing berger. The “blowout” was pretty tame coming from Linus kill yourself now. The world will be a better place” Torvold.

The issue was a dev making a “fix” that didn’t have a documented problem. They reused some specific low level functions they did not understand the reason they were made.

@prologic@twtxt.net pretty nothing berger. The “blowout” was pretty tame coming from Linus kill yourself now. The world will be a better place” Torvold.

The issue was a dev making a “fix” that didn’t have a documented problem. They reused some specific low level functions they did not understand the reason they were made.

Mathieu Pasquet: slixmpp v1.8.5

• 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)
  

• Gitlab migration: see the otherblogpost
  
• Fix connections to Snikket instances:
  

Snikket decided to forbid PLAIN
authentication, which is good but exposed … ⌘ 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

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-happened ⌘ 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

Actually I might just be Lynx. Cause even without torsocks my messages dissapear when I refresh chat. Is Lynx using a previous document so it doesn’t have to get it from the server again or something?

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

@stigatle@yarn.stigatle.no Btw… I haven’t forgotten your ask of documenting the “Upload Media” API. I’m actually trying to work out how da fuq it even works myself 🤦‍♂️

House Republicans Accidentally Released a Trove of Damning Covid Documents
New documents show a scientist calling a lab leak “highly likely” — after drafting a paper claiming the opposite.

https://theintercept.com/2023/07/12/covid-documents-house-republicans/

Erlang Solutions: Effortlessly Extract Data from Websites with Crawly YML

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

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.

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.

I documented how I’ve been using the #Plume API to create posts, hopefully somebody might find it useful https://ouvaton.link/bGTcdV

** 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

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!

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

• Account creation: Don’t allow to add account twice
  
• File previews: Y … ⌘ 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!

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!

@xuu@txt.sour.is yeah, I know less about ISO27k (in part because you have to pay for access to the complete standards documents!!!), but I figured it was similar.

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

Find and Fix Vulnerabilities Faster Now that Docker’s a CNA
Docker is now officially a CNA under MITRE, which means you should get better notifications and documentation when we publish a vulnerability. ⌘ Read more

@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.

Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.

Also, never found a good explanation why I should add <link rel="self" … /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:

[…] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.

This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.

Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.

Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.

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

** 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

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

Tigase Blog: Tigase XMPP Libraries

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

Tigase Blog: Tigase Instant Communication, Presence and Messaging

First things first. What is this all about?

We say this is “Instant communication” or “Near real-time communication” and indeed, this is about communicating,
talking, sending messages, sending other information, documents. Instant or real-time means, whatever you send, is sent
right away, it is also delivered right away.

Would the receiving person get it right away too? Well, it depends, if the person is online, it … ⌘ Read more

GoToSocial seems like a promising alternative to Mastodon. It’s written in Go (👍 in my opinion), lightweight and pretty good documented so far. It’s still “alpha software” but seems to make great progress. In the past, I self hosted a microblog.pub instance and then after some time without any Fediverse profile other than my blog, which has ActivityPub support as well, signed up at Fosstodon to be able to reply to blog comments from the Fediverse. I already set up an instace of GTS, but will probably wait to use it … ⌘ Read more

I dream of a self-documenting wiki

@prologic@twtxt.net I do think the post about how to setup jenny + mutt over on the uninformativ.de blog is still a great post. I used that post to see the steps to set it up and it works fine. Though I can write some blog post with some more documentation for things like auto publishing. The big issue with plain twtxt is that I would have not seen your post unless I looked on twtxt.net when I was looking at yarn a little bit more. Twtxt does overcome the issue by introducing the registry but I can’t figure out any way to use them for Jenny and almost no one uses them in the first place. So I can’t see anyones replies or mentions unless I am following them. Yarn does overcome the issue by friends of friends as you would know as the creator of yarn.

Dino: Project Stateless File Sharing: First Steps
Hey, this is my first development update!
As some of you might already know from my last blog post, my Google Summer of Code project is implementing Stateless File Sharing for Dino.
This is my first XMPP project and as such, I had to learn very basic things about it.
In my blog posts I’ll try to document the things I learned, with the idea that it might help someone else in the future.
I won’t refrain from explaining terms you might take for gran … ⌘ Read more

Improved REST API documentation
We’re excited to announce some big improvements to our REST API documentation. We know developers rely on this documentation to integrate with GitHub, and we are committed to making it trustworthy, easy to find, and easy to use. ⌘ Read more

Understanding Color Management
I worked on a project where I dived deep into understanding how modern
color management works, including things like color spaces, ICC profiles
and more. As I learnt here and there, I decided to write this post, both
for my future self, and others who may struggle with some of the
concepts as well.

This post only aims to help you understand the basic concepts without
having to delve into dense literature and hard to grok technical
documents.

Color … ⌘ Read more

Annotate PDFs on Linux
This post is about a GUI tool called pdfrankestein that
fills a gap on mostly Linux machines where a powerful and easy to use
PDF annotator does not exist.

Adobe Acrobat® on Windows and Mac allow you to add text, drawings and
signatures to PDF documents. This is useful when filling forms or
marking notes to send back to someone. Such a tool with similar
capabilities and easy of use does not exist on Linux. The reason that’s
often cited is that PDF is a c … ⌘ Read more

seeing typos in LaTeX documents always throws me off, my brain still wants to classify the whole format as respectable

Documenting Microsoft’s funky attempts at porting software to UNIX
Listen now (15 min) | I was there for part of it. Trying to preserve that weird part of computing history. ⌘ Read more

Instead of banging my head on Advent of Code, I coded something useful today: Text-to-Speech for GoBlog using the official Google Text-to-Speech API. When posting, an audio file is generated automatically from the post content. And, I have to praise myself for this, I documented the feature as well! 😄 ⌘ Read more

Ignite Realtime Blog: Openfire 4.6.5 released
Although we’re preparing for the Openfire 4.7.0 release, the recently discovered vulnerability in the Apache Log4j utility prompted us to push an immediate release of Openfire to address that issue. This release, Openfire 4.6.5, is available now.

We urge you to update as soon as possible. If that’s not feasible, then we advise you to apply the documented workaround (in the form o … ⌘ Read more

I have now created a log documenting my attempts at making fudge: !fudgelog

Securing your GitHub account with two-factor authentication
The benefits of multifactor authentication are widely documented, and there are a number of options for using 2FA on GitHub. ⌘ Read more

If you must read the rest of this document to understand the behavior of your program, you are being too clever. Don’t be clever. The Go Memory Model - The Go Programming Language

I wrote “I don’t think price exists.” in a text document and predicted that later on I would be totally and utterly mystified what I meant by it originally. Turns out, that prediction was entirely correct.

@niplav@niplav.github.io Re: … < sharing ontologies: There’s an idea. If I want to write something, anything, documenting the words and concepts I use isn’t the dumbest idea.

Wanna Learn LaTeX?

Image

1. What is LaTeX?
   
2. Installing LaTeX
   
3. LaTeX Video Tutorials
   

I have a full video tutorial series on learning LaTeX, broken into small sensible parts, here.

Basically, it’s how big boys write and format documents.Every public brief, scientific article, book, cryptocurrency … ⌘ Read more

@(frogorbits.com) @niplav@niplav.github.io “I sign a lot less stuff these days now that my phone can pretend to be a credit card. Also: an impostor with a quantum computer can’t pretend to sign documents on my behalf…” -> It’s good that pen signatures are completely unfakeable. They’re unbelievably reliable. We can’t just copy & photoshop around the edges. Better worry about those definitely-soon-to-exist quantum computers that might crack cryptography.

@niplav@niplav.github.io I sign a lot less stuff these days now that my phone can pretend to be a credit card. Also: an impostor with a quantum computer can’t pretend to sign documents on my behalf…

Wanna learn LaTeX?

Basically, it’s how big boys write and format documents.
Every public brief, scientific article, book, cryptocurrency whitepaper or even outline written by people who know what they’re doing is written in LaTeX.

If you want to see examples of documents made with LaTeX, you can see my Master’s thesis here or another paper here that shows some diagrams and other features you can have in LaTe … ⌘ Read more

Documentation on i2c devices is so-so. Lots of good documentation on higher-level APIs, but not a lot of “this register does this” stuff.

finally finished all the initial ugen documentation. everything now has a sentence or two. the generated page can be accessed from the ugen wiki page [[/proj/monolith/wiki/ugens]] #updates #monolith

been adopting a document-as-you go approach to the !monolith wiki. as I dogfood my software to make pieces an etudes like !breathing_cards, I write about it in a wiki stub. #workflow #documentation

PeerTube documentation ⌘ https://docs.joinpeertube.org/#/maintain-tools?id=remote-tools

microblog.pub documentation | hexa.ninja ⌘ https://docs.microblog.pub/

The master plan is to export the !worgle bits of !monolith to a !weewiki, then begin adding user-level documentation that is able to dynamically reference bits of source code as another wiki page.

while eventually I hope to get all of literate org parts of !monolith posted online as a self contained !weewiki, I’ve decided to post little pieces as self-contained documents. here is a copy of !trigvm, the toy VM used to power a rhythmic computer-sequencer controlled entirely from the !monome_grid

I really want !btprnt to be integrated into !weewiki somehow. Both can speak !janet, and I already figured how to embed PNG images inside of an HTML document. In small doses, it could be fun. #halfbakedideas

documenting my experiments with twtxt/weewiki integration at the !twtxt_playground

Cryptee | Private, Secure, Encrypted Photos and Encrypted Documents ⌘ https://crypt.ee/

I mean, ‘quietly’ is a bit misleading since this has been in the news every few years for more than a decade, but you all might need a reminder: https://qz.com/1002927/computer-printers-have-been-quietly-embedding-tracking-codes-in-documents-for-decades/

Poor documentation is overrated as an attribute of jokes. (Some of my favorite jokes are literally humorous attempts at explaining other jokes.) The difference between standup comedy & UI design is even bad comics know this.

I love books about the history of tech, but no matter how well-researched, they’re typically mostly a documentation of tech’s mythology (or some countermythology). I prefer the countermythographies.

I documented what I’m trying to do with MfoM, so that I can write a proper postmortem later: https://medium.com/@/mfom-pre-postmortem-92683b15ff2c

Parallel documents! Interview, August 2018 - YouTube https://www.youtube.com/watch?v=PPBeHDxcVSA

GXemul - Documentation (0.6.1) http://gavare.se/gxemul/gxemul-stable/doc/guestoses.html#sprite

Heads up, apparently there are gonna be export restrictions on neural net, reinforcement learning, computer vision, NLP, & similar research done in the US: https://www.federalregister.gov/documents/2018/11/19/2018-25221/review-of-controls-for-certain-emerging-technologies

Just created my first proper document in Scribus. It worked better than I expected.

Document Moved https://sway.com/b1pRwmzuGjqB30On

Xanadu Basics 1b– INDIRECT DOCUMENT DELIVERY - YouTube https://www.youtube.com/watch?v=1gPM3GqjMR4

inferno@interstice.com and inferno@artnet.com.br list archives http://doc.cat-v.org/inferno/historical_documents/mailing_lists/interstice/

Technical Documentation For The Canon Cat Editor : David Alzofon, Lori Chavez, Jim Winter, David Caulkins, Terry Holmes, Minoru Taoyama, Jonathan Sand, John Bumgarner, Scott Kim. : Free Download, Borro… https://archive.org/details/TechnicalDocumentationForTheCanonCatEditorSep88

Genode - Sculpt with Visual Composition (VC) https://genode.org/documentation/articles/sculpt-vc