Pulsed Media

Pulsed Media is an BitTorrent Seedbox provider, formed in February, 2010.

Background information

Pulsed Media was formed in 2010 together with Custom Seedbox as a joint-effort. Since then Custom seedbox has been merged with Pulsed Media, and services from original Custom seedbox users for the most part migrated to newer Pulsed Media offerings utilizing the PM Software Stack.

Software development is done in-house with vast experience in web development, and PM Software Stack differs in a multitude of ways from competition. Concentration has always been in performance and usability, which are considered to be partially the same objective where performance optimization often results in better usability.

Services

Pulsed Media offers seedbox hosting, dedicated servers, virtual private servers with a multitude of value added services.

Pulsed Media concentration is in high value services, providing the best value for our customers is a key objective.

Company

Pulsed Media is part of Finnish company NuCode, registered early 2009. NuCode is VAT registered company and is therefore required to charge VAT from residents of the VAT area. NuCode VAT number is FI22551954. All listing prices exclude VAT, and VAT is added during checkout for VAT region residents.

Policies and terms

• Pulsed Media Refunds Policy
• Pulsed Media Privacy Policy
• Pulsed Media Seedbox SLA Policy
• Pulsed Media Free Bonus Disk Policy
• Pulsed Media Auctions Terms And Conditions

Development Bounty Program

We have started offering a development bounty program for various software issues.

This bounty program is offered by us and not affiliated with any particular project, repository or developer.

Bounty Program Terms

Payout is done either via Paypal, IBAN Wiretransfer or service credit towards our services. For payment we need your name, country and payment details. Receiver of the bounty is responsible for all taxes applicable to him/her. Payout is to be done within 30days from accepted work, unless monthly maximum has been reached. If monthly maximum in payouts has been reached your payout will be moved to next month's payables. Typical payout date is around 15th of each month.

Every payout has a grace period of 30days from the date when considered complete to see if any issues arise from that code. If any issues arise these have to be fixed before considered complete.

Maximum euro sum of monthly payouts is 1500€ for cash payments. Maximum for service credits is 3000€ monthly.

Service credit payouts are double value. Meaning for a 100€ bounty you receive 200€ in service credit. This requires an open and active billing profile with us, and you can use this credit for any of our publicly offered services.

Bounties are not considered complete until merged / implemented on main branch of applicable piece of software, and approved by the responsible developers of said software. For example, for rTorrent this person would be Rakshasa.

Only production ready fixes are applicable, if the code is not production ready or has issues the bounty is not considered complete. Production ready means something we can implement for our users to utilize right away.

We reserve rights to change these terms at any time. If you have questions please contact our support.

Open Bounties

Bounty sums are euro payouts, if you choose service credit you get double.

• pulsedBox conversion to ElectronJS and some stretch goals 500€ base, all stretch goals done 1250€
• rTorrent complete network traffic halts due to tracker issues 150€ 300€
• Multithreading library for rtorrent, and sample usage with schedulers 300€
• Increased threading for peer connections 200€
• Updating all trackers at torrent start at once, in a non-locking multithreaded way 150€
• Multithreading per each torrent to drive more scalable performance 150€
• "Blocking" peers for upload/download -- super slow peers which essentially block your up/down slots 50€
• Typo / Misconfiguration should not halt rTorrent from starting 25€

General code quality guidelines

All code should be thoroughly tested for a multitude for failure scenarios. We recommend that you first setup test scenarios for the desired outcome and failure modes. Reliability of the code is of utmost importance. Good documentation and code formatting are key values as well for future maintenance. Hence code should have at minimum one comment per 10 lines of code, no piece of code should nest multiple recursive functions on single line (especially without commenting!), and code should not exceed "4 levels of depth" for the particular function -- if it does split it into multiple functions / methods / classes. Code re-use is highly recommended as well, if you have something which you need to do fairly frequently have a separate function/method for it. No copy pasta salad.

Linux kernel development guidelines are a good source for having a great code quality.