danieloaks

9 ms·

1.
Where is a VPN service useful?(blog.danieloaks.net)
3 points by danieloaks 3y ago|0 comments
2.
by danieloaks 5y ago
terminal-wise, irssi and weechat are the traditional ones recommended these days. but there's a couple newer ones like catgirl: https://git.causal.agency/catgirl/about/ and some rust ones out there. GUI-wise
3.
by danieloaks 5y ago
Yeah we didn't need to agree in writing because I didn't sign anything giving them access, control, ownership, or anything else over my IRC projects. They offered to purchase one of them at one point, but I respectfully declined.
4.
by danieloaks 5y ago
Ah! So what we have right now is a websocket API (so clients can speak IRC via websockets), and our default config basically turns the ircd into a 'bouncer' (it automatically stays online all the time, caches message history, play
5.
by danieloaks 5y ago
inspircd++ Sadie and everyone who works on insp are great too <3
6.
by danieloaks 5y ago
It depends. There's a lot of people on/around IRC who really like it (see libera and all the other networks), and yeah there definitely are people spinning up new smaller networks. Especially with things like https://sr
7.
by danieloaks 5y ago
To be fair there was also collaboration between PIA and Linux Mint while I worked at PIA. That'd probably be a question best answered by the Mint people who're involved
8.
by danieloaks 5y ago
Oh haha, hey! I was employed by Andrew across a fair few of his companies (I didn't know Shells.com was owned by him while I was working there though). Buuuut this is entirely unrelated to him, same as my other project https:/&#x
9.
by danieloaks 5y ago
For what it's worth, we've been throwing around a websocket standard that should be supported across a range of servers. On the decoupling sessions from the TCP connection side, the server that I work on (Oragono https:/&#x2
10.
by danieloaks 5y ago
I can't speak for their possible ircd transition plans but OFTC's been working on https://solanum.chat which has a wide range of IRCv3 support.
11.
by danieloaks 7y ago
Yeah moved away from Ruby a while back. Took a little while to stabilise but the new app is a lot better these days.
12.
by danieloaks 8y ago
For the most part, the Foundation's just a project to support existing projects and developers who use the IRC protocol. This can mean providing financial support, access to more business-oriented resources like designers/legal&#x
13.
by danieloaks 9y ago
Can't speak for software but in the case of these specs, 'Modern' in the title pokes fun at the fact that the core protocol specifications most people refer to are around 25 and 18 years old, respectively. RFC 1459, very comm
14.
by danieloaks 9y ago
For what it's worth, there's been a bunch of work around backlogs (to simplify bouncers, though if more niche IRCds wanted to incorporate it natively that'd work too). CTCP isn't great, but the simplified CTCP I-D improv
15.
by danieloaks 9y ago
These specifications just capture how the IRC protocol currently operates, so that isn't described here (isn't widespread afaict, and there isn't a clear 'winner' in terms of implementations/mindshare). The iss
16.
by danieloaks 9y ago
Yep, pretty much. Unfortunately the protocol's gotten fairly complex without standardisation to keep everyone on the same track. I do my best to simplify the text where I can, but a little more in-depth and correct is better than somet
17.
by danieloaks 9y ago
Thanks, I'm glad it's useful! Feel free to check out this page for some other useful links if you dev on it in the future: https://ircdocs.horse/info/ :)
18.
by danieloaks 9y ago
The first page I wrote when I was making the site was this one ( https://ircdocs.horse/specs/ ) – and the initial drafts were a fair bit screechier than what's there now. I wanted people to know that everything on i
19.
by danieloaks 9y ago
Yeah, I admit the title's not great. I'll update it in the next few days, thanks for the feedback :)
20.
by danieloaks 9y ago
Thanks for posting this here! I will admit, it's hard to know when to start posting it around, but this is already a fair bit more accurate than the traditional RFCs in a lot of ways. It's also lead to an Internet-Draft around CTC
21.
by danieloaks 9y ago
This project (ircdocs) works in tandem with IRCv3. ircdocs tends to focus on currently-implemented stuff (such as the linked Modern docs), where v3 focuses more on establishing rough consensus around new specifications and features.
22.
by danieloaks 10y ago
For now, yeah. Devs from various servers are experimenting with alternate s2s protocols aiming to solve this though.
23.
by danieloaks 10y ago
Standardisation is weird in IRC. From what I've seen, most of it that has happened has been the result of one group implementing their custom command/extension and then a bunch of other vendors implementing it in the same way (as
24.
by danieloaks 10y ago
That's a really interesting look at the politics between those two. Applies to some stuff I'm involved in too. Useful link, thanks very much for sharing!
25.
by danieloaks 11y ago
Same over here in Aus, those are standard hours for most every school I've seen.
26.
by danieloaks 11y ago
The main way is the "Category: Standards Track" part at the top. There are a few different categories: Experimental, Informational, Historic, and Standards Track. This may not be 100% accurate, but basically: Anyone can submit an
27.
by danieloaks 11y ago
Just have to say, thank you very much for creating this. Use it every for every single new repo I setup, saves loads of time. It's just awesome!
28.
by danieloaks 11y ago
They're not a part of archive.org (just a totally separate group with similar interests, lead by Jason Scott). The specific project page is here: http://archiveteam.org/index.php?title=SourceForge The best place to pop
29.
by danieloaks 11y ago
Ditto, Explore is cool. Regarding the project itself, the license is strange, but it's a nice little userscript.
30.
by danieloaks 11y ago
I use <C-s> for my local machine, and I make the servers I login to use <C-a>. I bind the caps-lock key to ctrl, so it works out pretty well, and lets me work with both local and remote contexts at the same time fairly nicely.

More ›