The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act as a notification distributor.
In addition, I use Proton Mail which doesn't really allow custom notification services. Prism has a custom integration to work around that so your proton mail notifications don't have to touch google services.
The webpush endpoint registration is initiated from the client. The Android app can act as a client and it's the one that registers Mozilla's autopush service.
I meant that at the network level, should something be monitoring, your client would be making requests to a unique (ntfy) address that virtually nobody else ever uses. Requests to Mozilla are more crowd blended as it's quite popular already.
Yes, they are https so security is not a concern.
I want to crowd blend at the network level so that my requests don't aversive that I'm using a privacy notification system (or a VPN).
I would recommend people use comaps instead which is the actual FOSS fork. OM has a long history of malicious behaviour like quietly adding ads, turning a part of its previously open sourced code proprietary and misappropriating donations. OM has lost most of its community a year ago to comaps and are now rushing vibe coded features to compensate.
> OM has lost most of its community a year ago to comaps
> rushing to compensate
I understand that you, being a contributor to CoMaps which people can see on your page, want to promote it, but it’s just spreading false info. Just one Russian community of OrganicMaps in Telegram has 4000+ members, CoMaps RU is not even at 200. Global group of OM is at 1650, CoMaps is at 840 of it.
It’s not OM who is compensating all over the place in this thread.
Are you me? Somebody was talking about gitea on here yesterday and I also ended up self-hosting and moving all of my private projects to Ferjero yesterday after a bit of research. I can't bring myself to move public projects due to job prospects + GitHub network effect. Otherwise I'm role playing as a system admin now with 20 local services for various things I need. I think the most important thing is to have regular backups as you're now in charge of keeping your data from getting lost.
It's not really a refutation of my point about how building a good component library is hard, to suggest using another component library. Of course, if you use one it's easier, that was my entire point.
shadcn ui is not a component library but the basis for a component library that has great accessibility built-in from the start, so yes, it is a refutation.
Maybe we're arguing semantics, but I think calling shadcn a "basis for a design system" is more accurate than a traditional component library. The difference to me is that shadcn lives inside your codebase and you can fully customize it as you please. You cannot customize a component library like MUI nearly to that extent.
Understanding a perspective and agreeing with it aren’t the same thing. Herring’s point was about the ‘I don’t see why anyone would need this’ framing, not that the position itself is hard to grasp.
When I finished reading it I thought it was an anti-Trump piece, but the author also wrote: "That's why it baffles me that some prominent technologists embrace hateful ideologies.". Was Trump a techie too? He must have been behind the creation of JS.
"The ARM processor which powers the modern world was co-designed by a trans woman." This is not factually correct. Roger Wilson was one of the designers of the processor, but he didn't transition to become Sophie Wilson until 9 years after the first release of ARM1 according to Wikipedia.
Yes, the understanding is that trans people were always trans. It may have taken time for them to understand that and perhaps more to decide to adopt that identity publicly, but they're not "not trans" before that. Other queer identities are generally thought of the same way in queer communities: many people have early experiences (e.g. fixating on same-sex characters in fiction the way peers might opposite-sex characters) that they later realise were early expressions of their orientation.
The transgenderist stance is that once a man announces he is a woman, then he was always a woman and always will be. Unless he detransitions of course. Then he was always a man and always will be. Same for when a woman declares that she is a man.
So a man who builds his entire career as a man, with all the privilege that brings, as Wilson did, can identify as a woman and these prior achievements now all become that of a woman. Even if this stretches plausibility, what with the sexism of the industry at the time. He can even receive accolades reserved for women, as if he had to work ten times as hard to be taken seriously in a male-dominated field.
This rewriting of history is also why, for example, film credits listing Ellen Page have been retrospectively updated to Elliot Page even though there was no Elliot Page at the time of filming.
The code is partly refined AI generated slop and the UX is lacking. The functionality is very basic and needs to be more thoroughly tested. This type of project is half a work day tops for a senior+ dev to create with agentic coding.
I came to this conclusion as well. The README gives off some vibes but the sheer volume and writing style of the code comments is what really sells it for me. For example:
// Enhanced styling with column-specific classes and alignment
This sort of marketing-speak isn't what people typically put in their code, LLMs love buzzwords. It's not just this, it's everything, but hopefully you get what I mean.
The mindless code comments are a dead giveaway. It's always the same pattern of:
"a thing" <--- here is a thing
Generally a dev would clean these up, but when they don't it's a major red flag to me that it's just unreviewed vibe coded slop.
- "Electron comes with a few rather significant drawbacks" Not going to mention them at all though?
- what possible reason could one have to use Next with Electron? Not everything needs to be in Next and there's no reason for SSR + Node.js API server (primary advantages of Next vs React) when the client and server are on the same machine. The author's solution is to wrap this with another dubious framework (Nextron looks abandoned and hasn't been updated for over 10 months btw) to force them to somehow work together. Like why?
- the idea behind Tauri to leverage the user's system's webview may sound like free real estate, but as many Cordova devs have previously found out, it's incredibly risky when you have no control of your own runtime. Desktop webviews are not a uniform layer. Ex. Webrtc is not supported on Linux webviews.
Yeah, it makes zero sense to use a SSR framework for an Electron app. Just use React, Vue, or Svelte directly. It's one of the few use cases where a SPA makes sense, since the bundle is being served locally.
The difference: Your phone doesn't get notifications from your notification service directly, but from Mozilla which helps to hide your digital fingerprint of you using a separate notification provider like ntfy. Prism also allows Telegram or Signal to act as a notification distributor. In addition, I use Proton Mail which doesn't really allow custom notification services. Prism has a custom integration to work around that so your proton mail notifications don't have to touch google services.