Deleting channels?

2024-10-13 15:38:11

adminsforum@hubzilla.org

dynamic_hubzilla schrieb den folgenden Beitrag Sun, 13 Oct 2024 15:38:10 +0200

Deleting channels?

Is there any way to delete channels?

I previously set up several channels for myself to test things out, but right now they mostly feel like unnecessary clutter.

2024-10-13 15:41:45

Harald Eilertsen

harald@hub.volse.no

@dynamic_hubzilla Sure. Just go to the settings of the channel you want to delete, and then click the big red button in the top right corner :)

2024-10-13 15:43:54

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

Be careful, though: Once you've deleted a channel, nobody, not even yourself, can ever create a channel with this name on this hub ever again.

So if you think, "I don't need this channel right now, I'mma delete it, maybe I'll make a new one with the same name when I feel like it": No can do.

2024-10-13 17:35:37

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@dynamic_hubzilla

Once you've deleted a channel, nobody, not even yourself, can ever create a channel with this name on this hub ever again.

It is quite possible to recreate a channel with the same name. However, YOU must contact the administrator of the hub and ask them to delete the old channel name from the database. This does not involve any work.

---
Sent by a #Hubzilla instance to the #Fediverse

2024-11-07 22:59:58

od@zotum.net

@Rogue Runner
@Scott M. Stolz

Thė suggestions about keys seem great: how to create an environment for new programmers to join the project and write such vital feature?

2024-11-09 12:16:06

Scott's Code Journal

scott@codejournal.dev

@od I suppose the first step would be discussing it with @Mario Vavti and coming up with a plan on how to implement it.

This discussion came up several times before, and it is something that could be addressed, although with some caveats. I am not sure how much work it would take to make it happen though.

https://hubzilla.org/display/b64.aHR0cHM6Ly96b3RhZGVsLm5ldC9pdGVtL2QyNjY0ZTIxLTAyZGMtNDU1MC1iOGE3LTMxMTE4OTQyZGViMg

https://socialhub.activitypub.rocks/t/reuse-of-identity-channel-addresses-revocation-reissue-of-keys/2888

2024-11-09 14:31:30

od@zotum.net

Nomadic identity cannot work if security keys are _not_ mandatory.

2024-11-09 21:39:45

Rogue Runner

cisco@inlakech.site

@od
@Scott M. Stolz

Forcing to put your master/private key onto your own device upon install would make you able to prove your ID in case of a server meltdown or accidental loss of your master ID on the server. You would always have a master on your device to start over.

2024-11-12 08:29:40

Scott M. Stolz

scott@loves.tech

@Rogue Runner You can already download your JSON file with your key and everything necessary for recreating your account on another server. So you can do that now, it just is not mandatory.

2024-11-12 20:50:16

Rogue Runner

cisco@inlakech.site

@Scott M. Stolz ... That was why i used the word 'forcing' upon install, which would make it mandatory to backup your master/private key to your own device. Or an option to bypass this backup at your own risk.

But i was more leaning towards the key manager idea that could issue or revoke keys for the same channel to be used with a new ID and same actor.

2024-11-12 21:16:01

Scott M. Stolz

scott@loves.tech

@Rogue Runner I doubt a less tech savvy person would understand the concept of keys much less how to use one. Forcing people who are not tech savvy to do things they don't understand is a recipe for disaster. And it's akin to having them write their password on a post it note on their monitor. Anyone who has access to their unsecured computer has access to their identity. It would be less secure, not more, in that scenario.

So forcing people would not be a good idea.

But I do agree with the idea of issuing and revoking keys. I brought up the topic before.

2024-11-12 22:15:36

Rogue Runner

cisco@inlakech.site

@Scott M. Stolz ... Fair enough that it might be over the heads of the none tech savvy... which is why having the option to bypass that part of the install would be there. One would think though that if you are at a level of installing a new hub on your own server, that you would be confident enough in knowing what the process is all about. And you would also know how to encrypt a file or at least put it into an encrypted folder. The process could be explained in the install document.

I did see your posts about implementing the revoking and issuing of keys from posts that are a couple years old... i have not seen any follow up on those ideas. Is there a reason for not having this implemented..?

2024-11-15 20:27:28

od@zotum.net

@Scott M. Stolz

Forcing people who are not tech savvy to do things they don't understand is a recipe for disaster.

See matrix. Account creation forces new users to verify either by _second_ password or verification key. Works well.

2024-11-15 20:53:02

Harald Eilertsen

harald@hub.volse.no

@od Except when it doesn't... I've seen countless people struggle and in the end give up due to this. Even the ones who understands the process and what it is about struggle some times.

2024-11-15 21:25:05

dynamic_hubzilla

dynamic@hub.netzgemeinde.eu

@Harald Eilertsen @od

I'm with Harald. My spouse and I maintain a Matrix server, and password and key management, and maintaining verification, can be a real nightmare, especially when users try to log on from different devices. We entirely gave up on encrypted rooms because there was so much uncertainty over who would and wouldn't have access. And we aren't even federated, just a small space for us and people close to us.

2024-11-20 07:51:58

Ema エマ

ema@utasansh.in

When moving to another server, you‘ll have to copy over the database. @K&T Host helped me the last time doing it, and before that, it was @elmussol who helped me.
I think before doing it, you should go offline with your old server, and only when things are done, you should go online with the new server.

2024-11-21 14:27:05

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

With phpMyAdmin it's a piece of cake.

2024-12-01 17:07:36

Rogue Runner

cisco@inlakech.site

Why not issue a duplicate channel key to the admin every time a new channel is created on the server... these keys would be permanent and also delete-able. The user channel keys on the other hand would be time stamped and expire after a period of time... but some days or weeks prior to expiry, a warning to the user is issued to renew your key... if the key is not renewed by the user, the admin will have the option to renew, re-assign a new server, or delete the keys.

A modified version of guest access app could be used... except it would be modified for admin use only as key/token manager. That way a built in or addon UI would be possible for the admin to manage all the server keys.