GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE

  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by ilja (ilja@ilja.space), page 5

  1. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 21:20:29 JST ilja ilja
    in reply to
    • Hélène
    @helene Where/how do you see what's causing it? It seems like it's going down again, though

    And what's TLS state machines?
    In conversation Monday, 12-Sep-2022 21:20:29 JST from ilja.space permalink

    Attachments


    1. https://ilja.space/media/f43f9513-2c27-4503-a907-3b1058f3272d/Screenshot_20220912_141510.png
  2. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 21:12:31 JST ilja ilja
    in reply to
    • Hélène
    @helene If it gets too much, I'll just order something to drink, enjoy it all from the sidelines, while poking the fire some more from the there :blobfoxsmirk:
    In conversation Monday, 12-Sep-2022 21:12:31 JST from ilja.space permalink
  3. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 21:10:40 JST ilja ilja
    Why is pleroma using almost 1G RAM :blobfoxnotlikethis:

    Remember when it needed like only 60M :blobfoxcry:
    In conversation Monday, 12-Sep-2022 21:10:40 JST from ilja.space permalink

    Attachments


    1. https://ilja.space/media/2bd3c6cc-5d17-4cfc-a4bb-30cc85e9e7e6/Screenshot_20220912_140820.png
  4. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 21:08:10 JST ilja ilja
    in reply to
    • Hélène
    @helene Can't. I enjoy the chaos too much :heheevil:
    In conversation Monday, 12-Sep-2022 21:08:10 JST from ilja.space permalink
  5. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 21:05:42 JST ilja ilja
    I'm really glad with Hélène on pleroma team btw
    In conversation Monday, 12-Sep-2022 21:05:42 JST from ilja.space permalink
  6. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:59:16 JST ilja ilja
    in reply to
    • Hélène
    @helene

    > by writing everything in Elixir
    I'm sold :D

    LiveView seems interesting ? We probably still want things to be accessible via API (idk why, but somehow I think that's important), but having a build in FE doesn't exclude that. Having something that still allows to easily extend things seems good to me, and it would also allow us to fix the issue of having way too technical language and structure in the admin parts.
    In conversation Monday, 12-Sep-2022 20:59:16 JST from ilja.space permalink
  7. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:24:33 JST ilja ilja
    in reply to
    • Hélène
    @helene Not sure if it has to be BE, but yeah, I had the same feeling when first poking at it :/ There's probably stuff in there that can be reused, but there's stuff in there that don't even look like it's being used. It also seems like it was written to go in a certain direction, but that direction is different of where we're going, so it's like going against the tide with that...
    In conversation Monday, 12-Sep-2022 20:24:33 JST from ilja.space permalink
  8. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:24:24 JST ilja ilja
    in reply to
    • Hélène
    • ilja
    @helene For what needs to happen, https://git.pleroma.social/pleroma/admin-fe/-/merge_requests/209

    When a logged-in user isn't privileged, they shouldn't see whatever buttons or drop-downs allow them actions they aren't privileged too. The issue lists what still needs to be done for those.
    Then there's also the fact a bunch of calls are being made, but a lot can return a 403, so we need a way to handle that.

    The rest of the hiding, I can do since I'm already working on it. The calls is something I still have to figure out.
    In conversation Monday, 12-Sep-2022 20:24:24 JST from ilja.space permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: git.pleroma.social
      Draft: Handle moderation privileges (!209) · Merge requests · Pleroma / admin-fe · GitLab
      Fix #206 For BE MR...
  9. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:18:56 JST ilja ilja
    in reply to
    • Hélène
    @helene I think I'll just drop the tests for the other things that still need to happen. At least the "hide this element" ones. I also don't think these changes really improve admin-fe at all :/ They're needed for the changes in BE, but the whole thing just doesn't seem like it was really made for it and I'm just hacking it to make it work...
    In conversation Monday, 12-Sep-2022 20:18:56 JST from ilja.space permalink
  10. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:15:25 JST ilja ilja
    in reply to
    • Hélène
    @helene

    > and I'll try doing that!
    You mean writing the tests?
    In conversation Monday, 12-Sep-2022 20:15:25 JST from ilja.space permalink
  11. Embed this notice
    ilja (ilja@ilja.space)'s status on Monday, 12-Sep-2022 20:11:50 JST ilja ilja
    Last week I started working a it more ttd on admin-fe, but I'm honestly wondering how much sense it makes for what I'm doing.
    I'm basically writing a ton more code and spending time on the test than on the actual functionality. And the functionality isn't even that much. It's just hiding certain elements in specific cases, that's it...
    In conversation Monday, 12-Sep-2022 20:11:50 JST from ilja.space permalink
  12. Embed this notice
    ilja (ilja@ilja.space)'s status on Sunday, 11-Sep-2022 23:50:35 JST ilja ilja
    in reply to
    • ??StaceyQuest™️ :googlemuscleR:?:verified_neko:
    @lottev weigh regularly and if you see a trend of going up, you change eating habits to loose weight again until you're back at the number you're comfortable with
    In conversation Sunday, 11-Sep-2022 23:50:35 JST from ilja.space permalink
  13. Embed this notice
    ilja (ilja@ilja.space)'s status on Sunday, 11-Sep-2022 05:04:19 JST ilja ilja
    in reply to
    • infinite love ⴳ
    @trwnh yellow tomatoes seem cooler than red tomatoes, but the red ones actually taste better
    In conversation Sunday, 11-Sep-2022 05:04:19 JST from ilja.space permalink
  14. Embed this notice
    ilja (ilja@ilja.space)'s status on Saturday, 10-Sep-2022 23:08:24 JST ilja ilja
    in reply to
    • Hélène
    @helene I honestly have no idea what to do with them ^^ I've just been snacking on them now. I'm going to see friends tonight and prob just bring them with me. One of them likes to cook, so maybe they'll find them useful ^^'
    In conversation Saturday, 10-Sep-2022 23:08:24 JST from ilja.space permalink
  15. Embed this notice
    ilja (ilja@ilja.space)'s status on Saturday, 10-Sep-2022 22:33:34 JST ilja ilja
    in reply to
    • 「 Fried Fristi 」
    @fristi Oooh, please post about that when you do it!
    In conversation Saturday, 10-Sep-2022 22:33:34 JST from ilja.space permalink
  16. Embed this notice
    ilja (ilja@ilja.space)'s status on Saturday, 10-Sep-2022 22:33:03 JST ilja ilja
    in reply to
    • 「 Fried Fristi 」
    @fristi yup! Fun fact, the yellow cherry ones started with me putting a halve one from the store in some soil ;)
    In conversation Saturday, 10-Sep-2022 22:33:03 JST from ilja.space permalink
  17. Embed this notice
    ilja (ilja@ilja.space)'s status on Saturday, 10-Sep-2022 22:29:47 JST ilja ilja
    I cleaned up a bunch of my tomato plants and eeeh... Any one need some tomato :blobfoxnomtomato:
    In conversation Saturday, 10-Sep-2022 22:29:47 JST from ilja.space permalink

    Attachments


    1. https://ilja.space/media/528c2499-b086-463c-886e-c0c693dbb299/image20220910_132030650.jpg
  18. Embed this notice
    ilja (ilja@ilja.space)'s status on Friday, 09-Sep-2022 22:21:41 JST ilja ilja
    in reply to
    • Rin Patchouli
    @rin They know there are people who will be upset about this and it brings them joy to spread suffering
    In conversation Friday, 09-Sep-2022 22:21:41 JST from ilja.space permalink
  19. Embed this notice
    ilja (ilja@ilja.space)'s status on Thursday, 08-Sep-2022 07:13:17 JST ilja ilja
    in reply to
    • Dr. Quadragon ❌
    • Aurynn Shaw
    @aurynn @drq Sure! By the OP, I assume about the way pleroma is/was ran?

    Note that I only started to follow the project in 2018 and only got more involved about a year ago. So some things may be somewhat one sided.

    Basically lain started pleroma and other people started to contribute and work together. I don't know how it exactly evolved to this, but eventually you had some people working on pleroma based on some unwritten rules. Basically, if you wanted something in pleroma, you could make an issue or MR. In case of an issue, maybe someone would take it up. In case of an MR, people would review it. If a maintainer considered it good to merge, they approved it, if a second maintainer also agrees, they merge it. These were unwritten rules, so there are exceptions (mostly for smaller changes), but in general this worked.
    There were some frictions from time to time however, because sometimes things would happen that someone disagreed with, but things never really got discussed. I don't have examples of this, this is based on what I've been told later.
    Eventually these frictions got worse, remained undiscussed and ignored, and people started to leave. By this time there were payed devs, so development continued and the problems kept being ignored. Eventually the money ran out and it became clear that most people had either left or gotten burned out. Meanwhile pleroma had turned from a reputation of being a solid lightweight codebase, to being a buggy software no lighter than most other microblogging fedi software out there.
    Some people still wanted to work on pleroma, but it became clear there were two different (and incompatible) expectations. On the one hand you had people who wanted to work in a more consensus based way. On the other hand you had people who just wanted to push stuff as long as lain didn't complain.
    Eventually most of the people who wanted a more consensus based way of working left and started working on a fork. Two people still wanted to mend things between pleroma and the people who were now working on the fork, including lain who said they basically want the same thing.
    Talks happened and lain made it clear that they want a consensus way of decision making and always wanted that. It was also made clear that other maintainers have both the power and the permission to act when they see things going in a way they think is wrong. Some people returned to pleroma and the fork died out. This was around new year.
    By now there are people working on pleroma again and some things have been written down so expectations are more clear.
    Pleroma wants to be flexible, so there's no real direction other than what people contribute. Code quality needs to be acceptable, and you have to realise that your changes may affect other people and resolve issues if they arise, but there's no real "end" vision of what pleroma, as a software, must be outside of some generic goals.

    Personally I don't consider the people working on it now to be a committee. When someone says committee, I expect elected members, voting, big meetings where decisions are made... Pleroma doesn't have any of that. But I also don't think you can call it a bdfl run project. It's really just a bunch of people who decided they want to work on this project together in a way they can enjoy. At least that's how I see it.
    In conversation Thursday, 08-Sep-2022 07:13:17 JST from ilja.space permalink
  20. Embed this notice
    ilja (ilja@ilja.space)'s status on Thursday, 08-Sep-2022 05:55:12 JST ilja ilja
    in reply to
    • Dr. Quadragon ❌
    • Aurynn Shaw
    @drq @aurynn Committee sounds pretty formal to me. Pleroma never had that. What pleroma missed in the last couple of years imo was scrutiny of code quality (luckily this has been changing since february). For direction, pleroma does want to be flexible, so yeah, that kinda invites that it can go in all sorts of ways. But that's not because of a committee, afaict that was basically lain's vision from the start.
    In conversation Thursday, 08-Sep-2022 05:55:12 JST from ilja.space permalink
  • After
  • Before

User actions

    ilja

    ilja

    Hellooo :blobfoxwave: I'm ilja!I try to improve myself and the world by trying to contribute to the world of free software. Floss projects that currently interest me the most are Pleroma, YUNoHost and Ubuntu Touch. My main focus is currently Pleroma.I created the following bots: @citizeninitiativebot@ilja.space @translate@ilja.space @ccmusicbot@ilja.space @translate uses an MRF module I made with the goal of making it easier to create "reply and I respond"-type bots. If you're interested in that, check out it's profile.What people say about me:"I will haunt your soul for eternity, smartass" --fristi"one of the best lines in the pleroma code" --lain (talking about some code I wrote)"MEW MEW MEW MEW" --oceanTrans rights are human rights :transflag: :agenderflag: queer rights are human rights :rainbowflag: :lesbianlipstick_flag: And it's sad that over half a century after the Stonewall uprising, we still have to remember peop

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          1729
          Member since
          26 Jul 2022
          Notices
          206
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.