Enhancements for earnway.art Website

@mak94pk

I’ll start by refactoring the alias generation logic to allow unlimited custom aliases, fixing the current conflict. Next, I’ll integrate the registration gate and ad pop‑ups, then add tracking tables for IP and duration, and finally build the admin panel for link management and CSV export. I’ll deliver the complete feature set in 14 days. Do you have API keys for the ad networks and a preferred export schema?

@ranjika08

Your main risk is that the short-link system is now connected to member registration, task delivery, tracking, ads, and a merged PostgreSQL database, so each “small” change affects several business functions at once. The custom alias limitation, ad-before-result flow, redirect monetization, and member-only access all need to be handled at database and application level together, not as isolated edits. I’d review the existing source first, then map what should be removed, reused, and extended from the merged central database. I work a lot on existing systems where previous developers already delivered version one, but the second phase requires disciplined modification rather than quick fixes. In your case, Java/PostgreSQL experience matters because the work involves constraints, tracking storage, exports, permission logic, subscription conditions, and long-term data retention across one connected platform. A few details would help define the cleanest path: - Is the “About Us” document available in the project files here for the central database structure and design references? - Should the 5-year tracking retention stay only in PostgreSQL, or do you also want scheduled archive/export handling? - For tracking exports, do you need member-level self-download only, or admin download for all creators as well?

@Joya1996

The biggest challenge here is not the UI pieces, but rebuilding the short-link workflow so unlimited custom aliases, registration gating, ad display, creator-linked tracking, and subscription-based access all work reliably inside the current Java/PostgreSQL setup. With a merged central database already in place, the wrong implementation could create duplicate logic or messy reporting later. My approach would be to first inspect the current schema and short-link generation flow, then extend it in a way that keeps tracking, exports, and permissions consistent. I’ve worked on custom backend enhancement projects where link logic, user roles, paid/free feature separation, and reporting all had to be added onto an existing codebase. This brief reads like a proper phase-two backend development task, especially with the need for CSV/Excel exports, access duration logging, member backend controls, and ad/interstitial redirect behavior. Before giving a final scope breakdown, I’d want to pin down a few items: - How are invitation codes stored now, and should repeated custom alias reuse be unlimited per member or globally reusable under defined rules? - Do you already have the subscription plan rules documented, including which links are free vs paid for tracking? - Is there an existing admin/member dashboard we’ll extend, or should the member backend screens be newly created?

@marjanahmed13

Hi! My name is Marjan and I'm here to offer you my services as a skilled applicant with over a decade of experience working on Freelancer.com. I believe I am the best fit candidate for this project due to my extensive experience; I would like to have a discussion to get to know that we both are on the same page. Once the scope will be locked, I will start working on it right away.

@denisSolution

Hello, I'm Denis, a full-stack developer with experience working on Java and PostgreSQL-based systems, especially around CRM, wallet integrations, and link management workflows. I understand the core issues here: the custom alias restriction needs to be removed to allow repeated use of invitation codes, and the database consolidation requires careful cleanup of redundant functions while preserving essential features like member management and wallet systems. I'd approach this by first reviewing the existing Java and PostgreSQL setup to identify and remove unnecessary functions, then implement the new requirements in phases: removing the alias restriction, adding member verification for link generation, integrating ad display logic with countdown tracking, enhancing redirect pages with ad serving and tracking, and building the member backend for link management and reporting. The main risk would be data integrity during the database consolidation, which I'd handle by running parallel backups and validating migration steps before deletion. Another consideration is the ad integration timing—I'd ensure the short link only resolves after the ad window closes and tracking data is properly logged with creator attribution. I can start working right away. Let's connect and discuss the details. Thanks, Denis.

@bcosley

Hi, You're augmenting a Java/PostgreSQL stack with a gated, ad-supported short-link workflow and long-term data tracking. I’ve delivered similar link-shortener and analytics uplift work where reliability and clean data export matter for dashboards. I’d start by validating the current short-link flow, fix the alias collision to support repeated uses, then wire in the login gate, ad window, and tracking hooks. I’ll keep changes isolated, add test coverage, and prepare an exportable data schema for Excel/CSV. One risk is coordinating ad-window timing across generation and redirects without harming user experience. What fields and format do you want in the exported tracking data (IP, duration, creator IDs, timestamps, link) and preferred delivery format? Should the admin interface support five-year data retention with role-based access and export capabilities, and allow deletion/addition of short links? If we're aligned, I can outline the implementation phases before kickoff. Best regards, Brandon

@megauravpanwar

To fix the custom alias uniqueness constraint blocking repeated invitation codes, we must scope the alias uniqueness check to be nullable or scoped per user ID rather than globally unique in your PostgreSQL schema. Tech Stack & Architecture: • Backend: Java Spring Boot with optimized Hibernate mapping for high-throughput link generation. • Database: NetCup-hosted PostgreSQL, refactoring the merged CRM and wallet schema to drop redundant tables while indexing IP, access duration, and creator IDs. • Ad Interstitial & Redirect Layer: Stateful countdown logic with non-blocking WebSocket/Redis caching for 10-second redirect timers and ad network hooks (Adsterra, Google AdSense). • Tracking & Exports: Optimized SQL window functions for 5-year data retention, streaming large datasets directly to CSV/Excel to prevent memory spikes. I have 15+ years of experience engineering high-load Java backends, custom URL shorteners, and secure multi-tenant billing/subscription engines. Let us review your NetCup database dump and map out the milestone execution plan. Gaurav Panwar Senior Full-Stack Looking forward to discussing the architecture.

@mickeysz

Hello, The most useful thing I can flag is that item 1 and item 3D are the same data decision, and getting it right fixes the bug and enables everything you want to track later. Right now a custom alias is unique platform-wide, so the second member using their invitation code is rejected. But you do not actually want the same short URL pointing two places, that breaks redirects. You want many links carrying the same invitation code, each with its own real short URL. So separate the two: the short code stays globally unique for redirect, the invitation code becomes a separate repeatable field. That removes the restriction and gives you the per-creator tracking in 3C and 3D, since every click is then attributed to the creator's ID and invitation code. Any other way, the tracking export you want is not possible. On the advertising flow, the interstitial timing and the AdSense-style networks must be handled so views are counted honestly, since AdSense in particular suspends accounts for forced or auto-triggered ad views. I build the countdown and reveal to comply, or you risk losing the ad revenue the platform depends on. For the 5-year tracking data, IP and duration per click across many members grows fast, so I design that table for volume from the start, indexed for the date-range CSV exports in item 4. One question: is the merged PostgreSQL schema documented, or do I map the CRM, wallet and link tables from the source code first? That decides where I start.

@longngoc2307

Hi, there. - Truong here. "UNLIMITED CUSTOM ALIASES AND SHORT-LINK TRACKING" - I understand you need members to reuse invitation codes while adding ads, tracking, subscriptions, and PostgreSQL-based management without disrupting the existing system. I would first map the existing Java/PostgreSQL schema and short-link flow, then extend the current modules instead of rebuilding them. This reduces duplicated logic and protects the CRM, wallet, task, and member-management functions already in production. A common issue is tracking data growing rapidly over five years while exports become slow. I would use indexed event records, creator/date-based filtering, retention-aware storage, and queued CSV/Excel exports to keep reporting responsive. Which existing Java short-link module and PostgreSQL schema can you provide for local setup? Thank you.

@shayankhan333

Custom Alias uniqueness is a hard constraint in most short-link schemas, so lifting it means scoping aliases per user ID instead of globally, then reindexing. On the Java/PostgreSQL merged base I'll open aliases per member, gate generation behind registration with a countdown ad interstitial, and log IP plus dwell time into the tracking table for CSV export. 1. Is the existing codebase Spring Boot, or plain servlets? 2. Which ad network goes live first, AdSense or Adsterra? Happy to talk details in chat. Shayan

@AndrewJSMAN

I’ve architected and extended Java/PostgreSQL short-link systems with ad mediation, user auth, and subscription layers before—this maps directly to your stack. I’ll first patch the alias collision in `url_shortener` table by removing the unique constraint and adding a timestamp-based fallback for auto-generated aliases to prevent conflicts, then consolidate the merged PostgreSQL schema by pruning redundant tables and views while preserving the CRM, wallet, and task delivery tables. For the new ad workflow, I’ll inject a modal interstitial via a frontend overlay (Pure JavaScript) tied to a new `ad_queue` table, enforce member-only link generation with a Spring Security filter, and log every redirect event with IP and duration to a new `link_stats` table partitioned monthly to hit your 5-year retention. The member backend will reuse the existing admin UI but add a ShortLinkController with endpoints for CRUD, CSV export, and subscription tier checks against a new `subscription_plans` table—mapping free tier to daily task links only. I’ll align the ad mediation URLs with your AdSense/Adsterra endpoints and validate the 10-second redirect rule with a scheduled job. I can start immediately. Thanks, Andrii.

@tyronet2

You need the existing Java/PostgreSQL platform extended without breaking the merged CRM, wallets, task delivery, subscriptions, or partner data. I’ve shipped Java Spring Boot services, PostgreSQL systems, REST APIs, payment flows, and role-based management platforms. I’ll begin by auditing the source code, merged schema, authentication, and current alias constraints. Because one public alias cannot safely point to unlimited destinations simultaneously, I’ll implement user- or task-scoped aliases with versioned destinations and clear collision rules. I’ll then add membership checks, configurable advertising countdowns, redirect analytics, IP and visit-duration tracking, member link controls, subscription entitlements, and date-filtered CSV/Excel exports. All database changes will use documented migrations, indexed tracking tables, access controls, retention rules, and automated tests. Advertising integrations will respect each provider’s policies. Can you provide the repository, merged database schema, current deployment configuration, and required alias URL examples?

@pasion0128

★•══•★ Hi client ★•══•★ Your existing Earnway short-link system has several connected requirements: reusable custom aliases, member-only link creation, ad-gated redirects, creator tracking, IP/access-duration logging, member management, exports, 5-year data retention, and subscription-based tracking. I understand you want to extend the delivered Java/PostgreSQL system rather than rebuild everything. I can review the existing source and merged database, identify the current logic, then implement these features while preserving existing tracking and member functionality. I’ll pay particular attention to permissions, database performance, accurate attribution, and reliable CSV/Excel reporting. Could you provide the source code and current database structure so I can review the existing implementation and confirm the cleanest upgrade path? Best regards, Rico

@sonika1419

**DO NOT PAY ME UNTIL I COMPLETE! :)** Hello my valuable client :) I can definitely work on your working hours. My profile is new over here but I have 7 years of experience in this field. I have completely understood about your project. Also I will provide you free maintenance on your project for 1 year after project completion. Give me one chance to prove myself. Hit the chat button to get started. If you will not like my work then you dont need to pay me any money so dont worry and have faith in me :) I am eagerly waiting for your message.

@abhayk49

Hi, I can help enhance the existing Java + PostgreSQL platform without unnecessarily rebuilding the functionality that is already available in the central database. My approach would cover: ✔ Modify Custom Alias logic to support the required repeated invitation-code usage ✔ Integrate and optimize the existing merged PostgreSQL database ✔ Add member-only short-link generation with registration checks ✔ Implement configurable advertising/countdown flow for link creation and redirects ✔ Enhance tracking with IP, access duration, creator-based tracking, and CSV/Excel exports ✔ Develop the member/admin management interface and permissions ✔ Add daily-task link tracking and subscription-based tracking plans ✔ Maintain long-term SQL tracking data with a scalable database structure I have 6+ years of professional Java experience, including Spring Boot, REST APIs, PostgreSQL, database design, authentication, reporting, and production systems. I’m comfortable working with an existing codebase and extending it while keeping the current functionality stable. I’d first review the existing source code and database structure, then deliver the changes incrementally with proper testing and documentation. Best regards, Abhay Kumar

@mikes126

Ready to discuss the exact requirements privately and deliver a clean solution. I saw the project involves Python + mathematics/calculus in an education or academic context. Happy to jump on a short call or chat so you can walk me through the real scope instead of guessing. Quick approach once I understand the details: Clarify the exact deliverables and constraints with you Break the work into small, testable pieces Deliver working Python code (or supporting materials) with clear explanations so it’s usable in an academic setting Two quick questions: Is this primarily tutoring/support, building tools/scripts, or something else? What’s the preferred timeline and any must-have tech or format?

@dinobartolome

Senior Full Stack Developer here with 10+ years in tech. Your custom alias collision issue on the URL shortener is a straightforward fix -- the uniqueness constraint just needs to be scoped per user instead of globally, so each member can reuse their invitation code across multiple shortened links without conflict. I've worked with PostgreSQL extensively and have handled database merges like what you're describing with the NetCup migration and the central CRM database. The ad integration layer (AdSense, Adsterra, PropellerAds) with countdown timers and creator-level tracking is a well-understood pattern I've built before -- the tracking data export to Excel/CSV is the easy part once the event logging is solid. Honest note on Java: my daily drivers are Node.js, PHP and Python. I can read and work in Java codebases, but it's not my primary language. If you need someone who writes Java all day every day, worth filtering for that. If you're open to someone who can get the job done across the full scope -- shortener fixes, ad windows, member backend, subscription billing, tracking exports -- I'm your person. Want to start with a quick audit of the merged database and the alias issue? I can have a fix plan back to you within 48 hours.

@carlosv116

Hi. I have extensive experience successfully leading projects that involve feature modification and enhancement on web platforms, and I can execute this project with the same level of success. The requirements you outlined are clear, but I suggest we clarify the specific user experience you envision for the registration and advertising pop-ups, as well as the desired timeline for implementing these changes. To construct the project, I will focus on seamless integration with the existing PostgreSQL database while ensuring that the Java-based backend is optimized for the new functionalities, especially regarding link tracking and member management. It’s crucial to maintain a balance between user experience and necessary advertisements to ensure platform sustainability. What specific metrics do you envision using to measure the success of the new features post-implementation? Carlos

@Abror86

Hi-Abror Here From Uzbekistan. "Build Scalable Short-Link Tracking Features" - I can enhance your Java PostgreSQL platform using backend development, API integration, tracking, and database optimization. I can modify custom alias handling, member registration, advertising flows, redirect timing, IP tracking, access duration, subscription controls, and centralized franchise-style configuration. I will extend PostgreSQL storage, member management, CSV or Excel exports, five-year tracking retention, daily-task tracking, permissions, and subscription-based access controls. Would you like the existing Java source code and PostgreSQL schema reviewed first? Looking forward to working with you.