Oh. Nice feature request! Like instead of putting a star on the email on my client it sends the request to add the star on their end? Let's get the people @thunderbird
On the line. Is it worth a feature request?
Probably a custom read receipt system but instead of getting the Read: Subject you get Fav: subject.
set up an instance specifically for federating with Threads, for people who do want a window into that space
(maybe using one of the lower-maintenance ActivityPub packages)
...but also allow spambots to sign up
Are there people who want access to the Metaverse but also see the value in trying to make it unlivable? (Would it be likely that Threads would de-federate from a spammy instance, or is that "free speech" and therefore automatically good, or what?)
@woozle I'll just be looking more closely at the instance URLs of people I might want to follow, or who follow me, and vetting Threads users more closely, provided I can actually see content they've posted.
I may be looking for work again soon. I thought there was a commitment on the project to see it through to the planned delivery-date in September, but it's now looking very iffy as to whether that commitment remains in effect.
At least now (for the moment, anyway), I still have some current employment I can point to.
Any leads on #PHP work? (I now also have some experience with Laravel, Vagrant, and Pest.)
I would have preferred to work out some conditions* under which we would allow Meta to connect with our fedi, but perhaps it's best to come out of the gate with a big "NO" and not waste time working out terms when Meta probably doesn't see us as worth negotiating with any more than one would try to negotiate with a housefly.
...well, ok, be fair: I often do attempt to negotiate with houseflies before I deal with them more harshly, but I think you know what I mean. (They never listen, so the consequences are kinda on them, so to speak.)
@vantablack Where's that form again? I'll sign #TootCat on, and only reconsider if there's substantial disagreement from our users.
I can go into detail, but the ideas I had were very much not softball and would ensure that Meta would actually be contributing to the long-term health of fedi as a commons, rather than preying on it.
@woozle thank you! i was about to ask if you have considered this.
i like to think that there may be a future in which big corporations contribute to a web without walls to fence their users in. but since it would require whole new business models that they don’t have, it’s clear that they’re not interested in that at this point. cutting them out is the only way to survive.
I have to wonder what it is that all these ad-bots get from creating accounts that they never do anything with. Is it just so some PR firm can truthfully(ish) say to their clients "We've obtained presence for you on over 10,000 social media sites!" where like 9900 of those are different fedi instances, and the customer is sufficiently unwoke to accept this at face value? Or is there something else behind it?
(P.S. I'm going to start using "unwoke" as a synonym for "clueless"; pass it on.)
Is @tenacity only supporting Windows now? I went to the downloads page via a button which had a penguin-icon among the others, but it only had source-code and Windows downloads.
@woozle@tenacity This seems like something to bug @Codeberg about, they should set Content-Disposition on all release downloads to "attachment"... doesn't make much sense that they don't.
@andOlga
As far as I can tell, the attachment system does not differentiate between attachments e.g. to issues, and release attachments.
If there was a general Content-Disposition header, quickly viewing images and text files attached to an issue would become quite difficult.
Feel free to open an issue at Codeberg/Community/issues nevertheless to discuss this. Maybe we can add a ?download=true from the release links which triggers this, or something like this. @woozle@tenacity
Unless my ISP somehow authorizes email to be sent from my IP, Gmail will now bounce it.
Unless I am hooked up with an email service that somehow has clout with Google, Gmail will bounce it.
Since the "ISP" through whom I am attempting to send mail is #DigitalOcean, I find item #1 to be dubious. They are not blocking my outgoing mail port, and I have no problems sending to most recipients (Google and Microsoft being the only exceptions I'm aware of).
DigitalOcean seems to encouraging its users to use a 3rd-party service -- but I'm already paying them for hosting, and managing my own email service; I don't want to pay yet another service just for the privilege of being allowed to send messages to Gmail's increasingly walled garden.
@woozle@andrewt I agree w/putting MS & Google on the dark side of that line despite the fact that you lose reach to probably 90% of the population. But consider a simpler rationale: instead of digging into whether their config is malicious or yours is lacking, simply knowing that Google & MS harvest all #email they can & exploit it for #adSurveillance profits, that’s reason enough to boycott them
@andrewt@woozle Suppose you send a msg to bob@gmail·com. Bob gets gratis #email from Google b/c Google snoops on the msgs. Google doesn’t just snoop on Bob. Google snoops on everyone Bob talks to. That means you. So by emailing Bob, you help pay Bob’s email bill by pawning yourself to #Google. Regardless of MX configurations, do you really want to support that model? Simple decision for me.