标签：#web

I Built My First Token on Solana — Here's What Actually Surprised Me This week I went from zero tokens to minting, transferring, charging fees, and locking tokens so they can never move. Here's what stuck with me. Tokens don't live in your wallet Coming from Web2, I assumed tokens would just... show up in your account. Nope. On Solana, every wallet needs a separate token account for each token it holds. One mint, one folder. It felt weird at first. Now it makes sense. You can charge fees without writing a single backend The Token Extensions Program has a built-in transfer fee. One flag at mint creation time: spl-token create-token \ --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb \ --transfer-fee-basis-points 100 That's a 1% fee on every transfer, enforced by the blockchain. No middleware. No payment processor. No way to bypass it. You can make a token that literally cannot be transferred spl-token create-token \ --program-id TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb \ --enable-non-transferable I minted 10, tried to send 5, and watched the transaction get rejected. Not by my code — by the program itself. Perfect for credentials, badges, or certificates that should belong to one person forever. The biggest shift from Web2: these rules are set at creation and are permanent. You can't add a transfer fee to an existing token. You can't make a transferable token non-transferable later. It forces you to think about token design upfront, which is honestly a good constraint. solana #blockchain #webdev #beginners #100DaysOfSolana

I won't name names because I got in trouble for that last post but I interviewed with the biggest agency I've ever gotten a call back from. They are 150+ employees, at least one major national corporation as a client. You would think that because they are so high and mighty they have their s*** together but honestly no. The first interview was with the "big boss" the digital director. The second interview was actually 4 separate teams calls scheduled back to back with a total of 9 people. The director loved me and told me I would be moving on. He said my second call would be with three people which is hilarious because he wasn't even close to correct. My second interview was chaos. First call ended up being a different group of project managers than was listed, and they just hammered me with hypothetical situations of conflict the entire time. All rain clouds, no sun. Second call was two developers who didn't seem that invested in talking to me. They mainly just said that works comes in from many different places and you can be expected to work on a bunch of things while managing a bunch of people AND be suddenly put in front of a client at any point. My third call was hilarious because the top senior dev and the top senior designer in the company on this call loved me. We clicked on everything - our stance on AI, our views on WordPress and PHP in general, our approach to projects. My fourth call was back to doom and gloom - more managers and all just hypothetical situations about conflict and everything going wrong. The people on call four were telling ME that a person from call two has a "different idea of what finished means" and were basically talking s*** on this person who is probably their smartest back end developer. During all of this, the HR person had no idea who I was the entire time. I am interviewing virtually and would have to relocate and she sent me multiple emails about my "In Person Interview". My rejection email was actually the same email sent t

With Hov3r, you are able to switch between animated wallpapers, background audio, widgets, cursor skins, cursor animation, and create wake words or keybinded shortcuts. It also comes with a massive free library with thousands of cursor skins, background and background music for you to choose from. You can choose between a $2.99/month or a $9.99 lifetime subscription, and even refer friends and family to get either plan for free (more info on website). P.S. I have some free keys left from testing, while Hov3r offers a free trial for you to try the app out, shoot me a DM for a free license key to test the app out(if i still have any). Download now from: https://hov3r.app submitted by /u/CoolDownDude [link] [留言]

Hello guys, i am a 17 year old IT student and i have recently had a "trial job" at a Robotics company, the trial job is a part of my schools curriculum but one thing about the comapny is is that their website is horrible, it is years old and looks very outdated, so i wanted to propose the idea of making and effectively selling them a new one. The website has around 50 pages and made in Joomla however it is based on Joomla 3 so i would have to bring it over to a newer version. Anyway i was wondering how much i should ask for a website like this? From a discussion with a person who works in website selling and marketing the "big shot" companies would charge up to 20 500 Euro or 24 000 USD which is obviously too much for a person still in school with no actual professional experience, the price i made out to not be too much while also getting my money's worth was around 5 200 Euro or 6 000 USD. Despite me having no professional experience i have had time to redesign a tiny bit of their website simply so i can show them that i can actually make the website, so i am wondering if this price is appropriate for a web that would take me around 250-ish hours to make probably with the domain transfer and transfer to Joomla 5. The website is: www.exactec.com in case anybody wanted to check it out, it is in czech however you should still be able to tell the cost from the layout. also i think you can see which parts i did and didn't make. P.S: the current pages made by me aren't my full effort as they are not my trial job's fill and i only did them in spare time while learning robotics, the actual ones would be more thought through and professional. submitted by /u/Zealousideal-Mood-45 [link] [留言]

I've been specializing in frontend for more than ten years, gaining full stack and backend experience for the last four or five, and I'm starting to think I might just be done. Not to harp on the AI discussion that gets posted on here all the time, but I do feel like our jobs have fundamentally shifted over the last 12 months to something I no longer enjoy; I don't want to be a pseudo manager of AI agents, I want to write code, and if there's no longer a need for that I can just do something else. But I would like this community's help - looking at it from the ground up, what are fully unrelated jobs or industries where you feel like our skills would be most transferable? And I mean fully blue sky approach, things I might not have considered, not just coding in a different stack. I think I have above average computer skills and awareness of operating system details that would put me above a lot of other candidates from different backgrounds, so where could I go to leverage that (that is at least a little more future proof)? Or beyond computer at all, I feel like I have spent years building strong critical thinking skills and analytical reasoning; I just don't have a wide base of knowledge outside our industry to know where these would be best used. For practical purposes, I can't look at anything that would require its own degree and four more years back to school, but there have got to be lots of certifications I could get quickly to start to open doors and prove my qualifications. I'm certainly expecting a pay cut, but I'm open to entry level jobs if it means a good career path. So I am interested in your thoughts - if you were starting out today in any other field than webdev, where would you be looking? submitted by /u/mx-chronos [link] [留言]

- Good pay compared to many other professions - Remote/hybrid work options - Opportunities to travel or work in different countries - Working with global teams - Decent work-life balance - Solving interesting problems - Continuous learning - Respect and recognition in society What keeps you motivated to stay in software development? submitted by /u/Majestic-Taro-6903 [link] [留言]

I was not expecting gyroscope API to be this sensitive lol but it was a subtle bug in my implementation. ps. I even added Absolute orientation sensor to compare stability... You can visit the fixed live demo here - https://ctx-0.github.io/gyroscope/ (use a mobile device) Here's the repo if you want to take a look - https://github.com/ctx-0/gyroscope submitted by /u/goldbookleaf [link] [留言]

O&amp;#039; Billion dollar companies. It boggles the mind. Probably takes $500K in tokens for AI to figure it out. </rant> submitted by /u/centuryeyes [link] [留言]

I've had Claude make a few static website frameworks for me and I noticed some patterns. Rounded buttons, serif H1's that are soulful rather than descriptive, two contrasting buttons in the hero, loads of emdashes, "actually's", and hero "scroll down" directions. While this doesn't check all the boxes, it checks plenty of them. Reading the preview site text makes it seem like a joke. Is this for real??? On the other hand, it is missing the signature emphasis word in italics and a different color. submitted by /u/Adfarquhar [link] [留言]

I've been doing webdev for over a decade. Now I feel burnt out and worried about prospects. Mid-career and barely getting interviews. Not only do we have to compete on a global stage (I'm US based), but we have to deal with regular layoffs (and that's accelerated due to AI). What used to be reliable work with good pay, seems to have fallen off dramatically in both aspects. Do you agree? Would your recommend this field to a friend? submitted by /u/hypercosm_dot_net [link] [留言]

[ Removed by Reddit on account of violating the content policy . ] submitted by /u/Ok_Efficiency_1116 [link] [留言]

submitted by /u/cekrem [link] [留言]

Before a new template goes live, I like to crawl 10-20 rendered examples and check the boring stuff that tends to create SEO cleanup work later: Exactly one indexable canonical URL per page state Title and H1 are generated from different fields, not duplicated blindly No empty meta descriptions from missing CMS fields Pagination/filter URLs either have a clear index/noindex rule or are blocked from exploding into crawl traps Product/article schema is omitted when required fields are missing instead of outputting half-valid JSON-LD Internal links render server-side or at least appear in the initial HTML for important paths Most of this takes less time to catch in staging than it does to explain to a client after 5,000 thin URLs get indexed. The best SEO fixes are usually the ones that never make it to production. submitted by /u/VRTCLS [link] [留言]

TL;DR : Crypto arbitrage windows on liquid pairs now close in under 100 ms. A REST polling loop typically takes 1–1.5 seconds round-trip. WebSocket delivers the same data in 20–100 ms. If you're still polling REST endpoints for orderbook data in 2026, you're missing the majority of opportunities — not because your strategy is wrong, but because your data plane is fundamentally too slow. This post walks through the math, shows a benchmark I ran on a handful of major exchanges, and provides production-grade Python code for a WebSocket client that handles reconnects, heartbeats, and orderbook reconstruction. 1. The numbers that broke REST polling When I started writing crypto arbitrage bots a few years ago, polling Binance's REST API every 500 ms was perfectly acceptable. Spreads were wide, arbitrage windows lasted multiple seconds, and the orderbook for BTCUSDT moved slowly enough that a half-second-old snapshot was still tradeable. In 2026, the same approach doesn't work. Here are the numbers as they stand today: Metric Value Median crypto arbitrage window on liquid pairs 30–80 ms Window closes in under 100 ms ~90% of cases REST round-trip latency (request → response → JSON parse) 1.0–1.5 seconds WebSocket update delivery latency (push from exchange to client) 20–100 ms The math is brutal. A 100 ms window cannot be caught by a 1500 ms poll. By the time your REST response arrives, the orderbook you're reading is 15 cycles stale. You're not "slow" — you're not even in the same temporal universe as the event you're trying to react to. 2. Why REST is fundamentally slow REST APIs over HTTPS carry overhead that adds up: TCP handshake — three packets to establish, typically 50–150 ms on intercontinental hops. TLS handshake — another full round-trip, 30–100 ms. HTTP request/response — the actual data exchange. JSON parse — depending on payload size, 5–50 ms. Rate-limit budget — most exchanges cap REST to 10–20 requests per second per IP. Polling faster gets you banned. Yes,

Blockchain performance is determined by consensus rules. There is no acceleration layer within the protocol. One of the most common misconceptions about blockchain technology is the belief that transaction speed can be dramatically increased through special tools, hidden settings, or external services. While applications can improve user experience and optimize how information is presented, they cannot change the fundamental rules that govern how blockchain networks process transactions. At the core of every blockchain is a consensus mechanism. Consensus is responsible for ensuring that independent participants agree on the validity and order of transactions before they become part of the permanent ledger. Whether a network uses Proof of Work, Proof of Stake, or another consensus model, transaction processing remains tied to the protocol rules that all participants follow. Every transaction moves through a structured lifecycle: submit → validate → confirm Submission introduces the transaction to the network. Validation ensures that the transaction complies with protocol requirements and contains legitimate data. Confirmation establishes agreement across the network and records the transaction as part of the blockchain. These stages are not optional. They are essential to maintaining consistency and trust within decentralized systems. Because blockchain performance is governed by consensus, there is no protocol-level acceleration layer that can bypass validation or force immediate finality. No application can override consensus. No service can remove verification requirements. No external process can alter the execution sequence established by the protocol. What users often interpret as slow performance is usually the result of network conditions such as congestion, validator workload, transaction prioritization, or fee market activity. These factors can influence confirmation times, but they do not change the underlying rules of the system. Blockchain networks are d

Keyboard accessibility is one of the most important — and most neglected — aspects of web accessibility. An estimated 2.5 million Americans have motor disabilities that prevent mouse use. If your site can't be operated entirely by keyboard, you're excluding them completely. The Four Core Principles WCAG 2.2 Principle 2 (Operable) contains the keyboard requirements: 2.1.1 Keyboard (AA): All functionality must be operable via keyboard 2.1.2 No Keyboard Trap (AA): If focus moves into a component, it must be possible to move it out 2.4.3 Focus Order (AA): If page can be navigated sequentially, order must be logical and predictable 2.4.7 Focus Visible (AA): Any keyboard-operable UI must have a visible focus indicator 2.4.11 Focus Appearance (AA, new in 2.2): Focus indicator must meet size and contrast requirements Testing Without Automated Tools Start with the basic keyboard test: Unplug (or ignore) your mouse Press Tab to move forward through interactive elements Press Shift+Tab to move backward Use Enter/Space to activate buttons, links, checkboxes Use arrow keys for radio groups, menus, sliders Use Escape to close dialogs and menus Any element you can't reach or activate? That's a WCAG 2.1.1 failure. The Most Common Keyboard Failures Custom dropdowns and menus // ❌ Keyboard inaccessible function Dropdown ({ items }) { return ( < div onClick = { toggle } className = "dropdown" > { items . map ( item => ( < div onClick = { () => select ( item ) } > { item . label } </ div > )) } </ div > ); } // ✅ Fully keyboard accessible function Dropdown ({ items }) { return ( < div role = "combobox" aria-haspopup = "listbox" aria-expanded = { isOpen } tabIndex = { 0 } onKeyDown = { handleKeyDown } // handles Enter, Space, Arrows, Escape className = "dropdown" > < ul role = "listbox" > { items . map (( item , i ) => ( < li key = { item . id } role = "option" tabIndex = { - 1 } aria-selected = { i === activeIndex } onKeyDown = { e => e . key === ' Enter ' && select ( item ) } > { item

Hi, I'm Heet Sanghani, a Python Developer and AI/ML Engineer from Ahmedabad, Gujarat, India. I currently work at BrainerHub Solutions building backend systems and AI-powered applications. In this post, I want to share how I built BidXpert — a real-time auction platform using FastAPI. What is BidXpert? BidXpert is a real-time bidding platform where users can create auctions, place bids, and get instant updates using WebSockets. Tech Stack Backend: FastAPI + Python Database: PostgreSQL Real-time: WebSockets Auth: JWT Authentication Deployment: Docker What I Learned Building BidXpert taught me how to handle concurrent WebSocket connections efficiently in FastAPI and manage real-time state. About Me I'm Heet Sanghani — Python Developer & AI/ML Engineer based in Ahmedabad. Check out my portfolio and other projects at: 👉 https://heet-sanghani-portfolio.vercel.app/ python #fastapi #webdev #ai

Every inventory tool says real-time. Every single one. Open the settings. Find the sync frequency configuration. It says 15 minutes. Or 10. Or 30 on the cheaper plan. That's not real-time. That's a cron job. There's a meaningful architectural difference and the industry has collectively decided to pretend there isn't. I want to make the technical case for why this matters — and ask why so few tools have actually fixed it. What "real-time" actually means technically Real-time in distributed systems has a specific meaning. It means the system responds to events within a bounded, predictable latency — not on a schedule. javascript// This is NOT real-time — this is scheduled // Latency: up to 15 minutes (the full interval) setInterval(async () => { const stock = await getSourceOfTruth(); await syncToAllChannels(stock); }, 15 * 60 * 1000); // This IS real-time — event-driven // Latency: network round-trip (~milliseconds) orderEventBus.on('order.confirmed', async (event) => { const updated = await decrementStock(event.sku, event.qty); await propagateToAllChannels(updated); }); The first example responds to state changes on a schedule. The second responds to events as they happen. These are fundamentally different architectures with fundamentally different latency guarantees. Calling the first one "real-time" is technically incorrect. It's scheduled sync. The schedule is just short enough that most users don't notice — until they do. When users notice The failure mode is predictable and well documented: javascript// Flash sale scenario — 10x normal velocity const normalOrdersPerWindow = 500 / ((24 * 60) / 15); // ~5.2 const flashSaleOrdersPerWindow = normalOrdersPerWindow * 10; // ~52 // 52 orders processed against potentially stale stock // per 15-minute window // across multiple channels simultaneously // none of which know what the others have sold 52 orders per window. At 2% oversell rate — just over 1 oversell per window. Across 96 windows per day — nearly 100 oversel

Hello, I'm Maneshwar. I'm building git-lrc, a Micro AI code reviewer that runs on every commit. It is...

Server-side tracking on Shopify Plus is no longer optional in 2026. Browser-side analytics tags now miss around 30-40% of conversion events on Safari, Firefox, and ad-blocked sessions when ITP, consent rejection, and ad-blockers combine, and the server-side fix — a GTM server container or an equivalent gateway — is the difference between a usable Meta CAPI feed and a reporting hole that quietly tanks your paid-media ROAS. Why browser-side pixels broke first The structural decay started years ago and accelerated through 2025. Safari's Intelligent Tracking Prevention caps JavaScript-set first-party cookies (anything set via document.cookie ) at 7 days, and 24 hours when the URL carries a tracking parameter like fbclid or gclid . Server-set first-party cookies sent via the HTTPS Set-Cookie header can still persist up to 400 days, unless the cookie's host resolves through a CNAME to a third-party — then ITP collapses that lifetime back to 7 days. Combine that with Firefox Enhanced Tracking Protection (around 5-8% of UK desktop traffic), ad-blockers (around 30-35% adoption on desktop), and consent-management platform rejection (typically 20-40% of EU sessions), and a typical Shopify Plus storefront ships measurable signal for only 60-70% of real purchase events. We have audited stores where a server-side migration recovered around 28% of attributed purchases inside the first 7 days of switchover — not because the conversions stopped happening, but because the browser layer stopped reliably reporting them. What a server-side gateway actually does A server-side tracking gateway intercepts the event between the storefront and the destination platform (Meta, Google Ads, TikTok, etc.) and re-emits it from your domain. The browser still fires a lightweight web-side ping, but the heavy payload — order ID, customer hash, line items, value — travels server-to-server. Cookies stay first-party because the request originates from your own subdomain. The destination platform sees a c