I thought there was recently plugin capabilities that made forks less necessary with beaker? I may be talking out of my bum too but I swear I read that. But I would still support adding the man that had created beaker in the first place or even just spreading the love and appreciation a little to show this is a respectful community that wants to grow and flourish with others in the open source environment
I have a concern in regards to app development. If apps are going to have a lot of business logic in the front end, and we donāt have a robust browser like Chrome with V8 JavaScript engine to process the Javascript, wouldnāt that hinder a lot of app development.
Also, having a familiar browser that people already use, such as Chrome or Firefox, would make it easier for mass adoption.
Wouldnāt it be better to just make plugins or extensions for browsers already being used.
SAFEr is currently built with the electron framework which uses the V8 engine so you would theoretically get the same performance.
These are not mutually exclusive. we can have a browser dedicated to Safe and plugins for the other classic browser. Apparently itās ājustā Chrome that may cause a problem and this is part of the debate of using .safenet vs safe://.
Lol please read the ages of discussion and arguments against that, that have taken place above.
Both can be made eventually, but creation and promotion of the new safe:// protocol instead of http:// has been decided to be much more important now for everyone.
But yes you can make plugins, everyone can. And will. Go ahead
but weāve all decided to dedicate these scarce resources donated to this particular browser towards creating an entirely new, powerful protocol safe://, to give the world something very clear, exciting, and brand new in terms of serving internet data / apps
Did you install the latest version of Node JS?
Hello everyone,
Just a quick one from me. I know you guys are discussing creating your own browser ( safer browser).
I just came across a malware that happen to be of the same name:
So maybe would be work giving the product a different name.
Good time to remind the community to support @PaulFrazee Beaker project. Change the name from SAFEr to SAFE Beaker.
Morning all! Sorry, Iāve been off the grid the weekend, so catching up on this now.
Iāll fire in and get some responses shortly!
Iāll be posting updates as regularly as make sense once Iām started.
Iāll be on it (most likely) every Wednesday so that might make the most sense if I do go weekly. And yeh, as soon as I have installers (and then updates to them), Iād hope to be getting them in peopleās hands asap.
As Iāve not officially started yet. Thereās been some small work on the master fork, but nothing worth committing yet. This will pick up speed once funding is sorted.
As right now itās a simple fork of the code (with a few lines added/changed), the build instructions are the same at this point.
@DavidMtl It looks to me like you might not have run the npm run rebuild
step.
Beyond that, Iām not sure. Sometimes npm
fails on an install and youād have to wipe the whole node_modules
folder and start from that step again if the above doesnāt work.
Hopefully though, Iāll be able to dedicate some time to this and get the packages building so no one will have to go through NPM hell soon enough!
Yeh, the new plugin setup from @PaulFrazee is great and for safe:
and javascript injection a fork is not needed. Other changes to the code currently would need a fork (for some stretch goals, eg.).
@PaulFrazee Sounds absolutely reasonable.
My plan with any fork was only to go as far as needed for any extra functionality. I absolutely donāt want to erase ābeakerā naming even then (which Iām aware is in the terms to keep anyway). So your suggestion about a package system for additional functionality while keeping the beaker brand presence seems ideal
The SAFEr Browser could be more like a custom āSAFE buildā of Beaker or something, and then you could have an IFPS build and DAT build and so onā¦
Kinda like different flavors of Beaker
SAFE Beaker
IPFS Beaker
DAT Beaker
What is the plan for the name at the top right of the browser?
I hope you are not waiting until 100% of funding is complete before starting on the project?
My vote would be to keep it very simple:
SAFE Browser
In the top right SAFE would be enough IMO.
Safe Browser powered by Beaker
I like it but it is a bit lengthy.
And incognito mode a condom icon