Puppy's Website: Discussion

[raffy]

If we go either host (hostgator, bluehost), we will be given a domain, like

servername.hostname.com/~puppylinux

We develop the site then point the puppylinux.org DNS to it when ready. If WhoDo starts the purchase now, then we'll have achieved something this Easter. (You'll be surprised how fast these guys respond to customers.) As to other people contributing funds for the website, please send contributions to Barry's Paypal account.

Re: puppylinux.org - the nasty links are there again - will check how much damage was done. I guess it's an interjection that we really have to move hosting. (Addition: The index file was completely replaced by the crap links - someone must be reading this thread and trying to have some weird fun.)

Yes, our servage hosting includes pupweb.org, so we can still keep using the site even if puppylinux.org is moved to another host.

Addition: I will no longer upgrade the wiki (and risk corrupting parts of it) since its contents will be ported soon to the new site.

[WhoDo]

If WhoDo starts the purchase now, then we'll have achieved something this Easter. (You'll be surprised how fast these guys respond to customers.)

Done, raffy. Details included in a PM to you this afternoon my time. I have told them we will use our own domain name in puppylinux.org and simply re-point our name servers, so we'll see what access they send me.

[raffy]

Thanks, Warren (Whodo). Hostgator.com is puppylinux.org's new home.

It will take some time before the actual transfer of puppylinux.org, and Tom, Oli and other editors will now start working on the new site. Tom has the Cpanel details, and I suggest that he PMs a few helpers and they use the temporary URL (and possibly a Drupal forum in it) to coordinate while preparing the new site.

Happy Easter, everyone!

[Aitch]

Nice work, guys

Onward & upward!

as WhoDo said elsewhere,

Easter is a time of new beginnings

Happy Easter, everyone

aitch

[klu9]

Note2,
don't forget that the servage account for puppylinux.org is paid-up until about 2013. We have it for a long time, so should keep using it for something.

My suggestion: turn it into a repo for ISOs, SFSs, big dotpups/dotpets, manuals... but NOT an http/ftp repo.

Make it a BitTorrent "seedbox" instead, permanently sharing Puppy files via BitTorrent.

Why?

1. Puppy needs a constant BitTorrent source for files; maybe the Servage account could be it.

2. Servage=Pwnage

BitTorrent clients automatically hash pieces of a file and fix corruption.

A regular HTTP/FTP repo on Servage might be giving people corrupt files (which might require redownloading 100% of the file all over again after finding out what the problem is and then finding a reliable alternative server to use).

But if the files somehow get corrupted on a Bittorrent seedbox, the downloader's BitTorrent clients will simply ignore/fix the corrupted pieces.

Alternative/Workaround

If a BitTorrent repo/seedbox is not permissible with that Servage account, then maybe there's still a way: metalinks with MD5 / SHA1 hashes included, and Servage URLs among other download URLs.

People don't get to access the Servage repo directly, but only through metalinks that include anti-corruption info, thereby providing a layer protection against future Servage pwnage.

By including several download URLS in the metalink, the download client can always get uncorrupted pieces from those alternative sources.

[Caneri]

@klu9,

brilliant idea.

Eric

[tombh]

Okey Dokey, I've uploaded the proto-site to its new Hostgator home.

I decided to go with Drupal 5.7 as there are some necessary modules that have not yet been ported to version 6. There is no loss of security by doing this as Drupal supports the current version and previous whole number version concurrently. Drupal 7 is planned for release in 2009.

Now we can discuss the ins and outs of style and structure over at the Puppy Website: Looks, Bugs, Wishlists thread. I've made few comments there to get things going...

Time to get down to business then

[nic2109]

@klu9,

brilliant idea.

Eric

Since it's still Easter in the Christian calendar I'll also say "Amen" to that suggestion.

BitTorrent and/or Metalinks should be the way all our packages are presented. In this way the bandwidth requirements are shared among a much wider population. And we gain from the amazing Torrent paradox that the more popular a download is the more available it is and the quicker it comes (subject to connection speed, of course).

Baseline Puppy and all Puplets need to be set up to seed as well as read so that way anyone who has D/Ld a package or an iso can share it with the rest of us.

I know that some will worry about security and choose to be leeches, but they would need to take explicit "Opt out" action. I hope that the number that take that option would be small. I also recognise that those on dial-up might also want to opt-out. That's fair enough, but as they would benefit from the Torrent approach too some may choose to seed.

[Aitch]

Just in case anyone's wondering

http://www.murga-linux.com/puppy/viewto ... &t=10159//

http://murga-linux.com/puppy/viewtopic. ... 7fe99d83f7

http://www.wellminded.com/puppy/pupsearch.html

just for starters


Aitch

[nic2109]

Hi Warren and all,

Well shiver me timbers and blow me down...thar she blows.(This is for Tom as he lives where the pirates came from..lol..coorrr)

Well done gentlemen.

Best,
Eric

In honour of this welcome development I propose that we all talk (and write) like pirates for a while.

See http://www.talklikeapirate.com/ but let's not wait until September 19th!

[SirDuncan]

<pirate>

BitTorrent and/or Metalinks should be the way all our packages are presented.

(emphasis mine)
Thus preventin' them o' us in locations 'ere P2P connections be restricted (or outright banned in th' case o' me college) from enjoyin' this great distro. I think that metalinks might be a problem as well, since they be pulling from P2P networks, too, if'n I understand correctly.

Baseline Puppy and all Puplets need to be set up to seed as well as read so that way anyone who has D/Ld a package or an iso can share it with the rest of us.

I know that some will worry about security and choose to be leeches, but they would need to take explicit "Opt out" action. I hope that the number that take that option would be small. I also recognise that those on dial-up might also want to opt-out. That's fair enough, but as they would benefit from the Torrent approach too some may choose to seed.

Gi'en that a large percentage o' Puppy users be on dial-up or otherwise slow uploadin' connections (like Barry on satellite), I think havin' this be th' default behavior be a bad idee. If we be t' go t' a torrent based distribution system, 't would need t' seed only on request (which makes this system work less efficiently) an' nay open a P2P connection without informin' th' user. Otherwise swabbies who dasn't reckon how we be doin' things will get the'r bandwidth exceeded or they will get the'r computer banned from a shared network (like th' one on me campus).

This be nay t' say that distributin' ISOs or other large packages (SFS) through torrents or metalinks be a bad idee. 't jus' needs t' be an alternative an' nay th' only way.

I dasn't think that normal sized packages ortin' ta be distributed on P2P networks, on accoun' o' I think that 't would actually slow things down fer most swabbies an' may cause some swabbies issues. Be havin' ye erenoticed that wee things like songs be nay distributed that way? Bit torrent be very efficient fer large files, but nay wee ones. Thar be also th' technical challenge o' buildin' a torrent based package management system (might be a fun challenge tho).
</pirate>

[klu9]

<pirate>

BitTorrent and/or Metalinks should be the way all our packages are presented.

(emphasis mine)
Thus preventin' them o' us in locations 'ere P2P connections be restricted (or outright banned in th' case o' me college) from enjoyin' this great distro. I think that metalinks might be a problem as well, since they be pulling from P2P networks, too, if'n I understand correctly.

Baseline Puppy and all Puplets need to be set up to seed as well as read so that way anyone who has D/Ld a package or an iso can share it with the rest of us.

I know that some will worry about security and choose to be leeches, but they would need to take explicit "Opt out" action. I hope that the number that take that option would be small. I also recognise that those on dial-up might also want to opt-out. That's fair enough, but as they would benefit from the Torrent approach too some may choose to seed.

Gi'en that a large percentage o' Puppy users be on dial-up or otherwise slow uploadin' connections (like Barry on satellite), I think havin' this be th' default behavior be a bad idee. If we be t' go t' a torrent based distribution system, 't would need t' seed only on request (which makes this system work less efficiently) an' nay open a P2P connection without informin' th' user. Otherwise swabbies who dasn't reckon how we be doin' things will get the'r bandwidth exceeded or they will get the'r computer banned from a shared network (like th' one on me campus).

This be nay t' say that distributin' ISOs or other large packages (SFS) through torrents or metalinks be a bad idee. 't jus' needs t' be an alternative an' nay th' only way.

I dasn't think that normal sized packages ortin' ta be distributed on P2P networks, on accoun' o' I think that 't would actually slow things down fer most swabbies an' may cause some swabbies issues. Be havin' ye erenoticed that wee things like songs be nay distributed that way? Bit torrent be very efficient fer large files, but nay wee ones. Thar be also th' technical challenge o' buildin' a torrent based package management system (might be a fun challenge tho).
</pirate>

BitTorrent is P2P and is subject to blocking or throttling in some locations. Let me just say that I think it should be a well-supported option of several, not the only possibility.

Metalinks can include P2P URIs, but most clients only support regular HTTP/FTP URLs. (And so far I've only ever created Metalinks containing URLs.)
What might be blocked re metalinks is the P2P traffic/protocol of a p2p-containing metalink used by a p2p-enabled client, but not the HTTP/FTP traffic of the metalink. so a user can still get the file.

PS Please assume all the above was said in a pirate accent

[Aitch]

Oooaah me 'arties
mebee kenny's post'll cum use'll arter awl

http://www.murga-linux.com/puppy/viewto ... &t=10159//

diddle it do do, diddle iddle iddle do

[Caneri]

(Pirate)
arrrr me bucko's and me deadlamp is atwitter..arrrr

thar's a lost sea me hearties..it's the code I see that's a quizzle.

Speak in the tongue of the sea horde and ye shall be heard..arrrr

Best,
Commodore Drake the Black Arse

(English)

My eyes are sore but I see a need to translate from pirate to English,arrrr

Best,
Eric

PS.. @Nick good link this http://www.talklikeapirate.com/piratehome.html

[SirDuncan]

BitTorrent is P2P and is subject to blocking or throttling in some locations.

I suppose that pirate-speak may be hindering communication, but I never meant to insinuate that BitTorrent was not P2P.

Let me just say that I think it should be a well-supported option of several, not the only possibility.

I can agree with that.

Metalinks can include P2P URIs, but most clients only support regular HTTP/FTP URLs. (And so far I've only ever created Metalinks containing URLs.)
What might be blocked re metalinks is the P2P traffic/protocol of a p2p-containing metalink used by a p2p-enabled client, but not the HTTP/FTP traffic of the metalink. so a user can still get the file.

That makes me feel better about metalinks (I honestly don't know much about them).

Oh, right, pirate-talk . . . ummm . . . Yarr!!!!

[oblivious]

I don't know what anybody's talking about, but if you want regular people to have access to the downloads (if that's what you are even talking about), you need to make them normal http/ftp. Believe it or not, some people don't know what bittorrent, metalink, p2p are. (and don't want to find out.)

EDIT: Why does the protosite "look up" slfea.org and "get data" from success-and-career.ch? What's that all about?

[tombh]

EDIT: Why does the protosite "look up" slfea.org and "get data" from success-and-career.ch? What's that all about?

I'd seen that myself and did make me worry for a moment, what with all the virus and hacking that Puppy's websites are used to. Then I remembered that I'd got those tiny little flag images in the banner from random places in Google Images. Basically the images aren't stored on the server and are fetched from different sites all over the world, thus the reason for strange server addresses appearing whilst pages load. Naturally, I will be changing this by using LOF's recommendations of formal flag sets.

In honour of this welcome development I propose that we all talk (and write) like pirates for a while.

Garr! Be fair time me land-lubbers, batten down thar hatches, hoist thar main sail, thar's a storm a-brewing port-side 'n' it's our call to plunder ney those merry winds

[oblivious]

Basically the images aren't stored on the server and are fetched from different sites all over the world

Well, I hope they are from "non-dodgy" places - why they have "look up" rather than just load seems strange, and it sat there for an inordinately long time.....

what with all the virus and hacking that Puppy's websites are used to.

Yes, I've gotten to the stage where I just kill the page if I see anything unexpected. The Sri Lankan Foreign Employment Agency qualifies as unexpected

[tombh]

The Sri Lankan Foreign Employment Agency qualifies as unexpected

You're quite right! I've just deleted them.

[BarryK]

Okay, I've signed up with hostgator.com. My domain puppylinux.com is the primary domain, and I'll be moving over from Servage soon.

As announced earlier in this thread, forum member WhoDo has also signed up with Hostgator, and puppylinux.org will be moved there. Thanks for your generosity WhoDo.

Hey guys, my primary domain is pointing to directory 'public_html', but do you know if it is possible to change that? In Cpanel, I see that additional domains can be set to a particular directory, but there does not seem to be any way to change the directory of the primary domain.
Probably it doesn't matter really, as I suppose the directories of additional domains can be alongside 'public_html', not in it, so there should be no interference ...well, I hope so.

I've signed up for the 'baby' account, but I notice the next one up, 'swamp', has unlimited downloads ...can that really be true?