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 heluecht (heluecht@pirati.ca), page 6

  1. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 24-Jan-2023 03:58:28 JST heluecht heluecht
    in reply to
    • Fedilab Apps
    • marek
    • marek
    @apps @marek @marek Since the object in Mastodon is called "Status", I'd prefer in_reply_status instead. Is that okay?
    In conversation Tuesday, 24-Jan-2023 03:58:28 JST from gnusocial.jp permalink
  2. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 24-Jan-2023 03:51:58 JST heluecht heluecht
    in reply to
    • Fedilab Apps
    • marek
    • marek
    @apps @marek @marek What about nested replies? Means: When A is a comment to B, which is a comment do C, which commented on D? Should then the object of post A not only contain the post B, but inside the post B there is post C, which also contains post D? This can quickly decrease the performance a lot.
    In conversation Tuesday, 24-Jan-2023 03:51:58 JST from gnusocial.jp permalink
  3. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Monday, 23-Jan-2023 01:14:11 JST heluecht heluecht
    • Friendica Admins
    As you might have heard, there are issues with the Twitter API. Several favourite clients stopped working, while others (still) do. By now there hadn't been any word if there is some massive Problem or if this was some deliberate action.

    Whatever is causing these issues, at least my connection still works. How about yours? Is the Twitter connector on your systems still running?
    In conversation Monday, 23-Jan-2023 01:14:11 JST from pirati.ca permalink
  4. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Monday, 23-Jan-2023 01:13:43 JST heluecht heluecht
    in reply to
    • hankg
    • heluecht
    • andy
    • Friendica Admins
    @andy @hankg "regularly" is fetching really often, means every few minutes. That's why I recommend to set 'adjust_poll_frequency' => true, in your local.config.php and also to set 'min_poll_interval' => 5, to a minimal poll interval that you feel safe about (like the 5 minutes in the example)
    In conversation Monday, 23-Jan-2023 01:13:43 JST from pirati.ca permalink
  5. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Sunday, 22-Jan-2023 21:23:18 JST heluecht heluecht
    in reply to
    • kriegundfreitag
    @kriegundfreitag Was davon? "Life is life" oder "rhythm is a dancer"? Oder andere Glanzstücke?
    In conversation Sunday, 22-Jan-2023 21:23:18 JST from pirati.ca permalink
  6. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Wednesday, 18-Jan-2023 22:13:08 JST heluecht heluecht
    in reply to
    • hypolite
    @hypolite I also want to refer to the recurrent laryngeal nerve, that is often cited as evidence of evolution, since it doesn't make sense to route a nerve nearly 5 meters through the body of a giraffe instead of taking the direct path of some centimeters:
    en.wikipedia.org/wiki/Recurren…
    In conversation Wednesday, 18-Jan-2023 22:13:08 JST from pirati.ca permalink

    Attachments


  7. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Sunday, 15-Jan-2023 00:40:15 JST heluecht heluecht
    in reply to
    • 𝐿𝒶𝓃𝒶 :verifiedtrans:
    @LadyDragonfly Reggae: The world is fucked and I don't care?
    In conversation Sunday, 15-Jan-2023 00:40:15 JST from pirati.ca permalink
  8. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Thursday, 12-Jan-2023 14:50:34 JST heluecht heluecht
    in reply to
    • heluecht
    • Fedilab Apps
    • Matthias/E
    @one @apps Ah, yeah! You mean when you alter permissions on a comment?
    In conversation Thursday, 12-Jan-2023 14:50:34 JST from pirati.ca permalink
  9. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Thursday, 12-Jan-2023 06:49:11 JST heluecht heluecht
    in reply to
    • Friendica Support
    • Fedilab Apps
    • Matthias/E
    @one @apps This should not happen. There should be an error instead. Can you open an issue?
    In conversation Thursday, 12-Jan-2023 06:49:11 JST from gnusocial.jp permalink
  10. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 10-Jan-2023 09:06:28 JST heluecht heluecht
    in reply to
    • hypolite
    @hypolite Aren't we all more or less in the spectrum?
    In conversation Tuesday, 10-Jan-2023 09:06:28 JST from pirati.ca permalink
  11. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Thursday, 05-Jan-2023 02:44:43 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite I just had a small issue while testing this PR: github.com/friendica/friendica…
    In conversation Thursday, 05-Jan-2023 02:44:43 JST from pirati.ca permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      GitHub - friendica/friendica: Friendica Communications Platform
      Friendica Communications Platform. Contribute to friendica/friendica development by creating an account on GitHub.
  12. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Wednesday, 04-Jan-2023 23:16:48 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite No, only dumbness.
    In conversation Wednesday, 04-Jan-2023 23:16:48 JST from pirati.ca permalink
  13. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 16:45:00 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite From a database perspective it is really bad practice to store data that is already stored. In this case it is especially bad since there are depending tables (like the one with the reported posts) that with each update is deleted and inserted over and over again.

    Also when this technique was applied to some other places that have got a higher risk of race conditions we run into nightmare situations where some fields had been reverted to older situations because there had been some other (parallel) task between setting the class variables and saving all the fields. Let's say we had a situation where the one process set the avatar of a contact and a parallel process is setting the date of the last item. With the right (or better: bad) timing, the avatar or the date of last item was reverted when we worked that way.

    I do get your point of input validation. But that solution opens up a bunch of other problems that are even worse than the original problem.
    In conversation Tuesday, 27-Dec-2022 16:45:00 JST from pirati.ca permalink
  14. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 16:44:55 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite This sounds like coding with one hand tied on the back and then having the need to invent some workaround to counter the self caused limitations.

    So the easy task of setting the status will now consist of:
    - fetching all report fields (although we don't need the content for our task)
    - fetching all associated side table fields (the uri-ids) (although this is of no interest here)
    - processing the fields
    - returning the content
    - changing one value (the status)
    - storing all fields in the report table
    - delete all table entries for that report in the side table with the uri-ids
    - insert all table entries again, although we haven't change anything there

    And this process will even getting worse, when we have the need to set the status for a whole bunch of reports (when for example 10 people report the same, then we should be able to easily close 9 reports). In that case - instead of issuing a single update command with the array of the report ids - we had to execute the above steps in some loop. This will slow down the whole process and will increase the database load as well.

    I understand the reason why to work with class variables instead of associated arrays when handling with fetched data. But I don't see a reason why to limit ourselves upon updating as well.
    In conversation Tuesday, 27-Dec-2022 16:44:55 JST from pirati.ca permalink
  15. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 07:31:34 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite I thought that the "entity" only contains the class variables?

    What I want to do is to create constants for the status. So they are "entity-related", I guess.

    Also I want to create functions like "setDismissed" (and similar) to update the status. Also some "getOpenReports" that should return an array of reports. Concerning the returned data, I also want to return an enhanced set of data. Means: I don't only want to return the contact id of the reported contact and the uri-id of the posts, but also all needed contact related data (nick, name, url, avatar, ...) and the post related data (like title, body, creation date, ...). For this I want to create some view that then has to be called inside of that class.
    In conversation Tuesday, 27-Dec-2022 07:31:34 JST from pirati.ca permalink
  16. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 07:31:30 JST heluecht heluecht
    in reply to
    • heluecht
    • hypolite
    @hypolite I don't understand why we should split the setting of the status in two steps? Why not directly set and store the status? I don't see any sense in storing (and overwriting) all the existing fields when we only want to change some little status field.

    Concerning "createFromTableRow": I don't want to return just the array of the uri-ids there, but some array with enhanced data per record. So I guess that function needs some enhancement.
    In conversation Tuesday, 27-Dec-2022 07:31:30 JST from pirati.ca permalink
  17. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 07:12:30 JST heluecht heluecht
    in reply to
    • jakob
    • heluecht
    • hypolite
    • Peter Vágner
    • hamiller_friendica
    @hypolite @pvagner @jakob @hamiller_friendica That's what I thought of.
    In conversation Tuesday, 27-Dec-2022 07:12:30 JST from pirati.ca permalink
  18. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 07:04:32 JST heluecht heluecht
    in reply to
    • jakob
    • heluecht
    • Peter Vágner
    • hamiller_friendica
    @pvagner @jakob @hamiller_friendica We are doing so for many years.
    In conversation Tuesday, 27-Dec-2022 07:04:32 JST from pirati.ca permalink
  19. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Tuesday, 27-Dec-2022 06:36:15 JST heluecht heluecht
    • Friendica Developers
    I've got a question where to place the functions to return data for the reports and to set the status. There is the report "factory" and the report "repository". At least I guess that the functions wouldn't be placed in this report "entity".

    Concerning constants: I guess that they are placed in the "entity" class, aren't they?
    In conversation Tuesday, 27-Dec-2022 06:36:15 JST from pirati.ca permalink
  20. Embed this notice
    heluecht (heluecht@pirati.ca)'s status on Saturday, 24-Dec-2022 02:15:40 JST heluecht heluecht
    in reply to
    • heluecht
    • Michał "rysiek" Woźniak · 🇺🇦
    @blender @rysiek @SolarpunkPrompts I just was confused about a bunch of new users - then I saw this post ?
    In conversation Saturday, 24-Dec-2022 02:15:40 JST from pirati.ca permalink
  • After
  • Before

User actions

    heluecht

    heluecht

    Entwickelt Open Source in der Freizeit, hat zu viele Fahrräder und ist Fan des HSVH (Das erste "H" steht für "Handball") und von islieb, Franzbrötchen und guter Schokolade. Wunschliste: alles unter https://www.rausch.de/schokolade/Wer Amazon mag: https://www.amazon.de/hz/wishlist/ls/3VWK0ZL3MN3ZTLiberapay: https://liberapay.com/heluecht/donateBTC: 1AtJ9JVysdhWjSs5qQvp7Xt9xFdjMKSSA7BCH: qpjg2gwgr35fgz3dxy6lcpw3lt4szrfgev90uk3tfv

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          4834
          Member since
          12 Aug 2022
          Notices
          153
          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.