convos
mu
convos | mu | |
---|---|---|
17 | 29 | |
1,006 | 1,344 | |
0.5% | - | |
8.4 | 4.3 | |
20 days ago | 5 months ago | |
Perl | Assembly | |
Artistic License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
convos
-
Show HN: GodotOS: A Fake Operating System Interface Made in the Godot Engine
Excellent idea! You'll have a mature, open standard protocol under the hood, with no vendor lock-in, excellent extensibility, and great modern frontends like The Lounge (https://thelounge.chat/) or Convos (https://convos.chat/) to choose from (and you can choose).
-
Wave of Spam Hits IRC
And UnrealIRCD still rocks. For a quick-and-dirty setup I've deploy ng-ircd but Unreal has always been my go-to for anything serious. If nothing else it can be useful as a backup or internal platform during the rare events that Slack or Discord are having an incident. The common complaint is a lack of channel back-log but it can be front-ended with TheLounge [1] or Convos [2]. I personally prefer to handle that with gnu screen or tmux and WeeChat [3].
[1] - https://github.com/thelounge
[2] - https://github.com/convos-chat/convos/
[3] - https://weechat.org/
-
Matrix 2.0: How weβre making Matrix go voom
For the other layers one can front-end IRC with TheLounge [1][2] or Convos [3][4]. TheLounge only persists history in private mode meaning that users are created in that front-end and chat messages are in Redis. For small networks or groups of friends this is probably fine.
Notably missing is voice chat. I use the Mumble client [5] with the Murmur or uMurmur [6] server which is light-weight enough to run on ones home router. I use it on Alpine Linux, works great. It's not a shiny and attention grabbing as Discord but probably fine for everyone else. For people to create their own voice channels would require the full-blown Murmur server.
[1] - https://github.com/thelounge
[2] - https://thelounge.chat/
[3] - https://github.com/convos-chat/convos/
[4] - https://convos.chat/
[5] - https://www.mumble.info/
[6] - https://github.com/umurmur/umurmur/wiki/Configuration
-
IRCv3 2022 Spec round-up
FWIW TheLounge [1] and Convos [2] can front-end an IRC server giving it much of the look of a modern client and also chat persistence when using TheLounge in private mode. The trade-off in my opinion is scalability. With a bog standard IRCD I can handle tens of thousands of clients per node. Adding web persistent chat adds memory usage.
[1] - https://github.com/thelounge https://thelounge.chat/
[2] - https://github.com/convos-chat/convos/ https://convos.chat/
-
Eww: ElKowars wacky widgets
IRC is a mature, extensible, open protocol, with a wide variety of server and client implementations to suit many use cases, servers can be self-hosted and federated, and modern web-based clients like The Lounge or Convos offer a user experience equivalent to Discord, Slack, etc.
- Show HN: Convos Self Hosted IRC Web Client
-
Looking for OSS version of Teams For Buisnesses
Standard IRC with a web interface like The Lounge or Convos
-
Eric July - Discord "goes woke", begins banning "medical misinformation".
And there are some great web-based clients like the Lounge and Convos that offer an equivalent UX to Discord or Slack, are open-source, self-hostable, and based on a mature, reliable, and extensible open protocol.
-
IRC client with web interface?
Take a look at convos to see if it fits your needs: https://convos.chat/
-
Simplicity of IRC
There are web front-ends to IRC that can mitigate message loss without having to run bouncers. Convos [1] and TheLounge [2] come to mind but there are others [3]
[1] - https://convos.chat/
[2] - https://thelounge.chat/
[3] - https://www.ilmarilauhakangas.fi/irc_technology_news_from_th...
mu
-
Damn Small Linux 2024
Depending on how minimal a distribution you want, a few years ago I had a way to take a single ELF binary created by my computing stack built up from machine code (https://github.com/akkartik/mu) and package it up with just a linux kernel and syslinux (whatever _that_ is) to create a bootable disk image I could then ship to a cloud server (https://akkartik.name/post/iso-on-linode, though I don't use Linode anymore these days) and run on a VPS to create a truly minimal webserver. If this seems at all relevant I'd be happy to answer questions or help out.
- Ask HN: Good Books on Philosophy of Engineering
-
x86-64 Assembly Language Programming with Ubuntu by Ed Jorgensen
This was the thinking behind my https://github.com/akkartik/mu
- Show HN: FocusedEdit β a classic Macintosh to web browser shared text editor
-
Plain Text. With Lines
Yes thank you, I was indeed alluding to https://github.com/akkartik/mu. Perhaps a more precise term would be "software stack".
-
Inferno: A small operating system for building crossplatform distributed systems
I built a computer with its own languages, and I consider it to be _less_ cognitive load when everything is in 1/2/3 languages. I don't have to worry that the next program I want to read the sources will require "Go, Rust, C++, JS/TS, Python, Java, etc."
There are other metrics to consider besides your notions of cognitive load and productivity. Inferno predates most of the languages on your list. My computer (https://github.com/akkartik/mu) uses custom languages because I was able to design them to minimize total LoC, and to ensure the dependency graph has no cycles (unlike all of the conventional software stack, at least until https://www.gnu.org/software/mes connects up all the dots).
- Llisp: Lisp in Lisp
-
10 Years Against Division of Labor in Software
"Separation of concerns is a hard-won insight."
Absolutely. I'm arguing for separating just concerns, without entangling them with considerations of people.
It's certainly reasonable to consider my projects toy. I consider them research:
* https://github.com/akkartik/mu
* https://github.com/akkartik/teliva
"The idea that projects should take source copies instead of library dependencies is just kind of nuts..."
The idea that projects should take copies seems about symmetric to me with taking pointers. Call by value vs call by reference. We just haven't had 50 years of tooling to support copies. Where would we be by now if we had devoted equal resources to both branches?
"...at least for large libraries."
How are these large libraries going for ya? Log4j wasn't exactly a shining example of the human race at its best. We're trying to run before we can walk.
-
My self-hosting infrastructure, fully automated
I still believe :) I'm looking not for an economic argument but for a strategic one. I think[1] a self-hosted setup with minimal dependencies can be more resilient than a conventional one, whether with a vendor or self-hosted.
https://sandstorm.io got a lot right. I wish they'd paid more attention to upgrade burdens.
[1] https://github.com/akkartik/mu
-
My 486 Server
I'm very interested in the network stack, having explored it for a while for https://github.com/akkartik/mu before giving up. What sort of network card do you support?
What are some alternatives?
LANraragi - Web application for archival and reading of manga/doujinshi. Lightweight and Docker-ready for NAS/servers.
cosmopolitan - build-once run-anywhere c library
The Lounge - π¬ β Modern, responsive, cross-platform, self-hosted web IRC client
mtpng - A parallelized PNG encoder in Rust
DFeed - D news aggregator, newsgroup client, web newsreader and IRC bot
collapseos - Bootstrap post-collapse technology
slackcat - Post to Slack from stdin
mirage - MirageOS is a library operating system that constructs unikernels
spcss - A simple, minimal, classless stylesheet for simple HTML pages
librope - UTF-8 rope library for C
Kiwi IRC - π₯ Next generation of the Kiwi IRC web client
teliva - Fork of Lua 5.1 to encourage end-user programming