Bug 202401281030 channel deletion failure profile connections public exposure
Bug 202401211021 channel deletion import export failure
A channel was exported.
After activation of activitypub, diaspora, modules, system broke.
Review of server showed logs consumed entire virtual private server allocation, more than 19 gb
Deleted and restarted hubzilla with success
Import of channel failed
Deleted channel
Attempted to create new channel, same name, server response that not possible as channel name exists
In administrator account for hubzilla server, 'admin' side bar list 'channels' does not show the channel name
In the postgresq table 'channel', the channel name exists. Deleted via postgresql command 'DELETE FROM channel_name WHERE channel_name='thechannelnamethatshouldbedeletedbutisnot'; If a hubzilla server administrator deletes a channel from the hubzilla server administrator account, the channel is stated as deleted.
If a hubzilla server administrator enters the hubzilla server database, the channel is _not_ deleted because the channel name continues to be shown in the database tables.
If a hubzilla server administrator performs a search of a channel name within the logs, (s)he will see both the channel url and gain access to the entire list of connections via the url hubzillaserverdomain/poco/channelname
