kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev
_whitelogger has joined #sandstorm
frigginglorious has joined #sandstorm
frigginglorious has quit [Read error: Connection reset by peer]
frigginglorious has joined #sandstorm
michaeln3 has quit [Remote host closed the connection]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 260 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 256 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 240 seconds]
frigginglorious has quit [Ping timeout: 240 seconds]
_whitelogger has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 264 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 256 seconds]
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 256 seconds]
larjona has quit [Ping timeout: 256 seconds]
larjona has joined #sandstorm
michaeln3 has joined #sandstorm
michaeln3 has quit [Ping timeout: 265 seconds]
TC01 has quit [Ping timeout: 240 seconds]
<JacobWeisz[m]>
An odd golang stack issue I just hit, which strangely didn't impact the old package, was a complaint about installing out of gopath, despite being symbolic linked into gopath.
<JacobWeisz[m]>
Replacing cd /opt/app in build.sh with the folder /opt/app is linked to in gopath fixed it.
frigginglorious has joined #sandstorm
frigginglorious has quit [Quit: frigginglorious]
frigginglorious has joined #sandstorm
TC01 has joined #sandstorm
<isd>
Is this a new app that you're trying to build with it?
<isd>
Once 1.15 lands I'll update the toolchain; GOPATH is a deprecated mechanism anyway so stuff will probably go a bit smoother if we just default to go modules.
<isd>
I could update it now, but I figure if I wait a bit I get to only do it once.
<JacobWeisz[m]>
I made it build. We're good.
<JacobWeisz[m]>
I did something, don't remember what.
frigginglorious1 has joined #sandstorm
frigginglorious has quit [Ping timeout: 256 seconds]
frigginglorious1 is now known as frigginglorious
ill_logic has joined #sandstorm
<abliss>
GOPATH is deprecated?!
<isd>
I mean, I don't expect they'll drop support anytime soon. But modules are definitely the way to go these days
frigginglorious has quit [Read error: Connection reset by peer]
pie_ has quit [*.net *.split]
pie_ has joined #sandstorm
<JacobWeisz[m]>
So, I'm looking at twtxt, and it'd probably be pretty reasonable to package it, but it'd need something like the proxy for following other people.
<abliss>
For publishing, you could just use a ghost or a gitewb-pages text file.
<abliss>
or a davros grain even
<JacobWeisz[m]>
Well, I'm looking at prologic's twtxt.net. It's a Go app. But yeah I was wondering if web publishing was the best way to get a easily followable URL.
<JacobWeisz[m]>
It'd give us a selfhosted social network that wasn't as challenging to solve as Mastodon, presumably.
<abliss>
i've played with twtxt and honestly i'm not too impressed. for easy following, rss seems better in every respect. twtxt is nice for easy publishing, but it keeps reinventing basic useful concepts badly.
<abliss>
and there's not nearly as much content there as mastodon
<JacobWeisz[m]>
Yeah, it's definitely more rudimentary. Presumably some people like it that way.
<abliss>
i feel the same way about Gemini, which presumably we could also consider hosting
<JacobWeisz[m]>
I found the lack of linking replies to messages irritating when playing with it. But I'd mostly rather a federated social service not pretend to have private messages. And some features of Mastodon annoy a fair bit.