______________________________________________________________________________ | ________________________________________________________________________ | | | | | | | | | | | [ ] | | | | [] [ ][ ][ ][] /#\ | | | | [ ] [ ][] [ ][ ] /#####\ | | | | @jorgeelalto [] /#+#######\ /#\ | | | | /+++#++####++#\ /##+#+\ | | | | /-------- /+#+++++#+++++++++\/+++#+++++\ | | | | ---------------\ /+++++##++++++#++++##+\+++#++##++\ --- | | | |------/ ----- /++#+##++++#++#+++++#+++++\+++#+++#++\ \--| | | |___________________________/+##++++++#+++++###++++++###++\++#++++##+\___| | |______________________________________________________________________________| -------------------------------------------------------------------------------- L I N K S -------------------------------------------------------------------------------- INSTAGRM -+- LINKEDIN -+- PRSNLBCP __ ___/*~ | | / \_______ / \~ GITHUBRP -+- GITLABRP -+- SOUNDCLD \__/ \__//\\__/ | | __ / \\// __ PSPOTIFY -+- MYMUSICS -+- MUSICPGE / \__/ \______/ \ | | \__/ \__/ +- up 05/19 -+ -------------------------------------------------------------------------------- A B O U T M E -------------------------------------------------------------------------------- This is my personal, cozy, little page. Written in English because I don't want tildes or accents all over the place. And done in a minimalistic way (with random ASCII art) because it looks way l33ter and to keep bandwidth and server storage requirements down. Also because there is already enough bloat on the web. I am a bit of a computer nerd, and I love computer music as well. Contrary to common belief, I think there is a big part of the human soul in every computer, probably as a reflection of the people who build and program them. This happens especially around free software, and sustainable commercial software. I'm a computer music maker myself, having played the keyboards and piano in pop and rock bands from an early age. I shifted to digital music making in the exact moment I got a MIDI to USB adapter for my computer and got my first virtual instrument. I don't aim to make a career in music or even music for the people, but for myself. I work on my 7th Pyramid project as a hobby, to develop my music making and graphic design skills. As I advance in my Computer Engineering/Science degree and discover the state computer software, I'm trying to develop myself into a responsible programmer and software engineer, taking into account the future of software and humanity and how dependent we are and we will be on everything we, software developers, do and will do. If you want to check more stuff about me, just keep reading or go to my Instagram profile, Bandcamp page or LinkedIn CV. _______________ | | | Q U O T E S | |_______________| -------------------------------------------------------------------------------- xX -_-_- S P R E A D T H E I N F E C T I O U S B E A T -_-_- Xx _________________________________________________________________________ | | | - KCK -(@)-( )-( )-( ) ( )-( )-( )-( ) ( )-( )-(@)-( ) ( )-( )-( )-( ) | | - SNR -( )-( )-( )-( ) (@)-( )-( )-( ) ( )-( )-( )-( ) (@)-( )-( )-( )- | | - HHC -( )-( )-(@)-( ) ( )-( )-(@)-( ) (@)-( )-( )-( ) ( )-( )-(@)-( )- | |_________________________________________________________________________| -------------------------------------------------------------------------------- This is beautiful inspiration for software developers who are thinking about implementing a copy protection method which goes beyond serial or keyfile. Made by Vertion, KVR User. xX +-=-+ V's 10 Golden Rules of Copy Protection +-=-+ Xx 1. YOU CREATE YOUR CRACKER The better the copy protection mechanism, the better your cracker will be. Standard serial is okay. 2. EVOLVE FASTER THAN THE CRACKER Focus on evolving your software, not copy protection. 3. POLYMORPHIC COMPILATION Use header macros and hash the user identifier to compile a unique codebase for every customer. 4. UPDATE WEEKLY Add new features every week, even tiny ones. Make these changes visible and beautiful for the user to see. 5. CRACK YOUR OWN CODE Write your own cracks for (only) your own software and release. Design your software to extend on a flag being set given by a secondary program as a means for potential customers to further invest more time into your product. 6. INCOMPLETE DEMO Keep 2 compilations, the demo has missing code from it's codebase, also should be a different codebase shape than the full version (no copy/paste in asm). This can also be used for early releasing. 7. CONSERVE ENERGY Copy protection should require the least energy. Focus on your product and the features. No one will want to crack your software if it stinks. 8. DO NOT PUNISH WITH DONGLES This will build negative reputation and hedging among your customers. Avoid. 9. DO NOT PUNISH WITH ONLINE REQUIREMENTS OR DOWNLOADERS Customers have no idea how long your company or product will be available. If the means to validate online are unavailable, it will be a major disgrace to your company and it's products. Highly inadvisable. 10. BE THE JEWEL The ideal plugin is small and dedicated to what it does best. It sits in a zip file until it is ready to be placed in the appropriate directory. It needs only the serial it came with. In 100 years, we can still use it and feel joy in your wonderful product that stood the test of time, and now you are a legend. -------------------------------------------------------------------------------- P O W E R E D B Y O D D B O I /| /| /| /| /| / / | / | / | / | / | / / |/ |/ |/ |/ |/ F E A T . L O W P A S S E D E V E N /\ /\ /\ /\ /\ /\ / / \/ \/ \/ \/ \/ \/ -------------------------------------------------------------------------------- . . . . . . . . . .__________________________________________ . . . . . . . . . . . . . . . . . / \. . . . . . . . . . . . . . . . | T H A N K S F O R V I S I T I N G :) |. . . . . . . . . . . . . . . . \ /. . . . . . . . . . . . . . . . . .\ No copyright or anything, there is / . . . . . . . . . . . . . . . . . . . \ nothing innovative here. /. . . . . . . . . . . . . . . . . . . . . .\ 2019 / . . . . . . . . . . . . . . . . . . . . . . . \____________________________/. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .