Q: Why Google Drive? Can we add NextCloud or some FOSS alternative?
A: If you are self hosting NextCloud, you should just self-host a Nostr relay.
Google Drive is valuable specifically because it is the opposite of a Nostr relay. It fills a gap in the Nostr ecosystem. Using NextCloud to inch it further away misses the point. Google Drive Relay is used BECAUSE it's on the opposite end of the spectrum. I'm not saying there's no room for anything in between. But the further you try to inch it away, the closer you get to simply recreating Nostr Relays. I understand the skepticism. But in my view, this is how Nostr does an Extend-Embrace-Extinguish of legacy tech. This is Art of War. 😂
Q: Why Google Drive? Can we add NextCloud or some FOSS alternative?
A: If you are self hosting NextCloud, you should just self-host a Nostr relay.
Is it centralized? Sure! Is it slow? Yep! Will the # of files break GDrive? Probably. Will Google delete offensive stuff? For sure. Will Google close your account because of an event somebody else wrote? Definatelly. Should we build it anyway? Hell yes.
Is it centralized? Sure! Is it slow? Yep! Will the # of files break GDrive? Probably. Will Google delete offensive stuff? For sure.
With major companies like Meta realizing the future potential of decentralized social media, connecting across protocols has never been more important.
#Nostr users can soon follow anyone on Threads via the Mostr bridge as Meta adds support for Activity Pub. This opens up a massive base of mainstream users, breaking down the #networkeffect barrier that new protocols struggle to overcome. This is hugely important for user retention.
Hopefully, once Threads users discover Nostr through our bridged interactions, they will realize what they're missing out on by staying under the control of Meta! #GrowNostr
With major companies like Meta realizing the future potential of decentralized social media, connecting across protocols has never been more important.
#Nostr users can soon follow anyone on Threads via the Mostr bridge as Meta adds support for Activity Pub. This opens up a massive base of mainstream users, breaking down the
You can't parse HTML with regex. Because HTML can't be parsed by regex. Regex is not a tool that can be used to correctly parse HTML. As I have answered in HTML-and-regex questions here so many times before, the use of regex will not allow you to consume HTML. Regular expressions are a tool that is insufficiently sophisticated to understand the constructs employed by HTML. HTML is not a regular language and hence cannot be parsed by regular expressions. Regex queries are not equipped to break down HTML into its meaningful parts. so many times but it is not getting to me. Even enhanced irregular regular expressions as used by Perl are not up to the task of parsing HTML. You will never make me crack. HTML is a language of sufficient complexity that it cannot be parsed by regular expressions. Even Jon Skeet cannot parse HTML using regular expressions. Every time you attempt to parse HTML with regular expressions, the unholy child weeps the blood of virgins, and Russian hackers pwn your webapp. Parsing HTML with regex summons tainted souls into the realm of the living. HTML and regex go together like love, marriage, and ritual infanticide. The <center> cannot hold it is too late. The force of regex and HTML together in the same conceptual space will destroy your mind like so much watery putty. If you parse HTML with regex you are giving in to Them and their blasphemous ways which doom us all to inhuman toil for the One whose Name cannot be expressed in the Basic Multilingual Plane, he comes. HTML-plus-regexp will liquify the nerves of the sentient whilst you observe, your psyche withering in the onslaught of horror. Rege̿̔̉x-based HTML parsers are the cancer that is killing StackOverflow it is too late it is too late we cannot be saved the trangession of a chi͡ld ensures regex will consume all living tissue (except for HTML which it cannot, as previously prophesied) dear lord help us how can anyone survive this scourge using regex to parse HTML has doomed humanity to an eternity of dread torture and security holes using regex as a tool to process HTML establishes a breach between this world and the dread realm of c͒ͪo͛ͫrrupt entities (like SGML entities, but more corrupt) a mere glimpse of the world of regex parsers for HTML will instantly transport a programmer's consciousness into a world of ceaseless screaming, he comes~~, the pestilent slithy regex-infection will devour your HTML parser, application and existence for all time like Visual Basic only worse he comes he comes do not fight he com̡e̶s, ̕h̵is un̨ho͞ly radiańcé destro҉ying all enli̍̈́̂̈́ghtenment, HTML tags lea͠ki̧n͘g fr̶ǫm ̡yo͟ur eye͢s̸ ̛l̕ik͏e liquid pain, the song of re̸gular expression parsing~~ will extinguish the voices of mortal man from the sphere I can see it can you see ̲͚̖͔̙î̩́t̲͎̩̱͔́̋̀ it is beautiful the final snuffing of the lies of Man ALL IS LOŚ͖̩͇̗̪̏̈́T A***LL IS LOST the pon̷y he comes he c̶̮omes he co**mes t**he ichor permeates all MY FACE MY FACE ᵒh god n**o NO NOO̼***OO NΘ stop the an*̶͑̾̾̅ͫ͏̙̤g͇̫͛͆̾ͫ̑͆l͖͉̗̩̳̟̍ͫͥͨe̠̅s a̧͈͖r̽̾̈́͒͑e not rè̑ͧ̌aͨl̘̝̙̃ͤ͂̾̆ ZA̡͊͠͝LGΌ ISͮ̂҉̯͈͕̹̘̱ TO͇̹̺ͅƝ̴ȳ̳ TH̘Ë͖́̉ ͠P̯͍̭O̚N̐Y̡ H̸̡̪̯ͨ͊̽̅̾̎Ȩ̬̩̾͛ͪ̈́̀́͘ ̶̧̨̱̹̭̯ͧ̾ͬC̷̙̲̝͖ͭ̏ͥͮ͟Oͮ͏̮̪̝͍M̲̖͊̒ͪͩͬ̚̚͜Ȇ̴̟̟͙̞ͩ͌͝S̨̥̫͎̭ͯ̿̔̀ͅ
You can't parse HTML with regex. Because HTML can't be parsed by regex. Regex is not a tool that can be used to correctly parse HTML. As I have answered in HTML-and-regex questions here so many times before, the use of regex will not allow you to consume HTML. Regular expressions are a tool that is insufficiently sophisticated to understand the constructs employed by HTML. HTML is not a regular language and hence cannot be parsed by regular expressions. Regex queries are not equipped to break down...
@meso that refers only to html5 bullshit that fucking hipsers made so stupid that it may have recurrent inlaids. this is absolutely fucktards' shit that made everything in the world of parsers work fucking slowly and ineffectively. without html5 it was all fine and normal. I told them the new generatoions are drug users with totally rotten brains. that had to be aborted before they gave it the birth via their deep and dirty anal hole.
@meso the way out is to write normal parsers that will ignore the cyclic bullshit and parse only normal linear pieces. this seems the only way to kill that idiocy.
@meso really, the full PERL regex allow processing cyclic references (usually with limited indirection level), but this is killer ineffective and memory consuming process. and now every browser has to use totally inefective parsers. they're principally ineffective. this is the consequence of sick design of html5. moreover, it allows creating bomb HTML code that will intentionally devour CPU and memory and this is also a security undermine or something like this. needless to say, nobody really even needed that cyclic references in HTML. this was pure stupidity when they implemented that evil bug in HTML.
@meso really, the full PERL regex allow processing cyclic references (usually with limited indirection level), but this is killer ineffective and memory consuming process. and now every browser has to use totally inefective parsers. they're principally ineffective. this is the consequence of sick design of html5. moreover, it allows creating bomb HTML code that will intentionally devour CPU and memory and this is also a security undermine or something like this. needless to say, nobody really even...
Gregory's Server
