AI prompts
base on Text mode window environment. A terminal emulator and multiplexer with mouse support, overlapped windows and networked clients. Text-mode equivalent of X11 server + VNC server --------------------------------------------------------------
Twin - a Textmode WINdow environment
--------------------------------------------------------------
Version 0.9.1
Twin is text-based windowing environment with mouse support, window manager,
terminal emulator, networked clients and the ability to attach/detach
mode displays on-the-fly.
It supports a variety of displays:
* plain text terminals: Linux console, twin's own terminal emulator,
and any termcap/ncurses compatible terminal;
* X11, where it can be used as a multi-window xterm;
* itself (you can display a twin on another twin);
* twdisplay, a general network-transparent display client, used
to attach/detach more displays on-the-fly.
Currently, twin is tested on Linux (i386, x86_64, arm, arm64, PowerPC, Alpha, Sparc),
on macOS (x86_64, arm64), on FreeBSD (i386, x86_64) and on Android (arm64 both on termux and UserLand).
I had yet no chance to seriously test it on other systems.
The following screenshot shows an example of twin with various clients:

Documentation
--------------------------------------------------------------
[Tutorial](docs/Tutorial)
A quite complete tour of twin features: the user interface,
how to use twin clients, compression, attaching/detaching
displays, fonts. It also contains installation instructions
and some caveats for system administrators.
[COPYING](COPYING)
License: twin server and clients are GPL'ed software.
[COPYING.LIB](COPYING.LIB)
Library license: the libraries libtutf, libtw
are LGPL'ed software.
[INSTALL](INSTALL)
Quick compile/install guide.
[twinrc](twinrc)
A detailed example of ~/.config/twin/twinrc look-n-feel configuration file.
The following documentation is useful mostly to developers:
[Configure](docs/Configure)
Description of twin configuration options with the meaning
of every single one.
[README.git](README.git)
Hints to build twin from GIT repository.
[README.porting](README.porting)
Tips and warnings to compile twin on unsupported OSes.
[libtw.txt](docs/libtw.txt)
reference API for programmers who want to write twin clients (INCOMPLETE).
[libtw++.txt](docs/libtw++.txt)
reference API for programmers who want to write twin C++ clients (INCOMPLETE).
--------------------------------------------------------------
Getting twin
Since you are reading this README, you probably already have it,
anyway twin can be downloaded from
https://github.com/cosmos72/twin
--------------------------------------------------------------
Building and installing twin
For detailed instructions about compiling and installing twin,
see sections 3 and 4 of the file [docs/Tutorial](docs/Tutorial)
For the impatient, it basically reduces to
```
./configure
make
```
then run as root
```
make install
```
on Linux, also remember to run as root:
```
ldconfig
```
on FreeBSD instead, remember to run as root:
```
ldconfig -R
```
To compile twin you need the following programs installed
on your system:
* a Bourne-shell or compatible (for example bash, dash, ash...)
* make (most variants are supported: GNU make, BSD make...)
* an ANSI C compiler (for example gcc or clang)
Note: it is STRONGLY recommended to install at least the following packages before compiling twin
(the exact names depend on the operating system or Linux distribution):
* x11-dev - may be named x11-devel, libx11-dev ...
* xft-dev - may be named xft-devel, libxft-dev ...
* ncurses-dev - may be named ncurses-devel, libncurses-dev ...
* zlib-dev - may be named zlib1g-dev, zlib-devel, libzlib-dev ...
On Linux, it is STRONGLY recommended to also install the following package before compiling twin:
* gpm-dev - may be named gpm-devel, libgpm-dev ...
For a discussion about MANUALLY configuring twin (almost never necessary),
see the file [docs/Configure](docs/Configure).
-- WARNING: if you manually enable options that were disabled by `./configure',
build will almost certainly fail! --
--------------------------------------------------------------
Other topics:
See the rest of the documentation, starting from the [Tutorial](docs/Tutorial)
Greetings,
Massimiliano Ghilardi
", Assign "at most 3 tags" to the expected json: {"id":"14041","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"