#koype — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #koype, aggregated by home.social.
-
Going to add more instructions but running #Koype is as simple as pulling down a Docker container now! https://hub.docker.com/r/blackaf/koype is going to be the canonical place for pulling it.
`docker pull blackaf/koype` :)
-
alright bet
So @zee and I are going to go live. Largely going to look into #Koype and kinda winging it (lol not really)
Pull up at 9 PM PDT to https://twitch.tv/jackyalcine
-
@kensanata For a while, I considered using diaspora* to write long-form blog posts (I didn't though), but the diaspora* instance I signed up on disappeared without notice taking my account down with it. 😥
Sticking with good old blogs for now. POSSE FTW I guess.
I should probably take a look at @jalcine 's koype project sometime.
https://koype.net/ -
I want to make hosting for #koype accessible for all but I also need to make sure I keep the servers running. I keep looking at Dat + Multi-writer support as a potential answer for this. But I'd also would need Dat available either in Elixir or build some kind of syndication tool between Dat and Koype.
-
Hey there! If you wanna keep me moving on things like #activitydesk or #koype; let @fosstodon know! https://donations.fosstodon.org/index.php/241929?lang=en
-
That's for #activitydesk. I need to really look into stuff for #koype soon.
-
-
I think the "only" thing about AP so far that's been interesting for me is that it has a concept of "closed" messages (aka things that won't appear on the timeline without authentication). That's something that's been thought about in the IndieWeb world (https://indieweb.org/private_posts) and tbh if a implementation comes out before I get some basic AP support into #Koype, I might not bother with AP
-
working on figuring out release builds for #koype so I can make it easier to share / build / test for people
-
That said, I'm overdue for a blog post update about #koype and its place in the #fediverse.
I have to be honest with y'all - it's more or less a CMS that's socially inclined, lol.
-
Lmfao my personal server just automatically restarted just as I was attempting to federate some posts from #koype
-
I don't know where I should hold chat about #koype (like live chat). I think I'm going to forgo that and just make a Discourse instance somewhere
-
I just need to do the following now:
- get tests in order
- get user docs in shape
- get dev docs in shape
- build docker imagesthen I'll tag and release then do the following:
- move https://koype.net to run on #koype and be the authority of its info re: content -
#koype soooooooooooooooooooooooooooooooooooooooooooooooooooooooooooon lol
-
yeah I might just have to work on getting native AP support into #Koype.
-
For those of y'all interested in #Koype, I've made a survey to get some thoughts to help rear in some product direction I have for it. https://blackaf.typeform.com/to/l7fKGo
-
Nah, Erlang is freaking amazing. It comes with a decompression library for tarballs and Zip files. That's making the logic for downloading new themes into #Koype SO much easier.
Now I'm wondering how many extra Hex packages I pull when I can leverage system libraries.
https://v2.jacky.wtf/post/a69df41c-4582-47f8-ae40-fd9b2dee5453
-
Hey in case you missed it, #Koype moved from my personal Git server at https://git.jacky.wt/indieweb/koype to https://gitlab.com/black.af/koype. I'm still moving the issue to Gitlab but feel free to check it out!
-
Took a bit of work but I’ve moved #Koype from my personal Git server over to the umbrella organization for @blackaf on Gitlab. This’ll be the more communal place for the project.
https://v2.jacky.wtf/post/4c0cc60a-179a-442e-bad3-af5511ecf49a
-
I finally did it. #Koype has support for custom themes.
https://v2.jacky.wtf/post/4453b88d-8a33-4b07-9bae-61a9fb08d15e
-
-
Took me like 1hr30mins to add a bunch of tests (acceptance and unit) for TOTP secret rotation (a new feature in #Koype) - all live! Recorded here on Twitch. Maybe in the future, I’ll run it live from my own server!
(read more: https://v2.jacky.wtf/post/e0a176b2-5e40-4389-b444-5b5f32fc25f5)
-
ohai! I decided to live-code some stuff I'm working on for #Koype (namely cycling TOTP secrets when they've expired) http://twitch.tv/jackyalcine/
-
updated the INSTALL docs for #Koype over at https://docs.koype.net/dev/install/
-
ugh I wanna show y'all want I'm working on for #Koype but this actually has to be a 'secret' of sorts
-
I just became a Patreon of @jalcine . He's the first person I've ever backed on that platform.
https://www.patreon.com/jackyalcine
He's generous (quickly offered to host a video on PeerTube for me, answers questions on Mastodon regularly, etc.) and I love the way he is tying together #intersectional politics with #FreeSoftware and the #IndieWeb.
He's building #Koype a personal website with IndieWeb features baked in. It's taking a user-centered approach, intending to be as easy as Wordpress.
-
Going to see if I can optimize #Koype for Heroku-buildpack style deploys. I use that via Dokku for my personal and work sites. Might be interesting to use that for Erlang binary deploys as well.
-
shit someone on here emailed me about building #Koype.
that said, if you do wanna try your hand at https://git.jacky.wtf/indieweb/koype/src/branch/develop/INSTALL.markdown
-
One thing I'm eyeballing for the future with #Koype is to literally backfill _all_ of my data from silos and then doing a edit/delete of the other copies. I'm just wondering if the tool would be useful to other people. It'd be converting everything into #Microformats2 friendly information.
-
Getting closer to having #Koype more #indieweb compliant. I'm using Indigenous (https://indigenous.adobe.pub) for Android to handle mobile posting and Quill (https://quill.p3k.io) to handle desktop posting. So far, it's a little janky.
Once I get proper JF2 storage, then I can probably have simple MF2 markup (and maybe squeeze in some other markup formats?) in there.
After that, I can either look into making it simpler to deploy/turn-key host or look into adding #litepub support.