@fristi From what I understood from chat; The new phoenix framework allowed some code to be simplified. This was done and all tests passed. But now, in production, it turns out that this caused the inbox url from local accounts to loose it's protocol+domain part. Nothing was wrong immediately, until someone on latest develop changed their profile. This update also made the "inbox" url just be "/inbox" instead of the full url.
Other instances started fetching the updated profile (either because they received an Update activity, or because they refetch from time to time), so now they also had this profile with "/inbox" as the inbox url.
And then the problem was that when making a post, akkoma tried to deliver to /inbox, which is not possible bc it's not an url, so it failed and blocked the whole queue.
I couldn't get this out of my head, so I hereby present the Anti-Attribution License (4d is the extra stipulation, the rest was just getting the references to Creative Commons out (by which I hope I didn't break a license)). Am not a lawyer, yadayadayada
Anti Attribution Legal Code
AA0 1.0 Universal
DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN ATTORNEY-CLIENT
RELATIONSHIP. THIS INFORMATION IS PROVIDED ON AN "AS-IS" BASIS. NO
WARRANTIES ARE MADE REGARDING THE USE OF THIS DOCUMENT OR THE
INFORMATION OR WORKS PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR
DAMAGES RESULTING FROM THE USE OF THIS DOCUMENT OR THE INFORMATION OR
WORKS PROVIDED HEREUNDER.
Statement of Purpose
The laws of most jurisdictions throughout the world automatically confer
exclusive Copyright and Related Rights (defined below) upon the creator
and subsequent owner(s) (each and all, an "owner") of an original work of
authorship and/or a database (each, a "Work").
Certain owners wish to permanently relinquish those rights to a Work for
the purpose of contributing to a commons of creative, cultural and
scientific works ("Commons") that the public can reliably and without fear
of later claims of infringement build upon, modify, incorporate in other
works, reuse and redistribute as freely as possible in any form whatsoever
and for any purposes, including without limitation commercial purposes.
These owners may contribute to the Commons to promote the ideal of a free
culture and the further production of creative, cultural and scientific
works, or to gain reputation or greater distribution for their Work in
part through the use and efforts of others.
For these and/or other purposes and motivations, and without any
expectation of additional consideration or compensation, the person
associating AA0 with a Work (the "Affirmer"), to the extent that he or she
is an owner of Copyright and Related Rights in the Work, voluntarily
elects to apply AA0 to the Work and publicly distribute the Work under its
terms, with knowledge of his or her Copyright and Related Rights in the
Work and the meaning and intended legal effect of AA0 on those rights.
1. Copyright and Related Rights. A Work made available under AA0 may be
protected by copyright and related or neighboring rights ("Copyright and
Related Rights"). Copyright and Related Rights include, but are not
limited to, the following:
i. the right to reproduce, adapt, distribute, perform, display,
communicate, and translate a Work;
ii. moral rights retained by the original author(s) and/or performer(s);
iii. publicity and privacy rights pertaining to a person's image or
likeness depicted in a Work;
iv. rights protecting against unfair competition in regards to a Work,
subject to the limitations in paragraph 4(a), below;
v. rights protecting the extraction, dissemination, use and reuse of data
in a Work;
vi. database rights (such as those arising under Directive 96/9/EC of the
European Parliament and of the Council of 11 March 1996 on the legal
protection of databases, and under any national implementation
thereof, including any amended or successor version of such
directive); and
vii. other similar, equivalent or corresponding rights throughout the
world based on applicable law or treaty, and any national
implementations thereof.
2. Waiver. To the greatest extent permitted by, but not in contravention
of, applicable law, Affirmer hereby overtly, fully, permanently,
irrevocably and unconditionally waives, abandons, and surrenders all of
Affirmer's Copyright and Related Rights and associated claims and causes
of action, whether now known or unknown (including existing as well as
future claims and causes of action), in the Work (i) in all territories
worldwide, (ii) for the maximum duration provided by applicable law or
treaty (including future time extensions), (iii) in any current or future
medium and for any number of copies, and (iv) for any purpose whatsoever,
including without limitation commercial, advertising or promotional
purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
member of the public at large and to the detriment of Affirmer's heirs and
successors, fully intending that such Waiver shall not be subject to
revocation, rescission, cancellation, termination, or any other legal or
equitable action to disrupt the quiet enjoyment of the Work by the public
as contemplated by Affirmer's express Statement of Purpose.
3. Public License Fallback. Should any part of the Waiver for any reason
be judged legally invalid or ineffective under applicable law, then the
Waiver shall be preserved to the maximum extent permitted taking into
account Affirmer's express Statement of Purpose. In addition, to the
extent the Waiver is so judged Affirmer hereby grants to each affected
person a royalty-free, non transferable, non sublicensable, non exclusive,
irrevocable and unconditional license to exercise Affirmer's Copyright and
Related Rights in the Work (i) in all territories worldwide, (ii) for the
maximum duration provided by applicable law or treaty (including future
time extensions), (iii) in any current or future medium and for any number
of copies, and (iv) for any purpose whatsoever, including without
limitation commercial, advertising or promotional purposes (the
"License"). The License shall be deemed effective as of the date AA0 was
applied by Affirmer to the Work. Should any part of the License for any
reason be judged legally invalid or ineffective under applicable law, such
partial invalidity or ineffectiveness shall not invalidate the remainder
of the License, and in such case Affirmer hereby affirms that he or she
will not (i) exercise any of his or her remaining Copyright and Related
Rights in the Work or (ii) assert any associated claims and causes of
action with respect to the Work, in either case contrary to Affirmer's
express Statement of Purpose.
4. Limitations and Disclaimers.
a. No trademark or patent rights held by Affirmer are waived, abandoned,
surrendered, licensed or otherwise affected by this document.
b. Affirmer offers the Work as-is and makes no representations or
warranties of any kind concerning the Work, express, implied,
statutory or otherwise, including without limitation warranties of
title, merchantability, fitness for a particular purpose, non
infringement, or the absence of latent or other defects, accuracy, or
the present or absence of errors, whether or not discoverable, all to
the greatest extent permissible under applicable law.
c. Affirmer disclaims responsibility for clearing rights of other persons
that may apply to the Work or any use thereof, including without
limitation any person's Copyright and Related Rights in the Work.
Further, Affirmer disclaims responsibility for obtaining any necessary
consents, permissions or other rights required for any use of the
Work.
d. You shall attribute yourself, and not the affirmer as the creator
of the work.
@lanodan Would an option to do "static except these specific things" make sense? :blobfoxthink: Or are we just back at square one then? Because if OpenSSL can be such a problem, I assume distros make sure they have the newest version any how, so it wouldn't create the compatibility issues we see now. Or am I seeing things too simplistic?
@lanodan what's the problem with that? Is it that OpenSSL needs to be easily/more quickly updateable?
Embed this noticeilja (ilja@ilja.space)'s status on Sunday, 06-Aug-2023 00:58:30 JST
iljais there any one smart enough to file an issue somewhere to get the Elixir release builds be static builds? So we don't need all these flavours any more and people can just drop the binary on w/e distro they have as long as the cpu architecture is good. (As I understand, that should be possible with static builds, right?)
I guess having dynamic builds makes sense for corporations who control their infra, but for floss projects, that just seems like a bother in a lot of cases...
I'm not smart enough. I don't know where to ask, how to ask, and if they want more information, I'll probably not even understand the question :/
When your instance goes down, you get annoying 500 errors, right. But what if you can set a retry in the http proxy and tell it to retry for several seconds. You could basically restart while it looks like you still have uptime, hehe (just bigger latency).
And a quick glance tells me something like that may be possible in Caddy by using the load balancers lb_try_duration and lb_try_interval. And yes, this is load balancing settings, but who's to say you can't have a load balancing setup with only one node :blobfoxcomfysmirk:
Embed this noticeilja (ilja@ilja.space)'s status on Saturday, 05-Aug-2023 06:16:44 JST
iljaAs the fediverse grows, moderators and administrators will need tools to help with moderation. In particular I propose to send all posts to X. X can determine if a post should be blocked before it is distributed via ActivityPub. I propose an architecture in which the origin server makes a single call to X, and then relays an attestation to all recipient servers. The recipient server can then check the attestation and decide whether to accept the message, without requiring additional calls to X.
Embed this noticeilja (ilja@ilja.space)'s status on Monday, 31-Jul-2023 13:05:13 JST
iljay' know what'd be nice to have. An exporter that dumps all posts and stuff into Activity Stream representation. And then an importer to get all of it back in. I'm thinking this should be possible in *oma. First dump everything in a big json or csv. Then have a mix task to pass the objects one by one to the pipeline. And the fetcher can be changed so that it doesn't fetch over http, but reads from the dump.
It wouldn't fully solve migrating softwares bc not all software use the same iri-schema for representing things, but it could be a start. And bc it would use AS, it's already using a standard representation everyone understands.
@Moon it's an operating system written by someone named Richard Stallman. He prefers to call it gnu+linux bc the linux mascot is a gnu (which is a type of penguin)
@lain Hey, and welcome to Mastodon, Katy! May I suggest you use the #instroduction hashtag for better discoverability. You see, here on Mastodon we don't have full text search because only people who want to harass people would ever want to search things. Anyhow, welcome to Mastodon, I hope you have a tooting time!
Thank you for your email and interest in our product and services, my Fediverse related consultancy fee is 10.000 10grans for each started hour.
If this is acceptable to you, please do forward the details so I can make up a contract.
I understand the conversation will be OTR. As a first word of advise (by reading further you agree with the consultancy fee as described in the first paragraph of this email, and understand that you, or the legal entity you represent, will be billed for this advise accordingly), I propose to use OMEMO instead of OTR. OMEMO has better user experience, and, due to it's use of double ratchet, has better confidentiality.
The instance has a sane blocking policy, allowing broad federation, and it's admin is someone who's known to put a lot of effort in keeping the instance run well for the people who use it.
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