As part of a study project, I have written a code to play bingo in a very simple version.
The Bingo.java creates a multidimensional matrix with 5×5 fields as an 2D-array, generate 20 (default) pseudo-random numbers with a mersenne-twister (seed: 2^19937 -1), set them in a hashset to be unique between the array, generate 5 more numbers with the same periodity in antoher hashset as the “conférencier” and compare the arrays.
If there are the 5 numbers equal to five numbers in the cardset, the code try to find if the numbers are in a row, a colum or diagonal.
When they are, the code throws a “BINGO”

The Bingo-Code is also ready to analyze the game. It write out where the win was, how many numbers are equal to the drawn numbers and throw a win-boolean.

There is also a CSimulator-Class to play the game automatically and take the information about the last situation. At the end of the iteration, there are methods to build a summary of all things like, equality-counter, wins, row-wins, column-wins, diagonal-wins and the sum of all games.
There is a method to export the values in a csv via ICSVFileWriter which uses the OPEN-CSV Lib.

The code is for free-use only, not for commercial use!
All rights reserved!

All used sources, documents and code-examples are placed in the whitepaper.

The csv-Sheets are generated by the CSimulator-Class and are part of the paper.

OpenCSV Example by mykong.com

OpenCSV Maven Repository

Apache Commons Repository (MersenneTwister)

Doc of JAVA random-Class

Doc of JAVA MersenneTwister-Class

Have a nice day

Alex

Light-Novel-Yuedu-Source

由于多重原因，该项目处在非维护周期内，任何对于书源的无法正常使用等情况的报告issue，在正常情况下都不会进行解决。
目前由 @gongfuture 转入半维护周期，由于能力不足和精力有限等原因，任何对于书源的issue，可能都不会及时进行解决。

欢迎 fork 本仓库修复维护后提出 PR 进行合并。

1. Japan_based_bookSource.json：日轻小说书源文件
2. China_based_bookSource.json：国轻小说书源文件
3. Japanese_original_bookSource.json：日语原版轻小说书源文件
4. All_bookSource.json：日轻、国轻、日轻原版书源合集文件
5. original_comment.md：部分书源完整注释内容（文件位于/old_ver目录下）

1. 使用这些源时不需要额外的净化规则
2. 真白萌、轻小说文库(.cc)、轻小说文库(.net)和有度轻小说登录后方可正常使用
3. 部分源搜索存在问题，建议前往原网站找到所需阅读书籍的网址后，使用阅读APP主页面右上角菜单⠇内的添加网址功能导入书籍
4. 由于该项目处在非维护周期内，不保证书源的有效性
5. 日语原版轻小说书源文件的说明请见：日本Web小说 Book Source
6. 详细原使用说明请见：原README文件

1. 访问Release发行版，复制所需书源/书源合集的JSON文件的链接或者下载对应的文件
2. 打开阅读APP
3. 我的
4. 书源管理
5. 右上角菜单⠇
6. 网络导入/本地导入
7. 复制链接/选择文件
8. 确认

使用规则订阅可便于更新书源

1. 于下方表格复制对应订阅源的链接
2. 打开阅读APP
3. 订阅
4. 规则订阅
5. 右上角添加+
6. 类型选择书源，填写任意名称，于Url框内粘贴链接
7. 确认

1. 发现页、管理书源、编辑书源三处菜单的“登录”均可使用
2. 登录完成后，点击右上方的√，保存返回后即可正常使用。

1. 哔哩轻小说原始源缝合了源仓库里叶落岚起+关耳/乃星改的灰色章节可阅的规则脚本，后续又由酷安@吉王义昊以及柚屿☆等多位进行多次修正维护，但由于原网站使用了各种防爬措施以及字体混淆等，基本无法长期正常使用。
2. 动漫之家的轻小说站如有需要可使用动漫之家Flutter客户端
3. （2022年前）轻之国度(LK)维护完毕后网站有所改动，先前的源全部失效，由酷安@转义字符 以及 酷安@金01461重新写了源，新源可正常使用
4. ESJ的源来自酷安@户山香澄Official的帖子并做了更新，详细使用说明请看另一原帖，发现若需正常使用请科学后登录
5. 本仓库内书源的发现使用了酷安@关耳010225提供的方法进行了美化，大部分源的发现均有进行增加
6. 内容来源于酷安评论区、源仓库，未发帖公开的源均已得到原作者许可公开，并且筛选、修复解析和发现保证使用有效 由于该项目处在非维护周期内，不保证书源的有效性

Monkey programming language compiler designed in Writing A Compiler In Go (Ball, T. 2018). The book is awesome and I believe every programmer who mainly uses dynamically typed languages such as Ruby or Python should read it.

This implementation has added several features to the one implemented in the above book:

• Added support for running a single Monkey script file
• Added support for single-line comments (#)
• Added support for floating-point numbers and their arithmetic (+, -, *, /) and comparison (<, >, ==, !=) operations
• Added support for “greater than or equal to” (>=) and “less than or equal to” (<=) comparison operators
• Added support for logical AND (&&) and OR (||) operators
• Added support for variable assignment statements without let keyword
• Added support for variable reassignment statements
• Added support for setting values into existing arrays and hash maps
• Added support for nil literal

Go 1.12 or later is required to build the compiler.

Install the Monkey compiler using go get command:

$ go get -v -u github.com/skatsuta/monkey-compiler/...

The easiest way to get started is to run REPL:

$ $GOPATH/bin/monkey-compiler
This is the Monkey programming language!
Feel free to type in commands
>> puts("Hello, world!")
Hello, world!
>> 

The compiler also supports running a single Monkey script file (for example script.monkey file):

$ cat script.monkey
puts("Hello, world!")
$ $GOPATH/bin/monkey-compiler script.monkey
Hello, world!

You can define and reassign to variables using = operator. Variables are dynamically typed and can be assigned to objects of any type in Monkey. You can use let keyword when defining variables, but it’s completely optional and there is no difference between with and without let keyword.

Two number types are supported in this implementation: integers and floating-point numbers.

>> let a = 1;  # Assignment with `let` keyword
>> a
1
>> b = 2.5;  # Assignment without `let` keyword
>> b
2.5
>> b = "a";  # Reassignment to b
>> b
a

You can do basic arithmetic and comparison operations for numbers, such as +, -, *, /, <, >, <=, >=, ==, !=, && and ||.

>> let a = 10;
>> let b = a * 2;
>> (a + b) / 2 - 3;
12
>> let c = 2.25;
>> let d = -5.5;
>> b + c * d
7.625
>> a < b
true
>> c == d
false

You can use if and else keywords for conditional expressions. The last value in an executed block is returned from the expression.

>> let a = 10;
>> let b = a * 2;
>> let c = if (b > a) { 99 } else { 100 };
>> c
99
>> let d = if (b > a && c < b) { 199 } else { 200 };
>> d
200

You can define functions using fn keyword. All functions are closures in Monkey and you have to use let along with fn to bind a closure to a variable. Closures close over an environment where they are defined, and are evaluated in the environment when called. The last value in an executed function body is returned as a return value.

>> let multiply = fn(x, y) { x * y };
>> multiply(50 / 2, 1 * 2)
50
>> fn(x) { x + 10 }(10)
20
>> let newAdder = fn(x) { fn(y) { x + y }; };
>> let addTwo = newAdder(2);
>> addTwo(3);
5
>> let sub = fn(a, b) { a - b };
>> let applyFunc = fn(a, b, func) { func(a, b) };
>> applyFunc(10, 2, sub);
8

You can build strings using a pair of double quotes "". Strings are immutable values just like numbers. You can concatenate strings with + operator.

>> let makeGreeter = fn(greeting) { fn(name) { greeting + " " + name + "!" } };
>> let hello = makeGreeter("Hello");
>> hello("John");
Hello John!

You can build arrays using square brackets []. Array literal is [value1, value2, ...]. Arrays can contain values of any type, such as integers, strings, even arrays and functions (closures). To get an element at an index from an array, use array[index] syntax. To set a value at an index in an array to another value, use array[index] = value syntax.

>> let myArray = ["Thorsten", "Ball", 28, fn(x) { x * x }];
>> myArray[0]
Thorsten
>> myArray[4 - 2]
28
>> myArray[3](2);
4
>> myArray[2] = myArray[2] + 1
>> myArray[2]
29

You can build hash maps using curly brackets {}. Hash literal is {key1: value1, key2: value2, ...}. You can use numbers, strings and booleans as keys, and objects of any type as values. To get a value under a key from a hash map, use hash[key] syntax. To set a value under a key in a hash map to another value, use hash[key] = value syntax.

>> let myHash = {"name": "Jimmy", "age": 72, true: "yes, a boolean", 99: "correct, an integer"};
>> myHash["name"]
Jimmy
>> myHash["age"]
72
>> myHash[true]
yes, a boolean
>> myHash[99]
correct, an integer
>> myHash[0] = "right, zero"
>> myHash[0]
right, zero

There are some built-in functions in Monkey.

len built-in function allows you to get the length of strings or arrays. Note that len returns the number of bytes instead of characters for strings.

>> len("hello");
5
>> len("∑");
3
>> let myArray = ["one", "two", "three"];
>> len(myArray)
3

puts built-in function allows you to print out one or more objects to console (i.e. stdout).

>> puts("Hello, World")
Hello, World

first built-in function allows you to get the first element from an array. If the array is empty, first returns nil.

>> let myArray = ["one", "two", "three"];
>> first(myArray)
one
>> first([])
nil

last built-in function allows you to get the last element from an array. If the array is empty, last returns nil.

>> let myArray = ["one", "two", "three"];
>> last(myArray)
three
>> last([])
nil

rest built-in function allows you to create a new array containing all elements of a given array except the first one. If the array is empty, rest returns nil.

>> let myArray = ["one", "two", "three"];
>> rest(myArray)
[two, three]
>> rest([])
nil

push built-in function allows you to add a new element to the end of an existing array. It allocates a new array instead of modifying the given one.

>> let myArray = ["one", "two", "three"];
>> push(myArray, "four")
[one, two, three, four]

Special function, quote, returns an unevaluated code block (think it as an AST). Opposite function to quote, unquote, evaluates code inside quote.

>> quote(2 + 2)
Quote((2 + 2)) # Unevaluated code
>> quote(unquote(1 + 2))
Quote(3)

You can write single-line comments by starting with #. Comments begin with a hash mark (#) and continue to the end of the line. Thery are ignored by the compiler.

>> # This line is just a comment.
>> let a = 1;  # This is an integer.
1

You can define macros using macro keyword. Note that macro definitions must return Quote objects generated from quote function.

# Define `unless` macro which does the opposite to `if`
>> let unless = macro(condition, consequence, alternative) {
     quote(
       if (!(unquote(condition))) {
         unquote(consequence);
       } else {
         unquote(alternative);
       }
     );
   };
>> unless(10 > 5, puts("not greater"), puts("greater"));
greater
nil

Here is a Fibonacci function implemented in Monkey:

let fib = fn(x) {
   if (x <= 1) {
     return x;
   }
   fib(x - 1) + fib(x - 2);
};

let N = 15;
puts(fib(N));

Running the above script gives us:

$ $GOPATH/bin/monkey-compiler fibonacci.monkey
610

Other example Monkey scripts are also placed in examples directory.

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.

The page will reload when you make changes.
You may also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

This paper presents a novel approach to the image inpainting problem using a Generative Adversarial Network (GAN) architecture. We undertook a formal optimization process on an existing EdgeConnect model to improve its performance in a specific domain.

The method proposed in this paper achieved a precision of 28%, recall of 25% and, feature matching loss of 25% while keeping the number of iterations at bare minimum of 175,000. In contrast, EdgeConnect [1] achieved precision of 27%, recall of 25% and, feature matching loss of 45%.
Our model can be useful for various image editing tasks such as image completion, object removal and image restoration, where fine details are crucial. Our approach addresses the limitation of current state-of-the-art models in producing fine detailed images and opens new possibilities for image inpainting applications.
The book is aimed at researchers, practitioners, and students in the fields of computer vision, image processing, and deep learning who are interested in learning about the latest advancements in image inpainting and how to improve current methods.

• Python 3
• PyTorch 1.13
• Eel 0.16
• scikit-image
• opencv 4.5.4.60

• The development was utlizing PyCharm IDE by JetBrains

• Cloning repo

git clone https://github.com/MoshPe/InpaintGAN.git
cd InpaintGAN

• Install Python dependencies

pip install -r requirements.txt

We use HumanFaces datasets. To train the model on the dataset please download the dataset from Kaggle website with your registered user.

Warning The dataset must contain only images with any type of jpg, jpeg, png and the folder path Must be in english !!!

To train the model simply run main.py to open up Eel GUI to operate in system.

• Head over to train tab and configure the model.

  

• Select what model to train, method of masking an image and which edge detection model to utilize

  

• Hit next for further configuring the model

  

• In the following section is the configuration of both generator and discriminator for Edge and Inpaint models accordingly.

  Option	Default	Description
  LR	0.0001	learning rate
  D2G_LR	0.1	discriminator/generator learning rate ratio
  BETA1	0.0	adam optimizer beta1
  BETA2	0.9	adam optimizer beta2
  BATCH_SIZE	8	input batch size
  INPUT_SIZE	256	input image size for training. (0 for original size)
  SIGMA	2	standard deviation of the Gaussian filter used in Canny edge detector (0: random, -1: no edge)
  MAX_ITERS	2e6	maximum number of iterations to train the model
  EDGE_THRESHOLD	0.5	edge detection threshold (0-1)
  L1_LOSS_WEIGHT	1	l1 loss weight
  FM_LOSS_WEIGHT	10	feature-matching loss weight
  STYLE_LOSS_WEIGHT	1	style loss weight
  CONTENT_LOSS_WEIGHT	1	perceptual loss weight
  INPAINT_ADV_LOSS_WEIGHT	0.01	adversarial loss weight
  GAN_LOSS	nsgan	nsgan: non-saturating gan, lsgan: least squares GAN, hinge: hinge loss GAN

  

• Running and training the model.

  
  2023-06-23.12-58-53.online-video-cutter.com.1.mp4
  
  

  
  

In this step the model is utilized for testing. Uploading and image, creating a mask on the uploaded image and run the model on the masked image.

In this section the user is able to draw the mask onto the image for the model to fill.
The user can choose between several thicknesses of lines to draw and clear the drawn lines.

Warning The model was trained upon a square mask so different kind of drawing might won’t return the expected results.

Created and used with the help of Edge-LBAM article and github repo implementation.
Image Inpainting with Edge-guided Learnable Bidirectional Attention Maps
Created and used with the help of EdgeConnect article and github repo implementation.
EdgeConnect: Generative Image Inpainting with Adversarial Edge Learning
EdgeConnect: Structure Guided Image Inpainting using Edge Prediction:

@inproceedings{nazeri2019edgeconnect,
  title={EdgeConnect: Generative Image Inpainting with Adversarial Edge Learning},
  author={Nazeri, Kamyar and Ng, Eric and Joseph, Tony and Qureshi, Faisal and Ebrahimi, Mehran},
  journal={arXiv preprint},
  year={2019},
}

@InProceedings{Nazeri_2019_ICCV,
  title = {EdgeConnect: Structure Guided Image Inpainting using Edge Prediction},
  author = {Nazeri, Kamyar and Ng, Eric and Joseph, Tony and Qureshi, Faisal and Ebrahimi, Mehran},
  booktitle = {The IEEE International Conference on Computer Vision (ICCV) Workshops},
  month = {Oct},
  year = {2019}
}

This is a sample project that demonstrates how to use the Auth0 IDP service to protect RESTful APIs written in Spring Web MVC.

If you are interested in the custom JWT authentication with the Spring WebMvc stack, check spring-webmvc-jwt-sample for more details.

If you are interested in the custom JWT authentication with the Spring WebFlux stack, check spring-reactive-jwt-sample for more details.

• Secures RESTful APIs with Spring Security 5 and Auth0

Make sure you have installed the following software:

• Java 17 +
• Apache Maven 3.x
• Docker

Clone the source code from GitHub.

git clone https://github.com/hantsy/spring-security-auth0-sample

Open a terminal, switch to the root folder of the project, and run the following command to build the whole project.

docker-compose up postgres // start up a postgres
mvn clean install // build the project

Run the application.

mvn spring-boot:run
// or from command line after building
java -jar target/xxx.jar

Any suggestions are welcome, filing an issue or submitting a PR is also highly recommended.

• The Complete Guide to Angular User Authentication with Auth0
• Quickstarts: Single-Page App/Angular

This project was bootstrapped with Create React App.

In the project directory, you can run:

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify

System designated to implement in company easy TV display system.
It allows deploy TVs (endpoints) based on linux (e.g. Raspberry Pi) and manage all of them using single pc.

System consists of 3 main parts:

• Server – that manages whole system
• Endpoint – any display connected to PC
• Client – that allows to manage system (change settings etc.)

Main purpose of this system is to allow you to easily setup display system (e.g. in company) and give you user-friendly access to manage it.

Very important is that, this system is opensource, so you can customize it how you want and adapt to your needs.

Install server on linux machine that will have access to connect to endpoints and will give access for clients to connect. After installation and configuration you need to allow connections on firewall to server port.

Next step will be deploying endpoints. Follow installation process, and after that you can add your endpoints in server configuration. You can also deploy endpoints on the go (when server is running), but you will need to restart server after changing configuration.

Server and Endpoints are using syslog to write some logs. This allows you to verify if everything is working.

Client allows you to manage system. When server starts you will be able to connect to it using client and change configurations. You need to provide address, port and credentials to connect to server.

All new endpoints will use global configuration if config is not found.

To install server daemon you need to build and create default config files. To do that just run below command in repo directory:

sudo make clean install

Server do not require any external libraries

If you don’t want to override your configs use (probably temporary solution):

sudo make clean ndinstall

Next important step will be configuration of basic settings – read here

After that you can simply run tmsd.service. Ex:

systemctl start tmsd

You can verify if everything is correctly running in syslog.

To disable daemon just stop service. Ex:

systemctl stop tmsd

Download installer .msi or portable version from Releases.

• for installer follow simple installation process (by default client is installed in C:\Program Files (x86)\23vbq\TMSC)
• for portable just extract .7z file (dll’s must be in same directory as executable)

If you want to build client by your self you need to download and install Qt, clone repository and open project from CMakeLists.txt.

To deploy your build you can use windeployqt tool which is installed with Qt. It will copy all required libraries to directory with executable. Also you can use AdvancedInstaller template to deploy it in installable package.

To install endpoint application first build it:

sudo make clean install

Or without overriding your existing config:

sudo make clean ndinstall

Next step will be configuration – read here

After configuring endpoint you can add it to server configuration.

To start endpoint you need to add it to your .xinitrc. If you don’t know how to do this here is xinit configuration. Installed binaries are in /usr/bin by default.

To run endpoint application use:

startx

For closing endpoint there are two methods:

• Kill it from shell (ex. pkill tmse)
• Use keyboard shortcut ALT + Q

Linux

Server is responsible for managing the entire system. It’s primary role is to communicate with endpoint to distribute configuration and manage them. The server doesn’t hosts any resources (e.g. images, files). These can be obtained with external solutions like Samba. Server performs various functions including: processing change requests, providing responses to queries, checking the connection with the endpoints, and ensuring that client is always updated with latest configuration.

Server also provides interface to manage configurations, endpoints and server it self with Client application.

Network functions:

• Accepts connection from clients and response to their queries
• Connects to endpoints and sends data to them

Windows

Client application gives end-user ability to easily manage the system. It provides GUI based communication with server, so it is user-friendly. You can check actual status of endpoints, manage global / per endpoint configuration and reload endpoints settings.

Linux

Endpoint allows to display images on TV (any display connected to machine), using X11 library. Its main advantage is that is written in C++, so it allows to obtain low system requirements. That allows you to make low cost and practical display system (e.g. TV connected to Raspberry Pi). Endpoint program gets settings from server. Files to be displayed are obtained from provided path. To make fully centrally managed system (meaning easy access to files on endpoint) you can setup SMB server, mount it on every endpoint and configure path on tv-managing-system server to this mountpoint.

After configuration you can copy your config files to .def files in repo to not be overridden after installing. In future maybe there will be provided some mechanism to not override your files and easily update configs, if new variables will be required.

Server configuration is stored in /etc/tmsd/. Default settings are stored in def files in repo and are copied to desired location when installing.

Server uses two files for it’s configuration:

• settings.cfg – to store basic server socket settings
• authkey – to store authentication key for server (now it is stored in plain text – read here])

File settings.cfg stores configuration of basic server socket settings and also list of endpoints, that server needs to connect to.

In authkey you only need to store your server password (in plain text), that will need be required for clients to connect.

Configuration of each endpoint is stored in /etc/tmsd/epconf/ and is automatically generated by server on changes. By default endpoint configuration is empty struct. Global endpoint configuration is stored in file named [Global Settings].ep.

At this point client do not store any settings. Maybe in future it will be able to save IP, certificates etc.

Endpoint configuration is stored in /etc/tmse. Default settings are stored in def files in repo and are copied to desired location when installing.

Endpoint uses two files for it’s configuration:

• settings.cfg – to store basic settings
• authkey – to store authentication key for server (now it is stored in plain text – read here) NOW IS UNUSED – wait for update

By default endpoint is using feh, but it can be to any image viewer. You can set up any command you want for opening images (through settings.cfg). Opening images is implemented in SlideshowManager::OpenAllImages().

Endpoint do not store major configuration (meaning directory to lookup for images, etc.). It is provided by server when connection occurs. It prevents endpoint from loading old configuration. Endpoint waits for server and then will be able to display desired views. This configuration is stored in EndpointSettings struct in memory.

At this point of developement all connections are not secured (in plain text). Also passwords are stored in plain text.

It is planned to implement hashed passwords and SSL secured connections.

ToDo list: here

SEGFAULT COUNTER: 9

System designated to implement in company easy TV display system.
It allows deploy TVs (endpoints) based on linux (e.g. Raspberry Pi) and manage all of them using single pc.

System consists of 3 main parts:

• Server – that manages whole system
• Endpoint – any display connected to PC
• Client – that allows to manage system (change settings etc.)

Main purpose of this system is to allow you to easily setup display system (e.g. in company) and give you user-friendly access to manage it.

Very important is that, this system is opensource, so you can customize it how you want and adapt to your needs.

Install server on linux machine that will have access to connect to endpoints and will give access for clients to connect. After installation and configuration you need to allow connections on firewall to server port.

Next step will be deploying endpoints. Follow installation process, and after that you can add your endpoints in server configuration. You can also deploy endpoints on the go (when server is running), but you will need to restart server after changing configuration.

Server and Endpoints are using syslog to write some logs. This allows you to verify if everything is working.

Client allows you to manage system. When server starts you will be able to connect to it using client and change configurations. You need to provide address, port and credentials to connect to server.

All new endpoints will use global configuration if config is not found.

To install server daemon you need to build and create default config files. To do that just run below command in repo directory:

sudo make clean install

Server do not require any external libraries

If you don’t want to override your configs use (probably temporary solution):

sudo make clean ndinstall

Next important step will be configuration of basic settings – read here

After that you can simply run tmsd.service. Ex:

systemctl start tmsd

You can verify if everything is correctly running in syslog.

To disable daemon just stop service. Ex:

systemctl stop tmsd

Download installer .msi or portable version from Releases.

• for installer follow simple installation process (by default client is installed in C:\Program Files (x86)\23vbq\TMSC)
• for portable just extract .7z file (dll’s must be in same directory as executable)

If you want to build client by your self you need to download and install Qt, clone repository and open project from CMakeLists.txt.

To deploy your build you can use windeployqt tool which is installed with Qt. It will copy all required libraries to directory with executable. Also you can use AdvancedInstaller template to deploy it in installable package.

To install endpoint application first build it:

sudo make clean install

Or without overriding your existing config:

sudo make clean ndinstall

Next step will be configuration – read here

After configuring endpoint you can add it to server configuration.

To start endpoint you need to add it to your .xinitrc. If you don’t know how to do this here is xinit configuration. Installed binaries are in /usr/bin by default.

To run endpoint application use:

startx

For closing endpoint there are two methods:

• Kill it from shell (ex. pkill tmse)
• Use keyboard shortcut ALT + Q

Linux

Server is responsible for managing the entire system. It’s primary role is to communicate with endpoint to distribute configuration and manage them. The server doesn’t hosts any resources (e.g. images, files). These can be obtained with external solutions like Samba. Server performs various functions including: processing change requests, providing responses to queries, checking the connection with the endpoints, and ensuring that client is always updated with latest configuration.

Server also provides interface to manage configurations, endpoints and server it self with Client application.

Network functions:

• Accepts connection from clients and response to their queries
• Connects to endpoints and sends data to them

Windows

Client application gives end-user ability to easily manage the system. It provides GUI based communication with server, so it is user-friendly. You can check actual status of endpoints, manage global / per endpoint configuration and reload endpoints settings.

Linux

Endpoint allows to display images on TV (any display connected to machine), using X11 library. Its main advantage is that is written in C++, so it allows to obtain low system requirements. That allows you to make low cost and practical display system (e.g. TV connected to Raspberry Pi). Endpoint program gets settings from server. Files to be displayed are obtained from provided path. To make fully centrally managed system (meaning easy access to files on endpoint) you can setup SMB server, mount it on every endpoint and configure path on tv-managing-system server to this mountpoint.

After configuration you can copy your config files to .def files in repo to not be overridden after installing. In future maybe there will be provided some mechanism to not override your files and easily update configs, if new variables will be required.

Server configuration is stored in /etc/tmsd/. Default settings are stored in def files in repo and are copied to desired location when installing.

Server uses two files for it’s configuration:

• settings.cfg – to store basic server socket settings
• authkey – to store authentication key for server (now it is stored in plain text – read here])

File settings.cfg stores configuration of basic server socket settings and also list of endpoints, that server needs to connect to.

In authkey you only need to store your server password (in plain text), that will need be required for clients to connect.

Configuration of each endpoint is stored in /etc/tmsd/epconf/ and is automatically generated by server on changes. By default endpoint configuration is empty struct. Global endpoint configuration is stored in file named [Global Settings].ep.

At this point client do not store any settings. Maybe in future it will be able to save IP, certificates etc.

Endpoint configuration is stored in /etc/tmse. Default settings are stored in def files in repo and are copied to desired location when installing.

Endpoint uses two files for it’s configuration:

• settings.cfg – to store basic settings
• authkey – to store authentication key for server (now it is stored in plain text – read here) NOW IS UNUSED – wait for update

By default endpoint is using feh, but it can be to any image viewer. You can set up any command you want for opening images (through settings.cfg). Opening images is implemented in SlideshowManager::OpenAllImages().

Endpoint do not store major configuration (meaning directory to lookup for images, etc.). It is provided by server when connection occurs. It prevents endpoint from loading old configuration. Endpoint waits for server and then will be able to display desired views. This configuration is stored in EndpointSettings struct in memory.

At this point of developement all connections are not secured (in plain text). Also passwords are stored in plain text.

It is planned to implement hashed passwords and SSL secured connections.

ToDo list: here

SEGFAULT COUNTER: 9

• 🇺🇦 Простий бот повітряних тривог для вашого Discord серверу. Ви можете безкошновно створити власного бота та розмістити його на власному віддаленому сервері (наприклад на Oracle Cloud Free Tier) за допомогою цієї інструкції, або використовувати готове рішення на вашому Discord серверу. Бот використовує стороннє API.
• 🇬🇧 A simple air-raid bot for your Discord server. You can create your own bot for free and place it on your own remote server (e.g. on Oracle Cloud Free Tier) using these instructions, or use a ready-made solution on your Discrod server. Bot uses API.

  $ git clone https://github.com/correaAlex/SirensDiscordBot.git

  $ cd SirensDiscordBot

docker-compose.yml

  MYSQL_USER: yourUserName
  MYSQL_PASSWORD: yourPassword

App.config

  <add key="ConnectionString" value="server=db;port=3306;user=yourUserName;password=yourPassword;database=sirens_bot"/>

  <add key="Token" value="YOUR_TOKEN"/>

  $ sudo docker-compose up

  $ git clone https://github.com/correaAlex/SirensDiscordBot.git

  $ cd SirensDiscordBot

docker-compose.yml

  MYSQL_USER: yourUserName
  MYSQL_PASSWORD: yourPassword

App.config

  <add key="ConnectionString" value="server=db;port=3306;user=yourUserName;password=yourPassword;database=sirens_bot"/>

  <add key="Token" value="YOUR_TOKEN"/>

  $ sudo docker-compose up