Daughter is crazy about #Minecraft.
We played together using the multiplayer feature yesterday and she was over the moon!
Once upon a time, #PageKite supported the Minecraft protocol, to make it easier for people to play with remote friends - but the protocol kept changing and I wasn't hearing much love from users for the feature. Eventually I stopped keeping up, it stopped working.
Last night I coded a fix. It might take me a while to get it deployed, but I feel good about this.
It's another accounting and taxes day!
Therefore, I have sorted out some of my daughter's summer activities, chased my bank on some personal issues, had a nice long chat with my girlfriend, and helped a client with #pagekite integration.
Very productive! Just no progress on the taxes... yet. Need to elevate my stress levels just a wee bit more.
It has been a good, geeky work-week so far. Not much tootin' been busy.
I did some #devops twiddling for #pagekite. Yay SSL certs?
Made more progress on grant applications for #Mailpile.
Studied #Matter (https://en.wikipedia.org/wiki/Matter_(standard) ) a bit, within the context of #esp32 and #micropython development.
I also had multiple naps and stared out the window a lot going HMM.
Now it's time for another window gazing session, before I dive back into #moggie related #OpenPGP work...
#devops #pagekite #mailpile #matter #esp32 #MicroPython #moggie #OpenPGP
@rysiek @nextcloud One of my many fantasies for #PageKite was to create a desktop tool that let you send people links and they could HTTPS upload directly to your desktop.
I even prototyped it, had it sort of working... and then totally failed to ship and promote.
(Downside: a bit slow. Upside: you could see progress real time in a desktop GUI.)
A long-time, trusted client asked me the other day why I prefer to publish my work as #FOSS. Why would I give it away? Aren't I worried people will just steal it and not give me credit?
I told him straight up that it was largely idealism.
But also - for #PageKite, it's a selling point. My company is so small and the bus factor so low, that most sensibly run businesses will hesitate to depend on me.
My code being open source provides a backup plan and an escape route. It's a form of insurance.
Hello world! An #introduction.
I'm Bjarni, an Icelandic coder who mainly writes Python programs and gives them away as open source. My focus is on autonomy and privacy online; mostly relating to email (#mailpile) and the web (#pagekite).
I'm fluent in security (#passcrow), but I'm more excited by creating neat tools and empowering people, than I am in exploits and encryption algos.
I plan to use this account to discuss my work & hopefully connect with folks working on related things. Say hi!
#passcrow #pagekite #mailpile #introduction
So... before I dive in here too much, I guess it's worth asking: Am I on the right instance? Pretty sure the answer is no.
After browsing https://instances.social/ ... I still feel kinda lost.
It seems instances don't really let you sample the local timeline without creating an account. Which is fair enough I guess, but still a speedbump.
I'm looking for folks to chat with about my work: Python, #email security (#mailpile, #pgp) and DIY/embedded hosting (#pagekite, #esp32), #decentralization.
#email #mailpile #pgp #pagekite #esp32 #decentralization
https://purl.org/rzr/privacy# #SOSCON19 #WebThings #IoT #Security is based on #HTTPS #LetsEncrypt #TLS #PageKite #OAuth and #JWT for resources #ACL
#SOSCON19 #webthings #iot #security #https #letsencrypt #tls #pagekite #oauth #jwt #acl
@emacsen
Maybe also have a look at #pagekite (https://pagekite.net/). It has its own (dis)advantages over the VPS+VPN solution
Geeks tend to assume #PageKite is solving the problem "I want to run a local server, but I don't have a public IP address."
This is mostly a misunderstanding.
PageKite is solving the problem "I want to run a local server, but cannot* reconfigure my router**."
*) Or just don't want to.
**) Or my router's router***, or my router's router's router.
***) Or s/router/firewall/g
@CharredStencil Tooting my own horn a bit, but this was part of the concept behind #PageKite - instead of a VPN, it just forwards HTTP or TLS traffic over a tunnel.
The other aspects of the overall design are very similar.
I never did get so far as to package up FOSS social apps with PageKite integrated, for one-click installs, but I am aiming to do that with Mailpile when I have the time and energy...
Woohoo, found and fixed a bug in the #pagekite .net API server!
Will deploy tomorrow probably.
Now, it's time to go to daughter's play school for a summer party!
So, I've got #PageKite tunneling over the Websocket protocol now! The modified relay code is being canaried on a couple of my live relays right now.
That's the low level, super geeky part. The next stage of this project, the "mere matter of Javascript" is much harder.
I need to:
a) Learn enough idiomatic JS culture to write a library I can put in npm.
b) Learn enough JS to know how to write something useful in both browsers and Node.
c) Write pagekite.js
Not a trivial project!
... I feel kinda dumb for not having done this ages ago. Of course, I was distracted by Mailpile. But still.
#PageKite, both as a FOSS project and as a small business might be in a very different place today if I had properly embraced the Node and Electron communities.
Ah well.
Better late than never, right?
I'm hacking on #PageKite a bit, doing something I shoulda done ages ago: making it possible to tunnel over a WebSocket instead of my custom protocol.
I'm only using a custom protocol at all, because PageKite predates websockets. That stopped being a good reason years ago!
Once I get this working, it'll be "a mere matter of Javascript" to have a public web server in your browser... and yes, I remember Opera Unity: its failure convinced me not to bother.
Iodide & Electron changed my mind.
I've been working on the IPv6 support in #PageKite a bit lately.
There are two sides to it: being able to connect to a relay over IPv6 (or not), and making your site reachable (or not) over IPv6.
The former is mostly about connectivity, the latter mostly about DNS responses.
My previous attempts at this had conflated the two, which was dumb and wrong. I'm fixing that.
It's been a #PageKite day!
I've fixed bugs and merged PRs in https://github.com/pagekite/libpagekite/ , answered support e-mails and questions online, and made some progress on dusting the bit-rot off our IPv6 support.
The latter needs more work; a lot of things get confusing when the same PageKite relay is visible under multiple addresses on what are effectively multiple networks.
This whole two-overlapping-Internets thing kinda sucks...
The #PageKite website seems down https://pagekite.net/ :owo_thanking: @HerraBRE
Trying #pagekite to go fully #selfhosted.
Also came across this... this is definitely a deep rabbit hole 😅 https://github.com/Kickball/awesome-selfhosted/blob/master/README.md