Make no mistake, the massive layoffs are intentional SHORT TERM sabotage by business decision makers with the goal of LONG TERM benefits for them.
They're trying to drive down the costs of labor. Specifically, they're firing everyone so that we'll accept lower wages upon rehire.
In #infosec, this will backfire on them.
By firing everyone, the level of security technical debt will increase that they'll have to hire everyone AND THEN SOME back at even higher rates.
So. Neat. Fucking great.
In the mean time, research how to create unions. Start doing so. Tech folks and infosec are not used to needing collective bargaining. You need it now.
Learn about the concepts of Economic Leverage and how it works as an individual contributor and when that fails how Collective Leverage works. The whole "if you fire that one person, we all quit" sort of thing works.
You all hack systems every day. You all study Social Engineering and combat it every day.
Hack the labor market. Socially engineer our mutual protection.
every new user being shocked that DMs aren’t actually private is kinda scary because it means that everybody just assumes DMs on other platforms are private
because they aren’t. the only difference between fedi and other social media is that fedi admins don’t have a vested interest in making you think DMs are private
@fleeky I don't know the folklore but probably. Have you played Disco Elysium? Kinda like all the personalities talking to each other and the user. Maybe each gets "You only respond if you think this is relevant to you" in their system prompt and have an order for processing.
Thinking about how to add memory to an #LLM
Might be good to have two models running in tandem. One is trained to use a memory API. The other is just the personality. Before the personality gets data, memory decides if it wants to do some RAG queries. Then the result is fed to personality to respond with without it needing to understand memory. Then memory asks itself if it needs to remember any of personality's outputs.
Neat article my coworker found about some of the limitations of LLMs and so called #GenAI (generative AI?).
https://www.aspendigital.org/report/navigating-uncharted-waters/
@Hyolobrika Ooo. If you remember the names I'd love yo learn about them. :o
What Apple is going to do to PWAs in less than two weeks in the EU is dastardly.
Their goal is to remove the only versions of Push, Fullscreen, Homescreen Icons, and Badging that didn't require paying them to be in the App Store *and make sure no other browser can have them either*.
They tried to sneak it under the noise of the alt-store drama, in a clearly premeditated fashion.
It's no exaggeration to say they've gone to war with the web & we don't owe the benefit of the doubt ever again.
Suuuper rough sketch for anyone interested. Basically we'll have a list of accounts you follow in localStorage, then ingest their outboxes into this. Then we'll set up fully p2p identities and use the #DistributedPress #SocialInbox as another source to ingest stuff like followers only posts and replies from people you don't follow.
https://github.com/hyphacoop/reader.distributed.press/pull/3
@ryanramage Yeah quest 3 is probably the most pragmatic choice right now. I personally wouldn't allow anything Facebook related on my face and scanning my home, but I am one of those tinfoil hat types so YMMV :P Defs more usable and stable than any open source setup.
@jonny Yeah the model itself is super simple. Just an object store with indexes. 😅 Initially I wanted to do some zany stuff with RDF but time constraints got in the way.
@jonny I can send you a link when we have something more substantial but for now we're working on v1 here: https://github.com/hyphacoop/reader.distributed.press/pull/1
@Hyolobrika Right now timelines exist in the code of large codebases for stuff like Mastodon and require an update for everyone as well as a bunch of security concerns since all the data is mushed together into a single db for instance users. Our approach puts data into a client side db based on a users follows and uses simple js/html/css to make it easier to hack on.
@jonny For now we'll start by just rendering notes but having an easy way to filter/sort. We'll be ingesting data into IndexedDB in the client and using minimal-ish code to make it easier to fork and customize the feed.
https://soundcloud.com/mixmag-1/premiere-oyubi-tomys-siren
Music to review code to. 🤓
Bouta start a new database for client side indexing of ActivityPub data and making user curated timelines that much easier.
Hot take that I only partially believe, but that is made unnecessarily inflammatory for the sake of social media brevity:
Nearly every bad thing in tech traces back to that the tech sector is one of the first to grow in post-Reagan disruption of labor rights and antitrust regulations, such that it is uniquely concentrated in a few unaccountable effective monopolies.
Occult Enby that's making local-first software with peer to peer protocols, mesh networks, and the web.
Exploring what a local-first cyberspace might look like in my spare time.