I *really* want to see #rss get into the #mainstream https://www.niemanlab.org/2022/12/this-i.. I still believe it needs to handle two problems: 1. #redistribution checking (content #hash ) and 2. #comments . #comments could be handled via #email but ideally #rss itself woudl handle this. Anyway, I still want to see #deadsocial based on #rss and completely #distributed .
The #deadsocial #gui , now known as #deadgui is somewhat #mature now it seems, with it doing the bare #minimum of allowing you to create tonnes of #pending #messages and then #send them when the #server or #internet come back, which seems to happen often.
In fact, it appears #deadsocial or the #internet just went out. So it will be interesting to see how it handles this #edgecase ... #fingerscrossed all the #messages get sent once the #server or #internet comes back #online .
Oops, I had quite a #serious #bug in the #deadsocial #gui that meant it added the #message as an #array of #characters to the #pending #list . Needless to say, it caused some problems!
Another test #message from the #deadsocial #gui ... The #plan is to make using the #website #offline possible (as often happens with the bad #internet ) that we have where I live.
This is a test #message from a new #deadsocial #gui written to make #posting much easier.
Not to self, #deadsocial should #save #login #sessions to #disk and try to bring them back after a #restart - it is incredibly annoying to have to #login all of the time! Maybe I look into this for the next #version ...
Probably now running too much on the #coffeespace #server , it keeps #crashing due to low #ram ! There aren't many tricks left in my book to #reduce the #ram on the #server . The largest #program is actually #deadsocial ... Using 20% of the #ram all by itself.
At some point I will eventually get around to #replacing #deadsocial with a #version written in C. I have most of the #libraries #written now and even have some #compelling #security #ideas now. I am still yet to #solve some basic #issues such as #anonymous #comments for non- #users , but I get there slowly.
@barray on Thu Mar 03 04:21:45 UTC 2022 said: &eLooks like this #server #crashed #again - but only #deadsocial . My guess is that we are running out of #ram ...Starting to #suspect that this #server is #randomly #rebooting ... Ouch!
Very interesting #authentication #method using pure #http without #cookies or #javascript ! https://saucecode.bar/posts/06-using-www.. Even #deadsocial uses a single #cookie ! I will need to check it out, but this is potentially extremely cool!
Yeah... #text #rendering and #ui #design around #fonts is *really* tough: https://gankra.github.io/blah/text-hates.. For this reason alone, #deadsocial only supports 7 bit #ascii - the reason being that it's better off #supporting a #subset really well, rather than a #superset really badly... I do not envy the lost #souls that work in such areas...
Sometimes I #forget how blazingly fast #deadsocial is by #design ... Despite running on a #potato of a #server - it is currently using less than 10MB of #ram and #responses are under 1ms! I would suggest that's pretty hard to beat!
The #scuttlebutt #protocol will be well worth a read when #designing the new #deadsocial #platform https://ssbc.github.io/scuttlebutt-proto.. The part about #keypair #encryption is of specific interest. What I am looking to do will essentially be a #hybrid of this and super old #technology ...
Interesting #article and #website #dedicated to running your own #socialmedia https://runyourown.social/ It reminds me that I still need to write my #coffeespace #article about the #design for the #deadsocial #successor !
Interesting, now I am wondering whether #deadsocial should have a #relational #database such as #sql or a non-relational database such as #nosql https://lowendbox.com/blog/sql-vs-nosql-.. Given that currently everything is in #json #format - the transition to #nosql would likely be far easier! #deadsocial was specifically #designed with this #datastructure in mind!