Skip to content

parm-is-coding/Commandline-Messaging-System

View on GitHub ↗Related repositories →

Commandline Messaging System written in C that has TCP sockets with TLS encryption via openSSL.

active 2024-12-112024-12-19 (UTC)

Complete coverage26,568 / 26,568 hourly files (100%) · 2 absent upstream2023-08-152026-08-25 (UTC)
Events
24
Pushes
6
Pull requests
2
Issues
10
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 9 days from 2024-12-11 to 2024-12-19. Pushes: 6 total, peak 3 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 10 total, peak 5 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
parm-is-coding18620

Recent activity

Latest issues, pull requests and releases

  • Issue#9parm-is-coding2024-12-12 22:06
    Remove the Extra server.c and client.c files from the remote repo
  • Pull request#10parm-is-coding2024-12-12 22:05
  • Pull request#10parm-is-coding2024-12-12 22:05
  • Issue#9parm-is-coding2024-12-12 01:25
    Remove the Extra server.c and client.c files from the remote repo
  • Issue#8parm-is-coding2024-12-12 00:47
    Encrypt the payload using TLS openSSL
  • Issue#7parm-is-coding2024-12-12 00:45
    Create a GUI for the messaging System
  • Issue#6parm-is-coding2024-12-12 00:33
    convert inet_addr to inet_aton to add error checking of invalid ip addressese
  • Issue#4parm-is-coding2024-12-11 06:24
    set up threads that alternate on the server
  • Issue#4parm-is-coding2024-12-11 01:24
    set up threads that alternate on the server
  • Issue#3parm-is-coding2024-12-11 01:03
    establish a TCP connection between client and server
  • Issue#2parm-is-coding2024-12-11 00:59
    Get input of text working on Client
  • Issue#1parm-is-coding2024-12-11 00:13
    Get TCP Sockets working between Client and Server

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.