It depends on what the remote server does with the federated delete command. You should generally assume that anything you post to the fediverse is permanent.
@ThatOneKirbyMain2568
truly a long time issue! arrows work for the 2nd page only > same problem occurs in the microblogging section: arrows do not work
i get all kinds of new communities by just clicking into the remote community, and then clicking subscribe
edit: aaww maybe you just dont like where you currently type it, and want to type it somewhere else? i spose. i agree the interface currently isnt very clear
i get all kinds of new communities by just clicking into the remote community, and then clicking subscribe
Maybe you misunderstand what I mean. Right now, if I were to create a new community on lemmy.world called /c/thatonekirbymainisawesome, it wouldn't show up if I searched for it here on the kbin.social magazines page. That's because kbin.social currently doesn't know that this community exists and thus isn't fetching anything from it. The same goes for any other two instances. If you want a non-hypothetical example, go to sh.itjust.works and search "geometrydash". You won't find /m/geometrydash (or at least I didn't at the time of making this comment). If you go to https://sh.itjust.works/c/geometrydash@kbin.social, you just get an error, because sh.itjust.works doesn't know about geometrydash@kbin.social yet.
To fix this, someone needs to essentially tell an instance, "Hey, this community over here exists, and you should start fetching stuff from it." On Kbin, this is done by putting the community's address in the general search bar. So if I were to search "thatonekirbymainisawesome@lemmy.world" on kbin.social's, that community would finally appear, and I'd be able to subscribe from it and see any posts made after that point.
What I'm suggesting is that instead of having to type the full community address in the normal search bar (which can be unintuitive), there should be a dedicated interface for adding remote communities (i.e., letting your instance know that communities on other instances exist). PieFed does this with its "Add Remote" interface, and I think it'd be nice for Kbin (and Lemmy as well) to have something similar.
my subscriptions have been mostly coming through posts about new communities.
when someone posts a link to a remote, they are formed in such a way that my mbin instance automagically searches for, creates and dumps me into that newly created remote community. im sure its just a part of its search/routing.
at that point, the instance is subscribed to the remote community.
then i click 'subscribe', which subs my specific account.
edit: yep, theyre crafting the links to force it through the processor like this
True, and the same happens here on kbin.social. However, in the case where there isn't a link to automatically do the search for you, I still think it'd be helpful to have something more intuitive than the community only appearing when the exact address is put in the general search bar.
EDIT: To give an example where this would be useful, what if you're someone on a newer Kbin instance and want to add an existing community? You'll have to know the method of doing it, and if you don't, you're out of luck. Having a dedicated button and interface for this would make it much more intuitive. When I saw PieFed's "Add Remote" button, I immediately got what it did, whereas I still have no clue how to make Kbin communities visible on most Lemmy instances.
Threadiverse is still in its nascent stages of development, and it is even earlier stages for kbin. Anyone who have been around in the internet long enough knows that these issues are common at this stage. People who are complaining are failing to realise that this is still just a passion project of a single individual who is really not making any real profits in return, and is not a multi-billion enterprise with server farms of its own across the world. Even Reddit and Twitter had lots of such hiccups when they started out.
Thanks for all the work you are doing, Ernest! Always happy to be here!
you need to have an honest conversation with yourself before you address any further issues publicly.
from “if the update isn’t out by september consider this project dead” to “i’ll be working on it for a few hours then it should be good to go” you clearly have trouble estimating the amount and scope of work necessary to maintain a site of this caliber.
i’m not trying to be insulting to you, but you need to understand it’s starting to get tiring as a user too. take stock of what you are doing and pause for a moment before you give your users a defined timeframe.
the post where you said it would be a few hours is still up and unedited. that was 3 days ago. i wouldn’t have minded you saying “it will be a few days, maybe a week or longer” at the get-go but now we’re approaching 1000% estimated time to recovery and it feels like you are no closer than you were 3 days ago. it’s insulting and it definitely doesn’t need to be that way.
Good luck trying to convince this man. I'm sad to say that what I predicted, now two months ago, is happening. My advice; don't rely on kbin.social, find another instance (I recommend Mbin) or make one of your own.
There are a lot of instances, just keep looking. Find the communities/instances you like, and subscribe to them from whatever quick, lightly-used, geographically-close to you instance you find to register on.
There's literally no location indicator for the instances servers so I'm not sure how you expect me to do that. And smaller instances are more likely to get abandoned, go down and vanish.
I don't quite understand what you mean. The problem is that in such a case, it's challenging to provide a specific estimate. That's why I occasionally provide updates in case the work is prolonged. It seems to me that this is how it works. Issues arose without any interference in the code or infrastructure. I addressed hardware problems, but it turned out that wasn't the only issue. Throughout this entire period, I've been attempting to ensure that the instance operates as smoothly as possible. It should be significantly better now, but I'm still actively working on it. Unfortunately, taking a holiday break here doesn't help either.
“I’ll be working on it for the next few hours” is different than “I’ll be working for a few hours today but have not identified root cause yet so I can’t say how long the fix will be”
“The update will come in September or consider the project abandoned” vs “I want to have the update out by the end of September but can’t guarantee any timeframes until I’m further along in the work”
“It should be back up in a few hours” vs “I’ll update everyone again once I’ve identified the issues and am working towards a clear resolution”
I’m not asking for more work or more communication, just honest communication.
Issues like the one that occurred are typically resolved within an hour, hence this post - mainly to quickly inform that work is underway on it. But you're right, I'll strive to improve communication in the future. Your examples gave me something to think about, thanks.
Honestly @ernest I don't think you have anything to worry about.
It is your platform. Make it at your own pace. Most of us are very happy to be invited on this journey and recognise that there are going to be ups and downs.
As an aside, I downloaded one of the Lemmy apps to get my fix while things were having issues here. And while it wasn't bad, I'm definitely glad to be back. Huge appreciation for the function and form of Kbin and the tremendous amount of effort put in to keep it awesome.
kbinMeta
Aktywne
Magazyn ze zdalnego serwera może być niekompletny. Zobacz więcej na oryginalnej instancji.