#Code Similarity API
Explore tagged Tumblr posts
Text
The modder argument is a fallacy.
We've all heard the argument, "a modder did it in a day, why does Mojang take a year?"
Hi, in case you don't know me, I'm a Minecraft modder. I'm the lead developer for the Sweet Berry Collective, a small modding team focused on quality mods.
I've been working on a mod, Wandering Wizardry, for about a year now, and I only have the amount of new content equivalent to 1/3 of an update.
Quality content takes time.
Anyone who does anything creative will agree with me. You need to make the code, the art, the models, all of which takes time.
One of the biggest bottlenecks in anything creative is the flow of ideas. If you have a lot of conflicting ideas you throw together super quickly, they'll all clash with each other, and nothing will feel coherent.
If you instead try to come up with ideas that fit with other parts of the content, you'll quickly run out and get stuck on what to add.
Modders don't need to follow Mojang's standards.
Mojang has a lot of standards on the type of content that's allowed to be in the game. Modders don't need to follow these.
A modder can implement a small feature in 5 minutes disregarding the rest of the game and how it fits in with that.
Mojang has to make sure it works on both Java and Bedrock, make sure it fits with other similar features, make sure it doesn't break progression, and listen to the whole community on that feature.
Mojang can't just buy out mods.
Almost every mod depends on external code that Mojang doesn't have the right to use. Forge, Fabric API, and Quilt Standard Libraries, all are unusable in base Minecraft, as well as the dozens of community maintained libraries for mods.
If Mojang were to buy a mod to implement it in the game, they'd need to partially or fully reimplement it to be compatible with the rest of the codebase.
Mojang does have tendencies of *hiring* modders, but that's different than outright buying mods.
Conclusion
Stop weaponizing us against Mojang. I can speak for almost the whole modding community when I say we don't like it.
Please reblog so more people can see this, and to put an end to the modder argument.
#minecraft#minecraft modding#minecraft mods#moddedminecraft#modded minecraft#mob vote#minecraft mob vote#minecraft live#minecraft live 2023#content creation#programming#java#c++#minecraft bedrock#minecraft community#minecraft modding community#forge#fabric#quilt#curseforge#modrinth
1K notes
·
View notes
Text
“Cooking up comfort”
mpreg!Choso x you
next part here<3
Summary: Neither you or Choso imagined that this could ever be possible, at first it was just a thought that crossed your mind. Since Choso was a half curse and had connection with the sorcery world. Would it be too crazy to find a way for him to get pregnant? Well, after doing an extensive research for a couple of months, and ten weeks later, Choso was expecting your child.
Even though it resulted possible for him to get pregnant, it wasn’t something common, a man getting pregnant was still something rare even though a lot of strange things were normal in this sorcery world. It was truly a blessing for both of you, it had its risks and complications, but he really wanted this, to form a family with you, and you would be there for him in every step of the way.
or
Where you cook lunch for your pregnant boyfriend and he gets too emotional (and nauseous)
contents: Mpreg Choso x female reader, fluff and slight angst, emotional hurt/comfort, slice of life, Unconventional Pregnancy, Alternate Universe - Canon Divergence
Notes: Long story short, I was using Janitor AI, my API code was about to expire and I was bored and came up with this JSKSJS It wasn’t exactly like this, this is more of an inspired fic.
I mention this briefly on the fic, but basically they made their research until they found a doctor who could help them. The doctor was also a sorcerer, of course average people didn’t knew this, but other sorcerers did.
the doctor’s cursed technique was similar to Mahito’s technique, in the way he could modify the bodies of his patients without having to necessarily use a scalpel. He temporarily modified Choso’s reproductive system, giving him a female reproductive system until he conceived and his baby was born.
For you to be able to impregnate Choso, the doctor made an incantation for you, so first he modified your reproductive system turning it into a male one, but it was temporary, like Choso’s procedure but with a slight difference. With an incantation given to you by the doctor, you were able to change your reproductive system from male to female and viceversa, you couldn’t do it too often as you had to wait a few hours because of how energy consuming this was, but aside from that, you could modify it as you pleased. Choso’s procedure wasn’t like this, because to have a baby he needed a stable reproductive system that could be fertile, that’s why he had to have a female one during his whole pregnancy until the baby is born.
𓈒 ݁ ₊ ݁
Choso remembers well how he felt that day, when all your efforts and the procedures you both had to get through finally paid off. He felt shock, excitement, fear, extreme happiness, truly an adrenaline mix of emotions, after all, it’s not every day you’re a man who gets told that he is pregnant.
He was beyond excited to start a little family with you, the love of his life. He was grateful to have you by his side, supporting and loving him so sincerely, it was a genuine kind of love. He was totally convinced that you two were soulmates, sometimes it made you giggle by the way he explained so passionately to you that hypothesis.
It’s been already ten weeks since you two received the good news, but it hasn’t been exactly easy for him. The doctor explained this beforehand, so you two would know the risks and complications that were involved in Choso’s unique condition. Since he had a male body with a now female reproductive system, his body had to adapt and prepare for it, and now that he was finally pregnant, some symptoms were significantly stronger for him than they would be in an average pregnancy.
On the good side, since he had his blood manipulation technique, he could control things like his blood pressure, which was a really great advantage for him. On the other side, things like mood swings, cravings (and food aversions), and morning sickness were just a pain in the ass.
Choso couldn’t help but feel guilty that you had to keep up with him, you were just so kind to him it made him want to cry. Right now, he was reading a knitting and crocheting magazine next to you on the sofa, he enjoyed creating yarn pieces for his loved ones, but it mainly helped him to feel more human in a way, it had significantly helped with his existencial crisis as a half-curse, so it was a great hobby for him.
Focused on reading, he had a small frown on his face, which you thought it was adorable because he didn’t even noticed when he did it. You gently brushed the wrinkles between his eyebrows with your thumb, getting Choso’s attention and making him smile awkwardly when he noticed he was frowning unconsciously.
“I was doing it again.” He chuckled, now gently holding your hand that was caressing his frown. “I found an interesting pattern that I can do with a thin yarn.” He showed you on the magazine. “I think it would be perfect for the baby, because I need a special yarn for them so it doesn’t hurt their skin.” He explained with his usual calmed demeanor, and the idea of him crocheting things for the baby made your heart melt.
You took a look at the magazine, giggling at the images of tiny gloves and baby hats. “Yeah, our baby will look so cute with the tiny crochet pieces you’ll do for them, and it will also keep them warm, it’s perfect.”
You looked at the clock on the wall and noticed that it was time for lunch. Ever since Choso’s cravings started, you’ve improved your cooking skills so much that now cooking him specific plates he craved was like a personal challenge for you.
You stood up from the couch and stretched your arms above your head, Choso’s eyes subtly looked at you and the way your t-shirt lifted up just enough to see a strip of skin of your lower abdomen, making him blush slightly and turn to look down, back at his magazine.
“I’ll cook lunch for us.” You announced and Choso looked at you again, with a special shine in his eyes. “Is there something specific that you want?”
Choso thought about it for a moment, he loved the way you cook and having lunch next to you was one of his favorite parts of the day “What about avocado pasta? it’s been a while since I’ve eaten avocado.” He suggested.
You didn’t have a single avocado in the house. But it wouldn’t stop you.
“Sounds really good, avocado pasta it is.” You smiled at him, turning around to walk towards the main entrance. “I’ll be right back, I’ll go get some avocados!”
He couldn’t say a word before you were already outside. Half an hour later, you came back home with a bag of three avocados and also some cream, but you noticed a certain smell in the air, you walked into the kitchen to see Choso stirring a pot, boiling the noodles, he once again looked at you with that awkward smile of his.
“But Choso, I was going to cook lunch for us.” You said, leaving the avocados in the kitchen counter to walk towards him.
“I know, I know! I just wanted to do something while you were at the store. I want to help you as much as I can while I’m still not useless, you know?” He answered with a slight pout, he appreciated that you wanted to do things for him, but sometimes he felt like a burden, so he wanted to keep helping you now that his baby bump wasn’t big or heavy.
You caressed his strong arm, resting your cheek against his skin, “You won’t be useless, Choso. You’re carrying our baby and it takes lots of effort.” You said reassuringly. “I just want you to be relaxed, alright?” You explained to Choso your desire for him to experience a peaceful and relaxed pregnancy as much as he could, knowing that his journey wouldn’t be as easy as a regular pregnancy.
He put aside the wooden spoon he was using to stir the noodles and sighed, his gaze fixed on the bubbling water. Your arms moved to wrap around his waist, and your hands found their way to caress the small bump.
“Thank you for boiling the noodles, though.” You murmured, your cheek resting against his back. “But please don’t worry about cooking or washing dishes, let me take care of it so you and the baby can crochet something or watch a movie on TV.” A smile appeared on your face when you felt him chuckle.
He turned around to cup your face with his big hands, leaning in to leave a kiss on your forehead, “Alright, I can’t argue with you.” He smiled softly, looking at you with those tired eyes. “I’ll go to the living room, but please tell me if you need me to help.”
You nodded, standing on your tippy toes to leave a kiss on his lips.
𓈒 ݁ ₊
Choso understood completely that you wanted to do things for him, to make his day a little bit easier, he would do the same thing in your place, or he might be even worse. But again, he felt guilty.
It was most likely a product of his condition and hormones, because he just felt really bad that you were doing so much for him every day, things he could perfectly do himself. With this weight on his heart, he looked at you from the sofa, the food was ready and you placed the two plates on the table.
“Avocado pasta for your majesty.” You said playfully, taking your seat at the table.
Choso chuckled at your words, taking a seat next to you. He picked his fork and look down at the vibrant plate, the noodles were saturated with this creamy avocado sauce that you prepared just for him, and without wasting any more time, he pinched a few short noddles and started to eat.
But as he chewed, he started to think about how weird it felt to eat hot mashed avocado, the taste of the ripe fruit almost reminding him of a trash-bag with rotten vegetables, that smell was stuck on his nose and the slimy texture didn’t help. He started to chew more slowly, lowering the fork and setting it down with a soft clink against the plate.
While you were eating, you noticed Choso’s change of demeanor, and an expression on his face that seemed like he was about to cry and throw up, it worried you. “Choso? Are you alright?” You asked carefully, with a hint of concern.
He looked at his almost untouched plate with a mix of guilt and frustration. He felt overwhelmed by his fluctuating emotions, and this sudden aversion to the flavor of avocado only added to his distress.
“I’m sorry, love. I just… I can’t handle the taste of avocado right now,” Choso replied, his voice filled with frustration. He quickly looked at you “It’s not your fault, I know you put effort into cooking for us. It’s just… this pregnancy is messing with my taste buds and it’s driving me crazy.”
He sighed, his eyes welling up with tears. “I hate feeling like this, like I’m being ungrateful for all the things you do for me,” he continued, his voice wavering. “But the hormones are making everything so intense and overwhelming. I just want to be normal again and enjoy the things I used to.”
You felt a wave of sadness wash over your heart, it was difficult to see him like this, knowing that his pregnancy state is amplifying even more his frustrating emotions, you wished you could take all his suffering away from him.
You moved his plate aside and got closer to him, protectively wrapping him into your arms, his cheek rested against your collarbone while he hid in the crook of your neck. “It’s alright, it’s alright…” You cooed really softly, caressing his hair and letting him cry as much as he needed.
Choso shook his head, “it’s not alright, you even had to go out to buy the avocados to cook what I asked you and now I can’t even eat it.” He looked up at you, his eyes big and filled with guilt, “I didn’t want to make you upset, I just really can’t stand the taste of it right now, b-but I can make up for it! I can do whatever you want, I can cook something for you, just ask and I’ll-“
Before he could start to hyperventilate further more, you cupped his face in your hands, making him look into your eyes with his own glossy ones. When you pressed your lips on his forehead so softly and tenderly, he could only pout because of how endearing it was, you were too good to him, he didn’t felt like he deserved it.
“Breathe, baby, just try to breathe deeply for a moment.” You instructed gently, helping Choso to feel more grounded.
Wiping some stray tears with your thumbs, you continued to talk to him. “I’m not upset, pretty thing, it’s just avocado and some noodles, I couldn’t possibly get mad at you for it.” You smiled at him, your soft giggles making him feel more at ease.
Even though that pet name made him blush slightly, he still had some lingering self-deprecating thoughts. He opened his mouth to keep talking, but you stopped him right away with a short kiss.
You continued, with the softest voice. “I know this has been a really difficult journey for you, baby. I know you wish you could be like before, but I want you to remember that it will all be worth it in the end.” You smiled softly and reassuringly at him, “Some months ago, we wouldn’t even think this could be possible, but now look at you! You’re ten weeks along and you’re doing it amazingly.”
He smiled softly, his crying starting to cease. He leaned his head back on your shoulder, finding comfort in your warmth. “I think I’ve never imagined myself being pregnant.” His voice tinged with a mix of vulnerability and gratitude. “Well, I never really pictured myself living a peaceful life… But now, I feel so glad that I get to experience it with you.”
Choso now sat straight, wiping the remaining tears from his cheeks and sniffling his nose a couple of times, “Thank you for keeping up with me, even when I’m difficult sometimes.” He reached out to cup your face with his hand, gently caressing your cheek with his thumb.
You nuzzled into his touch, “Your body is going through big changes, it’s natural that you feel overwhelmed. But you’re not alone, we’re a team.” You kissed his palm, your lips lingering for a moment before you gently pulled away.
Choso's eyes reflected gratitude as he let out a small sigh. "I appreciate that more than I can express."
Now that he was more calmed, you remembered that he still had to eat something, he needed to eat good for him and the baby.
"How about we distract ourselves for a bit? I'll cook something different, and you can join me in the kitchen. It might be a good way to take your mind off things."
His eyes brightened with interest. "Cook together?"
"Yeah," you chuckled. "We'll make it a You and Me cooking special. What do you think?"
Notes: I’m not completely satisfied so I’ll write more one-shots for this mpreg Choso au !!
likes and reblogs are greatly appreciated!! it motivates me a lot<3
#jujutsu kaisen#fanfic#jjk choso#jjk imagines#jjk mpreg#jjk x reader#jjk fanfic#choso imagine#choso one shot#choso#choso kamo#choso x reader#mpreg choso#mpreg fic
102 notes
·
View notes
Text
About my fake staff ask
How I made it:
Currently, the tumblr API just... lets you make a post in which you "reply" to an "ask" from an arbitrary user, containing arbitrary content.
In tumblr's Neue Post Format (NPF), responses to asks look similar to other posts. The only difference is that they have a special entry in their "layout," specifying which part of the post is the ask, and who it is from.
Right now, if you try to create an NPF post with this kind of layout entry in it, it just works! You can use this to make an "ask" from anyone, containing anything, and answer it.
This is a huge bug and presumably will get fixed sometime soon?
How I discovered the bug:
Weirdly enough, I find out about it while trying to improve @nostalgebraist-autoresponder's alt text features this past week.
As you may have noticed, Frank now writes alt text differently, with more clarity about which pieces are AI-generated and what role they play.
While making this change, I found myself newly frustrated with my inability to use line breaks in alt text. The API used to let me do it, but then it stopped, hence all the "[newline]" stuff in older alt texts.
After poking around, I found that you can use line breaks in alt text on tumblr, and you can do this through the API, but only if you create posts in NPF.
Frank creates posts in legacy, not NPF. This has been true forever, and it works fine so I've had no reason to change it.
Fully rewriting Frank's post creation code to use NPF would take a lot of work.
Right now, Frank's language model generates text very close to a limited subset of HTML, which I can send to tumblr as "legacy" post content basically as-is. To create posts in NPF, I'd have to figure out the right way to convert that limited HTML into NPF's domain-specific block language.
I wasn't going to do that just to support this one nicety of alt text formatting.
"But wait...", I thought.
"Frank is already making these posts, with the alt text, in legacy format. And once they exist on tumblr, it's easy to determine how to represent them in NPF. I just fetch the existing post, in NPF format."
So all I need to do is
Have Frank make the post, as a draft, with the alt text containing "[newline]" or something in place of the line breaks I really want.
Fetch this draft, in NPF.
Create a new NPF post, with the same contents that we just fetched, in whichever state we wanted for the original post (draft, published, or queued).
Delete the draft we made in step 1.
This was convoluted, but it worked! I patted myself on the back for a clever workaround, and went on to do other stuff for a while...
...and then it hit me.
In the case where the post was a response to an ask, Frank was doing the following:
Responding to the ask.
Fetching the response in NPF.
Creating a completely new post, identical to the response -- including the contents of the original ask.
Deleting the original ask.
Meaning, you can just make asks ab nihilo, apparently.
So after a few more tests, I went and made the @staff ask, as one does.
Unfortunately, once the bug gets fixed, Frank's newlines-in-alt-text solution won't work for asks anymore... oh well, it wasn't a big deal anyway.
444 notes
·
View notes
Text
Just learnt how to turn HTML to Image
Friday 6th October 2023
Yeah just figured out how to turn HTML tags into an image you can download and save! The idea popped up because I came across a image generator from the user inputting the text and images and the generator would merge all of that into a .png file for you to save. So, I thought "mmmh I could do that?" (^^)b
・゚: *✧・゚:* and I did *:・゚✧*:・゚
Now I'll use this for future project ideas! Especially a similar project to those "Code Snippets to Image" generators I use to share code on my blog! I'll make a proper post of how I did because it took me forever from an API with limited conversions to an outdated tutorial with broken links 😖
art used @fraberry-stroobcake 🌷
⤷ ○ ♡ my shop ○ my twt ○ my youtube ○ pinned post ○ blog's navigation ♡ ○
#codeblr#coding#progblr#programming#studyblr#studying#computer science#tech#html css#html5 css3#code#programmer#comp sci#web design
81 notes
·
View notes
Text
"TUTORIAL HELL" is Both Harmful and Imaginary
Day 2862
Every time I go on a programming subreddit or other public forum, I see so many distraught learners in anguish that they can't start "A Real Project", and are "stuck" on tutorials, as state which has now come to be referred to as "Tutorial Hell."
It honestly makes me extremely mad that people have made Tutorial Hell into such a meme that new programmers are now scared of it. It's unnecessary gate-keeping around what counts as A Real Project, and it's harming programming students who could otherwise be happily progressing on their way to mastery if they hadn't been poisoned by this idea.
There are zero useful aspects to the concept, and it only prevents students from learning rather than helping them learn. Every programmer in the world, from you to the creators of Google, has to get their ideas based on SOMETHING:
A problem they want to solve for themselves (or a friend, or a customer).
Some knowledge they already had, applied in a new way
A new skill they've just picked up from another project or lesson
A new feature that was just introduced into some technology they use
There's literally no way to get an idea except to have had some experience that leads you to it.
So starting from a completely empty file, and divining a new project based purely on inspiration is of course a very intimidating task, but luckily we don't ever actually have to do that.
The process of developing projects is actually very natural (even inevitable???) if you transfer your code more gradually from "100% Tutorial" to "100% Project":
Start off by doing the tutorials as written. Make sure that you're actually coding along and checking in your code to a github repo.
Every time you finish a tutorial, think of some tiny change you can make to the code to "make it your own." This can start out as small as just changing some text on the screen, or the colors it's using.
Over time you'll naturally get some more ambitious ideas for how to make the project into something even cooler, and you'll start adding larger things like a new feature with its own functions.
Eventually you'll get enough practice expanding projects and applying ideas that the project is mostly your "custom" code instead of code the tutorial told you to write.
Now maybe you have an idea to make a clone of this project but make it even better.
Now you're making A Real Project, From Scratch, but it doesn't rely on you having some eureeka moment of inspiration.
Here's what those steps could look like in a more specific example, from a common tutorial:
Complete a tutorial on how to fetch data from a weather API.
Think, "how could I do some additional fetching to practice more?"
Decide to fetch some data from a movie API instead.
Think, again, "how could I do some additional fetching to practice more?"
Realize that you could use the skills you've learned to fetch two different movies, and iterate through the casts to see which actors they have in common.
Think, again, "how could I do some additional fetching to practice more?
Realize that you could do something similar by fetching two actors, and see what movies they have in common.
Remember that the meme "6 degrees of Kevin Bacon" is related to actors being in the same movies together.
Realize that you could make an app that tracks Kevin Bacon degrees by putting together your movie overlap code and your actor overlap code.
Take the code you've written to modify the tutorial and paste it into a new project, where start turning it into its own app.
https://apps.apple.com/us/app/six-degrees-movie-trivia/id328926385 (not my app)
Coding learners, you're going to be ok - you can take it gradually! Try to just focus on programming a lot, and what kinds of things you program will evolve naturally over time. If you want to consciously lead things in the direction of building your own projects from scratch that's great!
But trying so hard to make this transition that it discourages you from coding is hurting you for no good reason. If you stay curious enough and excited enough about programming, over enough time you'll reach this goal without even trying to.
118 notes
·
View notes
Text
sometimes I really wish C# had C/C++ style preprocessor macros. I know they have their issues, especially when it comes to accidental code obfuscation, but sometimes sometimes being able to use semantic similarities between two otherwise entirely different objects can be really handy.
like the API I'm working with has a bunch of various event classes that all use paired Subscribe and Unsubscribe methods, and I'd like to have it so every time I Subscribe to an event, that same event also gets added to a list to make sure it gets Unsubscribed later, but since most events calls use different types of arguments, the method calls are functionally too different for a simple generic solution.
If it were C/C++, I'd just be able to do #define SUBEVENT(ev, fun) ev.Subscribe(fun); unsubscribe.Add(() => { ev.Unsubscribe(fun); }); and call it a day, but since C# doesn't have the C preprocessor, it depends on me remembering to manually add each subscribed event to the unsubscribe list.
Feels like there's got to be a better way, but hells if I know what it'd be.
6 notes
·
View notes
Text
Crypto trading mobile app
Designing a Crypto Trading Mobile App involves a balance of usability, security, and aesthetic appeal, tailored to meet the needs of a fast-paced, data-driven audience. Below is an overview of key components and considerations to craft a seamless and user-centric experience for crypto traders.
Key Elements of a Crypto Trading Mobile App Design
1. Intuitive Onboarding
First Impressions: The onboarding process should be simple, guiding users smoothly from downloading the app to making their first trade.
Account Creation: Offer multiple sign-up options (email, phone number, Google/Apple login) and include KYC (Know Your Customer) verification seamlessly.
Interactive Tutorials: For new traders, provide interactive walkthroughs to explain key features like trading pairs, order placement, and wallet setup.
2. Dashboard & Home Screen
Clean Layout: Display an overview of the user's portfolio, including current balances, market trends, and quick access to popular trading pairs.
Market Overview: Real-time market data should be clearly visible. Include options for users to view coin performance, historical charts, and news snippets.
Customization: Let users customize their dashboard by adding favorite assets or widgets like price alerts, trading volumes, and news feeds.
3. Trading Interface
Simple vs. Advanced Modes: Provide two versions of the trading interface. A simple mode for beginners with basic buy/sell options, and an advanced mode with tools like limit orders, stop losses, and technical indicators.
Charting Tools: Integrate interactive, real-time charts powered by TradingView or similar APIs, allowing users to analyze market movements with tools like candlestick patterns, RSI, and moving averages.
Order Placement: Streamline the process of placing market, limit, and stop orders. Use clear buttons and a concise form layout to minimize errors.
Real-Time Data: Update market prices, balances, and order statuses in real-time. Include a status bar that shows successful or pending trades.
4. Wallet & Portfolio Management
Asset Overview: Provide an easy-to-read portfolio page where users can view all their holdings, including balances, performance (gains/losses), and allocation percentages.
Multi-Currency Support: Display a comprehensive list of supported cryptocurrencies. Enable users to transfer between wallets, send/receive assets, and generate QR codes for transactions.
Transaction History: Offer a detailed transaction history, including dates, amounts, and transaction IDs for transparency and record-keeping.
5. Security Features
Biometric Authentication: Use fingerprint, facial recognition, or PIN codes for secure logins and transaction confirmations.
Two-Factor Authentication (2FA): Strong security protocols like 2FA with Google Authenticator or SMS verification should be mandatory for withdrawals and sensitive actions.
Push Notifications for Security Alerts: Keep users informed about logins from new devices, suspicious activities, or price movements via push notifications.
6. User-Friendly Navigation
Bottom Navigation Bar: Include key sections like Home, Markets, Wallet, Trade, and Settings. The icons should be simple, recognizable, and easily accessible with one hand.
Search Bar: A prominent search feature to quickly locate specific coins, trading pairs, or help topics.
7. Analytics & Insights
Market Trends: Display comprehensive analytics including top gainers, losers, and market sentiment indicators.
Push Alerts for Price Movements: Offer customizable price alert notifications to help users react quickly to market changes.
Educational Content: Include sections with tips on technical analysis, crypto market basics, or new coin listings.
8. Social and Community Features
Live Chat: Provide a feature for users to chat with customer support or engage with other traders in a community setting.
News Feed: Integrate crypto news from trusted sources to keep users updated with the latest market-moving events.
9. Light and Dark Mode
Themes: Offer both light and dark mode to cater to users who trade at different times of day. The dark mode is especially important for night traders to reduce eye strain.
10. Settings and Customization
Personalization Options: Allow users to choose preferred currencies, set trading limits, and configure alerts based on their personal preferences.
Language and Regional Settings: Provide multilingual support and regional settings for global users.
Visual Design Considerations
Modern, Minimalist Design: A clean, minimal UI is essential for avoiding clutter, especially when dealing with complex data like market trends and charts.
Color Scheme: Use a professional color palette with accents for call-to-action buttons. Green and red are typically used for indicating gains and losses, respectively.
Animations & Micro-interactions: Subtle animations can enhance the experience by providing feedback on button presses or transitions between screens. However, keep these minimal to avoid slowing down performance.
Conclusion
Designing a crypto trading mobile app requires focusing on accessibility, performance, and security. By blending these elements with a modern, intuitive interface and robust features, your app can empower users to navigate the fast-paced world of crypto trading with confidence and ease.
#uxbridge#uxuidesign#ui ux development services#ux design services#ux research#ux tools#ui ux agency#ux#uxinspiration#ui ux development company#crypto#blockchain#defi#ethereum#altcoin#fintech
2 notes
·
View notes
Text
I'm no longer gonna be able to comfortably play my special interest, which fucking sucks. Rant under cut. It's about League of Legends and Riot's anti-cheat software, Vanguard, if you're interested.
Riot Vanguard (vgk) is a kernel-level software that scans all of a system's processes to detect cheat engines, which itself is fine - industry standard - except it boasts a particular effectiveness due to how it's run. Vgk runs on start-up so that it's running before a user has the chance to launch a cheat engine, and it can ID hardware so that if a player is caught cheating, they won't be able to play again on the same device. Unless it is disabled manually, it will run 24/7, whereas other AC software will start and stop in line with the game's execution.
It's more effective than other AC software, but it absolutely bricked some PCs back upon its initial release when Valorant dropped in 2020. This was a new game, fresh code, but the anti-cheat borders on a fucking rootkit - a term I'm using liberally, because vgk isn't malware, but it works in the same way on a systemic level. Equally as invasive, and can potentially be equally as destructive; one of those is intended, and the other is an unfortunate by-product of invasive software being developed by a video game company.
League of Legends is a 15 year old game with some pretty tragic code. If vgk caused people to bluescreen after exiting Valorant, then even more people are going to encounter issues with the shitshow that is LoL's code base.
Three weeks ago, an attempt to fix a bug regarding an in-client feature fucked over a far more significant API in several major servers. Every time a particular game-mode called "Clash" launches (every other month or so), it bricks the servers. This is currently a running gag in the community: that whenever the client acts up (embarrassingly often for such a well-funded game) Riot must be dropping Clash early. But when you introduce a bloody rootkit into the mix that runs in tandem with spaghetti code and beyond the closing of the game app, this is going to undoubtedly fuck some computers up.
I'm not someone who cheats at games, but I care about my system too much to risk this. Something that relies on the BIOS, that is known to have caused permanent damage to systems while running alongside a much better programmed game, that continuously scans your system while it's active (and always activates upon start-up until disabled) is obscenely risky. With a 24/7 invasive software, it can disable drivers regardless of what you're playing and when; the worst cases - plural - I've read about anecdotally were people's cooling systems being disabled erroneously by vgk, causing gpu melting. You bet any antivirus software you have installed is going to scan without pause because of it, which will cause more system-wide performance issues, too.
There's also the (albeit minor) risk of other scripts triggering the uh-oh alarm and leading to unfair account bans, and I've poured almost 7 years into this game. I mod some of my single-player games and write scripts. No thanks.
And while I'm lucky enough to have a decent system, the TPM 2.0 and secure boot requirement for Windows 11 users means that vgk will effectively - while the phrase is crude, I haven't seen a concise alternative - "class-ban" League players. Similar to the release of OW2, where a unique SIM was required for every account, including existing ones until that got changed after enough backlash - except buying a phone number is far cheaper than buying a laptop or PC. Even with the requirements, the performance issues will tank low-end systems, which would already be at higher risk of hardware fuckery from increased and extended cpu usage. And the game is currently designed to be comfortably playable on low-end rigs, so it will force-out a good number of players.
If you play League and intend to continue playing after vgk is made mandatory in Jan/Feb 2024, give it a few months after it goes live before you play. That's enough time for any catastrophic issues to unfold, because if the testing period was anything like it is for game features, it won't be sufficient, and the number of cases of system damage will be worse than it was for Valorant upon release.
This rant does read like I'm trying to dissuade people from playing post-vgk, and I'm not, but I am urging people to be cautious and informed on the legitimate controversies surrounding Vanguard, especially anything hardware related. Familiarise yourself with how the program works and assess whether your system will likely be affected, and how permanent any damage could be to your hardware. Read forums (that aren't moderated by Riot employees where possible) and verify the information you're reading. Including this. It's 3:30am and I'm writing this angrily, so my limited explanations of the software could stand to be more thorough.
I'm hoping that there will be enough of a reduction in League's ~200m monthly player-base to spark a reversal in the decision to implement vgk. Not out of consideration for people who don't want to install a rootkit for a video game, but because Riot would lose money and shit their corporate britches.
Having to say goodbye to my favourite game, a universe I love and one of the more significant outlets to socialisation in my life absolutely sucks, though. The actual season changes looked super cool too, and I was stoked about Ambessa coming to the game. I'll enjoy the game while I can, but yeah this feels like a bitter breakup lmao.
#enforcing a rootkit to ban a few xerath mains was not on my 2024 bingo card#i think i've encountered two cheaters in my 7 years of playing#rant post#league posting
8 notes
·
View notes
Text
Do You Want Some Cookies?
Doing the project-extrovert is being an interesting challenge. Since the scope of this project shrunk down a lot since the first idea, one of the main things I dropped is the use of a database, mostly to reduce any cost I would have with hosting one. So things like authentication needs to be fully client-side and/or client-stored. However, this is an application that doesn't rely on JavaScript, so how I can store in the client without it? Well, do you want some cookies?
Why Cookies
I never actually used cookies in one of my projects before, mostly because all of them used JavaScript (and a JS framework), so I could just store everything using the Web Storage API (mainly localstorage). But now, everything is server-driven, and any JavaScript that I will add to this project, is to enhance the experience, and shouldn't be necessary to use the application. So the only way to store something in the client, using the server, are Cookies.
TL;DR Of How Cookies Work
A cookie, in some sense or another, is just an HTTP Header that is sent every time the browser/client makes a request to the server. The server sends a Set-Cookie header on the first response, containing the value and optional "rules" for the cookie(s), which then the browser stores locally. After the cookie(s) is stored in the browser, on every subsequent request to the server, a Cookie header will be sent together, which then the server can read the values from.
Pretty much all websites use cookies some way or another, they're one of the first implementations of state/storage on the web, and every browser supports them pretty much. Also, fun note, because it was one of the first ways to know what user is accessing the website, it was also heavy abused by companies to track you on any website, the term "third-party cookie" comes from the fact that a cookie, without the proper rules or browser protection, can be [in summary] read from any server that the current websites calls. So things like advertising networks can set cookies on your browser to know and track your profile on the internet, without you even knowing or acknowledging. Nowadays, there are some regulations, primarily in Europe with the General Data Privacy Regulation (GDPR), that's why nowadays you always see the "We use Cookies" pop-up in websites you visit, which I beg you to actually click "Decline" or "More options" and remove any cookie labeled "Non-essential".
Small Challenges and Workarounds
But returning to the topic, using this simple standard wasn't so easy as I thought. The code itself isn't that difficult, and thankfully Go has an incredible standard library for handling HTTP requests and responses. The most difficult part was working around limitations and some security concerns.
Cookie Limitations
The main limitation that I stumbled was trying to have structured data in a cookie. JSON is pretty much the standard for storing and transferring structured data on the web, so that was my first go-to. However, as you may know, cookies can't use any of these characters: ( ) < > @ , ; : \ " / [ ] ? = { }. And well, when a JSON file looks {"like":"this"}, you can think that using JSON is pretty much impossible. Go's http.SetCookie function automatically strips " from the cookie's value, and the other characters can go in the Set-Cookie header, but can cause problems.
On my first try, I just noticed about the stripping of the " character (and not the other characters), so I needed to find a workaround. And after some thinking, I started to try implementing my own data structure format, I'm learning Go, and this could be an opportunity to also understand how Go's JSON parsing and how mostly struct tags works and try to implement something similar.
My idea was to make something similar to JSON in one way or another, and I ended up with:
Which, for reference, in JSON would be:
This format is something very easy to implement, just using strings.Split does most of the job of extracting the values and strings.Join to "encode" the values back. Yes, this isn't a "production ready" format or anything like that, but it is hacky and just a small fix for small amounts of structured data.
Go's Struct Tags
Go has an interesting and, to be honest, very clever feature called Struct Tags, which are a simple way to add metadata to Structs. They are simple strings that are added to each field and can contain key-value data:
Said metadata can be used by things such the encoding/json package to transform said struct into a JSON object with the correct field names:
Without said tags, the output JSON would be:
This works both for encoding and decoding the data, so the package can correctly map the JSON field "access_token" to the struct field "Token".
And well, these tokens aren't limited or some sort of special syntax, any key-value pair can be added and accessed by the reflect package, something like this:
Learning this feature and the reflect package itself, empowered me to do a very simple encoding and decoding of the format where:
Can be transformed into:
And that's what I did, and the [basic] implementation source code just has 150 lines of code, not counting the test file to be sure it worked. It works, and now I can store structured data in cookies.
Legacy in Less Than 3 Weeks
And today, I found that I can just use url.PathEscape, and it escapes all ( ) < > @ , ; : \ " / [ ] ? = { } characters, so it can be used both in URLs and, surprise, cookie values. Not only that, but something like base64.URLEncoding would also work just fine. You live, and you learn y'know, that's what I love about engineering.
Security Concerns and Refactoring Everything
Another thing that was a limitation and mostly worry about me, is storing access tokens on cookies. A cookie by default isn't that secure, and can be easily accessed by JavaScript and browser extensions, there are ways to block and secure cookies, but even then, you can just open the developer tools of the browser and see them easily. Even though the only way to something malicious end up happening with these tokens are if the actual client end up being compromised, which means the user has bigger problems than just a social media token being leaked, it's better to try preventing these issues nonetheless (and learn something new as always).
The encryption and decryption part isn't so difficult, Go already provides packages for encryption under the crypto module. So I just implemented an encryption that cyphers a string based on a key environment variable, which I will change every month or so to improve security even more.
Doing this encryption on every endpoint would be repetitive, so adding a middleware would be a solution. I already made a small abstraction over the default Go's router (the DefaultMuxServer struct), which I'm going to be honest, wasn't the best abstraction, since it deviated a lot from Go's default HTTP package conventions. This deviation also would difficult the implementation of a generic middleware that I could use in any route or even any function that handles HTTP requests, a refactor was needed. Refactoring made me end up rewriting a lot of code and simplifying a lot of the code from the project. All routes now are structs that implement the http.Handler interface, so I can use them outside the application router and test them if needed; The router ends up being just a helper for having all routes in a struct, instead of multiple mux.HandleFunc calls in a function, and also handles adding middlewares to all routes; Middlewares end up being just a struct that can return a wrapped HandlerFunc function, which the router calls using a custom/wrapped implementation of the http.ResponseWriter interface, so middlewares can actually modify the content and headers of the response. The refactor had 1148 lines added, and 524 removed, and simplified a lot of the code.
For the encryption middleware, it encrypts all cookie values that are set in the Set-Cookie header, and decrypts any incoming cookie. Also, the encrypted result is encoded to base64, so it can safely be set in the Set-Cookie header after being cyphered.
---
And that's what I worked in around these last three days, today being the one where I actually used all this functionality and actually implemented the OAuth2 process, using an interface and a default implementation that I can easily reimplement for some special cases like Mastodon's OAuth process (since the token and OAuth application needs to be created on each instance separately). It's being interesting learning Go and trying to be more effective and implement things the way the language wants. Everything is being very simple nonetheless, just needing to align my mind with the language mostly.
It has been a while since I wrote one of these long posts, and I remembered why, it takes hours to do, but it's worth the work I would say. Unfortunately I can't write these every day, but hopefully they will become more common, so I can log better the process of working on the projects. Also, for the 2 persons that read this blog, give me some feedback! I really would like to know if there's anything I could improve in the writing, anything that ended up being confusing, or even how I could write the image description for the code snippets, I'm not sure how to make them more accessible for screen reader users.
Nevertheless, completing this project will also help to make these post, since the conversion for Markdown to Tumblr's NPF in the web editor sucks ass, and I know I can do it better.
2 notes
·
View notes
Text
Critical Vulnerability (CVE-2024-37032) in Ollama
Researchers have discovered a critical vulnerability in Ollama, a widely used open-source project for running Large Language Models (LLMs). The flaw, dubbed "Probllama" and tracked as CVE-2024-37032, could potentially lead to remote code execution, putting thousands of users at risk.
What is Ollama?
Ollama has gained popularity among AI enthusiasts and developers for its ability to perform inference with compatible neural networks, including Meta's Llama family, Microsoft's Phi clan, and models from Mistral. The software can be used via a command line or through a REST API, making it versatile for various applications. With hundreds of thousands of monthly pulls on Docker Hub, Ollama's widespread adoption underscores the potential impact of this vulnerability.
The Nature of the Vulnerability
The Wiz Research team, led by Sagi Tzadik, uncovered the flaw, which stems from insufficient validation on the server side of Ollama's REST API. An attacker could exploit this vulnerability by sending a specially crafted HTTP request to the Ollama API server. The risk is particularly high in Docker installations, where the API server is often publicly exposed. Technical Details of the Exploit The vulnerability specifically affects the `/api/pull` endpoint, which allows users to download models from the Ollama registry and private registries. Researchers found that when pulling a model from a private registry, it's possible to supply a malicious manifest file containing a path traversal payload in the digest field. This payload can be used to: - Corrupt files on the system - Achieve arbitrary file read - Execute remote code, potentially hijacking the system The issue is particularly severe in Docker installations, where the server runs with root privileges and listens on 0.0.0.0 by default, enabling remote exploitation. As of June 10, despite a patched version being available for over a month, more than 1,000 vulnerable Ollama server instances remained exposed to the internet.
Mitigation Strategies
To protect AI applications using Ollama, users should: - Update instances to version 0.1.34 or newer immediately - Implement authentication measures, such as using a reverse proxy, as Ollama doesn't inherently support authentication - Avoid exposing installations to the internet - Place servers behind firewalls and only allow authorized internal applications and users to access them
Broader Implications for AI and Cybersecurity
This vulnerability highlights ongoing challenges in the rapidly evolving field of AI tools and infrastructure. Tzadik noted that the critical issue extends beyond individual vulnerabilities to the inherent lack of authentication support in many new AI tools. He referenced similar remote code execution vulnerabilities found in other LLM deployment tools like TorchServe and Ray Anyscale. Moreover, despite these tools often being written in modern, safety-first programming languages, classic vulnerabilities such as path traversal remain a persistent threat. This underscores the need for continued vigilance and robust security practices in the development and deployment of AI technologies. Read the full article
2 notes
·
View notes
Text
Finding APIs to Work with
Day 225 - Jun 17th, 12.024
Another Monday, another return to work. I have to admit that I'm kinda lost on my website, but I'm still able to do some progress, today was just a simple blog section for the homepage. What is breaking and filling my mind is the lack of software to manage art and drawings, like, one of my ideas was having a gallery section for my drawings, but I can't just host all the images or place them on the source code, I need it to be dynamic. Things like ArtStation feels like a possibility, but they don't have an official API to use, and most of the alternatives have similar limitations.
Hopefully I find something until the website is completed, since I also want to be able to develop similar websites for friends and artists.
Today's artists & creative things Music: Frown - by Title Fight
© 2024 Gustavo "Guz" L. de Mello. Licensed under CC BY-SA 4.0
2 notes
·
View notes
Text
Top 10 Front-End Frameworks and Libraries for 2024
As the web development landscape continues to evolve, staying updated with the latest front-end frameworks and libraries is crucial for any developer. Whether you're a seasoned pro or just starting out, knowing which tools to use can significantly impact your productivity and the quality of your projects. In this post, we’ll explore the top 10 front-end frameworks and libraries that are set to dominate in 2024.
1. React
React remains one of the most popular front-end libraries, known for its simplicity and flexibility.
Key Features of React
Component-Based Architecture: Reusable components make development efficient and manageable.
Virtual DOM: Enhances performance by minimizing direct DOM manipulation.
Strong Community Support: A vast ecosystem of tools, libraries, and tutorials.
2. Angular
Angular, backed by Google, is a powerful framework for building dynamic single-page applications (SPAs).
Why Choose Angular?
Two-Way Data Binding: Synchronizes data between the model and the view.
Dependency Injection: Improves code maintainability and testability.
Comprehensive Documentation: Extensive resources for learning and troubleshooting.
3. Vue.js
Vue.js has gained popularity due to its gentle learning curve and versatility.
Advantages of Vue.js
Reactive Data Binding: Simplifies state management.
Single-File Components: Encapsulate HTML, CSS, and JavaScript in one file.
Flexibility: Can be used for both large-scale and small-scale applications.
4. Svelte
Svelte is a relatively new player that compiles components into highly efficient vanilla JavaScript at build time.
Svelte’s Standout Features
No Virtual DOM: Directly manipulates the DOM for better performance.
Less Boilerplate: Cleaner code with minimal overhead.
Ease of Use: Intuitive and straightforward syntax.
5. Bootstrap
Bootstrap is a front-end framework that provides pre-designed components and a responsive grid system.
Benefits of Using Bootstrap
Responsive Design: Ensures your site looks great on all devices.
Pre-Styled Components: Saves time with ready-to-use UI elements.
Customizable: Easily customize with Sass variables and Bootstrap’s extensive options.
6. Tailwind CSS
Tailwind CSS is a utility-first CSS framework that allows for rapid UI development.
Tailwind CSS Features
Utility-First Approach: Use utility classes directly in your HTML.
Customizable: Extensive configuration options to suit your project’s needs.
Consistency: Enforces a consistent design language across your project.
7. Ember.js
Ember.js is a robust framework for building ambitious web applications.
Why Ember.js Stands Out
Convention over Configuration: Reduces the amount of decision-making and boilerplate code.
Strong Routing: Powerful routing capabilities for managing application state.
Productivity: Focuses on developer productivity with built-in best practices.
8. Alpine.js
Alpine.js offers a minimal and lightweight way to add interactivity to your websites.
Key Features of Alpine.js
Lightweight: Small footprint with only a few kilobytes.
Declarative Syntax: Similar to Vue.js, making it easy to understand and implement.
Ease of Integration: Can be easily integrated into existing projects.
9. Next.js
Next.js is a popular React framework that enables server-side rendering and static site generation.
Benefits of Using Next.js
Server-Side Rendering (SSR): Improves performance and SEO by rendering pages on the server.
Static Site Generation (SSG): Pre-renders pages at build time for fast load times.
API Routes: Allows you to create API endpoints within your application.
10. Lit
Lit is a simple library for building fast, lightweight web components.
Advantages of Lit
Web Components: Embraces the web components standard for reusable, encapsulated HTML elements.
Performance: Lightweight and highly performant.
Simple API: Easy to learn and use with a minimal API surface.
Conclusion
Choosing the right front-end framework or library can significantly impact your workflow and the quality of your projects. Whether you prefer the flexibility of React, the structure of Angular, or the simplicity of Svelte, there's a tool out there to suit your needs.
Final Tips for Selecting a Framework or Library
Project Requirements: Consider the specific needs of your project.
Community and Support: Look for frameworks with strong community support and documentation.
Learning Curve: Choose a tool that matches your current skill level and the time you have available to learn.
By staying informed about the latest tools and trends, you can ensure that your skills remain relevant and that you can deliver the best possible results in your projects. Happy coding!
Remember, the best tool is the one that helps you get the job done efficiently and effectively. So, dive into these frameworks and libraries, and take your front-end development skills to the next level!
Share Your Thoughts
I'm curious to know your thoughts on these front-end frameworks and libraries. Have you used any of them in your projects? Which one is your favorite, and why? Share your experiences and insights in the comments below.👇
2 notes
·
View notes
Text
Top Mobile App Development Frameworks in 2023 - Lode Emmanuel Palle
As of my last knowledge update in September 2021, I can provide information about some of the popular mobile app development frameworks up to that point. However, please note that the landscape of technology can change rapidly, and new frameworks may have emerged or gained popularity since then. Here are some of the well-known mobile app development frameworks mentioned by Lode Emmanuel Palle that were popular up to 2021:
React Native: Developed by Facebook, React Native is a widely used open-source framework for building cross-platform mobile apps. It allows developers to use JavaScript to create native-like user interfaces for both iOS and Android.
Flutter: Created by Google, Flutter is another popular open-source framework for building cross-platform apps. It uses the Dart programming language and provides a rich set of customizable widgets, enabling high-quality and performant user interfaces.
Xamarin: Owned by Microsoft, Xamarin allows developers to build native apps for iOS, Android, and Windows using a single codebase in C#. It provides a way to share a significant portion of code across platforms while still delivering native user experiences.
Ionic: Built on top of Angular and using web technologies like HTML, CSS, and JavaScript/TypeScript, Ionic is a framework for building cross-platform mobile apps with a native-like feel. It also provides a suite of UI components.
Vue Native: Based on Vue.js, Vue Native lets developers build mobile apps using Vue's declarative syntax. It's designed to be similar to React Native, making it easy for developers familiar with Vue.js to transition to mobile development.
PhoneGap / Apache Cordova: PhoneGap is an open-source framework that uses web technologies to build mobile apps that can run on various platforms. It leverages Apache Cordova to access native device features.
SwiftUI (for iOS): Introduced by Apple, SwiftUI is a framework for building user interfaces across all Apple platforms using Swift programming language. It's mainly focused on iOS, macOS, watchOS, and tvOS app development.
Kotlin Multiplatform Mobile (KMM): Developed by JetBrains, KMM is a relatively new framework that aims to allow developers to share code between Android and iOS apps using Kotlin. It's designed for more seamless cross-platform development.
NativeScript: NativeScript enables building native apps using JavaScript, TypeScript, or Angular. It provides access to native APIs and components, offering a truly native experience.
According to Lode Emmanuel Palle. the choice of a mobile app development framework depends on various factors including your familiarity with the programming language, the complexity of the app, the desired platform(s), and the specific features you need. It's always a good idea to research and stay updated on the latest developments in the field to make informed decisions.
9 notes
·
View notes
Text
Introducing Alt Text Creator
Images on web pages are supposed to have alternate text, which gives screen readers, search engines, and other tools a text description of the image. Alt text is critical for accessibility and search engine optimization (SEO), but it can also be time-consuming, which is why I am releasing Alt Text Creator!
Alt Text Creator is a new browser extension for Mozilla Firefox and Google Chrome (and other browsers that can install from the Chrome Web Store) that automatically generates alt text for image using the OpenAI GPT-4 with Vision AI. You just right-click any image, select "Create Alt Text" in the context menu, and a few seconds later the result will appear in a notification. The alt text is automatically copied to your clipboard, so it doesn't interrupt your workflow with another button to click.
I've been using a prototype version of this extension for about three months (my day job is News Editor at How-To Geek), and I've been impressed by how well the GPT-4 AI model describes text. I usually don't need to tweak the result at all, except to make it more specific. If you're curious about the AI prompt and interaction, you can check out the source code. Alt Text Creator also uses the "Low Resolution" mode and saves a local cache of responses to reduce usage costs.
I found at least one other browser extension with similar functionality, but Alt Text Creator is unique for two reasons. First, it uses your own OpenAI API key that you provide. That means the initial setup is a bit more annoying, but the cost is based on usage and billed directly through OpenAI. There's no recurring subscription, and ChatGPT Plus is not required. In my own testing, creating alt text for a single image costs under $0.01. Second, the extension uses as few permissions as possible—it doesn't even have access to your current tab, just the image you select.
This is more of a niche tool than my other projects, but it's something that has made my work a bit less annoying, and it might help a few other people too. I might try to add support for other AI backends in the future, but I consider this extension feature-complete in its current state.
Download for Google Chrome
Download for Mozilla Firefox
#chrome extension#chrome extensions#firefox extension#firefox extensions#chrome#firefox#accessibility#a11y
2 notes
·
View notes
Note
Hi! I’m a student currently learning computer science in college and would love it if you had any advice for a cool personal project to do? Thanks!
Personal Project Ideas
Hiya!! 💕
It's so cool that you're a computer science student, and with that, you have plenty of options for personal projects that can help with learning more from what they teach you at college. I don't have any experience being a university student however 😅
Someone asked me a very similar question before because I shared my projects list and they asked how I come up with project ideas - maybe this can inspire you too, here's the link to the post [LINK]
However, I'll be happy to share some ideas with you right now. Just a heads up: you can alter the projects to your own specific interests or goals in mind. Though it's a personal project meaning not an assignment from school, you can always personalise it to yourself as well! Also, I don't know the level you are, e.g. beginner or you're pretty confident in programming, if the project sounds hard, try to simplify it down - no need to go overboard!!
But here is the list I came up with (some are from my own list):
Personal Finance Tracker
A web app that tracks personal finances by integrating with bank APIs. You can use Python with Flask for the backend and React for the frontend. I think this would be great for learning how to work with APIs and how to build web applications 🏦
Online Food Ordering System
A web app that allows users to order food from a restaurant's menu. You can use PHP with Laravel for the backend and Vue.js for the frontend. This helps you learn how to work with databases (a key skill I believe) and how to build interactive user interfaces 🙌🏾
Movie Recommendation System
I see a lot of developers make this on Twitter and YouTube. It's a machine-learning project that recommends movies to users based on their past viewing habits. You can use Python with Pandas, Scikit-learn, and TensorFlow for the machine learning algorithms. Obviously, this helps you learn about how to build machine-learning models, and how to use libraries for data manipulation and analysis 📊
Image Recognition App
This is more geared towards app development if you're interested! It's an Android app that uses image recognition to identify objects in a photo. You can use Java or Kotlin for the Android development and TensorFlow for machine learning algorithms. Learning how to work with image recognition and how to build mobile applications - which is super cool 👀
Social Media Platform
(I really want to attempt this one soon) A web app that allows users to post, share, and interact with each other's content. Come up with a cool name for it! You can use Ruby on Rails for the backend and React for the frontend. This project would be great for learning how to build full-stack web applications (a plus cause that's a trend that companies are looking for in developers) and how to work with user authentication and authorization (another plus)! 🎭
Text-Based Adventure Game
If you're interested in game developments, you could make a simple game where users make choices and navigate through a story by typing text commands. You can use Python for the game logic and a library like Pygame for the graphics. This project would be great for learning how to build games and how to work with input/output. 🎮
Weather App
Pretty simple project - I did this for my apprenticeship and coding night classes! It's a web app that displays weather information for a user's location. You can use Node.js with Express for the backend and React for the frontend. Working with APIs again, how to handle asynchronous programming, and how to build responsive user interfaces! 🌈
Online Quiz Game
A web app that allows users to take quizzes and compete with other players. You could personalise it to a module you're studying right now - making a whole quiz application for it will definitely help you study! You can use PHP with Laravel for the backend and Vue.js for the frontend. You get to work with databases, build real-time applications, and maybe work with user authentication. 🧮
Chatbot
(My favourite, I'm currently planning for this one!) A chatbot that can answer user questions and provide information. You can use Python with Flask for the backend and a natural language processing library like NLTK for the chatbot logic. If you want to mauke it more beginner friendly, you could use HTML, CSS and JavaScript and have hard-coded answers set, maybe use a bunch of APIs for the answers etc! This project would be great because you get to learn how to build chatbots, and how to work with natural language processing - if you go that far! 🤖
Another place I get inspiration for more web frontend dev projects is on Behance and Pinterest - on Pinterest search for like "Web design" or "[Specific project] web design e.g. shopping web design" and I get inspiration from a bunch of pins I put together! Maybe try that out!
I hope this helps and good luck with your project!
#my asks#resources#programming#coding#studying#codeblr#progblr#studyblr#comp sci#computer science#projects ideas#coding projects#coding study#cs studyblr#cs academia
178 notes
·
View notes
Text
Exploring Essential Laravel Development Tools for Building Powerful Web Applications
Laravel has emerged as one of the most popular PHP frameworks, providing builders a sturdy and green platform for building net packages. Central to the fulfillment of Laravel tasks are the development tools that streamline the improvement process, decorate productiveness, and make certain code quality. In this article, we will delve into the best Laravel development tools that each developer should be acquainted with.
1 Composer: Composer is a dependency manager for PHP that allows you to declare the libraries your project relies upon on and manages them for you. Laravel itself relies closely on Composer for package deal management, making it an essential device for Laravel builders. With Composer, you may without problems upload, eliminate, or update applications, making sure that your Laravel project stays up-to-date with the present day dependencies.
2 Artisan: Artisan is the command-line interface blanketed with Laravel, presenting various helpful instructions for scaffolding, handling migrations, producing controllers, models, and plenty extra. Laravel builders leverage Artisan to automate repetitive tasks and streamline improvement workflows, thereby growing efficiency and productiveness.
3 Laravel Debugbar: Debugging is an crucial component of software program development, and Laravel Debugbar simplifies the debugging procedure by using supplying exact insights into the application's overall performance, queries, views, and greater. It's a accessible device for identifying and resolving problems all through improvement, making sure the clean functioning of your Laravel application.
4 Laravel Telescope: Similar to Laravel Debugbar, Laravel Telescope is a debugging assistant for Laravel programs, presenting actual-time insights into requests, exceptions, database queries, and greater. With its intuitive dashboard, developers can monitor the software's behavior, pick out performance bottlenecks, and optimize hence.
5 Laravel Mix: Laravel Mix offers a fluent API for outlining webpack build steps on your Laravel application. It simplifies asset compilation and preprocessing duties together with compiling SASS or LESS documents, concatenating and minifying JavaScript documents, and dealing with versioning. Laravel Mix significantly streamlines the frontend improvement procedure, permitting builders to attention on building notable consumer reviews.
6 Laravel Horizon: Laravel Horizon is a dashboard and configuration system for Laravel's Redis queue, imparting insights into process throughput, runtime metrics, and more. It enables builders to monitor and control queued jobs efficiently, ensuring most beneficial performance and scalability for Laravel programs that leverage history processing.
7 Laravel Envoyer: Laravel Envoyer is a deployment tool designed specifically for Laravel packages, facilitating seamless deployment workflows with 0 downtime. It automates the deployment process, from pushing code adjustments to more than one servers to executing deployment scripts, thereby minimizing the chance of errors and ensuring smooth deployments.
8 Laravel Dusk: Laravel Dusk is an cease-to-give up browser testing tool for Laravel applications, built on pinnacle of the ChromeDriver and WebDriverIO. It lets in builders to put in writing expressive and dependable browser assessments, making sure that critical user interactions and workflows function as expected across exceptional browsers and environments.
9 Laravel Valet: Laravel Valet gives a light-weight improvement surroundings for Laravel applications on macOS, offering seamless integration with equipment like MySQL, NGINX, and PHP. It simplifies the setup process, permitting developers to consciousness on writing code instead of configuring their development environment.
In end, mastering the vital Laravel development tools noted above is important for building robust, green, and scalable internet packages with Laravel. Whether it's handling dependencies, debugging troubles, optimizing overall performance, or streamlining deployment workflows, those equipment empower Laravel developers to supply outstanding answers that meet the demands of current internet development. Embracing these gear will certainly increase your Laravel improvement enjoy and accelerate your journey toward turning into a talented Laravel developer.
3 notes
·
View notes