New Slackware domains - what to do with them?
 

I've purchased a couple of Slackware domains to go with my collection of .uk ones:
and would like to do something useful to the community with them. They're not active yet, so no point visiting them! :)

Does anyone have any ideas of what I could do with each site?
Obviously I could just make them aliases for slackware.uk, but I'd like to do something more with them.

Any suggestions? :)

Slackware based web hosting (cloud) and slackware based email and communication (network)

slackCloud, for private online storage. Only accessible from slackVPN. A network that advocates strong encryption && subtlety. A google cloud replacement.

Or, maybe something less daunting.... Slacktodon. Where quality posts award slack. Can use one domain to store media assets and the other to handle communication between members.

More propaganda could be fun. Maybe one of those web meme generators that pairs text with our pipe-smoking Tux?

That I would be interested in as well.

+1

jabber server

We use openfire internally, yes yes its java based... but its reliable

..or IRC server.... or both :)

I would be interested in that. :cool:

+1

I'd much rather pay a yearly fee to Tadgy than adding to commercial actors' profits.

Maybe an IPFS-based Slackware package repository?

These are things I'm considering, but I think there may be a couple of issues with doing them...

The web hosting would be fairly simple to do, and I pretty much already have that functionality on the servers right now - but doing commercial web hosting would need a whole set of accounting processes that would just be a PITA; and I can't believe there are no other Slackware based web hosts out there (but I'm willing to stand corrected)? :)

Also, are you talking about hosting people's own domains? Or providing something like foobar.slackware.cloud ? That I could sort of get behind.

For the .network suggestion, slackware.uk already offers mailboxes for Patreons of a certain donation level. Again, I'm not adverse to providing email addresses @slackware.network - but at what cost?

Extra input would be appreciated! :)

This would be nice, except for the data storage requirements. I'd probably need to get another "storage" based server with plenty of spinning rust for such a project... which would come with a lot of extra costs, and would probably never to able to compete with the other data warehouse people out there that have the infrastructure and disk space already available.

I have no idea what this means? I recognise the words, but their combined usage draws a blank :)

Interesting.... I'll have to have a think about the Jabber server :)

As for IRC, we already have the ##slackware channel on libera.chat that is already fairly well used (though not as much as the old Freenode channel was - we seem to have lost a lot of users in the move).

I guess I could make a sub-domain like irc.slackware.network point to the libera.chat servers, but I'd have to check with them whether this is a good idea, or something they wouldn't mind.

What sort of fee are we talking about? :)

That's one of the biggest problems with entering the web hosting market - what price point to you place your products at?

Plus, if sites generate _a lot_ of traffic, I'd have bandwidth quotas and resource usage to take into account as I'm sure none of us would want slackware.uk going down :)

Sorry, I have no clue what an "IPFS-based Slackware package repositor" means - can you explain a little more? :)

The biggest problem is like we faced, customer control panel.

Those sods over at cpanel, plesk, DA etc, only support RH, though I heard one was looking at d....n too in recent times.
You can work it, but they will not help, so you're better off doing what we did and go custom, probalby more secure too this way :)