fediverse

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

wlf_warren, in Flipboard stops tweeting, launches new podcast about decentralized social apps
@wlf_warren@pebble.social avatar

@stopthatgirl7 šŸ‘

solowolf, in Towards the fediverse as a repository of knowledge like how reddit used to be

The general setup of Kbin was a little confusing at first but after playing with it for a few moments was easy

density,
@density@kbin.social avatar

Still working on making on-topic responses I see. :) you'll get there eventually. just give it a few more moments.

solowolf,

this is true

ContentConsumer9999, in Thinking on creating a guide on leaving Twitter etc. for creators, etc., some tips on what it should include?

Maybe you could include some recommendations on carrying over content/followers. Especially if there're bots to do it.

0x4E4F, in Thinking on creating a guide on leaving Twitter etc. for creators, etc., some tips on what it should include?

Fediverse = Gab + some cryprobros + maybe Pawoo

I donā€™t actually get any of this šŸ˜‚. Yes, I am that old šŸ˜‚.

I think Iā€™ll try to explain the working of the Fediverse in simple drawings, add a few instances recommended for certain types of creators, and make a page long FAQ section with stuff like about GDPR requests, etc.

There was a nice image, like a tutorial with Q&As, during the Reddit migrationā€¦ canā€™t seem to recall who made it, but it was well explained, in laymanā€™s terms, what the fediverse is. It was aimed at Lemmy, but it could easilly be remade for any other fediverse social media as well (I think the author also released the GIMP file as well). Sure, itā€™s not perfect, but it gives you a general idea of what the fediverse is.

If someone could remember the image and share it, or a link to where it may reside, that would be great ā˜ŗļø.

CJOtheReal, in Thinking on creating a guide on leaving Twitter etc. for creators, etc., some tips on what it should include?

Next DNS and set Twitter.com and X.com to the block list, you just use it out of habit, you wonā€™t even bother changing it back.

testing, in blahajzone unusable once again
@testing@kbin.social avatar

sharkey test instance at blahajzone also down

Die4Ever, in Towards the fediverse as a repository of knowledge like how reddit used to be

thereā€™s been some talk about changing the way the URLs are formatted for Lemmy

github.com/LemmyNet/lemmy-ui/issues/2097

github.com/LemmyNet/lemmy/issues/875

github.com/LemmyNet/lemmy/issues/2987

density,
@density@kbin.social avatar

Thanks for sharing! Looks like a lot of agreement and no opposition. Just a matter of getting it done. Hopefully someone who has the skill and time will get it on their TODO list someday.

palordrolap, in Towards the fediverse as a repository of knowledge like how reddit used to be

I only know that one time an obscure thing I was talking about here on kbin.social, perhaps as a response to a post on some Lemmy or another, ended up being indexed incredibly quickly by Google regardless of however things are structured in URLs.

This became apparent when I tried to do further research on the topic and I found myself staring at my own comment as federated on yet another Lemmy.

As long as search engines remain as on the ball as whatever happened there, we might actually end up with a repository anyway.

density,
@density@kbin.social avatar

Is there a name for that phenomena? It used to happen to me with reddit.

Especially disappointing for longstanding problems that I would walk away from and return to at a later date. I would of course initiate a renewed effort with a websearch containing key words. I guess in a sufficiently idiosyncratic/unique way that I would find my own thread, but not recognize it. Momentarily get excited like "this person has the precise same problem as I do!" hoping there would be a solution in the thread. Only to realize that the whole thing was a little too framiliar and it was myself, last year, struggling with the same problem having made zero progress.

Do you think that's why you found your own writing? Like if I am trying to research the present question and I do a search with keywords like fediverse repository knowledge lemmy kbin URL search reddit I could imagine finding this because it is an unusual combination of words. But if I were to use totally different phrasing I doubt I would get here.

can, in Pebble, a startup that tried and failed to take on Twitter, finds new life on Mastodon | TechCrunch

To me pebble is still the startup that made a watch.

ono, in Faircamp is a Free Bandcamp Alternative

Iā€™m a fan of static site generators, but unless Iā€™m missing something, this wonā€™t replace the most important part of Bandcamp: a platform for selling music.

deadsuperhero,
@deadsuperhero@kbin.social avatar

@ono Yeah, fair point. It's more geared towards patron support and donation prompts, but it does support things like redeemable codes, which could be paired with some kind of recurring donation system.

It does make me wonder what it would take to build in a checkout system, and whether that goes way beyond what a static site can handle.

TheVillageGuy, in Mbin: A kbin fork that promises to never review PRs before merging them

As a person who hangs around in repos but isn't a developer that sounds totally insane.

Why do you hang around there then? So you can write articles like this in an attempt to stir the shit? What is there to gain from that, for the fediverse?

I'd also like to know how you hang out there then, as I can't seem to find a person called Density hanging around? I might not be looking in the right place, of course

celeste, in Mbin: A kbin fork that promises to never review PRs before merging them
@celeste@kbin.social avatar

This early in a project, figuring out how to manage it effectively is a big part of the work, I think. There's no inevitability to either project failing or succeeding. I hope both projects do something cool, and if one fails I hope there are a few forks of it ready to carry on with the best parts of it.

melroy, in Mbin: A kbin fork that promises to never review PRs before merging them
@melroy@kbin.melroy.org avatar

Thanks for your feedback.

We do have code reviews in GitHub and discussions on Matrix. We updated the README that reflect our latest way of working. As stated in the comment section we are also working on it in PR: https://github.com/MbinOrg/mbin/pull/34. Feel free to comment on that.

SamXavia, in Mbin: A kbin fork that promises to never review PRs before merging them
@SamXavia@kbin.run avatar

I do love Mbin, I just wish we had an area instead of Matrix to talk about things that we want and stuff.

density,
@density@kbin.social avatar

they don't use github issues?

SamXavia,
@SamXavia@kbin.run avatar

They do but it would be nice to have a place to talk about it in a Magazine instead of having to go to external sites

density,
@density@kbin.social avatar

Can't make a magazine? https://kbin.run/newMagazine

SamXavia,
@SamXavia@kbin.run avatar

It's not that I can't make a magazine, it's just it won't be looked at or be used as an official one. So it would be worthless creating one

density,
@density@kbin.social avatar

How do you know the future?

If you are correct, it is very strange. Why would people who are so passionate about creating a social media platform refuse to use it?

melroy,
@melroy@kbin.melroy.org avatar

That is correct, we do not have an "official" instance or an "official" magazine. What follows now is MY OWN opinion, other community members might think differently.

Mbin is aiming for a federated and decentralized social network, I think the whole point of the fediverse is that there shouldn't be one main instance, right? Feel free to create a magazine where ever you want! Isn't that the beauty of activitypub? Maybe the idea takes some getting used to.

density,
@density@kbin.social avatar

here we all are talking about it on fediverse@kbin.social which certainly isn't Official Fediverse comm.

melroy,
@melroy@kbin.melroy.org avatar

kbin.social is the official instance of kbin ;)

density,
@density@kbin.social avatar

Your community members ("I do love Mbin") are expressing that they are unhappy with the mediums available for discussion and feel excluded. What is done about it?

melroy,
@melroy@kbin.melroy.org avatar

I feel a bit of negativity from you. This will be my last reply in this thread. She has resolved it herself by creating a magazine by herself on Mbin for Mbin: https://kbin.run/m/Mdev

density,
@density@kbin.social avatar

@melroy great!

@SamXavia

ripcord,
@ripcord@kbin.social avatar

I'm still not getting the point of mbin. I mean, options are nice, but what's the value it brings over kbin?

cacheson, in Mbin: A kbin fork that promises to never review PRs before merging them
@cacheson@kbin.social avatar

It looks like they're still working out what they want their process to be:

https://github.com/MbinOrg/mbin/pull/34

Seems like your concern is addressed there:

Pull Requests require at least one (1) other maintainer approval before the PR gets merged (built-in peer review process).

The mbin fork happened when kbin development was looking a lot less active. In any case, it's not necessarily bad to have a diversity of approaches. Due to their differing organizational structures, mbin will likely tend to have more features and more rapid development, but also potentially more bugs, while kbin remains more stable.

density,
@density@kbin.social avatar

I cant follow the convo to tell if this is the actual state of things or just something thst was being discussed but:

16 Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, (c) engaging with the Contributor on improving their patch quality.

What an idea.

cacheson,
@cacheson@kbin.social avatar

From the PR comments:

Maintainers MAY merge incorrect patches from other Contributors with the goals of (a) ending fruitless discussions, (b) capturing toxic patches in the historical record, (c) engaging with the Contributor on improving their patch quality.

I asked around and asked in the C4 specification matrix room.
And the reason is actually simple. If you merge bad code, have a record of proof in git (pull requests aren't forever it's only a github/gitlab thing).

So the idea is if you merge bad code you have proof in the git record that there is a bad actor. You can always revert the commit again or fix it. And the record can act as a proof in case the community want to get rid of bad actors.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • ā€¢
  • random
  • fediverse@kbin.social
  • meta
  • Macbeth
  • All magazines