TheVillageGuy

joined 1 year ago
[–] [email protected] 65 points 1 month ago (26 children)

The landlord will then have to have the drains cleared and hear exactly what they found blocking it. This will improve your relationship with your landlord and they will feel happy that you decided to take revengeful steps against them which don't really serve any purpose and are just a waste of resources. No way are they going to somehow claim back those costs from you

[–] [email protected] 1 points 1 month ago (1 children)

which there is already plenty of

Please elaborate

[–] [email protected] 1 points 1 month ago (1 children)

The solution is making your own instance. You've basically got a copy of your own of everything you follow on the fediverse. If it goes down for a while, messages are indeed queued for a reasonable time. And even if you do miss them, things like comments, up and down votes will act as 'reminders'

[–] [email protected] 1 points 1 month ago

You can make your own instance. Not everybody's cup of tea, but in the future it will likely become easier. It will only go down when you let it

[–] [email protected] 7 points 4 months ago (3 children)
[–] [email protected] 3 points 4 months ago* (last edited 4 months ago)

https://www.instagram.com/naturejab_?igsh=c2hiMnd6a2IxNTNl Check out this guy who does pyrolysis in his back yard

[–] [email protected] 5 points 4 months ago (4 children)

I care. Sorry to see you go. The fediverse can still grow, I suggest you at least stay to lurk and see. It's just not happening at the pace we were all hoping for at the time. Is reddit really that much better? You're not an asshole for being honest

[–] [email protected] 3 points 7 months ago (2 children)

Check out https://kbin.melroy.org as well, it's a forked version of kbin

[–] [email protected] 6 points 7 months ago (1 children)
[–] [email protected] 2 points 7 months ago* (last edited 7 months ago)

If you want to be your own community's host, you'll also want to start your own community on your instance. The longer you wait, the more users will have to move from the current to the new community. We started ours on an existing server (and it still exists) but we realized early that it would not give us enough control over the posted content (specifically filesize limitations) So we quickly started our own instance.

 

I know some of you consider this as documented whining. I hear you but won't stop sharing my opinion and reminding. I recommend continuing commenting on the original post to keep it a bit organized (this post is a link to it)

Update: this thread has gotten out of hand. This is not what I intended, this is not what anybody should want. Let's leave it at this, for now.

37
submitted 10 months ago* (last edited 9 months ago) by [email protected] to c/[email protected]
 

I almost feel like it's October last year, when I pled for improvement on all fronts regarding the Kbin development strategy. Now it seems development has ceased once again and there hasn't been chat on the matrix channels for over a week. Update: that's two weeks now (including his blog) and over a month of no visible Development.


Update: According to https://fedidb.org/software/kbin there are a grand total of 29 active kbin servers. Of 61,489 users on all instances, 59,962 of these are on kbin.social. To those users I would like to say that should kbin.social fail, there will always be Mbin servers to fall back to.


What is going on?

We can only speculate, based on what has happened in the past. Several mind bending theories can come to mind.

Perhaps Ernest (and whatever team still exists) is continuing development in the background, not publicly sharing his work on codeberg. He may have had enough of all the criticism and wants to do it his way without interference. This may sound a bit far fetched, but he's admitted in the past that he prefers concentrating on coding over communicating with his community.

Other theories could involve something bad involving Ernest personally, let us hope that is not the case. Ernest is a great person, nobody would wish anything bad upon him.

But in reality, speculation doesn't change anything, we can only deal with the situation at hand.

I believe waiting for a new release comes with too many risks in the current setting. Nobody can monitor the code during progress or do any testing for themselves while development is ongoing (assuming it is). If anything, what's coming next? Your guess is as good as mine.

A new version may well break compatibility between Kbin and Mbin. Mbin is trying to stay compatible with Kbin for as long as reasonably possible. However, staying compatible with something that is out of sight and out of one's control is challenging, if not impossible. A break in compatibility would mean there will be no easy way to migrate to Mbin after an upgrade for Kbin users who have patiently waited for one, should they want to.

I would not want the future of my instance to be dependent of such a level of uncertainty, now or in the future.

view more: next ›