Show newer

I've decided to follow anyone who looks interesting even if they don't match my interests. After a month or two I can trim that list. It is easy to do on qoto.org since the follow button can be displayed under the icon.

@deadbeef

I consider both techniques to be guards. Generally, I use the pragma.

One of the nice things about qoto.org is the short URL. Easy to type.

Just saw an instance where the URL is 25 characters.

@deadbeef Only to prevent errors about duplication of entities at either compile or link time.

@allochthonous @rvawonk

Excuse this pedantry if you are familiar with disaster phases.

1. Mitigation
2. Preparation
<the disaster aka the boom> "hunker down"

3. Response
4. Recovery
...repeat

The public needs messages during phases 2-4. That's the service Twitter, and FB provide with some success.

I'll address this for individuals and mainly reference hurricane disasters. But this is generally applicable to all disasters.

Phase 1 is less critical. This is where you get an emergency generator or install roof tie-downs.

Preparation is mainly done immediately before the disaster. Purchase water and food, plywood, fill gas tanks, etc.

Response after the boom is getting people to safe locations. Where are shelters? What roads are closed? Where are gas stations and food stores open?

Recovery is restoring normalcy. This is agencies explaining how to get assistance. This is FEMA, local disaster recovery groups, etc.

Recovery goes on for years, even for individuals. Because of this, it isn't feasible to bring up an instance for a specific disaster.

Is it feasible to create something new in a reasonable time? I don't know for sure. The core is providing messages, although providing a discussion area for pros might be useful. I see it as a local timeline that is only federated for outgoing messages. You don't want individuals chiming in on this instance.

Rud boosted

obituary 

Fred Brooks, architect of the IBM/360 and its OS, author of The Mythical Man Month, and advocate for the 8-bit byte (enabling lower case letters!), passed away today.

Few in computing have influenced so many.

@SteveBellovin posted on death of Fred Brooks. Click his link.
@gdinwiddie

@cowgirlcoder

Of Mythical Man Month

Rud boosted

Sad news from UNC Chapel Hill Computer Science — Fred P. Brooks, the founder and long-time chair of the department (and a major influence on my professional outlook) passed away a few hours ago.

@allochthonous @rvawonk

Saw that on the bird site. I think Mastodon can address the need with a disaster-specific instance.

1. Instance is by invitation only to verified disaster specialists or organizations, e.g., local / state EOC.

2. Instance is federated, so anyone can follow the discussions and alerts on their timeline.

It would be interesting to see if some hashtags could be restricted to that instance to complement the 'verified' timeline. This would prevent, say, being used by just anyone.

It would be good if the instance could be mirrored.

@radehi

I tried it both with backticks and four spaces which are standard Markdown. Here is it without Markdown turned on:

```
using StringVec = std::vector<std::string>;

std::expected<StringVec, ErrorCode> ;
```

using StringVec = std::vector<std::string>;

std::expected<StringVec, ErrorCode> f();

@itsjoshbruce

qoto.org has a 65k character limit. Others may have longer ones, also. It is dependent on the server.

Qoto also allows Markdown and Latex.

Playing with Markdown for code. It won't keep the line break in the code. Tried both 4 space indent and the three backspace.

using StringVec = td::vector<std::string>;
std::expected<StringVec, ErrorCode>

using StringVec = td::vector<std::string>;
std::expected<StringVec, ErrorCode>

```

using StringVec = td::vector<std::string>;
std::expected<StringVec, ErrorCode>

using StringVec = td::vector<std::string>;
std::expected<StringVec, ErrorCode>

```
@freemo

@cowgirlcoder

I''ve been doing a delete & re-draft because it isn't working properly. Can't get an NL to work.

@rttf @c_discussions

A better starting point is std::optional. Look at my post in response to the OP, which has a link to an article I did on this before std::expected.

I'd do the simplification of your question as:

```
using StringVec = td::vector<std::string>;

std::expected<StringVec, ErrorCode>
```

I spent a little time thinking about the creation of a social network. The technology isn't trivial, but ultimately, it is straightforward.

The safety, legal, and security/privacy issues are terrible.

Here's one set of thoughts and the original article it is based on about Mastodon.

changelog.com/news/scaling-mas

@niconiconi

What if you replaced the 1 with a `const uint8_t one {1};`

Rud boosted

@hearthborn @KuJoe Local timeline is there just not very discoverable. It's called "Community", found under the search section

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.