Git SHA 45.77.39.149 of GoNix boots up okay in Vultr which is good 😅 But I'm missing a few things, and I'm not sure if networking came up 😂Need to build equivalents for:
-
ip addr show or ifconfig-
pingAt the very least 😂
Git SHA 45.77.39.149 of GoNix boots up okay in Vultr which is good 😅 But I'm missing a few things, and I'm not sure if networking came up 😂Need to build equivalents for:
-
ip addr show or ifconfig-
pingAt the very least 😂
This is _really_ interesting 😎
This is _really_ interesting 😎
Came across this today. Interesting take on "Social Media", if you read about it you'll see a familiar set of values and concepts not too different from Yarn.social 👌
Tried to "Signup" but quickly realised I would not be able to post without an "Invite Code", what a shame 😅
Anyway, I _think_ it's cool and interesting to see more concerted efforts to bring back the "good" in "social media" like it used to be back when it all started with blogs and status updates (remember Finger, Status.net, etc? 😂)
Speaking of which @mckinley how did we go with the other one we found the other day and integrating it with the Twtxt spec and some of the Yarn.social extensions? -- I _feel_ like we should try to do the same with CoHost too -- But at this point I'm not completely sure how to reach out to these three that are running this thing 🤔
Came across this today. Interesting take on "Social Media", if you read about it you'll see a familiar set of values and concepts not too different from Yarn.social 👌
Tried to "Signup" but quickly realised I would not be able to post without an "Invite Code", what a shame 😅
Anyway, I _think_ it's cool and interesting to see more concerted efforts to bring back the "good" in "social media" like it used to be back when it all started with blogs and status updates (remember Finger, Status.net, etc? 😂)
Speaking of which @mckinley how did we go with the other one we found the other day and integrating it with the Twtxt spec and some of the Yarn.social extensions? -- I _feel_ like we should try to do the same with CoHost too -- But at this point I'm not completely sure how to reach out to these three that are running this thing 🤔
- And finally if you need High Availability or a Server<->Client model there is the builtin
bitcaskd which provides a Redis-compatible API for a server/client model or the bitraft which provides Raft-based HA with a Redis-compatible API.
- And finally if you need High Availability or a Server<->Client model there is the builtin
bitcaskd which provides a Redis-compatible API for a server/client model or the bitraft which provides Raft-based HA with a Redis-compatible API.
yarnd) you _should_ know some things up front:- Be aware of a design flaw / bug #238 whereby your program will deadlock if you attempt to do
.Get()(s) inside of a .Scan() or .Fold(). This is a known problem, so avoid doing this. The work-around is to copy the keys you want to work with, then perform your operations on them separately.With that out of the way:
Hopefully most of the information on the README will be enough to get you started and understand performance characteristics and the overall API.
Couple of additional things to note:
- There export/dump commands to help you debug your database. As well as import/restore the other way around.
For example, I use this frequently:
h
$ bitcask -p ./dinofs.db dump | jq '. | map_values(@base64d)'
...continued...
yarnd) you _should_ know some things up front:- Be aware of a design flaw / bug #238 whereby your program will deadlock if you attempt to do
.Get()(s) inside of a .Scan() or .Fold(). This is a known problem, so avoid doing this. The work-around is to copy the keys you want to work with, then perform your operations on them separately.With that out of the way:
Hopefully most of the information on the README will be enough to get you started and understand performance characteristics and the overall API.
Couple of additional things to note:
- There export/dump commands to help you debug your database. As well as import/restore the other way around.
For example, I use this frequently:
h
$ bitcask -p ./dinofs.db dump | jq '. | map_values(@base64d)'
...continued...
> Maybe long-term: OAuth/etc. But that goes against the rule of simplicity and
puts a big hole in the privacy part.
I'd recommend implementing IndieAuth. You can even test against _any_
yarnd instance out there as they're all valid IndieAuth providers (or one locally even)
> Maybe long-term: OAuth/etc. But that goes against the rule of simplicity and
puts a big hole in the privacy part.
I'd recommend implementing IndieAuth. You can even test against _any_
yarnd instance out there as they're all valid IndieAuth providers (or one locally even)
Recommend Bitcask of course 😅 Or Badger or Bolt
Recommend Bitcask of course 😅 Or Badger or Bolt
> The thing yarnd uses seems a bit odd to Lyse.
I didn't choose it 😅 I have no experience in this kind of thing 😂
> The thing yarnd uses seems a bit odd to Lyse.
I didn't choose it 😅 I have no experience in this kind of thing 😂