Search
1000 results for “im_a_GDeveloper”
-
No, but my Linux distro includes a boss key because, why not. [See screenshot.] Actually, I think that this is referred to as a "Show Desktop" button, but I'm not sure that I see the difference.
In the 1990s, my CEO at IPT would have been outraged if he'd thought that people were sneaking game time on the sly. But I don't recall that he minded when we set up the office openly, just for a few days, so that everybody could blast away in Doom. I think that we even ran extra cables.
We must have used DOS TCP packet drivers. The details are lost to time, but I remember that it worked pretty well.
A young developer named Leon, now an aging CEO in Norway, brought his two daughters to the office for a visit. We booted up a DOS game called "Katie's Farm" for them and they apparently talked for days about picking strawberries in the game. Nobody minded that.
However, if somebody had been caught using a boss key, that would have been the end of them.
I thought of boss keys, myself, primarily as humor. Wouldn't an approaching boss see you move quickly to hit just the one key? I suppose that somebody with nerves of steel would be able to bluff their way through it.
Link to a copy of Katie's Farm:
https://tinyurl.com/katies-farm
Screenshot: Boss key in #Laclin Linux with the desktop running BEWorld, a video game that has the distinction of being written entirely in Tcl [even the music data and other assets].
#DOS #games -
As a developer, naming things that have never existed is kind of the best part of the job.
Identifying things that should, but do not exist, bringing them into reality and then giving it a ridiculous name is ... (like, my whole vibe thingee, ya know?) ... an essential creative aspect of the profession I find both creatively inspiring and fulfilling.
Could have spent hours filling out this thread with much cleverer things, but I'm kind in the middle of doing it for real rn.
#hackers #creators #coders #imagination
#blankpage
:twitter:🔗https://twitter.com/mrcopilot/status/1564686539266859008 -
OK, that's a wrap for now.
My current impression is that Rust is decades behind Ruby in terms of developer experience. There are some neat ideas, some features that are only possible because of Rust's type system, performance is definitely incomparable. But the things that are called a framework in Rust would never be called that in Ruby. Rust can not be compared to Ruby in terms of development speed.
I can not stress that enough. What's done in Rails with a scaffold and a few lines of code took me like a solid week and I'm still nowhere near the end of it. Yes, I have to learn a lot. But I have to learn a lot precisely because basics are not covered in the docs and I can't copy-paste pieces to have the same (or analogous) thing as in Rails.
It's rather the basics are different. In Rails basics are CRUD. In Rust basics are how to run a router on top of a socket. A form to update a record in the db is an advanced topic in Rust web development. Unfortunately.
-
OK, that's a wrap for now.
My current impression is that Rust is decades behind Ruby in terms of developer experience. There are some neat ideas, some features that are only possible because of Rust's type system, performance is definitely incomparable. But the things that are called a framework in Rust would never be called that in Ruby. Rust can not be compared to Ruby in terms of development speed.
I can not stress that enough. What's done in Rails with a scaffold and a few lines of code took me like a solid week and I'm still nowhere near the end of it. Yes, I have to learn a lot. But I have to learn a lot precisely because basics are not covered in the docs and I can't copy-paste pieces to have the same (or analogous) thing as in Rails.
It's rather the basics are different. In Rails basics are CRUD. In Rust basics are how to run a router on top of a socket. A form to update a record in the db is an advanced topic in Rust web development. Unfortunately.
-
OK, that's a wrap for now.
My current impression is that Rust is decades behind Ruby in terms of developer experience. There are some neat ideas, some features that are only possible because of Rust's type system, performance is definitely incomparable. But the things that are called a framework in Rust would never be called that in Ruby. Rust can not be compared to Ruby in terms of development speed.
I can not stress that enough. What's done in Rails with a scaffold and a few lines of code took me like a solid week and I'm still nowhere near the end of it. Yes, I have to learn a lot. But I have to learn a lot precisely because basics are not covered in the docs and I can't copy-paste pieces to have the same (or analogous) thing as in Rails.
It's rather the basics are different. In Rails basics are CRUD. In Rust basics are how to run a router on top of a socket. A form to update a record in the db is an advanced topic in Rust web development. Unfortunately.
-
OK, that's a wrap for now.
My current impression is that Rust is decades behind Ruby in terms of developer experience. There are some neat ideas, some features that are only possible because of Rust's type system, performance is definitely incomparable. But the things that are called a framework in Rust would never be called that in Ruby. Rust can not be compared to Ruby in terms of development speed.
I can not stress that enough. What's done in Rails with a scaffold and a few lines of code took me like a solid week and I'm still nowhere near the end of it. Yes, I have to learn a lot. But I have to learn a lot precisely because basics are not covered in the docs and I can't copy-paste pieces to have the same (or analogous) thing as in Rails.
It's rather the basics are different. In Rails basics are CRUD. In Rust basics are how to run a router on top of a socket. A form to update a record in the db is an advanced topic in Rust web development. Unfortunately.
-
Confessions of a Software Developer: No More Self-Censorship
I haven't published since April because I've been afraid. I also avoided social media, news aggregators, and discussion forums for months. I'm done letting fear stop me. What was I afraid of? In this post I detail every single thing I've avoided admitting on this blog. […]https://kerrick.blog/articles/2025/confessions-of-a-software-developer-no-more-self-censorship/
-
id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.
https://github.com/positive-intentions/chat
https://positive-intentions.com/blog/introducing-decentralized-chat
im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.
using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.
- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).
- another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.
- to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.
- i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)
- the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.
i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.
while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.
(note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)
-
id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.
https://github.com/positive-intentions/chat
https://positive-intentions.com/blog/introducing-decentralized-chat
im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.
using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.
- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).
- another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.
- to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.
- i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)
- the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.
i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.
while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.
(note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)
-
id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.
https://github.com/positive-intentions/chat
https://positive-intentions.com/blog/introducing-decentralized-chat
im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.
using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.
- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).
- another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.
- to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.
- i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)
- the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.
i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.
while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.
(note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)
-
id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.
https://github.com/positive-intentions/chat
https://positive-intentions.com/blog/introducing-decentralized-chat
im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.
using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.
- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).
- another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.
- to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.
- i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)
- the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.
i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.
while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.
(note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)
-
#introduction By day I'm a quantum physicist, by early mornings/evenings/weekends I'm a developer, but in between the cracks I'm keen on #Monochrome aka #BlackAndWhite #Photography.
I keep things traditional with #Silver, #Pyro developers, and the magical #CarbonTransfer.
I'm a junkie and shoot mostly #Ilford film on #Leica in #35mm, #Hasselblad in #MediumFormat, #ArcaSwiss in #4x5 and #ChamonixCameras in #ULF #11x14. My home darkroom features a #Durst #L1200 + #RHDesigns and #Heiland extras.
-
Can I ask all the euro furs which countries are most resistant to fascist takeovers?
As we are queer and disabled We’re starting to consider the possibility of emigrating from the UK given the possibility of a MAGA style reform government.
Luckily I’m a fairly competent software developer so I should be able to get a work visa at least ^^
Currently considering Spain or Australia.
-
I'm looking for job, usually I prefer Mexican payrole jobs ( with mexivan law benefits and plus) but I open to a good contractor/freelance offer
I'm a software engineer and full stack developer with 7 years of experience.
My technologies are
The recent ones are
#ReactJS
#NextJS
#RubyOnRails
#AWS #microservices
#NodeJS #JavaScript and #TypeScript
#algolia #indexer
#CSM #contenful
I also have experience.
#Laravel #PHP
#workflow
#vuejs -
Does anyone have a good example of an ad, webpage, video or other marketing material that does a good job of both *educating* and selling? Ideally about a technical thing?
That’s generally what every pitch I send needs to do, and I’m having a hard time educating briefly enough that it "clicks” for people.
I'm a #freelance web developer mostly pitching static websites over WordPress / Squarespace.
#AskFedi #freelancer #marketing #education #StaticWebsites #WebDeveloper #AskFediverse
-
We have an opening on our team in Google Open Source for someone who works at the intersection of open source, technology, IP, and policy.
If you've ever said "Well, I AM a lawyer, but I'm not YOUR lawyer....", we'd love to hear from you ✨
-
I've work closely with Dave and can speak first-hand to the quality he brings to the team. If you are looking for a program lead with open source experience this is your lucky day, jump on this right now.
---
RT @davelester
On Friday my position was eliminated as part of #googlelayoffs.I’m thankful to have been part of the @GoogleOSS team. 🙏 You all are amazing.
I’m now open to new roles. Need someone to run your company’s developer …
https://twitter.com/davelester/status/1617523169153236992 -
Which #RSS / #Atom reader are you using on #Android? I'm still in love with #Flym but sadly the author decided to stop development after #Google has introduced some new mandatory rules for news apps: https://support.google.com/googleplay/android-developer/answer/10177647?visit_id=637410766788299017-71528281&rd=2#news
App should be #FreeSoftware / #FOSS. Might consider to setup a server software to synchronize my feeds across multiple devices.
-
Ever since #SplitWise started forcing my friends to sign up for a premium account ($40 a year!) just to essentially use the app for a single group trip I've been on the hunt for an alternate.
I don't understand how it's ok to charge $40? Do people actually pay this?? The app essentially becomes useless once you add more than 3 expenses a day.
I think I found one.
https://spliit.app #SpliitApp #Spliit
Sure it's a little rough and not quite as full featured but guess what? It's free. Open source. Not riddled with God knows what kind of tracking and I'm fairly certain it doesn't currently sell my data.
And now I'll gladly support the developer via GitHub Sponsorships and tell everyone I can to switch over..
See how easy that was #SplitWise? Build a good app, I'll support it.
So sick of this #enshittification bullshit.
-
Hello! I'm Alistair, developer of Mochi, a decentralised application platform. It's built with Go, libp2p, Starlark, and React. It ships with lots of apps such as feeds, forums, project management, CRM, and wikis. We're launching version 0.3 soon, and looking for early adopters who aren't afraid of rough edges.
Outside of coding: long-term traveller (141 countries and counting), pilot, sailor, and hiker.
-
A video of what Ive been building for a small RSS network of feeds (about 30), categorised and tagged for easy, tidy and calm browsing of sources without socmed noise (or RSS reader deluge). the jOYND concept has other sections, this is the networks section. Im using Grav for the framework, and big thanks to ongoing work from Ole Vik who is the developer of the Twigfeeds Grav plugin.
(Clip should play in a browser 🙂)
-
@raphael That is great to know :)
The code is released under the GPL license so you're free to reuse (parts of) it as long as whatever you distribute is also under the GPL license. With that said, it's in #purescript so I'm not sure how reusable it is, unless your project is also in Purescript.
In any case, if you'd like to join forces for some project, please let me know. It gets demotivating trying to build tools by myself as a developer for a use case that's specific to me as a user. I could do with potential users/fellow developers :)
-
Oh dear. They want me to be involved in an AI project which seems to involve training a model with about 20 years of hard drives data, backup tapes of project data, excel sheets, word docs, pdfs, photos, SQL dumps of Sharepoint & timesheet application data & staff CVs. With the intent of giving AI the proposal for a new project, work out the time, cost and staff required to complete it & supply the staff with background knowledge of similar completed projects. Sounds easy, I'm just about to ask ChatGPT. #ITProblems
-
Oh dear. They want me to be involved in an AI project which seems to involve training a model with about 20 years of hard drives data, backup tapes of project data, excel sheets, word docs, pdfs, photos, SQL dumps of Sharepoint & timesheet application data & staff CVs. With the intent of giving AI the proposal for a new project, work out the time, cost and staff required to complete it & supply the staff with background knowledge of similar completed projects. Sounds easy, I'm just about to ask ChatGPT. #ITProblems
-
Oh dear. They want me to be involved in an AI project which seems to involve training a model with about 20 years of hard drives data, backup tapes of project data, excel sheets, word docs, pdfs, photos, SQL dumps of Sharepoint & timesheet application data & staff CVs. With the intent of giving AI the proposal for a new project, work out the time, cost and staff required to complete it & supply the staff with background knowledge of similar completed projects. Sounds easy, I'm just about to ask ChatGPT. #ITProblems
-
Oh dear. They want me to be involved in an AI project which seems to involve training a model with about 20 years of hard drives data, backup tapes of project data, excel sheets, word docs, pdfs, photos, SQL dumps of Sharepoint & timesheet application data & staff CVs. With the intent of giving AI the proposal for a new project, work out the time, cost and staff required to complete it & supply the staff with background knowledge of similar completed projects. Sounds easy, I'm just about to ask ChatGPT. #ITProblems
-
Oh dear. They want me to be involved in an AI project which seems to involve training a model with about 20 years of hard drives data, backup tapes of project data, excel sheets, word docs, pdfs, photos, SQL dumps of Sharepoint & timesheet application data & staff CVs. With the intent of giving AI the proposal for a new project, work out the time, cost and staff required to complete it & supply the staff with background knowledge of similar completed projects. Sounds easy, I'm just about to ask ChatGPT. #ITProblems
-
RE: https://thepit.social/@peter/115824339431975101
today’s #AltTxt #yaddayadda are images of a subreddit Confessions post: “I’m a developer for a major food delivery app. The 'Priority Fee' and 'Driver Benefit Fee' go 100% to the company. The driver sees $0 of it.”
transcript as AltTxt:
https://infosec.exchange/@jernej__s/115824510774751653and as a post:
https://veganism.social/@faket/115825112372408975we here #workingClass but a lot of y’all in the white-collar end of the class spectrum.
may y’all learn in 2026 class solidarity with new friends in the non-tech, gig economy, servant classes
-
I hate notarization on #macOS #development so much. Just ready to push an update to my #SecureScuttlebutt client, got the github action building the app for all platforms just to fail on macOS cause Apple changed a license agreement so the CI was failing 403 until I went to their developer portal to agree.
I'm shipping FOSS apps, going through this hops is so absurd.
-
Time for #ThrowbackThursday!
Here is the official #MusicVideo of #Lineage2 South-East #Asia for the #Philippines: #Pasan by #Callalily
https://www.youtube.com/watch?v=TzYhSms3fCc
---
I used to work for #L2SEA as a content officer, which included #webdevelopment and community forums administration (backend, frontend, managed the community team) Oh, that included the #GuildWars (#GW) 1 Philippine community forums and website.
It was a blast working with the company, with #NCsoft Korea our partner and game developer, my managers and my team, and all the players I've met both online and offline events.