@dannekrose@kilioa.org
@dannekrose@kilioa.org avatar

dannekrose

@dannekrose@kilioa.org

Welcome to my little kbin instance and account.

ゲームが好きです。配信もしています。気軽に楽しくやりましょう。ゲーム以外もいろいろな趣味があります。よろしくお願いします。Playing Games. Streaming Games. Games for everyone. I have some hobbies outside of games, too. Nice to meet you.

(He/Him/His)

#gaming #dnd #twitch #ttrpg #xbox #xboxSeriesX #games #Bilingual #casualGames #ConsoleGaming #dndj #dnd5e #adhd #日本語 #adhd

This profile is from a federated server and may be incomplete. Browse more on the original instance.

dannekrose,
@dannekrose@kilioa.org avatar

@azezeB Some suggestions

  1. Dead By Daylight. 5 people with one being the Killer so you can rotate that if desired.
  2. Halo Infinite multiplayer can do 12 person parties for the “Big” map modes.
  3. I believe Lego Fortnite also lets you have up to 8. It’s more Minecraft and not a Battle Royale at all.
  4. Lethal company modded can support more than 4. That could be lots of fun.
  5. Retro FPS like Quake from various years. Just as a small distraction
dannekrose,
@dannekrose@kilioa.org avatar

@HarkMahlberg

The technical details will determine what can and can't be done, but from the Mastodon documentation:

https://docs.joinmastodon.org/user/moving/

Moving your account is the same as redirecting your account, but it will also irreversibly force everyone to unfollow your current account and follow your new account, if their software supports the Move activity. Your posts will not be moved, due to technical limitations. There is also a 30 day cooldown period in which you cannot migrate again, so be very careful before using this option!

Depending on if k/m/bin receives a "Move" activity, it may be possible to update user blocklists based on the information in the "Move" activity. However, "Move" activity is generally only sent to existing followers. (I don't know all the details on that) Activities are generally sent to an instance to handle, not individual user accounts, though, so I suspect this might not be as big of a hurdle as it might seem.

Short answer: Maybe. Depends on how they "Moved". It wouldn't be simple to implement, however I don't see anything preventing it in this particular case. You should open an Issue for feature request for it. I recommend including the above piece from the Mastodon documentation, however in your issue.

dannekrose,
@dannekrose@kilioa.org avatar

@ReverseModule

As someone who really enjoys PeerTube, I also feel like the technical barriers to it being as popular as other platforms are a bit tougher to overcome.

I would love for it to be more popular. I also know it's really hard to convince content creators and live streamers to embrace it.

I love PeerTube. I have been trying to help the projects however I can. I also know that the economics of moving to PeerTube is quite different. Very few people make money microblogging (Twitter). Very few people make money posting to Reddit.

Streaming on Twitch or YouTube, or making content for YouTube can and for many people does bring in money, though. Creating an ecosystem where viewers are willing to pay, while increasing viewer counts of content so that sponsorships can be more common, all while trying to slowly convince people that we should be supporting things financially that up to now has been "free(not really, but experientially it 'feels' free)" is a lot of work.

I plan on supporting PeerTube as much as I can in the future. I want it to grow. Maybe someday, it will get there. I can hope.

skele_tron, to kbinMeta
skele_tron avatar

KbinFAQ somewhere? What are threads, microblogs etc?

dannekrose,
@dannekrose@kilioa.org avatar

@skele_tron
It’s a little older but the magazine kbinfaqs@kilioa.org has a couple good ones

What's up with "The magazine from the federated server may be incomplete. Browse more on the original instance."? Is this working as intended or is it a bug?

I've been seeing this for quite a bit, and thought it'd resolve itself once CloudFlare was taken off, but I'm still seeing it on many external communities from e.g. Lemmy. Not all posts or comments are visible from Kbin. Any idea on what's going on?...

dannekrose,
@dannekrose@kilioa.org avatar

@Treedrake

One thing that also plays a role is the size of the queues on the different instances. Kbin.social may get things pushed to it, but with queue sizes reaching 500 thousand or more, it takes time to process them.

@Xepher @Chozo

dannekrose,
@dannekrose@kilioa.org avatar

@Treedrake

You're welcome!

Yes, it is working as intended. The idea is that each instance is responsible for pushing content once, then it's the responsibility of the receiving instance to process and display the content to the relevant users/accounts.

As a side note, if everything was "re-pushed" out, the load becomes even more on the "source of truth" for larger communities with wide federation and a lot of new content generated locally and remotely. I could see this being leveraged to take down servers by simply spamming really large communities (with large federation) with small content forcing the "source of truth" to now "re-push" the content to every server that is knows about for every single new comment, or reply, or post.

dannekrose,
@dannekrose@kilioa.org avatar

@Treedrake

Edit: ok, I think I get it. So if someone from a random instance posts to e.g., technology@beehaw.org, and that instance doesn't know about kbin.social, it won't get pushed to this instances representation of the technology@beehaw.org magazine?

Correct. It's only "pushed once" by the instance that the creator's account is on. Of course it will push to the source of truth, but it will only push to other instances it knows are also following that magazine since it doesn't necessarily know all of the instances that follow that magazine. In your example, yes, if the creator of the content (which in this example is an account not on beehaw.org) posts to technology@beehaw.org, their instance will push to beehaw.org and others, but if it doesn't know that kbin.social has any followers of the magazine/community, it won't push to kbin.social.

One other possibility is that the 3rd-party instance does know about kbin.social (for example), but has blocked (defederated with) kbin.social OR kbins.social has blocked that 3rd-party instance, my expectation would be that such content won't show up on kbin.social's "copy" of the community.

dannekrose,
@dannekrose@kilioa.org avatar

@Treedrake

Most replies here are correct. To clarify and summarize:

  1. The source of truth for a magazine/community is the server name that appears after the magazine name.

e.g. kbinMeta@kbin.social <--- the source of truth is kbin.social.
2. ActivityPub and the Fediverse is a "Push" model. What does this mean?

Imagine subscribing to a real-world newspaper or magazine with home delivery(few these days will actually remember this, but try to imagine at least). You will get all new issues delivered to you from the moment you became a subscriber, but you don't get copies of all the newspapers or magazines they have ever printed delivered to you. You only get things moving forward. That's the same with the Fediverse. After you subscribe or follow something, you will get all the new content moving forward, but not what has been created so far.

  1. To extend #2, it's a "push once" model. What does that mean? It means that if I create content from my instance (which is not kbin.social) to the magazine kbinMeta@kbin.social, my content will get pushed to kbin.social. Kbin.social, however, will not "re-push" that content to everyone that kbin.social knows is subscribed to the magazine.

So how does my new content that I created in kbinMeta@kbin.social show up on other instances that are not kbin.social? I thought you said your content only gets pushed once?

Correct. However, it's not quite as simple as my instance pushing just to kbin.social. Strictly speaking, (and this is based on experience with other platforms, not specifically how kbin works since I haven't verified this for kbin 100%) when I create the content, my instance will push to kbin.social and all other instances (not users) that my instance knows are also subscribed to specifically kbinMeta@kbin.social. So my instance actually knows a subset of the instances that are subscribed to kbinMeta@kbin.social and will push the new content to each of those other instances. My instance, however, won't necessarily know all the other instances that are subscribed to kbinMeta@kbin.social. As a result, some instances won't see my new content because it wasn't pushed to them.

  1. As a result, to let users know about this potential gap, not only does it mean that older content doesn't automatically show up, it also means that not necessarily all new content will show up either.

Note on #3: I haven't fully verified this. This statement is based on how other, non-kbin instances handle federation. This is how "likes" work across platforms like Mastodon, Calckey, etc. I see no evidence (yet) that this is any different for kbin.

dannekrose, to kbinfaqs
@dannekrose@kilioa.org avatar

Federation test. Please ignore.

dannekrose, (edited )
@dannekrose@kilioa.org avatar

@Brome

EDIT: I believe actually it's because the thread is of type Link. Did you create it as type "Link?" If so, try recreating it as type "Thread."

dannekrose,
@dannekrose@kilioa.org avatar

@Brome

You're welcome! Sort of. In general, Calckey and others (Mastodon as well) don't handle non-Note-type data very robustly. Those are used a lot with groups and Calckey doesn't really understand groups very well. It's know and it's on the road map, but I don't think this one example is a high priority at the moment (Link-type threads)

dannekrose,
@dannekrose@kilioa.org avatar

@HamSwagwich

This is a result of the original design. Kbin, up until just before the peak traffic hit, was using boosts as upvotes and favorites/likes were just below the post/thread (where boost sits now). Lemmy does it the way it is now (likes = upvotes) so Ernest changed it to match Lemmy behavior. But just as he changed it, he hadn’t changed the calculation for reputation to match when the server nearly melted down and he has to spend all his time just trying to keep the site alive by himself.

dannekrose,
@dannekrose@kilioa.org avatar

@peroleu

This is a great question and certainly confusing for those not used to the federation aspect.

A quick explanation:

If the magazine has a domain name at the end of it that isn’t the same as your kbin account, then it means that the magazine’s “home” is on a different instance.

Example:

technology@fedia.io

That means that all the instances (servers) will push content and updates to the “home” instance and receive updates and content from the “home” instance.

When an instance (server) subscribes for the first time to a magazine on a different instance, it will start to receive new content from that moment forward. However, older content isn’t pushed out to the newly subscribing instance. You can think of it as subscribing to a newsletter or something. You won’t automatically be sent copies of all the older content but you will get new things moving forward.

You can have older content show up by manually entering the direct link to the older content into the search bar on your home instance (in this case kbin.social) but it’s a manual process.

That why the message shows up about “may not be complete” since it doesn’t know how much total content there is on the remote instance.

This topic (called “backfilling posts/contents”) is one that has been discussed on the Fediverse for some time.

dannekrose,
@dannekrose@kilioa.org avatar

@kill

Do you have your notifications enabled in the Settings tab of your account? If you click on your account name and select Settings, on the General tab underneath the Writing and Privacy sections should be the notification section to choose what to enable.

"kbin How To" on front page would help people new to kbin

I feel like a highlighted basic "kbin how to" on the frontpage would really help kbin in the beginning, I still feel like I don't know exactly how all of this works, didn't knew what things like "boost" means, the difference between adding a new article/ post/ photo is still not clear to me. Just a really simple 1 minute how to...

dannekrose,
@dannekrose@kilioa.org avatar

@mpro

Welcome and I hope things are not too overwhelming.

It’s not quite the FAQ I think you’re looking for, but this little one might help with a few things. I’m working on more and hopefully will have a third one soon.

https://kbin.social/m/kbinfaqs@kilioa.org/t/20459/A-small-FAQ-to-hopefully-help-new-users-to-kbin

Good luck and cheers

A little more comfortable with Kbin now, but new questions FAQ (kilioa.org)

I'm glad my first FAQ was helpful for a lot of people new to Kbin and even to the Fediverse. It was made before some federation issues with kbin.social started so I created this new Magazine to help spread the load out a bit for FAQs....

A small FAQ to hopefully help new users to kbin (minor updated June 17 20:40 GMT) (kilioa.org)

I wanted to post this here since I want to help as much as I can in my own way to people coming here for the first time. I hope it is useful and helpful! I tried to assume low knowledge with the Fediverse in my responses which I collected here from a different post and assembled into a single article....

Crosspost: A small FAQ to hopefully help new users to kbin (updated June 11 17:00 GMT) (fedia.io)

Crosspost: Just trying to help spread information with this little FAQ I put together specific for kbin. If the Magazine mods don't want this here, please let me know and I'll remove from this magazine. That link should point to the local-to-fedia.io thread, but if not, you can also view it at the below link to the original...

/kbin logotype

A small FAQ to hopefully help new users to kbin (kilioa.org)

I wanted to post this here since I want to help as much as I can in my own way to people coming here for the first time. I hope it is useful and helpful! I tried to assume low knowledge with the Fediverse in my responses which I collected here from a different post and assembled into a single article....

/kbin logotype
Nodachi216, to kbinMeta
Nodachi216 avatar

Reddit refugee here with a big question, How do we create a subreddit-like experience here?
Most discussions about kbin right now are focused on the user side of things, what about mods who want to bring their communities to kbin? I'm not talking about moving all the existing discussions and content, just making the actual place for new content and discussion complete with moderation.
Would creating a magazine do this?

dannekrose,
@dannekrose@kilioa.org avatar

@Nodachi216 Magazines are the kbin equivalent of a subreddit. They have two large categories of content, threads and microblogging. Threads are any content not a “post” while threads are articles, links, and media posts. Threads are what you see on the “front page” with posts showing up in the microblogging part of a matching magazine.

dannekrose,
@dannekrose@kilioa.org avatar

@cache_miss

When you open up kbin.social or any other kbin instance at the moment, you'll be taken to the "front page" or main page which will show a list of "threads" with the following:

  1. Up and down vote arrows to the left
  2. A title, then maybe a description or some other body.
  3. Under each entry will be the person who added it, how long ago and which magazine it was added to.
  4. There will be a comment count, boost count, and the "more" button for each of these you see on the main page.

Those are "threads" and will have one of the following types:

  1. Article
  2. Link
  3. Photo
  4. Video.

They will not be of type "post."

I used the term microblogging because that's the menu item you have to select from inside a magazine to view "posts."

Looking at my screen which is almost certainly the same as that for kbin.social, after I select a magazine via the "Magazines" menu item at the top of the front page (or some other location where the magazine link takes you to the magazine page), it shows me a new "top bar" that consists of the following:

[Site name] /m/[magazine name] Threads Microblog People Magazines.

By default, when you open a magazine page, it will have the "Threads" menu item selected. It will look similar to the front page in that it will have a list of "threads" with the up and down vote buttons to the left, a title, and some content underneath depending on the type: article, link, photo, video.

If you click the Microblog menu item, it will show a much different screen with an empty text box at the top with the built-in editor, a selection box to the bottom right with the current magazine selected already and some other options.

Below the text box you will see options for changing the ordering of the content below. The content below this box are all "posts" that either originated on this instance, or else were federated in from other platforms like Mastodon, Calckey, etc.

From a user's perspective, this is the difference between a "Thread" and "Microblog" and is a distinction I believe doesn't exist in Lemmy. (I don't actually know though, since I've never actually used Lemmy)

Under the hood, the different types - article, link, photo, video, and post - use different Activity Pub types to distinguish them. I don't know exactly for all of them, but I know kbin articles are federated as type "Page" while Mastodon, for example, sends out posts as type "Note." A "Note" is then treated as type "Post" by kbin and will not show up in the "threads" view (that's the view with the upvote and downvote buttons to the left, the nice title and content in the middle and comment counts). To view "posts", you must look at the Microblog link for the Magazine that the content was created in, or routed into if it is a new post from an outside platform.

I don't mean to sound condescending or rude so if I did, that is a lack of skill on my word choices and I apologize.

I hope that helps clear up some confusion!

@Nodachi216

dannekrose,
@dannekrose@kilioa.org avatar

@cache_miss

The Why is going to be a bit subjective so I'll try to lay out the more "concrete" differences between creating a thread (of which article is just one type) and a post.

Posts:

  1. Will federate to all your direct followers regardless of platform. If they are using a microblogging platform like Mastodon, this means it will show up in their home feeds just like any other post.
  2. Will not be seen on the "front page" by default since the default behavior is to have the "front page" show threads, not posts. A person can click the "Microblog" tab at the top to view all the posts instead, but that requires a click.
  3. Posts, unlike threads, will display the conversation without needing to click. You can compare by checking it out on kbin.social, but you'll notice that the threads on the front page will just have the opening title and a small description, but will not show the comments or replies to it. If you click on the microblogging tab, you'll see posts along with their replies automatically without need to click on them.
  4. Posts do not have subject lines. This means that typically on a platform like Mastodon, the post will show up without any content-warning masking the body.
  5. While threads are relatively widely supported on other platforms, posts are almost universal due to being a core part of the microblogging Fediverse.
  6. I don't know for sure, but I believe posts don't show up on Lemmy instances. Someone will have to correct me on that, though.
  7. Replying to the OP Post is more intuitive. To reply to a Post, you just have to click at the bottom of the OP's Post on the "reply" link. This is different in a Thread (if you're trying to reply to the OP and not a comment)

Threads:

  1. Have a subject line and a body. This means on non-kbin/lemmy instances, it is likely that any content that is federated to them (Mastodon, etc) will show with a content warning and masked body.
  2. Will potentially show on the front page by default.
  3. Can show and embed media which can be displayed by default depending on an individual user's settings.
  4. Depending on the type, will federate in unexpected ways. Links, for example, that have a description can show on Mastodon without the description (I believe) and thus makes for unexpected behavior on non-kbin platforms.
  5. Threads will give you the option to add Badges to the content when you create it. I don't know when that will be fully implemented, but I suspect it will be a way for Magazine subscribers to "customize" the presentation of their thread depending on which badge(s) are applied.
  6. Replying to the OP's initial content can be more troublesome. For a thread that has a lot of comments on it, in order to add a comment, you have to scroll to the bottom of all comments (or all the comments on the first page of comments) to see the comment box. Replying to an existing comment on a thread is easy as the comment has a "reply" link at the bottom of the comment, but for a thread, the "add a comment" box is below all the current comments.

These are just the differences that I can think of off the top of my head. Also, if I'm wrong on any of these, I hope someone corrects me.

Thank you and I hope that helps.

@Nodachi216

dannekrose, to apexlegends
@dannekrose@kilioa.org avatar

Quick post test.

dannekrose, to kbin
@dannekrose@kilioa.org avatar

Are gup.pe groups fully supported on kbin? I get notifications about new posts and can see a small tiny part of the post in my notifications but when I go to click the link it doesn’t show. The remote profile shows there is a post (1) but it doesn’t show either when looking at the profile itself.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • Leos
  • vwfavf
  • magazineikmin
  • Youngstown
  • mdbf
  • rosin
  • slotface
  • thenastyranch
  • InstantRegret
  • PowerRangers
  • kavyap
  • osvaldo12
  • tsrsr
  • DreamBathrooms
  • anitta
  • everett
  • tacticalgear
  • khanakhh
  • ethstaker
  • ngwrru68w68
  • Durango
  • cisconetworking
  • modclub
  • cubers
  • GTA5RPClips
  • tester
  • normalnudes
  • provamag3
  • All magazines
    •