Artificial Intelligence AI LLM Large Language Models Table of Contents TOC

Artificial Intelligence AI LLM Large Language Models Table of Contents TOC Artificial Intelligence AI LLM Large Language Models Table of Contents TOC Page Search: eXtP7rp —————————————————————————————————— Artificial Intelligence AI Questions – Creative questions to accelerate learning Local Artificial Intelligence AI Search On a Website OpenAI Embeddings and Vector Databases Crash Course Read more…

OpenAI Embeddings and Vector Databases Crash Course

Summary

A quick run thru of vectorized databases.   He goes a bit quick.   Looks like the video is from 2 years ago so the free online tools he used might not still be available.  Might have to substitute others.

  • Demonstrates how words and phrases can be vectorized –  { how does this process get done? Math please }  – he uses OpenAI to generate.
  • Demonstrates storing vectorized phases into a vector database that consists of:   Phrase ,  Vectorized ( Phrase ) —> SQL:  Text , Blob 
  • Creates a search phrase –> Vectorize ( search phase ) and use it to search against the SQL Vectrorized ( Phrase ).  The search results are returned in descending order of match.  { how does the match get calculated?} 

Tools Used

  • Postman
  • GAI: what is postman software
  • Postman is a widely used API (Application Programming Interface) development platform that allows developers to design, build, test, document, and share APIs. It acts as an API client, enabling users to send various HTTP requests (GET, POST, PUT, DELETE) to web services and analyze responses, supporting REST, SOAP, and GraphQL. 
  • GAI: is there an open source version of postman for ubuntu
  • Yes, there are several open-source, offline-friendly Postman alternatives for Ubuntu that offer similar API testing functionality without requiring cloud accounts. The top recommendations include Bruno, Hoppscotch, and Insomnium, all of which are cross-platform and available on Linux.  ( ….more ) 

Research Links

WordPress Comment Rating System with Up and Down Arrows Like Zerohedge

Research Links

Several WordPress plugins provide comment rating systems featuring up/down arrows (like/dislike) to boost user engagement and collect feedback. The most comprehensive, specialized option for this is wpDiscuz, while general, lighter options include WP-PostRatings and WP ULike

Top Plugins for Comment Up/Down Voting

  • wpDiscuz (Recommended): This plugin replaces the default WordPress comment system. In the "Comment Thread Features" settings, you can enable voting buttons and select up/down arrows as the icon style. It also allows you to hide the downvote button to only show an upvote.
  • WP ULike: This plugin allows users to like or dislike comments (as well as posts and custom post types) with AJAX-based, real-time feedback.
  • WP-PostRatings: While primarily for posts, this plugin can be configured to add rating functionality to comments, offering various styles including up-down arrows, thumbs up/down, and plus-minus.
  • Echo Knowledge Base: This plugin offers a like/dislike feature specifically for knowledge base articles that can be set to use arrows or thumb icons. 

Key Features to Look For

  • AJAX-based: Enables voting without reloading the page.
  • Vote Limits: Protects against spam by limiting votes per IP address or logged-in user.
  • Display Options: Choose between total count (up minus down) or separate counts for up and down votes.
  • Sorting: Allows you to sort comments based on the highest rating. 

Implementation Steps (General Approach)

  1. Install the Plugin: Search for "wpDiscuz" or "WP ULike" in the WordPress Plugins > Add New section.
  2. Configure Settings: Navigate to the plugin settings to enable voting on comments.
  3. Select Style: Choose the arrows (/) icon set.
  4. Configure Privacy: Set restrictions (e.g., logged-in users only or IP-based) to ensure fair voting. 

Installing RocketChat on a Ubuntu Dedicated Server

Research Links

Installing Rocket.Chat on a dedicated Ubuntu server without limitations (meaning, full self-hosting with root access, no user-count restrictions, and full control over data) is best achieved by manual installation using Nginx as a reverse proxy. This method provides maximum performance and customization compared to snap or containerized deployments. The following guide uses MongoDB 6.0, Node.js, and Nginx on Ubuntu 22.04/24.04. 

Prerequisites

  • A dedicated Ubuntu server (22.04 or 24.04 recommended).
  • Root or sudo access.
  • A domain name pointed to your server's IP address (e.g., chat.example.com). 

Goes thru with bullet points hitting the high points

50 User Limit: Unregistered or unregistered-starter workspaces are generally restricted to a maximum of 50 users. If you exceed this limit, the workspace may become read-only.

If installed with snap pack yes.  if installed with docker no.

For high traffic go with the Docker install method

Yes, Rocket.Chat is an open-source communication platform. Its source code is publicly available on GitHub, allowing organizations and developers to inspect, modify, and audit the code to meet their specific needs. 

Yes, Rocket.Chat can be forked to create a new project. As a free and open-source team communication platform, its codebase is openly available on GitHub. 
Key points regarding forking and creating a new project with Rocket.Chat.  MIT license.

1. Mattermost (Best for Slack/Rocket.Chat Clone) 

Mattermost is widely regarded as the best self-hosted, open-source alternative for team collaboration, designed to mimic Slack's functionality while offering complete data control. 

  • True Open Source: It offers a self-managed version (Team Edition) under an open-source license, allowing for unlimited users, messages, and integrations.
  • Key Features: Organized conversations in channels, one-on-one/group messaging, searchable archives, file sharing, and webhooks.
  • Why it's the best clone: It is designed for enterprise-grade security and self-hosting, providing a familiar UI for those switching from Rocket.Chat. 

………..more. 

How does Git and Github Open Source Development Work?

Software 

 

Research Links


Software development using GitHub works by leveraging Git, a distributed version control system, hosted on a web-based platform that adds tools for collaboration, code review, and project management. This system allows multiple developers to work on the same codebase simultaneously without overwriting each other's changes. 

Key Concepts

  • Repository (Repo): A centralized storage location for all project files, folders, and their complete revision history.
  • Git: An open-source, local version control system that tracks changes, manages different versions, and allows developers to work offline.
  • GitHub: The cloud-based hosting platform that stores Git repositories remotely and provides a web interface with additional collaboration features.
  • Branching: The practice of creating a separate, parallel line of development to work on new features or bug fixes safely, without affecting the main codebase until the changes are ready.
  • Commits: Snapshots of a project at a specific point in time, each with an associated message describing the changes made.
  • Pull Requests (PRs): A mechanism for a developer to propose changes from a feature branch to the main branch, allowing for peer review and discussion before integration. 

The Typical GitHub Workflow

The standard process, often referred to as the GitHub flow, involves a series of steps to ensure code quality and seamless collaboration: 

  1. Set Up a Repository: A developer creates a new repository on GitHub or clones an existing one to their local machine using the git clone command.
  2. Create a Branch: A new branch is created from the main or development branch to isolate the new work. This is typically done with a command like git checkout -b <branch-name>.
  3. Make Changes and Commit: The developer works locally, making and saving changes with git add to stage files and git commit to record the changes as a snapshot in their local repository.
  4. Push Changes: The developer uploads their local commits to the remote repository on GitHub using the git push command.
  5. Open a Pull Request (PR): The developer opens a PR on GitHub to propose merging their changes into the main branch. This initiates a discussion and code review process among team members.
  6. Review and Discuss: Other team members review the proposed changes, provide feedback, suggest improvements, and run automated tests using tools like GitHub Actions.
  7. Merge: Once the changes are approved and all conflicts (if any) are resolved, the PR is merged into the main branch, integrating the new code into the project. The feature branch is then often deleted. 

This iterative cycle allows teams to manage complexity, track history, and maintain a stable main codebase while experimenting and collaborating efficiently. The process is further enhanced by integrated tools like Issues for task tracking and GitHub Actions for automation (e.g., automated testing and deployment). 


Gabor Szabo Presentation – Open Source Contribution with Focus on PERL and GetHub Use:1-24-2026

Links

From GS Email – 1/25/2026 – Post Presention Summary

In the first hour I showed some PRs I prepared for MIME::Lite you can watch the video here.

In the second hour we had two pair-programming sessions. In each one a participant was writing the code and I was giving the instructions. Driver-navigator style. Others added valuable comments. This part was also recorded and you can watch it here.

Please follow that channel and "like" the videos. That will help spreading them a bit further.

I've schedule a new event. You can register here.

I also mentioned that in order to make these events sustainable I am looking for corporate sponsors. If you work at a company that uses Perl a lot and you think these sessions are valuable, let's work out a way for them to sponsor the events.

Sponsors will be mentioned on the OSDC web site and in the Perl Weekly. They will also be able to give a list of modules important for them and we'll try to work on those in our sessions.