# orderedItems[].object.content
@brettcannon /v\d+/ -> hey CI, this is a formal release; please do the formal release things.

I'm aware that I now have two problems.

# orderedItems[].object.contentMap.en
@brettcannon /v\d+/ -> hey CI, this is a formal release; please do the formal release things.

I'm aware that I now have two problems.

# orderedItems[].object.content
On to the next phase of getting back to writing again:

https://www. licquia.org/posts/site-refacto r/

# orderedItems[].object.contentMap.en
On to the next phase of getting back to writing again:

https://www. licquia.org/posts/site-refacto r/

# orderedItems[].object.content
@dangillmor @elk seems to have pretty good threading. It's a Web client.

# orderedItems[].object.contentMap.en
@dangillmor @elk seems to have pretty good threading. It's a Web client.

# orderedItems[].object.content
Today: Europe has proposed the Pothole Resilience Act. Noting that potholes often result from flaws in road paving, they propose a stringent set of certifications and quality brands to ensure proper road construction and maintenance.

Next year: Wow, road construction costs are up 1200%, and most of the road companies are out of business! I suppose we can't afford to fix potholes this year.

5 years later: Remember when roads were paved? Those were good times.

# orderedItems[].object.contentMap.en
Today: Europe has proposed the Pothole Resilience Act. Noting that potholes often result from flaws in road paving, they propose a stringent set of certifications and quality brands to ensure proper road construction and maintenance.

Next year: Wow, road construction costs are up 1200%, and most of the road companies are out of business! I suppose we can't afford to fix potholes this year.

5 years later: Remember when roads were paved? Those were good times.

# orderedItems[].object.content
Sometimes, the algorithm does good things, like when YouTube suggests a random video on notes apps which leads to a whole warren of videos on personal productivity that has me excited to improve my life.

# orderedItems[].object.contentMap.en
Sometimes, the algorithm does good things, like when YouTube suggests a random video on notes apps which leads to a whole warren of videos on personal productivity that has me excited to improve my life.

# orderedItems[].object.content
Absolutely fantastic and insightful post on search, privacy, Mastodon culture, and practical ways to improve. From @timbray , which isn't surprising, as he makes a habit of saying sensible things.

https://www. tbray.org/ongoing/When/202x/20 22/12/30/Mastodon-Privacy-and-Search

# orderedItems[].object.contentMap.en
Absolutely fantastic and insightful post on search, privacy, Mastodon culture, and practical ways to improve. From @timbray , which isn't surprising, as he makes a habit of saying sensible things.

https://www. tbray.org/ongoing/When/202x/20 22/12/30/Mastodon-Privacy-and-Search

# orderedItems[].object.content
#GMail can be trippy sometimes. For example, when you discover you've saved a bunch of stuff somewhere that you don't need, and you try to delete it all. That task is surprisingly difficult on GMail.

# orderedItems[].object.contentMap.en
#GMail can be trippy sometimes. For example, when you discover you've saved a bunch of stuff somewhere that you don't need, and you try to delete it all. That task is surprisingly difficult on GMail.

# orderedItems[].object.content
(Never mind the question about whether you'd ever want to rely on someone who shuts down their critical infrastructure nationwide with 12 hours notice.)

# orderedItems[].object.contentMap.en
(Never mind the question about whether you'd ever want to rely on someone who shuts down their critical infrastructure nationwide with 12 hours notice.)

# orderedItems[].object.content
Just got a notice that #EVgo will be down in 12 hours for network maintenance. If you drive an #EV, and were planning a late-night trip tonight, you'll want to avoid them.

# orderedItems[].object.contentMap.en
Just got a notice that #EVgo will be down in 12 hours for network maintenance. If you drive an #EV, and were planning a late-night trip tonight, you'll want to avoid them.

# orderedItems[].object.content
Merry Christmas to everyone! I hope it was safe and enjoyable. And if it was not, may you be blessed in your time of trouble.

# orderedItems[].object.contentMap.en
Merry Christmas to everyone! I hope it was safe and enjoyable. And if it was not, may you be blessed in your time of trouble.

# orderedItems[].object.content
@anxiousmac This is the usual tension between open and closed development; if you give the rabble a vote, they'll eventually vote for something "undesirable".

I don't have a dog in this fight, except that I really hope Mastodon succeeds, and problems like this, if not handled well, have the potential to do a lot of damage. Which is why I'm trying to reframe this as a debate about what to do when the feature arrives, not whether the powers-that-be should allow it.

# orderedItems[].object.contentMap.en
@anxiousmac This is the usual tension between open and closed development; if you give the rabble a vote, they'll eventually vote for something "undesirable".

I don't have a dog in this fight, except that I really hope Mastodon succeeds, and problems like this, if not handled well, have the potential to do a lot of damage. Which is why I'm trying to reframe this as a debate about what to do when the feature arrives, not whether the powers-that-be should allow it.

# orderedItems[].object.content
@anxiousmac That's generally true, but only because popular features tend to be uncontroversial and get merged pretty quickly. When there are issues with a feature, forks can proliferate pretty widely; look at the crazy world of X11 compositors, or the Python GIL.

I don't know that we have a lot of experience with non-technical controversy in open source. And when we do, the forks seem like they win (see XFree86 and MySQL).

# orderedItems[].object.contentMap.en
@anxiousmac That's generally true, but only because popular features tend to be uncontroversial and get merged pretty quickly. When there are issues with a feature, forks can proliferate pretty widely; look at the crazy world of X11 compositors, or the Python GIL.

I don't know that we have a lot of experience with non-technical controversy in open source. And when we do, the forks seem like they win (see XFree86 and MySQL).

# orderedItems[].object.content
Another thought: if we think that the QT implementation details matter, then not creating the feature yourself means you're fine with whatever some other developer comes up with. It might be more difficult for opponents to get their tweaks in after the fact.

# orderedItems[].object.contentMap.en
Another thought: if we think that the QT implementation details matter, then not creating the feature yourself means you're fine with whatever some other developer comes up with. It might be more difficult for opponents to get their tweaks in after the fact.

# orderedItems[].object.content
To be clear, I'm not accusing the anti-QT side of anything. But best intentions get lost in the ether, and if the anti-QT folks decide to stand their ground, it could get ugly.

To that end, I'm hoping that we come to a consensus and that sticks, one way or the other. But if we don't, it seems prudent to think about how that will play out.

# orderedItems[].object.contentMap.en
To be clear, I'm not accusing the anti-QT side of anything. But best intentions get lost in the ether, and if the anti-QT folks decide to stand their ground, it could get ugly.

To that end, I'm hoping that we come to a consensus and that sticks, one way or the other. But if we don't, it seems prudent to think about how that will play out.

# orderedItems[].object.content
For me, the really odd thing about the quote-tweet debate is that, in one sense, QTs are likely inevitable. This is open source. If people want the feature badly enough, someone will come along and add it.

The interesting question, to me, is what happens next. The anti-QT folks may have a difficult decision coming: do they block instances with QT support? What would it look like if a bunch of admins made the call to block pro-journalist and pro-people-of-color homeservers over a feature?

# orderedItems[].object.contentMap.en
For me, the really odd thing about the quote-tweet debate is that, in one sense, QTs are likely inevitable. This is open source. If people want the feature badly enough, someone will come along and add it.

The interesting question, to me, is what happens next. The anti-QT folks may have a difficult decision coming: do they block instances with QT support? What would it look like if a bunch of admins made the call to block pro-journalist and pro-people-of-color homeservers over a feature?