Yes - well, almost! I made a read-only filesystem interface to Lemmy then wrote a small program for one of the Plan 9 text editors/programming environments to access it.
The real thing would be to serve that filesystem interface over the Plan 9 file protocol (9P).
Not quite there yet!
You know what's funny? I would never use something like this (my own Lemmy client is absolutely terrible in comparison!).
But I'm so happy that Alexandrite exists: it's proof that programming and web development can still be experimental and loads of fun. Congrats to the developers!
It certainly would make it a bit more impractical to enforce some of these silly laws.
The new tooling provides a buffer and a way to route around some of that silliness.
You could perhaps argue that without the threat of these kinds of bills becoming reality,
the impetus to develop this tooling in the first place may not have been enough to get it where it is today.
This comment really spoke to me; thanks for replying.
weâre iterating upon what already exists
Absolutely. Do I think Lemmy, Python, ActivityPub or any of this web stuff is ideal?
Personally: no.
But that ability to make a little gesture like this, maybe have it accepted (or not!), and make it all a bit easier to work is worth any sort of personal compromise and frustration I feel. That optimism that you mention is really powerful.
Me too! The differences really become apparent when more features are added.
Battery life I notice. Also just the way the thing feels; I can intuit where things are in the app because I already know how to use my iPhone.
I've managed to create an entire career (almost 10 years in now) out of the transparency in the tech community.
Especially in open source.
I'm hoping that paying it back like this inspires and provides the same opportunity to others!
Some per-session rate-limiting by a HTTP reverse proxy could go a long way.
Should any user be able to create a community via the API more than,
say, once every 10 seconds?
I'm not familiar with the rate limiting already built in to the Lemmy server, though.
Yeah that's another way. I'm pretty terrible with relational databases, though! I've sent over a Python script which does the job via the HTTP API. Hopefully the admins of lemmy.world will see the post: https://lemmy.world/post/1720870
The admin of lemmyworld said itâll take time to remove them,
but I donât know why (there seems to be the functionality in the API)
Indeed. Looks like it's just a matter of a big for loop over each community ID, POST /community/delete with body community_id=1234.
Maybe I'll try to see if it's possible to get some action on removing them by sending over some Python script or something that does the job.
Quick count shows almost 14%(!) of all communities indexed by lemmyverse are those junk communities:
A place I used to work at, Sol1, supported Linux on the desktop for small businesses in Sydney, Australia.
They're a ~10 person company and are really casual, so they'd probably be happy to answer any questions.
Because they canât or are not willing to investigate what happened at this particular company nor to its staff. The push of the story is therefore about whatâs happening on Twitter (âgetting absolutely roastedâ) because people connect with action.
A better story could recount the events up to now. Maybe something like this?
Find some fired staff members. How long were they working there?
Tell a little story of the day the staff first heard of the layoffs.
Show the layoff message or paraphrase what was said to them by CEO or whoever
Interesting point: Were they told they were being replaced by a large language model or some "AI" tech?
Now include the obnoxious tweet by the CEO
Finding this information and weaving it into a story that people go "And then what happened?!" is difficult and takes time. It's hard to justify when you can get clicks from shit like this article.
Iâve known dev teams who donât really know how to get their application to read from a configuration file (or similar). They would know how to do it in a âHello, world!â type tutorial. But they didnât have the skills to do it otherwise - let alone in the codebases they were maintaining. They just kept their apps chugging along on some super outdated .Net and they knew the databaseâs schema. Thatâs about it.
They were getting paid more and have more job security than me so I commend them.
Yes - well, almost! I made a read-only filesystem interface to Lemmy then wrote a small program for one of the Plan 9 text editors/programming environments to access it.
The real thing would be to serve that filesystem interface over the Plan 9 file protocol (9P). Not quite there yet!