kbin isn't even classed as beta yet, it's early alpha. There is LOTS of work still to come - which is part of the excitement. The fact that it even works as well as it does right now - is a good indicator of things to come.
asjmcguire
joined 1 year ago
Ernest gave similar figures yesterday in his post on /m/kbinMeta
https://kbin.social/m/kbinMeta/t/68541/kbin-server-update-or-how-the-server-didn-t-blow-up
Reddit: You broke the actual law. So we will ban you for 3 days.
What?!
(Note I am not suggesting you really did break the law, just that Reddit are claiming you did something - that would be actually breaking the real law)
Kbin is built around the idea of magazines, any content that arrives that is not part of a magazine, is added to the default magazine "random" so that's likely where the posts are going, I'm not sure if they will be under threads or microblog though, I think threads because it's a video - but I'd check both places to be sure.
Yes you can follow from Mastodon or anywhere. It's just another federated post.
Shouldn't fundamentally be much different to seti@home, boinc etc. Break a video into chunks, and let multiple computers encode a chunk each. If the chunks were small enough, most people probably wouldn't even realise their computer had just encoded a chunk of video
I suspect these 2 issues are the biggest problem:
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendations.
Feeds should not be served with the "application/xhtml+xml" media type
line 2, column 7357: Missing atom:link with rel="self"
The minimalistic content isn't a huge issue for me, as FreshRSS (and others, like TinyTinyRSS) will simply fetch the content from the link in the feed
Confirmed. However I can copy the @channel@instance and paste it into the kbin search and subscribe that way, eg: @ internet_famous @ poast.tv (remove the spaces)
Next step - should be a server that simply coordinates video transcoding, and users can run an application on their computer which will do the transcoding when it's idle and deliver the transcoded video back to the server. Like the rest of the Fediverse, make the community actually part of the community. I'm sure many of us would be happy to donate spare CPU time.
Yes I remember having a look at that the other day and browsing through all the POST requests that server received from other servers.... And thinking I'm not sure this is supposed to be publicly available...
The biggest reason I'm here, is Ernest. Getting in when a project is just getting off the ground, let's users have some say about the direction of things and features. And Ernest is very responsive to the community and asking for feedback. That's exciting, and makes the whole thing feel more of a community.
So I'm a bit confused by the last part of this post. The protocol is definitely more than a year old, ActivityPub is not new. By any means. And ActivityPub builds on top of protocols that came before it.
https://www.w3.org/TR/activitypub/
https://www.w3.org/TR/activitystreams-core/
http://martin.atkins.me.uk/activity-streams/
As for the posts that appear in the /m/random magazine, they are basically the same as looking at the federated tab on Mastodon - they are posts that arrive here, because someone else on this server follows that person, or they were written by someone on this server. No posts will magically appear on the server without someone here actively following either a person or a community on a remote server. They appear in random, because they are not attached to a magazine, though if they use a hashtag that does track that hashtag, then they will be added to the microblogging tab of that magazine, instead of being shoved in /m/random