1,305 karma · joined June 28, 2022
If you add a site to iOS' homescreen it automatically becomes a PWA. The best example I found of a site fully leveraging this feature is Cryptee[0]. They talk about the PWA thing here: https://crypt.ee/download
[0] https://en.m.wikipedia.org/wiki/DMARC
[1] https://en.m.wikipedia.org/wiki/DomainKeys_Identified_Mail
GitHub has its Sponsors program[0]. You can still contribute code safe in the knowledge that you can bring home the bacon if you've managed to get people to sponsor you.
[0] https://github.com/sponsors
> Dependency and Corporate Support: Given the heavy reliance of big corporations on OSS
Corporations depend on OSS, but they should compensate the developers if the project is a cornerstone of their service/product. This does happen, and I've seen it happen.
> Licensing Challenges: How effective do you find the current open-source licensing models, especially in terms of commercial use? Are there ways these licenses can be adapted to better protect and benefit OSS developers?
It's important to distinguish between 'Gratis' software (free as in free beer) and free, as in 'free speech'. If it's the latter, as in the FLOSS model, developers getting compensated is often a bonus and not the main goal.
> Community Engagement: What strategies have you found effective in building and maintaining a strong, active community around an OSS project?
Do cool stuff, tell people about it. It's that simple. Social media is one way. Another is through word of mouth. If the project fills a gap in the market, people will notice.
> Comparison with Proprietary Software: In your experience, what are the key advantages and disadvantages of OSS versus proprietary software, particularly regarding innovation, quality, and user engagement?
Proprietary software is often closed source and doesn't have community eyeballs on it, so as opposed to FLOSS, it's inferior, but still often needed (I use Windows for example, because I have to, but default to Linux for everything else).
[0] https://en.m.wikipedia.org/wiki/Third-party_doctrine
> Netflow data can be used to track network activity traffic through VPNs
Does this mean so called non-logging VPNs are handing over data? That seems unlikely depending on the provider. Mullvad seems pretty solid and seems like they don't sell 'Netflow' data. But I could be wrong?
I wouldn't use XP as a daily driver if that's what you intend. There's so many exploits that have piled up over the years that getting pwned is inevitable at some stage and the attack surface of XP is massive.
HTTPS/TLS prevents MITM attacks, but rogue certificates can be installed to sniff the plaintext, but that's exceedingly rare and hard to do. IANAC (I am not a cryptographer) and that's the best 2 cents I can manage, sorry. But things like DNS can be sniffed off the wire easily, and anything in plaintext HTTP is fair game.
Generalists can spread themselves thinly across disciplines and never hyperfocus, so again: another caveat. It depends on your situation whether you want to specialize or generalize, and this can be a case-by-case basis.
iPhones and other iDevices are more accessible. It used to be a certain cohort could afford such devices and the rest had to buy 'Peasant Android' devices. But you can get iPhones refurbished in good condition from many vendors, and at a good discount. Caveat: they're not brand new, but they are very close.
If you want a catchy e-mail use .com which people will remember. The only caveat is finding a short .com (All the good ones are taken, although Derek Sivers wrote a program to hunt for short domains so you could go that route)
One concern is that there are tech-illiterate people who fall victim of such an ID system and don't use a VPN to bypass it. I don't have numbers/stats, but I imagine a good chunk won't be using VPNs.
There is also another concern I have; that this verification database could be breached and people's 'preferences' are exposed. The only way to avoid such a breach is to not collect such data in the first place.
> Six degrees of separation is the idea that all people are six or fewer social connections away from each other. As a result, a chain of "friend of a friend" statements can be made to connect any two people in a maximum of six steps. It is also known as the six handshakes rule.[1]
I know it doesn't mean we're all 'blood brothers' but it's useful when discussing the 'small world' phenomenon.
- Search GitHub for projects other people have already done so you're not re-inventing the wheel (unless you want to learn how the wheel is made and that excites you).
- Build in business logic from the outset if you must. Learn the Stripe API. Don't tack on business logic later when your project becomes hyper-successful and you're scrambling to monetize.
- ChatGPT is just a guide. It will not spoonfeed you an entire SaaS Enterprise just by asking it to, there has to be a human in the loop with ChatGPT.
- Don't learn frameworks first, and then learn fundamentals. Start with vanilla JS, CSS & HTML, then choose a framework that doesn't insult your soul.
They have much more to be annoyed at. VPN companies, The Tor Project, AD blockers, etc
I use the Google One VPN[0] to cloak my real IP, but only sparingly. For most of my Internet surfing I use a two hop VPN setup. One VPN router with kill switch mode, and then I connect to another VPN service on top of that, a sort of fake Tor / private relay setup.
I don't funnel all my traffic into Google One's VPN. I like to compartment and not put all my eggs in one basket. Looks like I'll be doing the same when this new Google-owned IP cloaking feature ships.
Sometimes the groups want a good reputation for not disclosing stuff if the ransom was paid. They earn that reputation over time.