Comments

Reply to comment by /u/this_one in Decentralizing Raddle by /u/ziq

-1

asdfasdf wrote

I'll admit yes, colour theory is always important but there were noticeable problems with the theme itself. Visited links were an almost unreadable shade of grey since ziq forgot to add a:visited to the list of things that should have link colours.

Reply to comment by /u/ziq in Decentralizing Raddle by /u/ziq

-2

asdfasdf wrote (edited )

Don't pretend you're any good at theming. Ever seen /f/newwave? That was eye hurting material. All your good themes are just hacks around shiningwing's material themes and my various themes.

Reply to comment by /u/ziq in Decentralizing Raddle by /u/ziq

-1

asdfasdf wrote

The reason nettle didn't work was because the code wasn't up to snuff. Arrogant ego jerk goes here.

Who did you ask? ("Yourself" doesn't count.) You can't write a fucking CSS theme.

You're not ready to code something this complicated while you're still learning. Decentralized software is as complex as it gets.

Emma once told me I'd be able to write a lot more complex stuff than her very soon. I've surprised a lot of people, including professionals with PhDs, with what I've done and said in places like #lisp.

Reply to comment by /u/ziq in Decentralizing Raddle by /u/ziq

1

asdfasdf wrote (edited )

It would work if people were interested. Raddle and Postmill have that since you're somewhat of an influencer -- I'm not though. The main hurdles for web based nettle were to get object parsing and signatures working in the browser. I don't know much JavaScript and I'd rather not touch it with a ten foot pole, so I can't work on that. Writing markdown documents and using putfile worked perfectly fine though.

Edit since you did: popularity breeds complacency since you don't have to work for your following. Maybe trying to filter spam and bogus votes would be useful. I'm not the only person working on netfarm either, there's four of us designing and implementing our ideas. Ian's putting a lot of work into setting up a documentation system and they're certainly as much of a netfarm hacker as I am.

Reply to comment by /u/ziq in Decentralizing Raddle by /u/ziq

1

asdfasdf wrote (edited )

I've seen quite a lot of projects which start as a centralised service but somehow everyone gets confused on how to make it decentralised. You have to consider what is too tricky to do at a distance, such as counting votes, and work out alternative solutions. (Votes aren't very good actually. People are quite different and just averaging out people's opinions isn't the best solution.)

Nettle did work but I overestimated what could be done with a relatively simple format and system. Netfarm's had a lot of refinement and theory applied and I've talked to several interested people who have contributed to the design. I've had messages from people who have experience with decentralised systems and folks who implement object systems for their day job.

3

asdfasdf wrote

Unfortunately from experience, going from centralised to decentralised rarely works. You need to start with a provably decentralisable base and work from there. PHP isn't exactly a networking language either.

The fellas at Netfarm are working on a decentralised system which could fit the backend half of a decentralised forum, it's going to have a meta object protocol and ECDSA signing to keep stuff flexible and tamper proof.

1

asdfasdf wrote

What a waste to spin up a browser and parse through HTML. Just grab the method, action URL and fields you need and do something like this:

(let ((cookies (make-instance 'drakma:cookie-jar)))
  (drakma:http-request "https://website.org/login"
                       :method :post
                       :cookie-jar cookies
                       :parameters '(("username" . "foo")
                                     ("password" . "bar"))))

Now use :cookie-jar cookies for every other request you make in the let.